This is ridiculous. I cannot compose a message of any reasonable
length in a separate window in SM without getting a security error
when I try and send.
SquirrelMail version 1.4.23 [SVN]
By the SquirrelMail Project Team
ERROR
The current page request appears to have originated from an untrusted
s
We are using FreeBSD-11.2p4 as the SM web service host.
That host has php56-5.6.38 installed
The client browser is FireFox 63.0esr (64 bit)
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Do NOT open attachments nor follow links sent
On Wed, October 31, 2018 11:56, Rich Hall wrote:
> I believe the issue is with your mailer settings and not SM..
What mailer settings? Where?
The Postfix and IMAP services have not been altered at all. The only
change that has happened is that we moved our SM install from CentOS-6
to FreeBSD-
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
James B. Byrne via squirrelmail-users ezt írta:
> The Postfix and IMAP services have not been altered at all. The only
> change that has happened is that we moved our SM install from CentOS-6
> to FreeBSD-11. The distributed SM package in FreeBSD is 1.4.23 which
> indicates a minor change. We did
On Wed, October 31, 2018 12:10, Zsolt Udvari wrote:
> What version of php do you use? Please be aware to install the correct
> version of
> squirrelmail (please note the -php* postfixes).
>
>
On Wed, October 31, 2018 11:53, James B. Byrne via squirrelmail-users
wrote:
> We are using FreeBSD-11.
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
> when I try and send.
>
> SquirrelMail version 1.4.23 [SVN]
> By the SquirrelMail
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
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 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
Hmm.. possibly a web server configuration with session keys timing out?
On Wed, Oct 31, 2018, 10:39 AM Zsolt Udvari wrote:
> James B. Byrne via squirrelmail-users ezt írta:
> > The Postfix and IMAP services have not been altered at all. The only
> > change that has happened is that we moved our
11 matches
Mail list logo