On Wed, November 14, 2018 00:07, Paul Lesniewski wrote:
>
>
> On 2018å¹´10æ31æ¥ 10:06, James B. Byrne via squirrelmail-users
> wrote:
>>
>>
>> On Wed, October 31, 2018 11:45, James B. Byrne via
>> squirrelmail-users
>> wrote:
>>> This is ridiculous. I cannot compose a message of any reasonab
On 2018年10月31日 10:06, James B. Byrne via squirrelmail-users wrote:
>
>
> On Wed, October 31, 2018 11:45, James B. Byrne via squirrelmail-users
> wrote:
>> This is ridiculous. I cannot compose a message of any reasonable
>> length in a separate window in SM without getting a security error
>> w
These are the values that the code is using when the error is trigerred
$timestamp 1540839336
Wednesday, October 31, 2018 3:00:19 PM GMT-04:00 DST
$old_token_date 1540839512
Your time zone: Monday, October 29, 2018 2:58:32 PM GMT-04:00 DST
$now 1541012312
Your time zone: Wednesday, October 31, 2
On Wed, October 31, 2018 13:17, James B. Byrne via squirrelmail-users
wrote:
> These are the two possibilities. It appears that the cookie is
> expiring too quickly in the separate popup compose window. The main
> SM page in the browser remains connected.
>
This is where the error is caught.
These are the two possibilities. It appears that the cookie is
expiring too quickly in the separate popup compose window. The main
SM page in the browser remains connected.
/usr/local/www/squirrelmail/plugins/compatibility/includes/1.5.2/global.php
// reject tokens that are too old
//
i
I believe the issue is with your mailer settings and not SM.. I have used
SM for more than 10 yrs and many configs and can send huge emails without
problems..
-rich
On Wed, Oct 31, 2018, 9:46 AM James B. Byrne via squirrelmail-users <
squirrelmail-users@lists.sourceforge.net> wrote:
> This is ri
