squirrelmail-users — SquirrelMail Users Mailing List

Re: [SM-USERS] Uncaught TypeError: Unsupported operand types: string * int in date.php

[Alex <mys...@gm...>]

Hi,

> Most recent 1.4.23-svn appears to have a problem with emails with corrupt
> > date fields?
>
> Yes, unexpected timezone specifiers like "+UT" ... not sure what kind of
> system is claiming to be date-stamping its email messages to atomic
> clocks.
>
> I just put a patch for this into our repository.  The fix will be
> available in tarball format within the next 24 hours.
>

Thanks so much.

I'll diff this version with the one I currently have installed, as I've
made a few local changes that I don't want to overwrite.

Thanks again,
Alex

Re: [SM-USERS] Uncaught TypeError: Unsupported operand types: string * int in date.php

[Paul L. <pa...@sq...>]

> Most recent 1.4.23-svn appears to have a problem with emails with corrupt
> date fields?

Yes, unexpected timezone specifiers like "+UT" ... not sure what kind of
system is claiming to be date-stamping its email messages to atomic
clocks.

I just put a patch for this into our repository.  The fix will be
available in tarball format within the next 24 hours.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php


> Fatal error: Uncaught TypeError: Unsupported operand types: string * int
> in
> /usr/share/squirrelmail/functions/date.php:91 Stack trace: #0
> /usr/share/squirrelmail/functions/date.php(463): getGMTSeconds(1583293098,
> '+UT') #1 /usr/share/squirrelmail/functions/imap_messages.php(946):
> getTimeStamp(Array) #2
> /usr/share/squirrelmail/functions/mailbox_display.php(628):
> sqimap_get_small_header_list(Resource id #1, Array, 999999) #3
> /usr/share/squirrelmail/functions/mailbox_display.php(407):
> fillMessageArray(Resource id #1, Array, 3291, 999999) #4
> /usr/share/squirrelmail/functions/mailbox_display.php(518):
> getSelfSortMessages(Resource id #1, 1, 999999, 3291, '0', Array) #5
> /usr/share/squirrelmail/src/right_main.php(238):
> showMessagesForMailbox(Resource id #1, '2020', 3291, 1, '0', Array, 15,
> false) #6 {main} thrown in /usr/share/squirrelmail/functions/date.php on
> line 91
>
>     87          $tzc = '+'.$tzc;
>     88      }
>     89      $hh = substr($tzc,1,2);
>     90      $mm = substr($tzc,3,2);
>     91      $iTzc = ($hh * 60 + $mm) * 60;
>     92      if ($neg) $iTzc = -1 * (int) $iTzc;
>     93      /* stamp in gmt */
>     94      $stamp -= $iTzc;
>     95      /** now find what the server is at **/
>     96      $current = date('Z', time());
>
> There are like 3200 messages in the folder where this occurs, so I have no
> idea which message caused it or what the problem might be. Any ideas? How
> can I help troubleshoot this further?

Re: [SM-USERS] Uncaught TypeError: Unsupported operand types: string * int in date.php

[Alex <mys...@gm...>]

Hi Paul, thought I could follow up with you on this and see if you had any
thoughts on my error? Should I file a bug report?

On Mon, Nov 28, 2022 at 1:51 PM Alex <mys...@gm...> wrote:

> Hi,
>
> Most recent 1.4.23-svn appears to have a problem with emails with corrupt
> date fields?
>
> Fatal error: Uncaught TypeError: Unsupported operand types: string * int
> in /usr/share/squirrelmail/functions/date.php:91 Stack trace: #0
> /usr/share/squirrelmail/functions/date.php(463): getGMTSeconds(1583293098,
> '+UT') #1 /usr/share/squirrelmail/functions/imap_messages.php(946):
> getTimeStamp(Array) #2
> /usr/share/squirrelmail/functions/mailbox_display.php(628):
> sqimap_get_small_header_list(Resource id #1, Array, 999999) #3
> /usr/share/squirrelmail/functions/mailbox_display.php(407):
> fillMessageArray(Resource id #1, Array, 3291, 999999) #4
> /usr/share/squirrelmail/functions/mailbox_display.php(518):
> getSelfSortMessages(Resource id #1, 1, 999999, 3291, '0', Array) #5
> /usr/share/squirrelmail/src/right_main.php(238):
> showMessagesForMailbox(Resource id #1, '2020', 3291, 1, '0', Array, 15,
> false) #6 {main} thrown in /usr/share/squirrelmail/functions/date.php on
> line 91
>
>     87          $tzc = '+'.$tzc;
>     88      }
>     89      $hh = substr($tzc,1,2);
>     90      $mm = substr($tzc,3,2);
>     91      $iTzc = ($hh * 60 + $mm) * 60;
>     92      if ($neg) $iTzc = -1 * (int) $iTzc;
>     93      /* stamp in gmt */
>     94      $stamp -= $iTzc;
>     95      /** now find what the server is at **/
>     96      $current = date('Z', time());
>
> There are like 3200 messages in the folder where this occurs, so I have no
> idea which message caused it or what the problem might be. Any ideas? How
> can I help troubleshoot this further?
>
>
>
>

[SM-USERS] Uncaught TypeError: Unsupported operand types: string * int in date.php

[Alex <mys...@gm...>]

Hi,

Most recent 1.4.23-svn appears to have a problem with emails with corrupt
date fields?

Fatal error: Uncaught TypeError: Unsupported operand types: string * int in
/usr/share/squirrelmail/functions/date.php:91 Stack trace: #0
/usr/share/squirrelmail/functions/date.php(463): getGMTSeconds(1583293098,
'+UT') #1 /usr/share/squirrelmail/functions/imap_messages.php(946):
getTimeStamp(Array) #2
/usr/share/squirrelmail/functions/mailbox_display.php(628):
sqimap_get_small_header_list(Resource id #1, Array, 999999) #3
/usr/share/squirrelmail/functions/mailbox_display.php(407):
fillMessageArray(Resource id #1, Array, 3291, 999999) #4
/usr/share/squirrelmail/functions/mailbox_display.php(518):
getSelfSortMessages(Resource id #1, 1, 999999, 3291, '0', Array) #5
/usr/share/squirrelmail/src/right_main.php(238):
showMessagesForMailbox(Resource id #1, '2020', 3291, 1, '0', Array, 15,
false) #6 {main} thrown in /usr/share/squirrelmail/functions/date.php on
line 91

    87          $tzc = '+'.$tzc;
    88      }
    89      $hh = substr($tzc,1,2);
    90      $mm = substr($tzc,3,2);
    91      $iTzc = ($hh * 60 + $mm) * 60;
    92      if ($neg) $iTzc = -1 * (int) $iTzc;
    93      /* stamp in gmt */
    94      $stamp -= $iTzc;
    95      /** now find what the server is at **/
    96      $current = date('Z', time());

There are like 3200 messages in the folder where this occurs, so I have no
idea which message caused it or what the problem might be. Any ideas? How
can I help troubleshoot this further?

Re: [SM-USERS] php-8 upgrade left some users unable to login

[Alex <mys...@gm...>]

Hi Paul,

> Just to follow up here - I fixed the problem. It turns out it was an
> > unterminated comment in the css template some users were using.
> Apparently
> > it previously didn't matter with older versions of PHP, but now causes
> the
> > entire application to cease operating. Ridiculous.
>
> Thanks for following up.  Can you indicate what stylesheet that is?  We
> want to fix that if it's something we are distributing.
>

No, it was one we developed many years ago and set as the default for new
users. It hadn't changed in many, many years - it's surprising that only
now the problem was uncovered and that it would have such a dramatic effect
on users. I guess that's the nature of PHP.

Thanks,
Alex

Re: [SM-USERS] php-8 upgrade left some users unable to login

[Paul L. <pa...@sq...>]

Alex,

>> I've recently upgraded my SM to the latest 1.4.23-svn to support
>> php-8.0.25 on fedora35 with apache-2.4.54 and it appears some users are
>> unable to login. It results in an apache 500 error that I don't know how
>> to
>> troubleshoot. Some users have no difficulty logging in. I've also
>> deleted
>> any user prefs or data/ info related to the user.
>>
>> I've also enabled html_errors, log_errors, display_startup_errors,
>> error_reporting = E_ALL, and error_log, but there aren't any errors
>> generated when the 500 error occurs. The only indication that an error
>> occurred is in modsec_security.log:
>>
>> --35225a73-F--
>> HTTP/1.1 500 Internal Server Error
>
> Just to follow up here - I fixed the problem. It turns out it was an
> unterminated comment in the css template some users were using. Apparently
> it previously didn't matter with older versions of PHP, but now causes the
> entire application to cease operating. Ridiculous.

Thanks for following up.  Can you indicate what stylesheet that is?  We
want to fix that if it's something we are distributing.

Thanks,
-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

Re: [SM-USERS] php-8 upgrade left some users unable to login

[Alex <mys...@gm...>]

Hi,

Just to follow up here - I fixed the problem. It turns out it was an
unterminated comment in the css template some users were using. Apparently
it previously didn't matter with older versions of PHP, but now causes the
entire application to cease operating. Ridiculous.

Thanks so much for maintaining squirrelmail.

alex

On Tue, Nov 22, 2022 at 11:45 AM Alex <mys...@gm...> wrote:

> Hi,
>
> I've recently upgraded my SM to the latest 1.4.23-svn to support
> php-8.0.25 on fedora35 with apache-2.4.54 and it appears some users are
> unable to login. It results in an apache 500 error that I don't know how to
> troubleshoot. Some users have no difficulty logging in. I've also deleted
> any user prefs or data/ info related to the user.
>
> I'ver verified the users can login directly using IMAP, and it appears SM
> is also successfully logging them in:
>
> Nov 22 11:16:54 cipher dovecot[1228]: imap-login: Login: user=<alex>,
> method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=1386757, secured,
> session=<UskYgBHuhJx/AAAB>
> Nov 22 11:16:54 cipher dovecot[1228]:
> imap(alex)<1386757><UskYgBHuhJx/AAAB>: Disconnected: Logged out in=44
> out=1022 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0
> body_count=0 body_bytes=0
> Nov 22 11:16:54 cipher squirrelmail[664245]: Successful webmail login: by
> alex (example.com) at 68.195.111.42
>
> I have the following plugins installed, although I've tried limiting it
> even further, and I don't think one of them is causing the problem. I did
> have to delete quicksave, as that would prevent the inbox from being
> displayed - perhaps that's already included?
>
> 1.squirrelspell
> 2. compatibility
> 3. squirrel_logger
> 4. administrator
> 5. calendar
> 6. delete_move_next
> 7. filters
> 8. folder_sizes
> 9. local_autorespond_forward
> 10. lockout
> 11. message_details
> 12. sent_subfolders
> 13. timeout_user
> 14. info
>
> I've also enabled html_errors, log_errors, display_startup_errors,
> error_reporting = E_ALL, and error_log, but there aren't any errors
> generated when the 500 error occurs. The only indication that an error
> occurred is in modsec_security.log:
>
> --35225a73-F--
> HTTP/1.1 500 Internal Server Error
> Expires: Thu, 19 Nov 1981 08:52:00 GMT
> Cache-Control: no-store, no-cache, must-revalidate
> Pragma: no-cache
> Set-Cookie: SQMSESSID=2e73bd53fdfeedd857900953d6a69c13; path=/webmail/;
> secure; HttpOnly; SameSite=Strict
> X-Frame-Options: SAMEORIGIN
> Strict-Transport-Security: max-age=63072000; includeSubDomains
> X-XSS-Protection: 1; mode=block
> X-Content-Type-Options: nosniff
> Feature-Policy: geolocation 'self'; vibrate 'none'
> Content-Security-Policy: frame-ancestors 'self'
> Content-Length: 0
> Connection: close
> Content-Type: text/html; charset=UTF-8
>
> The configtest.php script also appears to run correctly:
>
> SquirrelMail configtest
> This script will try to check some aspects of your SquirrelMail
> configuration and point you to errors wherever it can find them. You need
> to go run conf.pl in the config/ directory first before you run this
> script.
>
> SquirrelMail version: 1.4.23 [SVN]
> Config file version: 1.4.0
> Config file last modified: 22 November 2022 11:37:14
> Checking PHP configuration...
>     PHP version 8.0.25 OK.
>     Running as apache(48) / apache(48)
>     display_errors:
>     error_reporting: 32767
>     variables_order OK: GPCS.
>     PHP extensions OK. Dynamic loading is disabled.
> Checking paths...
>     Data dir OK.
>     Attachment dir OK.
>     Plugins OK.
>     Themes OK.
>     Default language OK.
>     Base URL detected as: https://example.com/webmail/src (location base
> autodetected)
> Checking outgoing mail service....
>     SMTP server OK (220 cipher.example.com ESMTP Postfix)
> Checking IMAP service....
>     IMAP server ready (* OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS
> ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.)
>     Capabilities: * CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE
> IDLE LITERAL+ STARTTLS AUTH=PLAIN AUTH=LOGIN
> Checking internationalization (i18n) settings...
>      gettext - Gettext functions are available. On some systems you must
> have appropriate system locales compiled.
>      mbstring - Mbstring functions are available.
>      recode - Recode functions are unavailable.
>      iconv - Iconv functions are available.
>      timezone - Webmail users can change their time zone settings.
> Checking database functions...
>     not using database functionality.
> Congratulations, your SquirrelMail setup looks fine to me!
>
> Any ideas greatly appreciated.
>
>
>
>
>
>
>
>
>
>
>
>

[SM-USERS] php-8 upgrade left some users unable to login

[Alex <mys...@gm...>]

Hi,

I've recently upgraded my SM to the latest 1.4.23-svn to support php-8.0.25
on fedora35 with apache-2.4.54 and it appears some users are unable to
login. It results in an apache 500 error that I don't know how to
troubleshoot. Some users have no difficulty logging in. I've also deleted
any user prefs or data/ info related to the user.

I'ver verified the users can login directly using IMAP, and it appears SM
is also successfully logging them in:

Nov 22 11:16:54 cipher dovecot[1228]: imap-login: Login: user=<alex>,
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=1386757, secured,
session=<UskYgBHuhJx/AAAB>
Nov 22 11:16:54 cipher dovecot[1228]:
imap(alex)<1386757><UskYgBHuhJx/AAAB>: Disconnected: Logged out in=44
out=1022 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0
body_count=0 body_bytes=0
Nov 22 11:16:54 cipher squirrelmail[664245]: Successful webmail login: by
alex (example.com) at 68.195.111.42

I have the following plugins installed, although I've tried limiting it
even further, and I don't think one of them is causing the problem. I did
have to delete quicksave, as that would prevent the inbox from being
displayed - perhaps that's already included?

1.squirrelspell
2. compatibility
3. squirrel_logger
4. administrator
5. calendar
6. delete_move_next
7. filters
8. folder_sizes
9. local_autorespond_forward
10. lockout
11. message_details
12. sent_subfolders
13. timeout_user
14. info

I've also enabled html_errors, log_errors, display_startup_errors,
error_reporting = E_ALL, and error_log, but there aren't any errors
generated when the 500 error occurs. The only indication that an error
occurred is in modsec_security.log:

--35225a73-F--
HTTP/1.1 500 Internal Server Error
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Set-Cookie: SQMSESSID=2e73bd53fdfeedd857900953d6a69c13; path=/webmail/;
secure; HttpOnly; SameSite=Strict
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=63072000; includeSubDomains
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Feature-Policy: geolocation 'self'; vibrate 'none'
Content-Security-Policy: frame-ancestors 'self'
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

The configtest.php script also appears to run correctly:

SquirrelMail configtest
This script will try to check some aspects of your SquirrelMail
configuration and point you to errors wherever it can find them. You need
to go run conf.pl in the config/ directory first before you run this script.

SquirrelMail version: 1.4.23 [SVN]
Config file version: 1.4.0
Config file last modified: 22 November 2022 11:37:14
Checking PHP configuration...
    PHP version 8.0.25 OK.
    Running as apache(48) / apache(48)
    display_errors:
    error_reporting: 32767
    variables_order OK: GPCS.
    PHP extensions OK. Dynamic loading is disabled.
Checking paths...
    Data dir OK.
    Attachment dir OK.
    Plugins OK.
    Themes OK.
    Default language OK.
    Base URL detected as: https://example.com/webmail/src (location base
autodetected)
Checking outgoing mail service....
    SMTP server OK (220 cipher.example.com ESMTP Postfix)
Checking IMAP service....
    IMAP server ready (* OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS
ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.)
    Capabilities: * CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE
IDLE LITERAL+ STARTTLS AUTH=PLAIN AUTH=LOGIN
Checking internationalization (i18n) settings...
     gettext - Gettext functions are available. On some systems you must
have appropriate system locales compiled.
     mbstring - Mbstring functions are available.
     recode - Recode functions are unavailable.
     iconv - Iconv functions are available.
     timezone - Webmail users can change their time zone settings.
Checking database functions...
    not using database functionality.
Congratulations, your SquirrelMail setup looks fine to me!

Any ideas greatly appreciated.

Re: [SM-USERS] missing mime part 2 application/ms winmail.dat base64missing

[Paul L. <pa...@sq...>]

On Thu, September 1, 2022 1:32 pm, James B. Byrne via squirrelmail-users
wrote:
> 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-Type	Name		Encoding
> 1	text/plain	 		quoted-printable
> 2	application/ms	winmail.dat	base64
>
> RFC822 Message body
> . . .
>
> But the winmail.dat attachment is not shown in SM.  It is in the message.

It's not entirely clear what you mean by this, but it would be more
helpful if you forward an example message as an attachment so the full
message source is available for testing and reproduction.  Do you have the
TNEF Decoder plugin installed?

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php


> . . .
> --_000_YT2PR01MB5266C25E915D447A6B08EC54AF7B9YT2PR01MB5266CANP_
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
> . . .
>
>
> --_000_YT2PR01MB5266C25E915D447A6B08EC54AF7B9YT2PR01MB5266CANP_
> Content-Disposition: attachment; filename="winmail.dat"
> Content-Transfer-Encoding: base64
> Content-Type: application/ms-tnef; name="winmail.dat"
>
> eJ8+IklZAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEJgAEAIQAAADQ2OTEwRDc3
> Q0Y3MEE0NDE4RjM1OTcyREE2MjY1ODMyAP0GAQ2ABAACAAAAAgACAAEFgAMADgAAAOYHCQABAAwA
> . . .
>
>
> --_000_YT2PR01MB5266C25E915D447A6B08EC54AF7B9YT2PR01MB5266CANP_--
>
> I have no idea what is causing this but I do need it fixed.  Any ideas?

Re: [SM-USERS] force TLS1.1 or later

[Paul L. <pa...@sq...>]

> The problem with tarball install is that I'm concerned about dependencies,
> so to be honest, I'd prefer to use  a  "builtin", stable and proven
> version, for the moment.

SquirrelMail has minimal dependencies that probably won't change from what
you already have installed, but that's why you should install in a
parallel directory and test the upgraded installation.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

Re: [SM-USERS] force TLS1.1 or later [SOLVED]

[Ted H. <te...@io...>]

David,

I'm glad it worked.

We should give thanks to the original programmer who left the comment in 
their code.  Otherwise I'm sure I never would have found it.


Ted Hatfield




On Tue, 8 Nov 2022, David Carvalho wrote:

> Hello.
> After disabling tls1.0 on my MTA and  replacing
>
> $stream = @fsockopen('tls://' . $host, $port, $errorNumber, $errorString);
> with
> $stream = @fsockopen('ssl://' . $host, $port, $errorNumber, $errorString);
> In  Deliver_SMTP.class.php
>
> Everything is working fine!
> Thank you so much!
>
> Best regards
> David
>
>
> -----Original Message-----
> From: Ted Hatfield <te...@io...>
> Sent: 08 November 2022 11:02
> To: David Carvalho via squirrelmail-users
> <squ...@li...>
> Cc: David Carvalho <da...@di...>
> Subject: Re: [SM-USERS] force TLS1.1 or later
>
> On Tue, 8 Nov 2022, David Carvalho via squirrelmail-users wrote:
>> Good morning and thank you so much for the reply.
>>
>> This is not a single server. It is installed on  a web server which acts
> as an interface to send and receive e-mail from our mail server.
>> Can't use sendmail anymore, as I discovered a few years ago I needed
>> to specify relay for the web server IP in /etc/mail/access Config.php
>>
>> $domain                 = 'my.domain';
>> $imapServerAddress      = 'myserver.mydomain';
>> $imapPort               = 993;
>> $useSendmail            = false;
>> $smtpServerAddress      = 'myserver.mydomain';
>> /* $smtpPort               = 465;  */
>> $smtpPort               = 587;
>> $sendmail_path          = '/usr/sbin/sendmail';
>>
>>
>> The problem with tarball install is that I'm concerned about dependencies,
> so to be honest, I'd prefer to use  a  "builtin", stable and proven version,
> for the moment.
>> I have a docker with roundcube and it works fine whether I disable tls1 or
> not. Not sure if this helps. It has its own php version...
>>
>> Is it possible to change this in order to use tls 1.2?
>> File: Deliver_SMTP.class.php
>>
>>  if (($use_smtp_tls == true) and (check_php_version(4,3)) and
> (extension_loaded('openssl'))) {
>>            $stream = @fsockopen('tls://' . $host, $port, $errorNumber,
> $errorString);
>>        } else {
>>            $stream = @fsockopen($host, $port, $errorNumber,
>> $errorString);
>>
>>
>> Best regards.
>> David
>>
>> -----Original Message-----
>> From: Paul Lesniewski <pa...@sq...>
>> Sent: 07 November 2022 22:34
>> To: Squirrelmail User Support Mailing List
>> <squ...@li...>
>> Cc: David Carvalho <da...@di...>
>> Subject: Re: [SM-USERS] force TLS1.1 or later
>>
>>
>>> I'm using Squirrelmail 1.4.22-16 on an Oracle Linux 6 with PHP 5.3.3
>>>
>>> It's running on old hardware so probably it won't be upgraded anytime
>>> soon.
>>>
>>> Squirrelmail is working fine for many years, but I wanted to disable
>>> TLS1 support in sendmail. As soon as I do it, I get "Can't open
>>> Stream" error message. Changed port 465 to 587 but I get the same error.
>>>
>>> This PHP version supports TLS1.1 and 1.2, so,  is there a way to "force"
>>> squirrelmail to use these later protocols?
>>
>> SquirrelMail doesn't specifically ask for a TLS version, but it's possible
> the way it works with your PHP version may cause the downgrade.  You'd have
> to give more details about your configuration to know where to start.
>>
>> That said, if this is a single-server solution, there is no reason for
>> you to be encrypting connections to the same host.  Setting that up
>> (even if you have to create a custom port/local listener in sendmail
>> that is
>> non-encrypted) would likely be a more productive use of your time.  What's
> more, you don't even need to be using SMTP to send outgoing mail at all:
>> just configure SquirrelMail to use the sendmail command instead.  If you
> run the configuration tool, it will walk you through doing so (save a copy
> of your main configuration file just in case).
>>
>> Also, you know that running a system that far out of date is risky and
> will contain known security vulnerabilities.  For SquirrelMail's part, you
> can easily upgrade yourself by downloading a tarball of version 1.4.23-svn
> from our downloads page and install it in a parallel directory where you can
> test migrating your configuration and plugins over -- if it's lightly
> modified/configured, that probably won't cause too much trouble.
>>
>> --
>> Paul Lesniewski
>> SquirrelMail Team
>> Please support Open Source Software by donating to SquirrelMail!
>> http://squirrelmail.org/donate_paul_lesniewski.php
>>
>>
>
> David,
>
> I'm running SquirrelMail version 1.4.23 on my server.  The file:
> Deliver_SMTP.class.php is newer and has this comment in the code referencing
> the tls:// statement.
>
>
> // NB: Using "ssl://" ensures the highest possible TLS version // will be
> negotiated with the server (whereas "tls://" only // uses TLS version 1.0)
>
>
> You can try changing the php code from
>
> $stream = @fsockopen('tls://' . $host, $port, $errorNumber, $errorString);
>
> to
>
> $stream = @fsockopen('ssl://' . $host, $port, $errorNumber, $errorString);
>
> and see if this resolves the issue.  However if you do so you will need to
> keep a copy of your local changes just in case you reload the package and
> inadvertently overwrite the local changes.
>
> Good luck.
>
> Ted Hatifeld
>
>

Re: [SM-USERS] force TLS1.1 or later [SOLVED]

[David C. <da...@di...>]

Hello.
After disabling tls1.0 on my MTA and  replacing 

$stream = @fsockopen('tls://' . $host, $port, $errorNumber, $errorString);
with
$stream = @fsockopen('ssl://' . $host, $port, $errorNumber, $errorString);
In  Deliver_SMTP.class.php

Everything is working fine!
Thank you so much!

Best regards
David


-----Original Message-----
From: Ted Hatfield <te...@io...> 
Sent: 08 November 2022 11:02
To: David Carvalho via squirrelmail-users
<squ...@li...>
Cc: David Carvalho <da...@di...>
Subject: Re: [SM-USERS] force TLS1.1 or later

On Tue, 8 Nov 2022, David Carvalho via squirrelmail-users wrote:
> Good morning and thank you so much for the reply.
>
> This is not a single server. It is installed on  a web server which acts
as an interface to send and receive e-mail from our mail server.
> Can't use sendmail anymore, as I discovered a few years ago I needed 
> to specify relay for the web server IP in /etc/mail/access Config.php
>
> $domain                 = 'my.domain';
> $imapServerAddress      = 'myserver.mydomain';
> $imapPort               = 993;
> $useSendmail            = false;
> $smtpServerAddress      = 'myserver.mydomain';
> /* $smtpPort               = 465;  */
> $smtpPort               = 587;
> $sendmail_path          = '/usr/sbin/sendmail';
>
>
> The problem with tarball install is that I'm concerned about dependencies,
so to be honest, I'd prefer to use  a  "builtin", stable and proven version,
for the moment.
> I have a docker with roundcube and it works fine whether I disable tls1 or
not. Not sure if this helps. It has its own php version...
>
> Is it possible to change this in order to use tls 1.2?
> File: Deliver_SMTP.class.php
>
>  if (($use_smtp_tls == true) and (check_php_version(4,3)) and
(extension_loaded('openssl'))) {
>            $stream = @fsockopen('tls://' . $host, $port, $errorNumber,
$errorString);
>        } else {
>            $stream = @fsockopen($host, $port, $errorNumber, 
> $errorString);
>
>
> Best regards.
> David
>
> -----Original Message-----
> From: Paul Lesniewski <pa...@sq...>
> Sent: 07 November 2022 22:34
> To: Squirrelmail User Support Mailing List 
> <squ...@li...>
> Cc: David Carvalho <da...@di...>
> Subject: Re: [SM-USERS] force TLS1.1 or later
>
>
>> I'm using Squirrelmail 1.4.22-16 on an Oracle Linux 6 with PHP 5.3.3
>>
>> It's running on old hardware so probably it won't be upgraded anytime 
>> soon.
>>
>> Squirrelmail is working fine for many years, but I wanted to disable
>> TLS1 support in sendmail. As soon as I do it, I get "Can't open 
>> Stream" error message. Changed port 465 to 587 but I get the same error.
>>
>> This PHP version supports TLS1.1 and 1.2, so,  is there a way to "force"
>> squirrelmail to use these later protocols?
>
> SquirrelMail doesn't specifically ask for a TLS version, but it's possible
the way it works with your PHP version may cause the downgrade.  You'd have
to give more details about your configuration to know where to start.
>
> That said, if this is a single-server solution, there is no reason for 
> you to be encrypting connections to the same host.  Setting that up 
> (even if you have to create a custom port/local listener in sendmail 
> that is
> non-encrypted) would likely be a more productive use of your time.  What's
more, you don't even need to be using SMTP to send outgoing mail at all:
> just configure SquirrelMail to use the sendmail command instead.  If you
run the configuration tool, it will walk you through doing so (save a copy
of your main configuration file just in case).
>
> Also, you know that running a system that far out of date is risky and
will contain known security vulnerabilities.  For SquirrelMail's part, you
can easily upgrade yourself by downloading a tarball of version 1.4.23-svn
from our downloads page and install it in a parallel directory where you can
test migrating your configuration and plugins over -- if it's lightly
modified/configured, that probably won't cause too much trouble.
>
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php
>
>

David,

I'm running SquirrelMail version 1.4.23 on my server.  The file:
Deliver_SMTP.class.php is newer and has this comment in the code referencing
the tls:// statement.


// NB: Using "ssl://" ensures the highest possible TLS version // will be
negotiated with the server (whereas "tls://" only // uses TLS version 1.0)


You can try changing the php code from

$stream = @fsockopen('tls://' . $host, $port, $errorNumber, $errorString);

to

$stream = @fsockopen('ssl://' . $host, $port, $errorNumber, $errorString);

and see if this resolves the issue.  However if you do so you will need to
keep a copy of your local changes just in case you reload the package and
inadvertently overwrite the local changes.

Good luck.

Ted Hatifeld

Re: [SM-USERS] force TLS1.1 or later

[Ted H. <te...@io...>]

On Tue, 8 Nov 2022, David Carvalho via squirrelmail-users wrote:
> Good morning and thank you so much for the reply.
>
> This is not a single server. It is installed on  a web server which acts as an interface to send and receive e-mail from our mail server.
> Can't use sendmail anymore, as I discovered a few years ago I needed to specify relay for the web server IP in /etc/mail/access
> Config.php
>
> $domain                 = 'my.domain';
> $imapServerAddress      = 'myserver.mydomain';
> $imapPort               = 993;
> $useSendmail            = false;
> $smtpServerAddress      = 'myserver.mydomain';
> /* $smtpPort               = 465;  */
> $smtpPort               = 587;
> $sendmail_path          = '/usr/sbin/sendmail';
>
>
> The problem with tarball install is that I'm concerned about dependencies, so to be honest, I'd prefer to use  a  "builtin", stable and proven version, for the moment.
> I have a docker with roundcube and it works fine whether I disable tls1 or not. Not sure if this helps. It has its own php version...
>
> Is it possible to change this in order to use tls 1.2?
> File: Deliver_SMTP.class.php
>
>  if (($use_smtp_tls == true) and (check_php_version(4,3)) and (extension_loaded('openssl'))) {
>            $stream = @fsockopen('tls://' . $host, $port, $errorNumber, $errorString);
>        } else {
>            $stream = @fsockopen($host, $port, $errorNumber, $errorString);
>
>
> Best regards.
> David
>
> -----Original Message-----
> From: Paul Lesniewski <pa...@sq...>
> Sent: 07 November 2022 22:34
> To: Squirrelmail User Support Mailing List <squ...@li...>
> Cc: David Carvalho <da...@di...>
> Subject: Re: [SM-USERS] force TLS1.1 or later
>
>
>> I'm using Squirrelmail 1.4.22-16 on an Oracle Linux 6 with PHP 5.3.3
>>
>> It's running on old hardware so probably it won't be upgraded anytime
>> soon.
>>
>> Squirrelmail is working fine for many years, but I wanted to disable
>> TLS1 support in sendmail. As soon as I do it, I get "Can't open
>> Stream" error message. Changed port 465 to 587 but I get the same error.
>>
>> This PHP version supports TLS1.1 and 1.2, so,  is there a way to "force"
>> squirrelmail to use these later protocols?
>
> SquirrelMail doesn't specifically ask for a TLS version, but it's possible the way it works with your PHP version may cause the downgrade.  You'd have to give more details about your configuration to know where to start.
>
> That said, if this is a single-server solution, there is no reason for you to be encrypting connections to the same host.  Setting that up (even if you have to create a custom port/local listener in sendmail that is
> non-encrypted) would likely be a more productive use of your time.  What's more, you don't even need to be using SMTP to send outgoing mail at all:
> just configure SquirrelMail to use the sendmail command instead.  If you run the configuration tool, it will walk you through doing so (save a copy of your main configuration file just in case).
>
> Also, you know that running a system that far out of date is risky and will contain known security vulnerabilities.  For SquirrelMail's part, you can easily upgrade yourself by downloading a tarball of version 1.4.23-svn from our downloads page and install it in a parallel directory where you can test migrating your configuration and plugins over -- if it's lightly modified/configured, that probably won't cause too much trouble.
>
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php
>
>

David,

I'm running SquirrelMail version 1.4.23 on my server.  The file:
Deliver_SMTP.class.php is newer and has this comment in the code
referencing the tls:// statement.


// NB: Using "ssl://" ensures the highest possible TLS version
// will be negotiated with the server (whereas "tls://" only
// uses TLS version 1.0)


You can try changing the php code from

$stream = @fsockopen('tls://' . $host, $port, $errorNumber, $errorString);

to

$stream = @fsockopen('ssl://' . $host, $port, $errorNumber, $errorString);

and see if this resolves the issue.  However if you do so you will need to
keep a copy of your local changes just in case you reload the package and
inadvertently overwrite the local changes.

Good luck.

Ted Hatifeld

Re: [SM-USERS] force TLS1.1 or later

[David C. <da...@di...>]

Good morning and thank you so much for the reply.

This is not a single server. It is installed on  a web server which acts as an interface to send and receive e-mail from our mail server.
Can't use sendmail anymore, as I discovered a few years ago I needed to specify relay for the web server IP in /etc/mail/access
Config.php

$domain                 = 'my.domain';
$imapServerAddress      = 'myserver.mydomain';
$imapPort               = 993;
$useSendmail            = false;
$smtpServerAddress      = 'myserver.mydomain';
/* $smtpPort               = 465;  */
$smtpPort               = 587;
$sendmail_path          = '/usr/sbin/sendmail';


The problem with tarball install is that I'm concerned about dependencies, so to be honest, I'd prefer to use  a  "builtin", stable and proven version, for the moment.
I have a docker with roundcube and it works fine whether I disable tls1 or not. Not sure if this helps. It has its own php version...

Is it possible to change this in order to use tls 1.2?
File: Deliver_SMTP.class.php

  if (($use_smtp_tls == true) and (check_php_version(4,3)) and (extension_loaded('openssl'))) {
            $stream = @fsockopen('tls://' . $host, $port, $errorNumber, $errorString);
        } else {
            $stream = @fsockopen($host, $port, $errorNumber, $errorString);


Best regards.
David

-----Original Message-----
From: Paul Lesniewski <pa...@sq...> 
Sent: 07 November 2022 22:34
To: Squirrelmail User Support Mailing List <squ...@li...>
Cc: David Carvalho <da...@di...>
Subject: Re: [SM-USERS] force TLS1.1 or later


> I'm using Squirrelmail 1.4.22-16 on an Oracle Linux 6 with PHP 5.3.3
>
> It's running on old hardware so probably it won't be upgraded anytime 
> soon.
>
> Squirrelmail is working fine for many years, but I wanted to disable 
> TLS1 support in sendmail. As soon as I do it, I get "Can't open 
> Stream" error message. Changed port 465 to 587 but I get the same error.
>
> This PHP version supports TLS1.1 and 1.2, so,  is there a way to "force"
> squirrelmail to use these later protocols?

SquirrelMail doesn't specifically ask for a TLS version, but it's possible the way it works with your PHP version may cause the downgrade.  You'd have to give more details about your configuration to know where to start.

That said, if this is a single-server solution, there is no reason for you to be encrypting connections to the same host.  Setting that up (even if you have to create a custom port/local listener in sendmail that is
non-encrypted) would likely be a more productive use of your time.  What's more, you don't even need to be using SMTP to send outgoing mail at all:
just configure SquirrelMail to use the sendmail command instead.  If you run the configuration tool, it will walk you through doing so (save a copy of your main configuration file just in case).

Also, you know that running a system that far out of date is risky and will contain known security vulnerabilities.  For SquirrelMail's part, you can easily upgrade yourself by downloading a tarball of version 1.4.23-svn from our downloads page and install it in a parallel directory where you can test migrating your configuration and plugins over -- if it's lightly modified/configured, that probably won't cause too much trouble.

--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

Re: [SM-USERS] force TLS1.1 or later

[Paul L. <pa...@sq...>]

> I'm using Squirrelmail 1.4.22-16 on an Oracle Linux 6 with PHP 5.3.3
>
> It's running on old hardware so probably it won't be upgraded anytime
> soon.
>
> Squirrelmail is working fine for many years, but I wanted to disable TLS1
> support in sendmail. As soon as I do it, I get "Can't open Stream" error
> message. Changed port 465 to 587 but I get the same error.
>
> This PHP version supports TLS1.1 and 1.2, so,  is there a way to "force"
> squirrelmail to use these later protocols?

SquirrelMail doesn't specifically ask for a TLS version, but it's possible
the way it works with your PHP version may cause the downgrade.  You'd
have to give more details about your configuration to know where to start.

That said, if this is a single-server solution, there is no reason for you
to be encrypting connections to the same host.  Setting that up (even if
you have to create a custom port/local listener in sendmail that is
non-encrypted) would likely be a more productive use of your time.  What's
more, you don't even need to be using SMTP to send outgoing mail at all:
just configure SquirrelMail to use the sendmail command instead.  If you
run the configuration tool, it will walk you through doing so (save a copy
of your main configuration file just in case).

Also, you know that running a system that far out of date is risky and
will contain known security vulnerabilities.  For SquirrelMail's part, you
can easily upgrade yourself by downloading a tarball of version 1.4.23-svn
from our downloads page and install it in a parallel directory where you
can test migrating your configuration and plugins over -- if it's lightly
modified/configured, that probably won't cause too much trouble.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

[SM-USERS] force TLS1.1 or later

[David C. <da...@di...>]

Hello

 

I'm using Squirrelmail 1.4.22-16 on an Oracle Linux 6 with PHP 5.3.3

It's running on old hardware so probably it won't be upgraded anytime soon. 

Squirrelmail is working fine for many years, but I wanted to disable TLS1
support in sendmail. As soon as I do it, I get "Can't open Stream" error
message. Changed port 465 to 587 but I get the same error.

This PHP version supports TLS1.1 and 1.2, so,  is there a way to "force"
squirrelmail to use these later protocols? 

 

Kind regards

David

Re: [SM-USERS] user/mailbox name case munging

[Paul L. <pa...@sq...>]

> Postfix munges all mailbox names to lowercase which probably explains this
> behaviour.  Squirrelmail evidently does not.  Can SM be configured to do
> so?

The Login Manager (Vlogin) plugin will do that for you.  It has a log of
features you won't want to use, but I think you can pare down one of its
"meta configuration" files to do only the case correction.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

[SM-USERS] user/mailbox name case munging

[James B. B. <by...@ha...>]

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 logged onto the webmail
service using all caps instead of the expected all lowercase mailbox name.  In
so doing they successfully logged but their webmail configuration was gone.

Postfix munges all mailbox names to lowercase which probably explains this
behaviour.  Squirrelmail evidently does not.  Can SM be configured to do so?

Thanks,

-- 
***          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 links sent by e-Mail

James B. Byrne                mailto:By...@Ha...
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

[SM-USERS] missing mime part 2 application/ms winmail.dat base64missing

[James B. B. <by...@ha...>]

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-Type	Name		Encoding
1	text/plain	 		quoted-printable
2	application/ms	winmail.dat	base64

RFC822 Message body
. . .

But the winmail.dat attachment is not shown in SM.  It is in the message.

. . .
--_000_YT2PR01MB5266C25E915D447A6B08EC54AF7B9YT2PR01MB5266CANP_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
. . .


--_000_YT2PR01MB5266C25E915D447A6B08EC54AF7B9YT2PR01MB5266CANP_
Content-Disposition: attachment; filename="winmail.dat"
Content-Transfer-Encoding: base64
Content-Type: application/ms-tnef; name="winmail.dat"

eJ8+IklZAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEJgAEAIQAAADQ2OTEwRDc3
Q0Y3MEE0NDE4RjM1OTcyREE2MjY1ODMyAP0GAQ2ABAACAAAAAgACAAEFgAMADgAAAOYHCQABAAwA
. . .


--_000_YT2PR01MB5266C25E915D447A6B08EC54AF7B9YT2PR01MB5266CANP_--

I have no idea what is causing this but I do need it fixed.  Any ideas?

Regards,



-- 
***          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 links sent by e-Mail

James B. Byrne                mailto:By...@Ha...
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

[SM-USERS] functions/date.php fix invalid types

[Udvari Z. <uz...@uz...>]

Hi list,

could you please check this bug report: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265395 ?
Is the fix correct?

Thanks,
   Zsolt

[SM-USERS] [SOLVED]: Firefox and Squirrelmail

[James B. B. <by...@ha...>]

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 much greater
> than 10k in side.  This is likely a timeout error in Firefox but I cannot find
> any discussion of this.
>

This is a firewall issue and has nothing to do with either firefox or Sm


-- 
***          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 links sent by e-Mail

James B. Byrne                mailto:By...@Ha...
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

[SM-USERS] Firefox and Squirrelmail

[James B. B. <by...@ha...>]

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 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 much greater
than 10k in side.  This is likely a timeout error in Firefox but I cannot find
any discussion of this.

Has anyone else run into this and if so what was the fix?  Thanks.



-- 
***          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 links sent by e-Mail

James B. Byrne                mailto:By...@Ha...
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

Re: [SM-USERS] PHP-8.0 SM shared calendars plugin

[Paul L. <pa...@sq...>]

> sudo -u www tail
> /usr/local/www/squirrelmail/plugins/shared_calendars/setup.php
> ...

If that worked then I'd say you can start tracing the execution to see
where it fails.  The easiest thing to do is just insert some output in the
code.  Start with something like:

echo "<h3>Hello world</h3>";

And put that in the setup.php file, in the "cal_menu_link" function, or
whichever you choose to trace.  If that works, move the echo statement
further along into the code path and see where it ends.  If it didn't
work, then the plugin may not be registered at all.  You can open up
functions/page_header.php and search for "menuline" which will be in a
"do_hook" function call and right before that, you can put:

global $squirrelmail_plugin_hooks;
sm_print_r($squirrelmail_plugin_hooks);

Inspect the output of that, looking for the shared_calendars items that
correspond to what it has in its setup.php file.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

Re: [SM-USERS] PHP-8.0 SM shared calendars plugin

[James B. B. <by...@ha...>]

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 SELINUX or anything similar present.


> The Shared Calendars plugin has for a long time installed itself over the
> stock calendars directory.  Maybe your port changed that, you'd have to
> adjust as needed which is why I can't offer much more help.  The newer
> version of Shared Calendars no longer does that since is only created
> confusion.
>

calendar is installed to squirrelmail/plugins/calendar

shared_calendars is installed to squirrelmail/plugins/shared_calendars

Both are present.

>
> You completely left out the sudo part of the command which is the entire
> point.
>

sudo -u www tail /usr/local/www/squirrelmail/plugins/calendar/setup.php
/**
 * Adds Calendar link to upper menu
 * @return void
 */
function calendar() {
    displayInternalLink('plugins/calendar/calendar.php',_("Calendar"),'right');
    echo "  \n";
}

?>


sudo -u www tail /usr/local/www/squirrelmail/plugins/shared_calendars/setup.php
{

   include_once(SM_PATH . 'plugins/calendar/small_calendar.php');
   small_calendar_style_do();

}



?>



-- 
***          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 links sent by e-Mail

James B. Byrne                mailto:By...@Ha...
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

Re: [SM-USERS] PHP-8.0 SM shared calendars plugin

[Paul L. <pa...@sq...>]

On Thu, April 21, 2022 7:38 pm, James B. Byrne wrote:
>
>
> 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 something like this:
>>
>> $ sudo -u www-data tail
>> /usr/share/squirrelmail/plugins/calendar/setup.php
>>
>> At the moment, I don't have any other suggestions, but to say that this
>> is
>> very likely going to be a site configuration issue and not a
>> SquirrelMail
>> bug.
>>
>
> I appreciate the help.  I have opened a bug report for the port as
> shared_calendars is a FreeBSD package.

I doubt it's their problem either, but who knows.

> The Apache configuration is copied from the working installation with the
> ip
> addresses altered to suit.

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.

> What is the relationship between
> /usr/share/squirrelmail/plugins/calendar/setup.php and shared_calendars?

The Shared Calendars plugin has for a long time installed itself over the
stock calendars directory.  Maybe your port changed that, you'd have to
adjust as needed which is why I can't offer much more help.  The newer
version of Shared Calendars no longer does that since is only created
confusion.

> [root@webmail-1 ~]# tail
> /usr/local/www/squirrelmail/plugins/calendar/setup.php

You completely left out the sudo part of the command which is the entire
point.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php