On Thu, January 25, 2024 8:26 pm, James B. Byrne wrote:
> On Thu, January 25, 2024 14:38, Paul Lesniewski wrote:
>>> I have gotten SM to run under php-8.3. However, following
>>> authentication
>>> I now
>>> see this in the message pane:
>>>
>>> ERROR: Bad or malformed request.
>>> Query: FETCH
Correction: Calendar Preferences is where the shared calendar option is set but
none of the settings for shared calendars are displayed. Also, in calendar
administration one cannot add users or calendars.
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensiti
On Thu, January 25, 2024 15:40, James B. Byrne via squirrelmail-users wrote:
> How can I debug why the shared calendar plugin does not function? This is
> using SM 20240125 stable.
>
By renaming the calendar plugin directory and adding a soft link from calendar
to shared_calendars I now have the
How can I debug why the shared calendar plugin does not function? This is
using SM 20240125 stable.
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Unencrypted messages have no legal claim to privacy
Do NOT open attachments nor
On Thu, January 25, 2024 14:38, Paul Lesniewski wrote:
>> I have gotten SM to run under php-8.3. However, following authentication
>> I now
>> see this in the message pane:
>>
>> ERROR: Bad or malformed request.
>> Query: FETCH 1,3:5,7,10,12,18:19,28,50,119,121:123,125,127:128,132:135,138
>> (FLAG
> I have gotten SM to run under php-8.3. However, following authentication
> I now
> see this in the message pane:
>
> ERROR: Bad or malformed request.
> Query: FETCH 1,3:5,7,10,12,18:19,28,50,119,121:123,125,127:128,132:135,138
> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date T
Hello,
I have gotten SM to run under php-8.3. However, following authentication I now
see this in the message pane:
ERROR: Bad or malformed request.
Query: FETCH 1,3:5,7,10,12,18:19,28,50,119,121:123,125,127:128,132:135,138
(FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc
On Thu, January 25, 2024 10:16, James B. Byrne via squirrelmail-users wrote:
>
> Fatal error: Uncaught ArgumentCountError: Too few arguments to function
> simpleErrorHandler(), 4 passed in
> /usr/local/www/squirrelmail/plugins/vlogin/functions.php on line 187 and
> exactly 5 expected in
> /usr/loc
On Tue, January 23, 2024 16:26, Paul Lesniewski wrote:
>
> Your PHP isn't logging errors or you aren't looking at the right log file.
> See:
>
> https://www.squirrelmail.org/docs/admin/admin-11.html#ss11.1
>
>
There was an additional php package required (mod_php83) that was not pulled in
by the u
On Tue, January 23, 2024 8:49 pm, James B. Byrne via squirrelmail-users
wrote:
> I have to upgrade our webmail host to FreeBSd-13.2. This necessitates an
> upgrade to php as 7.3 is no longer supported. This in turn requires that
> squirrelmail be updated via freebsd's pkg system. The version o
I have to upgrade our webmail host to FreeBSd-13.2. This necessitates an
upgrade to php as 7.3 is no longer supported. This in turn requires that
squirrelmail be updated via freebsd's pkg system. The version of squirrelmail
is unknow as the package manager reports: Version : 20230207 and the port
The issue is resolved. The problem was that the incorrect version of mod_php
was installed for Apache. Evidently the php81 pkg install does not check for
this and the Apache24 package was installed prior to php81.
--
*** e-Mail is NOT a SECURE channel ***
Do NOT tra
On Fri, April 15, 2022 04:26, Paul Lesniewski wrote:
>
>
> On Thu, April 14, 2022 8:02 pm, James B. Byrne via squirrelmail-users wrote:
>> FreeBSD-13.0p11
>> php Version: 8.1.4_3
>>
>> I downloaded the most recent stable snapshot given above. I installed and
>> configured it. I enabled src/co
On Thu, April 14, 2022 8:02 pm, James B. Byrne via squirrelmail-users wrote:
> FreeBSD-13.0p11
> php Version: 8.1.4_3
>
> I downloaded the most recent stable snapshot given above. I installed and
> configured it. I enabled src/configtest.php. When I visit this url I
> obtain
> this error:
>
FreeBSD-13.0p11
php Version: 8.1.4_3
I downloaded the most recent stable snapshot given above. I installed and
configured it. I enabled src/configtest.php. When I visit this url I obtain
this error:
[Thu Apr 14 15:55:50.272309 2022] [php:error] [pid 43532] [client
216.185.71.41:40396]
PHP Fat
]On Sun, Jan 30, 2022 at 8:44 PM Paul Lesniewski
wrote:
>
>
> On Sun, January 30, 2022 10:56 pm, Robert Kudyba wrote:
> > [image: white-frame.png]
> >
> > I've seen this in older versions but we have an instance of an email that
> > is very large, i.e., lots of text. It results in a blank/white f
On Sun, January 30, 2022 10:56 pm, Robert Kudyba wrote:
> [image: white-frame.png]
>
> I've seen this in older versions but we have an instance of an email that
> is very large, i.e., lots of text. It results in a blank/white frame and a
> 500 Internal Server Error. I was able to strace the php-
> enabled the debugger
Not sure what that is, but all you need is to track down the right PHP
configuration
> and configured php.ini to log and even put the suggested .htaccess file in
> /usr/share/squirrelmail. I'm not getting any logs and the blank frame
> continues. I've restarted httpd as wel
Hi Paul,
I was the one that opened that bug report at
https://sourceforge.net/p/squirrelmail/bugs/2859/. I enabled the debugger
and configured php.ini to log and even put the suggested .htaccess file in
/usr/share/squirrelmail. I'm not getting any logs and the blank frame
continues. I've restarted
On Thu, January 6, 2022 7:55 pm, Robert Kudyba wrote:
>>
>> > As a follow up I used the D option and chose dovecot and I re-enabled
>> > undelete and delete_and_next.but this extra INBOX still exists:
>>
>> Please first manually check what folders are in the user's mail storage
>> on
>> the serv
2022.Január 6.(Cs) 20:55 időpontban Robert Kudyba ezt írta:
>>
>> > As a follow up I used the D option and chose dovecot and I re-enabled
>> > undelete and delete_and_next.but this extra INBOX still exists:
>>
>> Please first manually check what folders are in the user's mail storage
>> on
>> the s
>
> > As a follow up I used the D option and chose dovecot and I re-enabled
> > undelete and delete_and_next.but this extra INBOX still exists:
>
> Please first manually check what folders are in the user's mail storage on
> the server. Looks like additional one(s) may have been accidentally
> cre
On Thu, January 6, 2022 2:56 pm, Robert Kudyba wrote:
> As a follow up I used the D option and chose dovecot and I re-enabled
> undelete and delete_and_next.but this extra INBOX still exists:
Please first manually check what folders are in the user's mail storage on
the server. Looks like addi
>> > I also noticed the warning message about
>> > using the old config file that mentions there are probably new options
>> and
>> > to just use conf.pl.
>>
>> Another thing you can do is re-configure from scratch and use diff to
>> see
>> if there's anything you missed.
>>
>
> I see delete_move
On Thu, Jan 6, 2022 at 1:18 AM Paul Lesniewski
wrote:
> > I ended up backing up the config files and dropped the files in place.
> > When
> > logging in I did get asked to enter my reply email address so is there a
> > preferences file that I missed?
>
> Possibly your plugin configuration files.
> I ended up backing up the config files and dropped the files in place.
> When
> logging in I did get asked to enter my reply email address so is there a
> preferences file that I missed?
Possibly your plugin configuration files. If you're using version 1.5.2
then you should also migrate plugin_
On Tue, January 4, 2022 10:17 pm, Robert Kudyba wrote:
> On Tue, Jan 4, 2022 at 5:02 PM Paul Lesniewski
> wrote:
>
>>
>>
>> On Tue, January 4, 2022 9:49 pm, Robert Kudyba wrote:
>> >> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on
>> >> Fedora
>> >> > 35. First I don''t see
On Tue, Jan 4, 2022 at 5:02 PM Paul Lesniewski
wrote:
>
>
> On Tue, January 4, 2022 9:49 pm, Robert Kudyba wrote:
> >> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on
> >> Fedora
> >> > 35. First I don''t see a F35 RPM.
> >>
> >> With PHP 8 you're probably going to need a newe
On Tue, January 4, 2022 9:49 pm, Robert Kudyba wrote:
>> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on
>> Fedora
>> > 35. First I don''t see a F35 RPM.
>>
>> With PHP 8 you're probably going to need a newer version of
>> SquirrelMail.
>
> Does that mean having to compile fr
> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on Fedora
> > 35. First I don''t see a F35 RPM.
>
> With PHP 8 you're probably going to need a newer version of SquirrelMail.
>
Does that mean having to compile from source?
> After upgrading Apache works just fine
> > for loading
On Tue, January 4, 2022 9:17 pm, Robert Kudyba wrote:
> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on Fedora
> 35. First I don''t see a F35 RPM.
With PHP 8 you're probably going to need a newer version of SquirrelMail.
> After upgrading Apache works just fine
> for loadin
PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on Fedora
35. First I don''t see a F35 RPM. After upgrading Apache works just fine
for loading plain HTML pages but webmail gets an internal server error,
500.
I enabled debug logging and below is what I see in the SSl error logs wit
On Sat, November 20, 2021 1:23 pm, Jay Hart wrote:
>>
patch -d ../../ -p2 < patches/.diff
You may need to fiddle with the options until you get it right.
>>>
>>> This appeared to run better, but I ended up with this:
>>>
>>> [root@dream msg_flags]# patch -d ../../ -p2 <
>
>
>>> patch -d ../../ -p2 < patches/.diff
>>>
>>> You may need to fiddle with the options until you get it right.
>>>
>>
>> This appeared to run better, but I ended up with this:
>>
>> [root@dream msg_flags]# patch -d ../../ -p2 <
>> patches/msg_flags-squirrelmail-1.4.20.diff
>> patching file f
>> patch -d ../../ -p2 < patches/.diff
>>
>> You may need to fiddle with the options until you get it right.
>>
>
> This appeared to run better, but I ended up with this:
>
> [root@dream msg_flags]# patch -d ../../ -p2 <
> patches/msg_flags-squirrelmail-1.4.20.diff
> patching file functions/m
>
>
> On Sat, November 20, 2021 1:39 am, Jay Hart wrote:
>> A few notes below on the first issues I noted with the interface. I
>> disabled the 'preview-pane' plugin and resolved most of the issues.
>> I'll show which ones below. I don't use 'preview-pane' view, so it
>> appears this plugin was s
>> Using this version ^^above^^, do the following plugins need to be
>> patched:
>> - reply_button
>
> Nope
>
>> - msg_flags
>> - multiple_attachments
>
> There are unpublished updates for these (contact me offlist if you want to
> try them) but I think the existing ones still work fine.
>
>> I
On Sat, November 20, 2021 1:39 am, Jay Hart wrote:
> A few notes below on the first issues I noted with the interface. I
> disabled the 'preview-pane' plugin and resolved most of the issues.
> I'll show which ones below. I don't use 'preview-pane' view, so it
> appears this plugin was still ha
> Using this version ^^above^^, do the following plugins need to be
> patched:
> - reply_button
Nope
> - msg_flags
> - multiple_attachments
There are unpublished updates for these (contact me offlist if you want to
try them) but I think the existing ones still work fine.
> I have the follow
A few notes below on the first issues I noted with the interface. I disabled
the 'preview-pane' plugin and resolved most of the issues.
I'll show which ones below. I don't use 'preview-pane' view, so it appears
this plugin was still having some effect on the interface just
by being loaded/enab
Installed the above version dated 11.17.2021 and have it working.
I am missing functionality in the interface and am wondering if this might be
due to not being able to patch a few of the plugins.
Using this version ^^above^^, do the following plugins need to be patched:
- msg_flags
- reply_
On Fri, October 15, 2021 14:37, Paul Lesniewski wrote:
>
> This was on my radar, but given your situation, I went ahead and contacted
> both NIST and MITRE just now. If you have the FreeBSD maintainer's
> contact info, I can work with that person too, but I don't understand what
> you need fro
On Thu, October 14, 2021 10:09 pm, Paul Lesniewski wrote:
> On Thu, October 14, 2021 7:28 pm, James B. Byrne via squirrelmail-users
> wrote:
>> See: https://nvd.nist.gov/vuln/detail/CVE-2020-14933#match-5399106
>>
>> Has this been patched?
>
> There is no vulnerability here. Per OWASP:
>
> https:
On Fri, October 15, 2021 2:36 pm, James B. Byrne wrote:
> n Thu, October 14, 2021 18:09, Paul Lesniewski wrote:
>> On Thu, October 14, 2021 7:28 pm, James B. Byrne via squirrelmail-users
>> wrote:
>>> See: https://nvd.nist.gov/vuln/detail/CVE-2020-14933#match-5399106
>>>
>>> Has this been patched
On Fri, October 15, 2021 10:36, James B. Byrne via squirrelmail-users wrote:
> n Thu, October 14, 2021 18:09, Paul Lesniewski wrote:
>> On Thu, October 14, 2021 7:28 pm, James B. Byrne via squirrelmail-users
>> wrote:
>>> See: https://nvd.nist.gov/vuln/detail/CVE-2020-14933#match-5399106
>>>
>>>
On Fri, October 15, 2021 10:36, James B. Byrne via squirrelmail-users wrote:
> n Thu, October 14, 2021 18:09, Paul Lesniewski wrote:
>> On Thu, October 14, 2021 7:28 pm, James B. Byrne via squirrelmail-users
>> wrote:
>>> See: https://nvd.nist.gov/vuln/detail/CVE-2020-14933#match-5399106
>>>
>>>
n Thu, October 14, 2021 18:09, Paul Lesniewski wrote:
> On Thu, October 14, 2021 7:28 pm, James B. Byrne via squirrelmail-users
> wrote:
>> See: https://nvd.nist.gov/vuln/detail/CVE-2020-14933#match-5399106
>>
>> Has this been patched?
>
> There is no vulnerability here. Per OWASP:
>
> https://owa
On Thu, October 14, 2021 7:28 pm, James B. Byrne via squirrelmail-users
wrote:
> See: https://nvd.nist.gov/vuln/detail/CVE-2020-14933#match-5399106
>
> Has this been patched?
There is no vulnerability here. Per OWASP:
https://owasp.org/www-community/vulnerabilities/PHP_Object_Injection
=
In
I need to get back in track of a long time now I've not been online based
on some personal issues. I wish to learn back all I have lost.
On Thu, Oct 14, 2021, 8:47 PM James B. Byrne via squirrelmail-users <
squirrelmail-users@lists.sourceforge.net> wrote:
> See: https://nvd.nist.gov/vuln/detail/C
See: https://nvd.nist.gov/vuln/detail/CVE-2020-14933#match-5399106
Has this been patched?
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Unencrypted messages have no legal claim to privacy
Do NOT open attachments nor follow link
On Mon, January 11, 2021 11:45 am, David Carvalho wrote:
> Hello.
> So now I know that Squirrelmail does not work with starttls on port 25.
In fact it does. It works on any port that the SMTP server wants to
accept its connections on. That does not mean it's a good thing to set up
your mail se
Hello.
So now I know that Squirrelmail does not work with starttls on port 25.
I’ve changed $smtpPort value to 465 and maintained $use_smtp_tls = true and
$smtp_auth_mech = ‘login’ , but a network traffic inspection shows my web
server always connecting to the smtp server using port 25.
How c
2020.Február 7.(P) 09:25 időpontban Alfred Charles Stockton ezt írta:
> I see in squirrelmail.conf
> $squirrelmail_default_language = 'en_US';
> $default_charset = 'iso-8859-1';
>
> Now which is correct? The squirrelmail configuration or the OS setup?
>
I think you may hit this bug:
https://
I see in squirrelmail.conf
$squirrelmail_default_language = 'en_US';
$default_charset = 'iso-8859-1';
Now which is correct? The squirrelmail configuration or the OS setup?
> I am running Squirrelmail 1.4.23 on a raspberry pi, PHP7.0.33-0+deb9u6 and
> every now and again have to revert to Th
I am running Squirrelmail 1.4.23 on a raspberry pi, PHP7.0.33-0+deb9u6 and
every now and again have to revert to Thunderbird because a message cannot
be seen in whole or in part on Squirrelmail.
Could this have anything to do with the Locale setting, namely en_ZA.UTF-8
UTF-8 ?
--
Regards,
Alf St
On Sat, Dec 28, 2019 at 05:19:20PM -0600, Lindsay Haisley wrote:
> On Sat, 2019-12-28 at 15:49 -0600, Bob McClure Jr wrote:
> > I will give that a try and report back. Thanks.
> >
> > > > Platform:
> > > > 64-bit CentOS 6, fully up to date
> > > > squirrelmail-1.4.22-5.el6.noarch
> > > > php-7.2.
On Sat, 2019-12-28 at 15:49 -0600, Bob McClure Jr wrote:
> I will give that a try and report back. Thanks.
>
> > > Platform:
> > > 64-bit CentOS 6, fully up to date
> > > squirrelmail-1.4.22-5.el6.noarch
> > > php-7.2.26-1.el6.remi.x86_64 (recent upgrade from stock v5.3)
FWIW, PHP 7 threw a nast
Hi Markus,
On Sat, Dec 28, 2019 at 09:30:19PM +0100, Markus Robert Kessler wrote:
> Hi Bob,
>
> v.1.4.22 is absolutely incompatible with php > 5.
> I already wrote this on some wiki pages. Also, that there's version 1.4.23
> / svn out, which runs on php 7. You get it here:
>
> http://squirre
On Sat, Dec 28, 2019 at 01:53:58PM -0600, Lindsay Haisley wrote:
> On Sat, 2019-12-28 at 09:52 -0600, Bob McClure Jr wrote:
> > Platform:
> > 64-bit CentOS 6, fully up to date
> > squirrelmail-1.4.22-5.el6.noarch
> > php-7.2.26-1.el6.remi.x86_64 (recent upgrade from stock v5.3)
> >
> > I am gettin
Hi Bob,
v.1.4.22 is absolutely incompatible with php > 5.
I already wrote this on some wiki pages. Also, that there's version 1.4.23
/ svn out, which runs on php 7. You get it here:
http://squirrelmail.org/download.php
Let us know if it works.
Best regards,
Markus
> Platform:
> 64-bit C
Platform:
64-bit CentOS 6, fully up to date
squirrelmail-1.4.22-5.el6.noarch
php-7.2.26-1.el6.remi.x86_64 (recent upgrade from stock v5.3)
I am getting a boatload of warnings; the most common is:
[Fri Dec 27 07:55:07 2019] [warn] [client xx.xx.xx.xxx] PHP Warning:
session_set_cookie_params(): Can
Hi Anders,
just tested Squirrel 1.4.23/svn with PHP Version 7.3.8. -- Seems to work.
So, I assume that 1.5.2 also behaves as expected. Give it a try.
Best regards,
Markus
> Hi everyone
>
>
>
> Can I use Squirrelmail with PHP version 7.3?
>
>
>
> I have the following version of Squirrelmail i
Hi everyone
Can I use Squirrelmail with PHP version 7.3?
I have the following version of Squirrelmail installed:
SquirrelMail version: 1.5.2 [SVN)
Config file version: 1.5.0.
---
Thanks in advance for your answer, and have a nice day.
Regards,
Anders
-
squirrelmail-users m
PLEASE IGNORE -- ISSUE HAS BEEN SOLVED
This email was accidentally sent from a non-registered address and hence
it was kept in cache on the server and released ages later.
BR,
Markus
>> On , jan-jun.2...@dipl-ing-kessler.de wrote:
>>> Hi all,
>>>
>>>
>>> it seems that I have found a lit
> On , jan-jun.2...@dipl-ing-kessler.de wrote:
>> Hi all,
>>
>>
>> it seems that I have found a little bug.
>>
>> Therefore I've done a short recording for demonstration, see here:
>>
>>
>> https://www.dipl-ing-kessler.de/tmp/squirrel-mail_bug_1.mp4
>>
>>
>> When creating a new email and saving it
> Besides this, the timestamp shown in received emails seems to be the
> "sent" timestamp and not the timstamp received. So, I recognized this bug
> at all.
Click to sort messages by the received column. Otherwise, use the IMAP
info plugin to look at results of test number 6 and debug your system
> On , jan-jun.2...@dipl-ing-kessler.de wrote:
>> Hi all,
>>
>>
>> it seems that I have found a little bug.
>>
>> Therefore I've done a short recording for demonstration, see here:
>>
>>
>> https://www.dipl-ing-kessler.de/tmp/squirrel-mail_bug_1.mp4
>>
>>
>> When creating a new email and saving it
On , jan-jun.2...@dipl-ing-kessler.de wrote:
> Hi all,
>
>
> it seems that I have found a little bug.
>
> Therefore I've done a short recording for demonstration, see here:
>
>
> https://www.dipl-ing-kessler.de/tmp/squirrel-mail_bug_1.mp4
>
>
> When creating a new email and saving it as a draft, th
Hi all,
it seems that I have found a little bug.
Therefore I've done a short recording for demonstration, see here:
https://www.dipl-ing-kessler.de/tmp/squirrel-mail_bug_1.mp4
When creating a new email and saving it as a draft, then every second time
you're doing this, the timestamp in the
Hi all,
it seems that I have found a little bug.
Therefore I've done a short recording for demonstration, see here:
https://www.dipl-ing-kessler.de/tmp/squirrel-mail_bug_1.mp4
When creating a new email and saving it as a draft, then every second time
you're doing this, the timestamp in the
We have a working Squirrelmail (SM) install running with php-5.6 on
FreeBSD-11.9p2. I am trying to install SM for php-7.3 on
FreeBSD-12.0p3. The httpd server is Apache-2.4. After running
conf.pl when I run configtest.php in Firefox then I see this.
I believe that this is likely a configuration
Hi
you can find all possible options here:
http://php.net/manual/en/context.ssl.php
probably you were looking for 'allow_self_signed' option.
Also this config works for me to completely disable cert checks:
$imap_stream_options = array(
'tls' => array(
'verify_peer' => fa
Hi Ian,
> We downloaded the above version of Squirrelmail and set up a new e-mail
> account using this - competiti...@westburyasc.co.uk . We are able to send
> e-mail using this new account but when we try to send messages to the new
> account, from Outlook and G-mail so far, we get a message und
Hello,
We downloaded the above version of Squirrelmail and set up a new e-mail
account using this - competiti...@westburyasc.co.uk . We are able to send
e-mail using this new account but when we try to send messages to the new
account, from Outlook and G-mail so far, we get a message undeliver
I do not believe that this problem is due to squirrelmail (SM) but I
need to check out every possibility.
On January 8 both SM and cyrus_imapd (CI) were updated on their
respective hosts though the 'pkg upgrade' process of FreeBSD-11.2.
Since that time we have noted a marked increase in the numbe
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
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
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.
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
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
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
On 2018年06月02日 00:00, Michael Fritscher wrote:
> On 02.06.2018 05:47, Paul Lesniewski wrote:
>>
>>
>> On 2018年04月22日 08:35, Michael Fritscher wrote:
>>> Hello again,
>>>
>>> it seems that on every folder the main folder is displayed. only the
>>> count of shouwn mails is correct, but even the mai
On 02.06.2018 05:47, Paul Lesniewski wrote:
>
>
> On 2018年04月22日 08:35, Michael Fritscher wrote:
>> Hello again,
>>
>> it seems that on every folder the main folder is displayed. only the
>> count of shouwn mails is correct, but even the mails alltogether are
>> from the main folder.
>
> Sorry,
On 2018年04月22日 08:35, Michael Fritscher wrote:
> Hello again,
>
> it seems that on every folder the main folder is displayed. only the
> count of shouwn mails is correct, but even the mails alltogether are
> from the main folder.
Sorry, it's pretty hard to suggest anything with such limited
inf
Hello again,
it seems that on every folder the main folder is displayed. only the
count of shouwn mails is correct, but even the mails alltogether are
from the main folder.
Best regards,
Michael Fritscher
--
Check out th
e af Paul Lesniewski
Sent: March 12, 2018 11:25
To: Squirrelmail User Support Mailing List
; Anders Boholdt-Petersen
Subject: Re: [SM-USERS] Squirrelmail give me 3 errors after a new installation
On 2018年03月09日 04:01, Anders Boholdt-Petersen wrote:
> Hi
>
>
>
> I am
On 2018年03月09日 04:01, Anders Boholdt-Petersen wrote:
> Hi
>
>
>
> I am new regarding installation of your Squirrelmail Webmail.
>
>
>
> I have fine manually installed Squirrelmail on my webhost, but after I try
> to login, I see the following 3 errors:
>
> Warning: Illegal string offset
Hi
I am new regarding installation of your Squirrelmail Webmail.
I have fine manually installed Squirrelmail on my webhost, but after I try
to login, I see the following 3 errors:
Warning: Illegal string offset '' in
/var/www/boholdt.com/webmail/squirrelmail/functions/imap_general.php on l
Hi @all,
i want to compose html-mails with squirrelmail.
I am using firefox 52.4.0 (Windows 7 64) and he shows me only the "plain
text" editor.
The info-button from squirrelmail shows:
System information
You are using SquirrelMail version: 1.5.2 [SVN]
The administrator installed the follow
On 2016年12月18日 05:31, Alan in Toronto wrote:
> On Sat, December 17, 2016 5:15 am, Andrea wrote:
>> Hi all.
>>
>> I have a SquirrelMail version 1.4.23 [SVN] running on Debian 7.11 with PHP
>> 5.4.45-0+deb7u6 / Apache 2.2.22 .
>> This is the relevant section of config.php
>
>> About a few moths ag
On Sat, December 17, 2016 5:15 am, Andrea wrote:
> Hi all.
>
> I have a SquirrelMail version 1.4.23 [SVN] running on Debian 7.11 with PHP
> 5.4.45-0+deb7u6 / Apache 2.2.22 .
> This is the relevant section of config.php
> About a few moths ago I was notified that one user was having an issue where
Hi all.
I have a SquirrelMail version 1.4.23 [SVN] running on Debian 7.11 with PHP
5.4.45-0+deb7u6 / Apache 2.2.22 .
This is the relevant section of config.php
> $data_dir = '/var/lib/squirrelmail/data/';
> $attachment_dir = '/var/spool/squirrelmail/attach/';
> $dir_hash
I'm trying to make my site more mobile friendly, since most of us are
increasingly having to use it that way.
SquirrelMail works well on a desktop display and large tablet, but is
quite difficult to use on the limited display real estate of a smart
phone (touchable links are too small to avoid hit
On 2016年09月17日 15:31, David C. Rankin wrote:
> On 09/04/2016 02:36 PM, Chris wrote:
>> Hi,
>>
>> I have a server running postfix, courier, Squirrelmail for quite some
>> time without any issues. Now I upgraded the server to Ubuntu 16.04 which
>> comes with PHP 7.
>>
>> After migration, everythi
On 09/04/2016 02:36 PM, Chris wrote:
> Hi,
>
> I have a server running postfix, courier, Squirrelmail for quite some
> time without any issues. Now I upgraded the server to Ubuntu 16.04 which
> comes with PHP 7.
>
> After migration, everything's working, except Squirrelmail. When I login
> wit
Hi,
I have a server running postfix, courier, Squirrelmail for quite some
time without any issues. Now I upgraded the server to Ubuntu 16.04 which
comes with PHP 7.
After migration, everything's working, except Squirrelmail. When I login
with the right credentials (Thunderbird etc. is working)
1 - 100 of 1753 matches
Mail list logo
