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
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
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 exp
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
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
FreeBSD-12.3 & 13.1
SM-1.4.23
We have this situation. Our mailstore is a Cyrus-imapd-3.0.17 installation
sitting behind a Postfix-3.7.2 MTA. Our webmail (Squirrelmail) host connects
over ssl using the imap server host for authentication.
We have encountered a situation where one of our staff log
FreeBSD 12.3-RELEASE-p2
SquirrelMail version 1.4.23 [SVN] (FreeBSD Ports pkg squirrelmail-php73
Version: 20211024)
We are encountering a situation where some messages are arriving with the
following bodystructure:
Bodystructure
Entity Content-TypeNameEncoding
1 text/plain
On Fri, April 22, 2022 11:22, James B. Byrne wrote:
>
> Access to SM through the firewall has been accomplished and users and see and
> send email without difficulty.
>
> The problem that has surfaced is that Firefox now gives a
> PR_CONNECT_RESET_ERROR whenever someone attempts to add a file mu
We had an equipment failure last night and I am trying to get various bits and
pieces working. The hardware was the gateway router and the replacement has a
different network stack. Consequently we are forced to finally correct an
addressing error made many, many years ago.
Access to SM through t
On Thu, April 21, 2022 16:08, Paul Lesniewski wrote:
> Also check for things like SELinux context for the files and directories.
> It looks to me like some security/permissioning mechanism on your new
> server is preventing access to the files.
>
This is running a FreeBSD OS, there is no SELIN
On Thu, April 21, 2022 15:08, Paul Lesniewski wrote:
>
>
> If there are no typos in the config/config.php plugins[] entry for the
> plugin, then the web server may not be able to load the plugin file(s).
> Inspect the permissions for the plugin directory and files or manually
> test with somethi
On Tue, April 19, 2022 16:53, Paul Lesniewski wrote:
>
> Did you watch for PHP errors?
There are no PHP entries in /var/log/messages that cannot be accounted for.
> Do the calendar administrative options show up for users listed in
> $cal_admins in the plugin configuration?
No, they do not.
>
FreeBSD-13.0
SM 1.4.23
I have SM running from a FreeBSD binary package for PHP81. I likewise have
installed the shared_calendar plugin and its dependencies from FreeBSD
packages. I have configured SM to load this plugin. I also copied a
data/config.php file from another installation of SM where
I now have the current snapshot running on FreeBSD-13.0 under apache-2.4.53
connecting to cyrus imapd-3.0.17 running on a different host. This required
adjusting the $data_dir and $attachment_dir paths to match those used by the
FreeBSD port.
I can connect and authenticate. The left-hand-side fo
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
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
OS FreeBSD-13.0
I am migrating SM from one host to another. The new host runs php80. The old
runs php73. I am using the FreeBSD port for SM on FreeBSD-13.0.
There is a plugin that I installed many years ago called quicksave. I cannot
find this in the prepackaged SM plugin ports. The version I
On Mon, December 6, 2021 16:14, Paul Lesniewski wrote:
>
>
> On Mon, December 6, 2021 4:00 pm, James B. Byrne via squirrelmail-users
> wrote:
>> Can someone please tell me where I can find the share calendar
>> administrative interface?
>
> If it's
This is due to a failing memory, and compounded by a somewhat obscure SM
configuration interface. How does one add and remove users from shared
calendars? I have done this in the past. And I recall the the method was
located in some out of the way place. But I cannot recall where that is.
Can
On Sun, October 24, 2021 13:42, Paul Lesniewski wrote:
>
> You can't look at the code running on your own server?
>
./functions/strings.php:$version = '1.4.23 [SVN]';
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Unencrypted
On Sun, October 24, 2021 12:28, Paul Lesniewski wrote:
>
>
> On Sun, October 24, 2021 4:11 pm, James B. Byrne via squirrelmail-users
> wrote:
>> I am testing a FreeBSD package for squirrelmail built for PHP8
>
> You need to indicate what version
>
This is all th
I am testing a FreeBSD package for squirrelmail built for PHP8. I get this
error when I connect to the test server:
[Sun Oct 24 12:01:56.267457 2021] [php:error] [pid 13492] [client
216.185.71.41:15698] PHP Fatal error: Array and string offset access syntax
with curly braces is no longer support
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 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-
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-
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 vulnerabili
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 Wed, May 12, 2021 01:51, Paul Lesniewski wrote:
> Also as previously suggested, please indicate what you see on screen and
> where -- is the folder list showing a "you must be logged in" error? What
> happens if you right-click that frame and select H and then R?
>
I have pinned a note to
On Wed, May 12, 2021 00:04, Paul Lesniewski wrote:
>
> So if your change for some reason helps the problem, that'd be great to
> know, but it may not change what we need to do (or have already done) on
> our end.
>
The change I made to the samesite setting did not make a difference. I still
g
I have stumbled across these which appear to me to be related to the issue I
brought to your attention:
https://hacks.mozilla.org/2020/08/changes-to-samesite-cookie-behavior/
https://bugzilla.mozilla.org/show_bug.cgi?id=1617609
I have added our SM web address to the
'network.cookie.sameSite.laxB
On Mon, May 10, 2021 12:28, Paul Lesniewski wrote:
> Somewhere the reply-to address for the list got butchered. Latest reply
> from me:
>
> On Mon, May 10, 2021 3:09 pm, James B. Byrne wrote:
>>> What version of SM are you using?
>>
>> SquirrelMail version 1.4.23 [SVN]
>>
>>> When was the date
On Fri, May 7, 2021 06:35, Paul Lesniewski wrote:
>
>
> On Thu, May 6, 2021 6:30 pm, James B. Byrne wrote:
>> It has happened several time since but I neglected to run the inspector
>> before
>> logging on to SM. Until today. This is what I found:
>>
>> Cookie �SQMSESSID� will be soon reje
about the SameSite attribute, read
https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite
On Tue, May 4, 2021 20:16, Paul Lesniewski wrote:
>
>
> On Mon, May 3, 2021 5:04 pm, James B. Byrne via squirrelmail-users wrote:
>> I believe this to be a problem with
On Wed, May 5, 2021 03:43, Markus Robert Kessler wrote:
> Hi James, hi Paul,
>
> maybe this is a cookie-problem within firefox.
>
> Could you please verify that the squirrelmail cookie is there and is valid
> when you are logged out?
I will check the browser's cookie cache the next time it happ
I believe this to be a problem with Firefox (85.0.2 FreeBSD-12.2) and not with
squirrelmail; for the simple reason that SM has not been updated while FF has
and the behaviour only recently became evident.
However, I would like to know what is going on with FF and how to turn it off.
If anyone here
On Fri, March 19, 2021 02:51, Paul Lesniewski wrote:
>
> The person or mailer software that sent it munged the original and that's
> a problem on their side.
>
> You can just plug in the message to a base64 decoder and get the contents.
> The part you included is the beginning of a HTML format
On Thu, March 18, 2021 02:00, Paul Lesniewski wrote:
>
>
> On Wed, March 17, 2021 4:48 pm, James B. Byrne via squirrelmail-users wrote:
>> Is there a plugin to handle these things? I have a message encapsulated
>> in this format and I cannot extract the contents. U
Is there a plugin to handle these things? I have a message encapsulated in
this format and I cannot extract the contents. Usually I download and extract
using the tnef utility, but this time it says that 'Seems not to be a TNEF
file'.
--
*** e-Mail is NOT a SECURE channel **
On Tue, June 23, 2020 13:25, Zsolt Udvari wrote:
> James B. Byrne via squirrelmail-users ezt Ãrta:
>> The version we have is SquirrelMail version 1.4.23 [SVN] which is
>> packaged by
>> the port maintainer at FreeBSD.
> I'm the maintainer the package.
> The v
The version we have is SquirrelMail version 1.4.23 [SVN] which is packaged by
the port maintainer at FreeBSD.
This problem does not occur for every html message. Most show the html display
button and can be switched to the html view. But some do not.
Thank you for your attention to the matter.
I receive messages from e-bay whose message details contain this:
From: eBay
To: xx
Message-ID: <0A16D6F3-D1774F7F39A-0172B6CD7A67-01B86EE5@starship>
Subject: =?UTF-8?Q?=E2=9C=85_Order_Confirmed:_2-3_Days_Delivery_Ma...?=
MIME-Version: 1.0
Content-Type: multipart/mixed
On Fri, June 19, 2020 12:34, Paul Lesniewski wrote:
>
>
> Note: James sent me a copy offlist of such an offending message. Assuming
> version 1.4.23, the problem described does not exist in more recent
> versions of SquirrelMail (after my fix in January). If you cannot
> upgrade, try grabbing
On Wed, June 17, 2020 23:12, Paul Lesniewski wrote:
> Also, please make sure you're running a 1.4.23 snapshot newer than
> 2020-01-06 which contains a fix I made for things like this. If it's
> still broken, note that v1.5.2 uses an iframe to try and better isolate
> css for the message body.
I do not know how to deal with this in Squirrelmail. We have correspondents
sending html format email with this at the top:
Notification Template
body {
background-color: #ff;
font-size: 13px;
}
img {
border:0;
}
ta
We are setting up a test SM environment and cannot get past this error when
running configtest.php:
Fatal error: Uncaught Error: Call to undefined function
session_set_cookie_params() in
/usr/local/www/squirrelmail/functions/global.php:476 Stack trace: #0
/usr/local/www/squirrelmail/functions/gl
I cannot seem to raise https://squirrelmail.org. Is this just my problem or a
universal outage?
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Do NOT open attachments nor follow links sent by e-Mail
James B. Byrne
Our SM users are receiving this message:
> SquirrelSpell is misconfigured.
> I tried to execute '/usr/local/bin/aspell -a', but it returned:
>
> sh: /usr/local/bin/aspell: not found
>
> SquirrelSpell v0.3.8
However on the Squirrelmail host we see this:
# which aspell
/usr/local/bin/aspell
# /
We recently moved our SM installation and at that time upgraded the
TNEF viewer plugin to tnef_decoder-1.0-1.4.0.tar.gz from
attachment_tnef-0.7-1.4.0.hll.tar.gz.
However, we can no longer see winmail.dat attachments with the new
version of this plugin. We have followed the instructions in the new
SquirrelMail version 1.4.23 [SVN]
vlogin-3.10.2-1.2.7
We just moved our SM installation to a new host. We took this
opportunity to update some of the plugins that we use. One of these
is vlogin.
The new vlogin plugin works fine but we cannot seem to configure it
such that the site favicon stays
On Tue, March 26, 2019 12:07, James B. Byrne wrote:
> 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 t
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
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:
>>> Thi
On Wed, October 31, 2018 15:26, Rich Hall wrote:
> Hmm.. possibly a web server configuration with session keys timing
> out?
>
Yes. That appears to be the source of the problem. The default
httpd.conf for FreeBSD contains this:
#LoadModule session_module libexec/apache24/mod_session.so
#Loa
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 err
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
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
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-
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
We recently moved from SM-1.4.22 (CentOS-6.9) to SM-1.4.23
(FreeBSD-11.2p4). One of the plugins that we use is vlogin. We
configured the new install vlogin data/config.php file to match the
changes that we have configured in the old location. However, I must
have missed something.
In the vlogi
On Thu, May 24, 2018 14:40, James B. Byrne wrote:
>
> Starting this morning (2018-05-2) my Squirrelmail (SM) composed posts
> to a Listserv mailing list service are being bounced back with this:
>
. . .
> Does anyone have a clue as to what is happening and how it is
> resolved?
>
The temporary fi
Starting this morning (2018-05-2) my Squirrelmail (SM) composed posts
to a Listserv mailing list service are being bounced back with this:
Reporting-MTA: dns;smtp.utc.edu
Received-From-MTA: dns;NAM03-BY2-obe.outbound.protection.outlook.com
Arrival-Date: Thu, 24 May 2018 09:16:56 -0400
Original-R
On Mon, May 7, 2018 11:52, Seth Randall wrote:
>
> Did you select Cyrus from option D in configure? It will set
> options for your IMAP server type that might affect how the
> folders are displayed.
I had not bothered with that but in the spirit of adventure I did so
after your suggestion. That
FreeBSD-11.1
Cyrus-IMAP-3.0.5
Squirrelmail-1.4.23
Can someone tell me how to change the left hand frame in SM to display
folders as:
INBOX
Folder1
sub11
sub12
Folder2
sub21
sub22
sub221
sub23
. . .
instead of
INBOX
Folder1
Folder1/sub11
Folder1/sub12
Folder2
Folder2/sub21
Folder2/
I sent this to the list before and have had no reply.
I am running SM-1.4.23 under Apache-2.4 on FreeBSD-11.1. I am
connecting to a Cyrus-IMAP-3.0.5 service also running on FreeBSD-11.1.
I cannot get that SM instance to display mail folders in any other
formate besides the Delimited format where
I am now able to connect SM to both the old and the new IMAP services
without difficulty. However, on the new IMAP server I cannot seem to
get SM to display subscribed folders as an indented list.
This is what the SM page source says:
Selection List Style:
Long: "Folder.Subfolder"
Indented:
"
On Mon, April 30, 2018 13:22, Paul Lesniewski wrote:
>> Verify return code: 19 (self signed certificate in certificate
>> chain)
>
> That's likely your problem - SquirrelMail needs the homebrewed CA or
> you need to adjust the verify options.
>
That message is completely misleading. Every C
On Sat, April 28, 2018 14:45, Paul Lesniewski wrote:
>
> Off the top of my head, I'd suggest trying to write a small POC
> script to see if you can make the connection without any other
> code in the way. But it does seem clear that the IMAP server does
> not in fact have the CA's certificate, de
We have a currently running Squirremail (1.4.22-5.el6) (SM) running on
Apache-2.2.15 all hosted on a CentOS-6.9 x64 box. It connects via TLS
(:993) to a Cyrus_IMAP-2.3.16 service running on a different
CentOS-6.9 x64 host. Both services employ X509 certificates issued by
our own CA. All of the va
Recently all of our users began to experience the problem of invisibly
tiny printing when printing messages from the printable message window
of SM. This occurs when at least one header is excessively long. Is
there a way, short of rewriting all the css files myself, of
configuring SM to simply w
77 matches
Mail list logo
