Re: [SM-USERS] php8.3 support and deprecated functions
FYI, all the notices below are fixed in our repository and those fixes will be available in our next nightly snapshots on our downloads page. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php On Wed, July 31, 2024 12:30 pm, Alex wrote: > Hi, > > I should have added that the previous warnings below occur when going to > Options -> Autoresponder/Mail Forwarding and the local_autorespond_forward > plugin, I believe. > > These new warnings are related to just viewing a regular message. > Deprecated: Creation of dynamic property MessageHeader::$entity_id is > deprecated in > /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/mime/Message.class.php > on line 494 > Deprecated: Creation of dynamic property MessageHeader::$lines is > deprecated in > /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/mime/Message.class.php > on line 497 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] php8.3 support and deprecated functions
> When composing a new message, I have the following warning/error in the > compose text box: > > Deprecated: explode(): Passing null to parameter #2 ($string) of > type string is deprecated in > /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mime.php > on line 693 This is also fixed and will be in our next nightly snapshots. Thanks for the reports. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] php8.3 support and deprecated functions
Thanks for these reports. The following notices are all fixed in our repository and will appear in our next nightly snapshots. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php > Deprecated: Creation of dynamic property Deliver_SMTP::$dlv_ret_nr is > deprecated in > /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/deliver/Deliver_SMTP.class.php > on line 427 > > Deprecated: Creation of dynamic property Deliver_SMTP::$dlv_msg is > deprecated in > /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/deliver/Deliver_SMTP.class.php > on line 484 > > Deprecated: Creation of dynamic property Deliver_SMTP::$dlv_server_msg is > deprecated in > /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/deliver/Deliver_SMTP.class.php > on line 485 > > Warning: Cannot modify header information - headers already sent by > (output > started at > /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/deliver/Deliver_SMTP.class.php:427) > in /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/global.php > on > line 594 > > Warning: Cannot modify header information - headers already sent by > (output > started at > /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/deliver/Deliver_SMTP.class.php:427) > in /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/global.php > on > line 594 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] php8.3 support and deprecated functions
> More warnings from Disposition.class.php when viewing different messages. > > Deprecated: Creation of dynamic property Disposition::$name is deprecated > in > /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/mime/Disposition.class.php > on line 30 > Deprecated: Creation of dynamic property Disposition::$properties is > deprecated in > /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/mime/Disposition.class.php > on line 31 > Deprecated: Creation of dynamic property Language::$name is deprecated in > /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/mime/Language.class.php > on line 31 > Deprecated: Creation of dynamic property Language::$properties is > deprecated in > /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/mime/Language.class.php > on line 36 These warnings are fixed in our repository and the fixes will be in our next nightly snapshots on our downloads page. > Warning: Cannot modify header information - headers already sent by > (output > started at > /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/mime/Disposition.class.php:30) > in > /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/page_header.php > on line 69 > > I've added "#[AllowDynamicProperties]" as per the following to suppress > this for now while I continue to debug That's not a good solution. It's generally good to see notices, warnings or errors in logs, just make sure not to display them on screen for a production system. > but I'm REALLY hoping you can fix > these soon. Why? These are notices of a future incompatibility. The problem you seem to be facing is you have these notices set to display on screen, which is your primary problem. You need to turn off display_errors in your PHP configuration. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] php8.3 support and deprecated functions
> These occur when composing/sending a new message.
> Warning: Undefined array key "" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 76
This appears to indicate your message cache is corrupt. Just above line
76, you can put something like this:
if (empty($msgs[$key])) {echo "MSGS IS EMPTY FOR KEY: $key";
var_dump($key); echo ""; sm_print_r($msgs);}
That may or may not turn up an inconsistency, but it may not tell you much
about how it developed. You'll have to try to narrow it down, by logging
out and making sure your session is cleared, disabling your plugins and
re-enabling them only one at a time as you test.
The rest of the issues below are all follow-on to the same corruption so
will all be solved by the same solution.
> I had no idea how problematic squirrelmail support is for php8.3. This is
> a real problem for me.
I can't see how this is related to your PHP version, at least without
knowing more about how your cache became corrupt.
On the other hand, the fact that $key might be an empty string could be
the problem ($key should usually be an integer). In that case, you can
print out a backtrace that could be a little bit more enlightening:
if (empty($msgs[$key])) {echo "MSGS IS EMPTY FOR KEY: $key";
var_dump($key); echo ""; debug_print_backtrace(); echo
"";}
When you hit this issue, what is the message list showing? Is there one or
more blank or missing rows in the list? Does the output end unexpectedly?
--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php
> Warning: Trying to access array offset on null in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 93
> Deprecated: strlen(): Passing null to parameter #1 ($string) of type
> string
> is deprecated in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/imap_general.php
> on line 1127
> Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type
> array|string is deprecated in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/imap_general.php
> on line 1130
> Warning: Undefined array key "ID" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 213
> Warning: Undefined array key "SUBJECT" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 218
> Warning: Undefined array key "ID" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 225
> Warning: Undefined array key "ID" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 226
> Warning: Undefined array key "ID" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 240
> Warning: Undefined array key "RECEIVED_DATE_STRING" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 247
> Warning: Undefined array key "RECEIVED_DATE_STRING_FULL" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 248
> Warning: Undefined array key "TYPE0" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 297
> Warning: Undefined array key "PRIORITY" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 302
> Warning: Undefined array key "PRIORITY" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 302
> Warning: Undefined array key "PRIORITY" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 306
>
> Thanks,
> Alex
>
> On Wed, Jul 31, 2024 at 9:21 AM Alex wrote:
>
>> Hi,
>>
>> More deprecations when viewing messages. Not sure why these aren't all
>> showing up together.
>>
>> Deprecated: Creation of dynamic property Language::$name is deprecated
>> in
>> /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/mime/Language.class.php
>> on line 31
>> Deprecated: Creation of dynamic property Language::$properties is
>> deprecated in
>> /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/mime/Language.class.php
>> on line 36
>> Warning: Cannot modify header information - headers already sent by
>> (output started at
>> /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/mime/Language.class.php:31)
>> in
>> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/page_header.ph
Re: [SM-USERS] Download All plugin
On Thu, September 12, 2024 12:00 am, Harold Hallikainen via squirrelmail-users wrote: > According to conf.pl, I have this plugin installed ( > https://www.squirrelmail.org/plugin_view.php?id=205 ), but I do not see > the download all link after the list of attachments. > > Ideas? Explain how you installed it. Check requirements. Run SquirrelMail configtest and see if that shows any errors for the plugin. Make sure to test it with a message that has more than one attachment. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] squirrelmail and php-8.3
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 >>> 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 >>> From >>> Subject X-Priority Importance Priority Content-Type )]) >>> Server responded: Invalid field-name in UID Fetch >>> BODY.PEEK[HEADER.FIELDS >> >> You'll want to look for a solution for this with whatever IMAP server it >> is you are using. >> > > I downloaded and installed the latest svn stable snapshot and that fixed > the malformed headers problem. The original installation was also cured by > simply copying in the functions from the stable build directory over the > existing installation (after copying both to some safe place). Sorry, I assumed you already had up-to-date code. Normally that's always an expectation here. > Now my problem is that I cannot get the shared calendar plugin to work. So debug it same as anything else -- enable PHP logging and watch your logs. Also if problems persist, show the versions of the involved software. The shared_calendars plugin has evolved to the calendar_advanced plugin that doesn't overwrite the stock calendar plugin to avoid whatever oddities you ran into. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] squirrelmail and php-8.3
> 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 > From > Subject X-Priority Importance Priority Content-Type )]) > Server responded: Invalid field-name in UID Fetch BODY.PEEK[HEADER.FIELDS You'll want to look for a solution for this with whatever IMAP server it is you are using. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] squirrelmail and php-8.3
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 of > squirrelmail > is unknow as the package manager reports: Version : 20230207 and the port > information page provides no details. > > The point I am at now is that when I run URL/src/configtest.php I get a > blank > page. If I look in the logs I see this: > > [23/Jan/2024:15:11:03 -0500] 66.249.76.65 TLSv1.2 > ECDHE-RSA-AES256-GCM-SHA384 > "GET /robots.txt HTTP/1.1" 381 > [23/Jan/2024:15:11:26 -0500] 216.185.71.41 TLSv1.2 > ECDHE-RSA-AES256-GCM-SHA384 > "GET /src/configtest.php HTTP/1.1" - > [23/Jan/2024:15:28:58 -0500] 216.185.71.41 TLSv1.2 > ECDHE-RSA-AES256-GCM-SHA384 > "GET /src/configtest.src HTTP/1.1" 196 > [23/Jan/2024:15:29:57 -0500] 216.185.71.41 TLSv1.2 > ECDHE-RSA-AES256-GCM-SHA384 > "GET /src/configtest.php HTTP/1.1" - > > and nothing else. The file is: 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 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Day View in Calendar creates each() error with php8.2
On Wed, January 17, 2024 7:03 pm, Alex wrote:
> Hi,
>
> php8.2 on fedora38 when clicking "Day View" from the Calendar
>
> Fatal error: Uncaught Error: Call to undefined function each() in
> /usr/share/squirrelmail/plugins/calendar/day.php:99 Stack trace: #0
> /usr/share/squirrelmail/plugins/calendar/day.php(177): display_events() #1
> {main} thrown in /usr/share/squirrelmail/plugins/calendar/day.php on line
> 99
Thanks for the report. While I generally recommend using the "Calendar
Advanced" plugin, this stock plugin code was overlooked when weeding out
PHP 8 incompatibilities. Fixes will be in our next build, within the next
24 hours, or see:
https://sourceforge.net/p/squirrelmail/code/15009/
https://sourceforge.net/p/squirrelmail/code/15010/
-
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Drop down menu and add button missing in Indexing Options
Please don't top-post, thanks. >>> Ha! That clears up the matter. Thank you so much! >> >> FYI, you can see who the mail was sent to in 1.4.x by hovering your >> mouse >> over the checkbox. > > Yes, that works! Thank you. We needed "To" only on Sent-Mail > folder. But this is sufficient. Thanks again. The sent folder *does* show the to field instead of the from address. Simply make sure the sent folder is properly designated in Options->Folder Preferences. If you use non-standard or multiple sent folders, you can install the "Special Folders" plugin (ask me offlist) which allows you to choose as many "sent" folders as you need. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Drop down menu and add button missing in Indexing Options
On Thu, December 7, 2023 9:00 am, V. Nandagopal wrote: > Hi, > > Ha! That clears up the matter. Thank you so much! FYI, you can see who the mail was sent to in 1.4.x by hovering your mouse over the checkbox. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php >>> HTML source of the frame shows the elements are present. I have >>> not modified options_order.php at all and the error logs too >>> dont show anything. I noticed if I remove the lines order1=1 to >>> order6=6, I do get the dropdown menu and the Add button back, >>> but the dropdown menu does not show anything other than "Size". >>> And once I add "Size" the menu and Add button vanish. >>> >>> I would like to add "To" to the list. >> >> To is not an option in 1.4.x. >> >>> I think there is some limit set on the number of fields that can be >>> displayed and also on what fields can be displayed, and I do not know >>> how to change that. >> >> Once all the possible options are added, the dropdown goes away. Options >> in 1.4.x are: Checkbox, From, Flags, Date, Subject, Size >> >> -- >> Paul Lesniewski >> SquirrelMail Team >> Please support Open Source Software by donating to SquirrelMail! >> http://squirrelmail.org/donate_paul_lesniewski.php >> >> >>>>> I installed Squirrelmail version 1.4.23 >>>>> (squirrelmail-20230831_0200-SVN.stable.tar.gz) on a Debian >>>>> Buster system with Apache as web server and dove. >>>>> >>>>> It works fine, but in Indexing Order in Options, I am unable to >>>>> add >>>>> fields I want to be displayed as the dropdown menu and the Add >>>>> button are missing. It was available in earlier installations. I >>>>> have attached screenshot of the display. What am I missing? >>>> >>>> Works for me... I suggest inspecting the HTML source of the frame to >>>> see >>>> if the elements are there at all, and look for PHP errors in your web >>>> server's PHP and/or web server error logs. Short of that, make sure >>>> src/options_order.php is not modified. >>>> >>>> -- >>>> Paul Lesniewski >>>> SquirrelMail Team >>>> Please support Open Source Software by donating to SquirrelMail! >>>> http://squirrelmail.org/donate_paul_lesniewski.php >> >> >> >> - >> squirrelmail-users mailing list >> Posting guidelines: http://squirrelmail.org/postingguidelines >> List address: squirrelmail-users@lists.sourceforge.net >> List archives: http://news.gmane.org/gmane.mail.squirrelmail.user >> List info (subscribe/unsubscribe/change options): >> https://lists.sourceforge.net/lists/listinfo/squirrelmail-users >> > > === > V. NandagopalEmail: > nandg...@math.tifr.res.in > School of MathematicsTelephone: 22782672 > Tata Institute of Fundamental Research Fax: 22804610/11 > Homi Bhabha Road, Colaba, Bombay 400 005, India > > - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Drop down menu and add button missing in Indexing Options
> HTML source of the frame shows the elements are present. I have > not modified options_order.php at all and the error logs too > dont show anything. I noticed if I remove the lines order1=1 to > order6=6, I do get the dropdown menu and the Add button back, > but the dropdown menu does not show anything other than "Size". > And once I add "Size" the menu and Add button vanish. > > I would like to add "To" to the list. To is not an option in 1.4.x. > I think there is some limit set on the number of fields that can be > displayed and also on what fields can be displayed, and I do not know > how to change that. Once all the possible options are added, the dropdown goes away. Options in 1.4.x are: Checkbox, From, Flags, Date, Subject, Size -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php >>> I installed Squirrelmail version 1.4.23 >>> (squirrelmail-20230831_0200-SVN.stable.tar.gz) on a Debian >>> Buster system with Apache as web server and dove. >>> >>> It works fine, but in Indexing Order in Options, I am unable to add >>> fields I want to be displayed as the dropdown menu and the Add >>> button are missing. It was available in earlier installations. I >>> have attached screenshot of the display. What am I missing? >> >> Works for me... I suggest inspecting the HTML source of the frame to see >> if the elements are there at all, and look for PHP errors in your web >> server's PHP and/or web server error logs. Short of that, make sure >> src/options_order.php is not modified. >> >> -- >> Paul Lesniewski >> SquirrelMail Team >> Please support Open Source Software by donating to SquirrelMail! >> http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] page request could not be verified and appears to have expired
Bruce, On Tue, December 5, 2023 10:22 pm, Bruce Gowans wrote: > I can receive emails just fine, but I cannot reply or compose a new one, > and I'm trying to within 10 seconds after logging in. > > These are screenshots of the errors I receive when replying to an email, > or composing a new message. > https://i.postimg.cc/QxX0fQrf/Screen-Shot-1701781435.jpg - reply > https://i.postimg.cc/PJKbg7k2/Screen-Shot-1701781635.jpg - compose > > This is a screenshot from web host error logs. > https://i.postimg.cc/ZR2bH8nn/Clipboard01.jpg > > I don't have access to any mail server logs. > > Squirrelmail - 1.4.22, this is the version that I have installed > manually on my shared web host. At this time I only have the > Administrator and Compatibility add-ons installed. > > SquirrelMail - 1.4.19, this is the version that my web host has > installed themselves, and also works correctly. I can't stand it though, > as I have no control over just about anything, such as themes and CSS, > and I can't add any add-ons, I can't even disable or remove any of the > few they have installed. First thing to do is install version 1.4.23, which is available as a SVN snapshot on our downloads page and should be quite stable and it might fix the errors in your log. The expired token seems like it may also be related with the PHP session problem in your environment. The unauthenticated relay error is coming from your MTA and isn't an issue you'll resolve in SquirrelMail unless you require even local clients to authenticate -- in that case, make sure to enable authentication to the MTA in the SM settings. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Drop down menu and add button missing in Indexing Options
Nandagopal, > I installed Squirrelmail version 1.4.23 > (squirrelmail-20230831_0200-SVN.stable.tar.gz) on a Debian > Buster system with Apache as web server and dove. > > It works fine, but in Indexing Order in Options, I am unable to add > fields I want to be displayed as the dropdown menu and the Add > button are missing. It was available in earlier installations. I > have attached screenshot of the display. What am I missing? Works for me... I suggest inspecting the HTML source of the frame to see if the elements are there at all, and look for PHP errors in your web server's PHP and/or web server error logs. Short of that, make sure src/options_order.php is not modified. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] email header in message body
On Thu, January 26, 2023 7:37 pm, rtc--- via squirrelmail-users wrote:
> Hello All,
> I am new here on the list but not new to SM. Using SM 1.4.4 with php5.4 on
> Win
> with Apache is working just fine. Thought is time for a new install, did
> that
> and ran into one major problem. Working and looking into it for a few
> days,
> but can't solve the problem. Config test shows my current install and
> results.
> Webserver is Sambar with php running as/under cgi.IMAP server is Sambar.
There's a good chance the problem is to do with this IMAP server, for
which SquirrelMail has no default settings given it is shareware that
stopped development 15 years(!) ago. There's every reason in the world
that you should run something more up to date. You could enable the
"info" plugin and inspect how the server responds to some standard
commands.
> SquirrelMail version:1.4.22 Config file version:1.4.0 Config file last
> modified:24 January 2023 19:41:26
> Checking PHP configuration...
> PHP version 5.6.40-0+deb8u12 OK.
> Running as sambar(1002) / sambar(1002)
> display_errors:
> error_reporting: 22527
> variables_order OK: GPCS.
> PHP extensions OK. Dynamic loading is disabled.
> Checking IMAP service
> IMAP server ready (* OK IMAP4 Server ready )
> Capabilities: * CAPABILITY IMAP4 IMAP4rev1 QUOTA IDLE X-MOVE X-EXPN
> AUTH=CRAM-MD5 STARTTLS
>
> My problem:
> email headers are shown in the message body, either in html or plain-text
> view.Sample from the Welcome message of this list:
>
> X-UID32: 1449536338 X-DATE: 1674576292 Return-path:
> squirrelmail-users-boun...@lists.sourceforge.net X-Spam-Checker-Version:
> SpamAssassin 3.4.2 (2018-09-13) on mars.yorktondigital.ca
> X-Spam-Level: X-Spam-Status: No, score=-3.9 required=5.0
> tests=ALL_TRUSTED,BAYES_00,
> MAILING_LIST_MULTI,TVD_RCVD_IP,TVD_RCVD_IP4 shortcircuit=no
> autolearn=ham autolearn_force=no version=3.4.2 Received: from 216.105.38.7
> by
> mail.x.ca (SMTPD); id s20230124100451.1798; Tue, 24 Jan
> 2023
> 10:04:51 Received: from [127.0.0.1] (helo=sfs-ml-2.v29.lw.sourceforge.com)
> by sfs-ml-2.v29.lw.sourceforge.com with esmtp (Exim 4.95)
> (envelope-from ) id 1pKLmv-Dg-1p for u...@.ca;
> Tue, 24 Jan 2023 16:04:44 + MIME-Version: 1.0 Content-Type:
> text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject:
> Welcome to the "squirrelmail-users" mailing list From:
> squirrelmail-users-requ...@lists.sourceforge.net To: u...@xxx.ca
> X-No-Archive: yes Message-ID: Date: Tue, 24 Jan 2023 16:04:42 +
> Precedence: bulk X-BeenThere: squirrelmail-users@lists.sourceforge.net
> X-Mailman-Version: 2.1.21 List-Id: Squirrelmail User Support Mailing List
> X-List-Administrivia: yes Errors-To:
> squirrelmail-users-boun...@lists.sourceforge.net Status: R Welcome to
> the
> squirrelmail-users@lists.sourceforge.net mailing list! Thank you for
> joining
> the SquirrelMail community.If you have a question, you should check if
> it's already answered in our documentation:
>
> --
> And here are the php error messages when viewing:
>
> PHP Warning: Variable passed to each() is not an array or object in
> /home/sambar/sambar/vhosts/dev2/functions/mime.php on line 1594
There is at least one fix related to this in version 1.4.23-svn, which is
available to download and which I recommend. However, it is questionable
whether this would solve the problem of headers being shown in the
message.
> PHP Warning: Creating default object from empty value in
> /home/sambar/sambar/vhosts/dev2/class/mime/Message.class.php on line 367
This is probably where SquirrelMail is choking on an unexpected
BODYSTRUCTURE response. You can inspect it using the IMAP info plugin --
for example, I created a new folder called "test" and put a single message
in the folder. In the "IMAP server information" (found under "Options") I
enabled the SELECT command and changed it to "SELECT test" and enabled a
new test (the first blank space) and filled in the command as "FETCH 1
(FLAGS BODYSTRUCTURE)" (since the single message in that folder is ID 1).
Your commands may differ depending on the folder structure and ID
assignment of your server... you'll have to look at the commands yourself,
though the URLs of the message view page will give you a good indication
of what they should be.
A typical response to that command will look like:
* 1 FETCH (FLAGS (\Seen) BODYSTRUCTURE (("text" "plain" ("charset"
"us-ascii") NIL NIL "quoted-printable" 2040 54 NIL NIL NIL NIL)("text"
"html" ("charset" "us-asci
Re: [SM-USERS] user/mailbox name case munging
> 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 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] PHP-8.0 SM shared calendars plugin
> 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 "Hello world"; 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 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] PHP-8.0 SM shared calendars plugin
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 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] PHP-8.0 SM shared calendars plugin
On Thu, April 21, 2022 4:26 pm, James B. Byrne wrote: > I have removed SM from the target host and reinstalled it from FreeBSD > packages > together with the packaged shared_calendar plugin. After configuring the > new > installation the problem remains in that there is no evidence that the > plugin > is loaded. 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. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] shared_calendar plugin
On Tue, April 19, 2022 9:10 pm, James B. Byrne wrote: > > > 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. In that case, I'd check the permissions on the plugin directory and files therein. Make sure the web server can even load the files. And double check the spelling of the plugin in config/config.php -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] shared_calendar plugin
On Tue, April 19, 2022 6:13 pm, James B. Byrne via squirrelmail-users wrote: > 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 the > shared_calendar > plugin is in use. I compared the config.php.sample files from both > installations and they are identical. The modified file config.php differs > from > the sample only in that the names of the calendar administrators are > present. > > The problem is that the shared_calendar plugin does not appear when a user > is > logged on to that instance of SM. I cannot find any log file entries > indicating a problem but the plugin is not available to use. > > How can I tell what is happening when SM starts up and find out why the > plugin > does not function? Did you watch for PHP errors? Do the calendar administrative options show up for users listed in $cal_admins in the plugin configuration? Are you sure it is enabled in the right SM instance? Did you run configtest? I have newer code than will be from the port you get, so I personally can't help as much, but you can insert debug lines in the code to see where the code path ends before printing out the calendar link that you expect to see. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] PHP-8.0 SM plugins (quicksave) (calander file backend)
On Thu, April 14, 2022 3:52 pm, James B. Byrne via squirrelmail-users wrote: > 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 found on the > SM > website dates from 2010. > > The existing plugin gives this error when squirrelmail is opened: > > [Thu Apr 14 11:05:10.097504 2022] [php:error] [pid 92477] [client > 216.185.71.41:46251] PHP Fatal error: Array and string offset access > syntax > with curly braces is no longer supported in > /usr/local/www/squirrelmail/plugins/quicksave/login_functions.php on line > 308, You can contact me offlist for an updated version of that plugin or just change the curly braces in most cases to square braces in your copy of the code. > I also have run into this error which is unrelated to quicksave but which > I > could use some help with. The calander file backend is a ported plugin > but it > seems not to work. > > [Thu Apr 14 11:25:22.943031 2022] [php:error] [pid 91870] [client > 216.185.71.41:15239] PHP Fatal error: Uncaught Error: Non-static method > Calendar::getCalendarFromICal() cannot be called statically in > /usr/local/www/squirrelmail/plugins/calendar_file_backend/calendar_functions.php:483\n This is likely a bug in the Shared Calendar plugin (calendar/classes/calendar.php) in the getCalendarFromICal function (likely the use of $this-> or similar) but I don't have a copy of that older code handy at the moment. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Both Roundcube and Squirrelmail webmail cannot search for anything because there are more than 200, 000 emails in my Inbox
> Roundcube webmail doesn't show any error. Search results simply don't > show up after a long time. > > However, I got the following error in Squirrelmail webmail (using > Firefox web browser). > > ERROR: Connection dropped by IMAP server. > > Query: SEARCH CHARSET ISO-8859-1 ALL SUBJECT "keyword" > > How do I solve this problem where both Roundcube and Squirrelmail > webmail can't search for anything at all because there are too many > emails inside my inbox? First, sort your mail into sensible subfolder organization, if only by year or month, etc. Use server-side filtering to make this automatic. Second, make sure you actually *need* that many messages - most people don't and should be deleting most of them. Third, if you must load/sort/search that volume of message, webmail is not for you - try Thunderbird or just log into the server and learn how to use your IMAP server directly. For dovecot, doveadm has some powerful capabilities. https://wiki2.dovecot.org/Tools/Doveadm/Search https://wiki2.dovecot.org/Tools/Doveadm/SearchQuery -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] squirrelmail-20220414_0200-SVN.stable.tar.gz
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: > > [Thu Apr 14 15:55:50.272309 2022] [php:error] [pid 43532] [client > 216.185.71.41:40396] > PHP Fatal error: Uncaught Error: Call to undefined function > session_set_cookie_params() You might need to install a separate PHP package with session functions or check that it's not disabled in your PHP configuration (disable_functions). -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] php??
> Which php version should I be using? php-5 or php-7? I have found > that the latest squirremail--webmail-1.4.22 > seems to work with both. Ah I see both are supported, but which would > be better? It makes no difference from SquirrelMail's perspective, but you should generally always keep all software on your system the most up to date. Please also use SquirrelMail version 1.4.23-svn from the downloads page (SVN snapshot). -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] squirrelmail-20220130_0200-SVN.devel on Fedora 35, ISE 500 on large email
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-fpm process to see > where this happens. You have posted several threads here and been asked to watch your PHP logs, but you don't seem to do that. Please always look at your PHP logs first. Resorting to strace is fairly outrageous when you'll likely find an out-of-memory error in the PHP log and then you can google that error and the solution is straight forward. Or search the mailing list archives. Or search for hints on the SquirrelMail website/wiki. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] delete_move_next plugin: Trying to access array offset on value of type null
On Wed, January 19, 2022 5:12 am, Robert Kudyba wrote: >> >> >> On Wed, January 19, 2022 1:39 am, Robert Kudyba wrote: >> > Running squirrelmail-20220115_0200-SVN.devel.tar.gz >> >> Remember to make sure to indicate if this is version 1.4.23 or 1.5.2, in >> this case I believe it is 1.4.23 >> > > 1.5.2 from the nightly snapshot The delete_move_next plugin was integrated into the SquirrelMail core for version 1.5.2. You should uninstall the one you tried to add. I believe if you run configtest.php you will get information about that. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] delete_move_next plugin: Trying to access array offset on value of type null
On Wed, January 19, 2022 1:39 am, Robert Kudyba wrote: > Running squirrelmail-20220115_0200-SVN.devel.tar.gz Remember to make sure to indicate if this is version 1.4.23 or 1.5.2, in this case I believe it is 1.4.23 > on Fedora 35, PHP 8, > the delete_move_next plugin generates this error: > > Category: PHP > Message: Trying to access array offset on value of type null > FILE: /usr/share/squirrelmail/plugins/delete_move_next/setup.php > LINE: 187 Is line 187 this in your case: $prev = findPreviousMessage($mbx_response['EXISTS'], $passed_id); If so, BEFORE that line please add this and take a look at the output: sm_print_r($mbx_response); EXISTS is a required field in the response for the SELECT command, so it should not be null. You might need to look into your IMAP setup or see if your account is broken. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
> 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 well as php-fpm.service and dovecot. All that means is you haven't found the right configuration yet. Blank screen means PHP errors, nothing else. > Also: > php -i | grep php.ini Running php on the CLI is not the same as php-fpm. There are sometimes different ini files used for each. Look more closely and you'll find other PHP configuration files on your system. They may or may not be called exactly "php.ini" > Configuration File (php.ini) Path => /etc > Loaded Configuration File => /etc/php.ini > > In the php.ini file: > error_log = /var/log/php_errors.log > html_errors = On > log_errors = On > display_errors = on > error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED > > all php-fpm error log has is: > [10-Jan-2022 20:40:10] NOTICE: fpm is running, pid 286 > [10-Jan-2022 20:40:10] NOTICE: ready to handle connections > [10-Jan-2022 20:40:10] NOTICE: systemd monitor interval set to 1ms > (END) > > What am I missing? You can insert a call to phpinfo() into something like the configtest.php file to get a better idea. Or use locate, find, or grep for things like "display_errors" in /etc/php or similar. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
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 server. Looks like additional one(s) may have been accidentally >> created. > > > OK so I see these that are the correct ones, which I believe point to > /var/spool/mail/me: > > ls -lta /home/me/mail/.imap/ This looks like a mess of different INBOX types caused by changing your Dovecot and/or client mailbox settings. You might want to look at your Dovecot mail_location (unless you have good reason, leave it as default) and if you have no important mail, I'd suggest deleting the entire mail store and start again with better-synchronized settings. Get rid of the superfluous INBOXes and whatnot. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
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 additional one(s) may have been accidentally created. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
>> > 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_next plugin is not working. That is a vague statement that needs detail (maybe in its own thread) if you need help with it. > I also had the undelete plugin. Will those no longer work? Unless you moved from 1.4.x to 1.5.x then plugins should move over without any issues. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
> 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_hooks.php as well as the plugins you installed manually. > 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 do see now that there is a subfolder called 'mail' > that has an additional Drafts, Sent and Trash folder Best way to fix this is to run conf.pl and use option D to select your IMAP server -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
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 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? >> >> PHP is not a compiled language. It's just a matter of putting the >> source >> code on your server. It is possible that you could grab a tarball of >> 1.4.23-svn from our website and unpack that right on top of what you >> have, >> but that could get messy depending what the RPM author did or did not do >> with the source or configuration. Try placing the new tarball in a >> parallel directory, copy over the configuration and plugins, and see how >> that goes. >> > > Right, duh of course. So putting them in a place like > /usr/share/squirrelmail2 would be ok. Do I just re-run conf.pl? Which > files > hold the settings? Yes, you can re-run conf.pl or just copy over config.php from your other installation and most things will probably work fine assuming the RPM isn't heavily modified. Sometimes there can be custom configuration changes in config_local.php as well. Once copied over, you can still run conf.pl to make changes from there. >> >> > I enabled logging in /etc/php.ini now I see *Fatal error*: Array and >> > string >> > offset access syntax with curly braces is no longer supported in >> > */usr/share/squirrelmail/functions/strings.php* on line *634* >> >> That error indicates that in fact you need a newer version of >> SquirrelMail > > Will the new version you mentioned fix these? Yes -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
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 from source? PHP is not a compiled language. It's just a matter of putting the source code on your server. It is possible that you could grab a tarball of 1.4.23-svn from our website and unpack that right on top of what you have, but that could get messy depending what the RPM author did or did not do with the source or configuration. Try placing the new tarball in a parallel directory, copy over the configuration and plugins, and see how that goes. > I enabled logging in /etc/php.ini now I see *Fatal error*: Array and > string > offset access syntax with curly braces is no longer supported in > */usr/share/squirrelmail/functions/strings.php* on line *634* That error indicates that in fact you need a newer version of SquirrelMail. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
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 loading plain HTML pages but webmail gets an internal server error, > 500. More than likely the SSL connection problem is happening at a layer above SquirrelMail. I'd first try to get a static page to load using that same certificate/domain and then try SquirrelMail, also keeping an eye on the PHP logs as well. > I enabled debug logging and below is what I see in the SSl error logs with > these 2 lines having errors: > AH02008: SSL library error 1 in handshake (server OURDOMAIN:443) > SSL Library Error: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert > certificate unknown (SSL alert number 46) -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Adding users to shared calendars
On Mon, December 6, 2021 4:00 pm, James B. Byrne via squirrelmail-users wrote: > 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 someone please tell me where I can find the share calendar > administrative interface? If it's been configured already, "Calendar Administration" will show on the "Options" page. If you don't find that item listed, then you need to set your username in the config.php file, under $cal_admins -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Changing fields in folders
> Problem/Issue: The 'received' email folder (ie email-2005) has the From > field displayed, so I know the sender. The 'sent-email-2005' > folder is also displaying the 'From' field, but I need it to show the "To" > field, so I know who the recipient is. > > How can I change this??? There isn't, but should be, a plugin that can handle that for you. The primary hook you want for that is called "check_handleAsSent_result" If you aren't up for doing that yourself and you'd like to encourage me to write that plugin for you and beta test it, please contact me offlist. Cheers, -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail 1.4.23-SVN Functionality
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 < >>> patches/msg_flags-squirrelmail-1.4.20.diff >>> patching file functions/mailbox_display.php >>> Reversed (or previously applied) patch detected! Assume -R? [n] >>> >>> What do I want to do here??? >> >> Select 'no', or if you want to be sure you applied everything correctly, >> select 'yes' and see if it "unpatches" itself correctly. If not, you'll >> want to start from scratch. Otherwise, re-apply the patch and you're >> good. >> > > Ok, here is how things went: > [root@dream msg_flags]# patch -d ../../ -p2 < I don't recommend you work as root, especially if you are unsure about the commands you're running; even typos can end up being disastrous. > patches/msg_flags-squirrelmail-1.4.20.diff > patching file functions/mailbox_display.php > Reversed (or previously applied) patch detected! Assume -R? [n] n > Apply anyway? [n] n > Skipping patch. > 2 out of 2 hunks ignored -- saving rejects to file > functions/mailbox_display.php.rej > patching file src/move_messages.php > Hunk #1 succeeded at 150 with fuzz 2 (offset 13 lines). > Hunk #2 succeeded at 224 (offset 21 lines). > patching file src/left_main.php > Hunk #1 succeeded at 78 (offset 2 lines). > Hunk #2 succeeded at 192 (offset 2 lines). Yuck, one file was patched, the others not... although it looks like you applied everything, I'd personally start with a fresh codebase and apply the patches, making sure they all go in the first time. > 2. This plugin has other patches, do I apply just the 1.4.20 patch, or > others as well? > > msg_flags-squirrelmail-1.4.10.diff > msg_flags-squirrelmail-1.4.13.diff > msg_flags-squirrelmail-1.4.15.diff > msg_flags-squirrelmail-1.4.20.diff > msg_flags-squirrelmail-1.4.3a.diff > > I assume the 1.4.20 diff contains all the other patches, correct? This is > hinted at in the instructions. Yes, ignore all but the newest version. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail 1.4.23-SVN Functionality
>> 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/mailbox_display.php > Reversed (or previously applied) patch detected! Assume -R? [n] > > What do I want to do here??? Select 'no', or if you want to be sure you applied everything correctly, select 'yes' and see if it "unpatches" itself correctly. If not, you'll want to start from scratch. Otherwise, re-apply the patch and you're good. > This was the version of the msg_flags plugin I downloaded: > msg_flags-1.4.20-1.4.3.tar.gz > > Sounds like I don't 'need' to patch? Should select 'n'?? -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail 1.4.23-SVN Functionality
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 having some effect on the interface just > by being loaded/enabled in the ./conf.pl config, with no options checked > in the display settings.. It comes with patches for full installation, that could easily be the problem. An updated version of this is also available offlist. > The problem with patching is it appears the fact these plugins have > 'newer' file stamps, is causing patch to say the files don't exist. Nothing to do with date stamps. It's a file path problem. You can just copy/type in the file path that is given just above and it should work or IIRC run the patch command like so (from the directory of whatever plugin it is that you are patching for): patch -d ../../ -p2 < patches/.diff You may need to fiddle with the options until you get it right. > Here is what I see when trying to patch msg_flags: > > [root@dream msg_flags]# patch -p0 < > patches/msg_flags-squirrelmail-1.4.20.diff > can't find file to patch at input line 3 > Perhaps you used the wrong -p or --strip option? > The text leading up to this was: > -- > |--- ../../functions/mailbox_display.php.orig 2008-02-10 > 08:49:47.0 -0800 > |+++ ../../functions/mailbox_display.php2008-06-11 > 06:41:00.0 -0700 > ------ > File to patch: > > I am NO EXPERT here, looking for assistance on how to resolve, if I need > too! -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail 1.4.23-SVN Functionality
ing database functions... > not using database functionality. > > Congratulations, your SquirrelMail setup looks fine to me! > > 8. I do have some errors in the PHP log: > PHP Warning: fsockopen(): Peer certificate CN=`kevla.org' did not match > expected CN=`localhost' in /usr/share/squirrelmail.1423/src/c > onfigtest.php on line 454 > > PHP Warning: fsockopen(): Failed to enable crypto in > /usr/share/squirrelmail.1423/src/configtest.php on line 454 > > PHP Warning: fsockopen(): unable to connect to ssl://localhost:993 > (Unknown error) in /usr/share/squirrelmail.1423/src/configtest.php > on line 454 > > PHP Warning: fsockopen(): Peer certificate CN=`kevla.org' did not match > expected CN=`localhost' in /usr/share/squirrelmail.1423/src/c > onfigtest.php on line 454 > > PHP Warning: fsockopen(): Failed to enable crypto in > /usr/share/squirrelmail.1423/src/configtest.php on line 454 > > PHP Warning: fsockopen(): unable to connect to ssl://localhost:993 > (Unknown error) in /usr/share/squirrelmail.1423/src/configtest.php > on line 454 > > PHP Warning: fsockopen(): SSL operation failed with code 1. OpenSSL Error > messages: > error:1408F10B:SSL routines:ssl3_get_record:wrong version number in > /usr/share/squirrelmail.1423/src/configtest.php on line 454 > > PHP Warning: fsockopen(): Failed to enable crypto in > /usr/share/squirrelmail.1423/src/configtest.php on line 454 > > PHP Warning: fsockopen(): unable to connect to ssl://localhost:143 > (Unknown error) in /usr/share/squirrelmail.1423/src/configtest.php > on line 454 Those are all from configtest as it tries to learn about your system. If they don't show up under normal usage, I'd ignore. > PHP Warning: A non-numeric value encountered in > /usr/share/squirrelmail.1423/functions/date.php on line 91 This happens when? Can you get the input or other data related to how this happens? > PHP Notice: Undefined variable: output in > /usr/share/squirrelmail.1423/plugins/multiple_attachments/functions.php on > line 119 Inconsequential notice that is fixed in newer version of the plugin Cheers, -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Need help with Squirrelmail 1.4.23-SVN on Centos 8
On Fri, November 19, 2021 3:08 am, Jay Hart wrote: > Fixed the attachment directory write issue by setting setenforce to '0'. Not a good long-term solution. You can watch the audit log and use ls -Z to view file/directory contexts. Use tools like audit2allow to help you figure out what policies you may need to change, but it's probably just a matter of setting directory context correctly. There are lots of helpful tutorials for that online, and once you look into it, it's not (much) harder than fixing the permissions you already did. > Then I got held up on the IMAP server (dovecot) and had to set 'Secure > IMAP (TLS)' setting to 'disabled'. If it's on the same machine, and you're connecting on port 143, then that is correct, you don't want TLS. You only need that for over-network connections to log in, usually on port 993. > Does these sound ok? Or, do I have another issue?? > > Great news is I just logged into my new Squirrelmail setup!!! Good job -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Need help with Squirrelmail 1.4.23-SVN on Centos 8
On Fri, November 19, 2021 2:21 am, Jay Hart wrote: > I am past this point now. Solved a bit more items. But now stuck on > writing permissions to the attachment directory > (/var/spool/squirrelmail/attach/) Just watch your log file, walk the directory structure to your data/attachments directories looking at permissions. If SELinux is active, watch its logs and file/directory contexts also. Make sure not to open up permissions more than the minimum required. There are lots of past mailing list posts you can refer to as well as: https://squirrelmail.org/wiki/index.php?page=DataAndAttachmentsDirectories Cheers, -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] SM and PHP8
On Sun, October 24, 2021 5:29 pm, James B. Byrne wrote: > > > 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 the info that I can get. The package iteself will not open so > I > cannot tell what version SM thinks it is. You can't look at the code running on your own server? In any case, the problem is almost certainly that the package is built on slightly outdated upstream code. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] SM and PHP8
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 > 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 supported in > /usr/local/www/squirrelmail/functions/strings.php on line 634 Please show that line (and a few lines before/after it). I suspect this is a problem in the FreeBSD package and not in our current code, but I can take a look if you give some context. > Is squirrelmail usable with PHP8? Yes. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] squirrelmail CVE-2020-14933
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://owasp.org/www-community/vulnerabilities/PHP_Object_Injection > > = > In order to successfully exploit a PHP Object Injection vulnerability two > conditions must be met: > > The application must have a class which implements a PHP magic method > (such as __wakeup or __destruct) that can be used to carry out malicious > attacks, or to start a “POP chain”. > All of the classes used during the attack must be declared when the > vulnerable unserialize() is being called, otherwise object autoloading > must be supported for such classes. > = > > SquirrelMail doesn't qualify for that scenario. Whoever accepted/assigned > this CVE seems to have only taken the word of the reporter, who has no > proof that I know of that there is any security issue. If anyone knows > differently, please get in touch. > > I'll put something on our /security page to reflect the situation. See: https://squirrelmail.org/security/issue.php?d=2021-10-15 -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] squirrelmail CVE-2020-14933
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? >> >> There is no vulnerability here. Per OWASP: >> >> https://owasp.org/www-community/vulnerabilities/PHP_Object_Injection >> >> = >> In order to successfully exploit a PHP Object Injection vulnerability >> two >> conditions must be met: >> >> The application must have a class which implements a PHP magic method >> (such as __wakeup or __destruct) that can be used to carry out malicious >> attacks, or to start a â�POP chainâ�. >> All of the classes used during the attack must be declared when the >> vulnerable unserialize() is being called, otherwise object autoloading >> must be supported for such classes. >> = >> >> SquirrelMail doesn't qualify for that scenario. Whoever >> accepted/assigned >> this CVE seems to have only taken the word of the reporter, who has no >> proof that I know of that there is any security issue. If anyone knows >> differently, please get in touch. >> >> I'll put something on our /security page to reflect the situation. >> >> Cheers, > > My problem is that I am in the midst of a PCI audit; and we use > SquirrelMail; > and this CVE is an issue with them. I doubt that either I or anyone else > can > convince the auditors to ignore what is on the NIST website identified as > a > Critical error respecting SM. That said, I will show them your response. > One > never knows what can happen when dealing with people having much authority > and > little knowledge. > > I checked some Linux distros and the seem to have issued some sort of > patch to > deal with this. I have seen a request made to the FreeBSD bug tracker to > deal > with this as well. > > I need something done to address this CVE, either by having it removed > from > NIST as invalid or through some sort of patch, meaningless or not, that > convinces NIST that the issue is resolved. That probably requires a new > CPE, > and that will no doubt require the FreeBSD port maintainer to issue a > version > upgrade. Otherwise I am going to be forced into an unwanted, and > evidently > unnecessary, migration. For which I have neither the time nor resources > to > effect. 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 from that person? Maybe you want them to invalidate/reject the ticket on their bug tracker? -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] squirrelmail CVE-2020-14933
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 order to successfully exploit a PHP Object Injection vulnerability two conditions must be met: The application must have a class which implements a PHP magic method (such as __wakeup or __destruct) that can be used to carry out malicious attacks, or to start a “POP chain”. All of the classes used during the attack must be declared when the vulnerable unserialize() is being called, otherwise object autoloading must be supported for such classes. = SquirrelMail doesn't qualify for that scenario. Whoever accepted/assigned this CVE seems to have only taken the word of the reporter, who has no proof that I know of that there is any security issue. If anyone knows differently, please get in touch. I'll put something on our /security page to reflect the situation. Cheers, -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Date field for messages in Drafts Folder.
Ted, On Mon, May 10, 2021 12:18 am, Ted Hatfield wrote: > > Hey all, > > A question that I was unable to find an answer for. > > I had a user ask a question that I was unable to anser. When a message is > placed into the drafts folder the date field is the date/time when the > message was started not when it was actually sent. > > In his instance he started a message and saved it to his drafts folder, > then picked up the message a week later when he actually completed and > sent the message. > > The sent message showed the date/time when the message was started not > when the message was actually sent. > > I'm running the squirrelmail package from the FreeBSD ports system. > > squirrelmail-php73-20200422 > > Can anyone tell me if this is the intended result or if I need to update > to the newest version of the 1.43 stable branch to resolve the issue. This is not exactly intended, but it is the way it is coded -- fair to say that it's a bug. There was even a note in the code suggesting that this may be a problem. Suffice to say that is has been fixed and will be available in the next nightly snapshots on our download page (allow 24 hours). Thanks for pointing this out. Cheers, Paul -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] I keep getting logged out of webmail
On Wed, May 12, 2021 4:04 am, Paul Lesniewski wrote: > > > On Tue, May 11, 2021 5:14 pm, James B. Byrne wrote: >> 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 > > Thanks, but as I said, you saw an *advisory warning* in the console and it > should not have had anything to do with the problem. But if it is for > some reason causing an issue, there is a change in SVN now that should > eliminate any concerns about SameSite. > >> I have added our SM web address to the >> 'network.cookie.sameSite.laxByDefault.disabledHosts' setting in FF. I >> will >> report if the logouts continue or not following this change. > > The warning seems to be pointing out the opposite, where what you want is > Lax but it is currently using None (and thinks the cookies don't have the > Secure flag). There's a few issues with this that I pointed out > previously and again, the change I made in SVN should bypass the whole > conversation. Snapshot tarballs with that change are available on our > downloads page. > > 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. 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? -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] I keep getting logged out of webmail
On Tue, May 11, 2021 5:14 pm, James B. Byrne wrote: > 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 Thanks, but as I said, you saw an *advisory warning* in the console and it should not have had anything to do with the problem. But if it is for some reason causing an issue, there is a change in SVN now that should eliminate any concerns about SameSite. > I have added our SM web address to the > 'network.cookie.sameSite.laxByDefault.disabledHosts' setting in FF. I > will > report if the logouts continue or not following this change. The warning seems to be pointing out the opposite, where what you want is Lax but it is currently using None (and thinks the cookies don't have the Secure flag). There's a few issues with this that I pointed out previously and again, the change I made in SVN should bypass the whole conversation. Snapshot tarballs with that change are available on our downloads page. 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. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] I keep getting logged out of webmail
>> You keep ignoring my suggestion to look at $check_mail_mechanism. Is >> the >> left/folder frame where the "must be logged in" message appears? >> Right-click in that frame, hit H then R to cause that frame only to >> reload >> and see if you are in fact logged out. If you're not, changing this >> setting may help. >> > > I am not ignoring you. I have a lot of more serious things that require > my > attention. SM's changed behaviour is an occasional annoyance, not a > problem. > > I reported it so that you would be aware of this behaviour and possibly > correlate it with other reports, if any. When I get a few spare moments > then I > will take a look at the things you suggest. However, I am constrained to > use > whatever version of SM the FreeBSD port maintainer chooses to release > regardless if a fix is found or not. > > In any case, I deeply suspect that culpability lies with FF and not SM. Ok, thank you for the report. Hope to hear from any others that may be seeing this. - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] I keep getting logged out of webmail
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 of the last time you installed it? > > pkg info squirrelmail-php73 > squirrelmail-php73-20190904 > Name : squirrelmail-php73 > Version: 20190904 > Installed on : Sat Mar 21 20:16:30 2020 EDT > Origin : mail/squirrelmail > Architecture : FreeBSD:12:* > >> Can you please update it? > > Not until and unless the FreeBSD port package is updated. You can download a nightly tarball from our downloads page and install it in a parallel directory to see if it works any differently. >> When you are properly logged in, are the cookies shown to have the >> HttpOnly and Secure attributes enabled? > > A screenshot of the FF storage inspector is attached. Ok, the cookies look secure when you are logged in. FYI I have a better version of Quicksave that doesn't have such message size limitations as when storing its data in cookies. You keep ignoring my suggestion to look at $check_mail_mechanism. Is the left/folder frame where the "must be logged in" message appears? Right-click in that frame, hit H then R to cause that frame only to reload and see if you are in fact logged out. If you're not, changing this setting may help. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] I keep getting logged out of webmail
On Fri, May 7, 2021 8:09 pm, James B. Byrne wrote: > > > On Fri, May 7, 2021 12:44, Paul Lesniewski wrote: >> >> Also go to Options --> Folder Preferences and make sure "Auto Refresh >> Folder List" is enabled. >> > Auto Refresh Folder List: 5 Minutes What about the other things I advised you to check? Please provide as much information as you can. > Today the logout occurred while I was inspecting the cookies. These > screenshots shows the storage state immediately after the logout. What version of SM are you using? When was the date of the last time you installed it? Can you please update it? When you are properly logged in, are the cookies shown to have the HttpOnly and Secure attributes enabled? What you show looks unorthodox. Are you serving the installation over HTTPS? Is it on the local network or remote? I'd also say you should try to keep terminals open tailing three log files: web server, PHP and IMAP server and see what the corresponding log data looks like. Cheers, -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] I keep getting logged out of webmail
>> 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 rejected because it has the >>> �SameSite� >>> attribute set to �None� or an invalid value, without the >>> �secure� >>> attribute. To >>> know more about the �SameSite� attribute, read >>> https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite >> >> That's just a warning. It won't have anything to do with the logout. >> Try >> to see if you still have the SM cookies when it happens. And please try >> to better describe when/how it happens - there's nothing much to go on >> here. Was it as a result of the folder list refresh? Some other >> action? >> And as I suggested, please try to report on (and play with) the folder >> refresh config setting. >> > > I cannot recall it happening while I was in the middle of using SM, either > for > reading or composing. Generally, I leave the SM browser tab open, or nor, > with > FF open on the desktop (gnome/mate-FreeBSD-12.2) in the background. > Occasionally when I go to use SM I get the logged out notice and have to > log in > again. Also go to Options --> Folder Preferences and make sure "Auto Refresh Folder List" is enabled. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] I keep getting logged out of webmail
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 rejected because it has the �SameSite� > attribute set to �None� or an invalid value, without the �secure� > attribute. To > know more about the �SameSite� attribute, read > https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite That's just a warning. It won't have anything to do with the logout. Try to see if you still have the SM cookies when it happens. And please try to better describe when/how it happens - there's nothing much to go on here. Was it as a result of the folder list refresh? Some other action? And as I suggested, please try to report on (and play with) the folder refresh config setting. As for that warning, it looks like a bit of a bug in Firefox to me --- as I understand, the default should be Lax and not None. Furthermore, our cookies should be getting sent with the secure flag, assuming your site is served with SSL. I wouldn't expect Firefox to mix that up, but the cookies are all getting that flag attached as I see it. Moreover, if the default matched their docs, it would not cause this warning anyway. But I went ahead and added a 'strict' default for SameSite that should bypass all that. Pick it up in our next nightly snapshot or here are patches for 1.4.23: https://sourceforge.net/p/squirrelmail/code/14917/ Or 1.5.2: https://sourceforge.net/p/squirrelmail/code/14918/ -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php > 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 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 knows what is happening and how to prevent it I >>> would >>> appreciate having that information. >> >> Not really possible to guess what's happening without more description >> of >> the issue or debugging info. . . . > > > -- > *** 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. Byrnemailto:byrn...@harte-lyne.ca > 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 > > - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] I keep getting logged out of webmail
On Mon, May 3, 2021 5:04 pm, James B. Byrne via squirrelmail-users wrote: > 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 knows what is happening and how to prevent it I would > appreciate > having that information. Not really possible to guess what's happening without more description of the issue or debugging info. Watch the network debugging interface and see if the folder list refreshes are happening and if not, why not. The debug console should give you hints. I also recommend looking at what your $check_mail_mechanism is -- I use "advanced" but "basic" can also solve some refresh issues, though these only work if JavaScript is enabled (in the config tool, that's 4 (General Options) ==> 21 (Auto check mail mechanism) -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Planning on setting up Postfix + Dovecot + Webmail + Apache + MariaDB + PHP using Webmin Control Panel in the Cloud
On Wed, April 21, 2021 2:56 pm, Turritopsis Dohrnii Teo En Ming wrote: > Subject: Planning on setting up Postfix + Dovecot + Webmail + Apache + > MariaDB + PHP using Webmin Control Panel in the Cloud > > Good day from the Republic of Singapore, > > I am planning to setup Postfix Email Server + Dovecot IMAP/POP3 > Incoming Mail Server + Webmail (Roundcube or Squirrelmail) + Apache > Web Server + MariaDB Database Server + PHP using Webmin Control Panel > specifically, in the cloud, preferably Amazon EC2. > > Are there any very good and well written guides on doing this type of > setup? I personally don't care for guides and like to refer to the documentation for each product itself so you know what its possibilities are. Guides are great as a learning tool, but the authors often make choices for you. That doesn't have to be a bad thing, especially when the author helps you understand those decisions. In this day and age, I'd expect there are plenty of great guides. If you need help with SquirrelMail, just let us know. Please make sure to install the 1.4.23-svn snapshot from our downloads page. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] faulty email contents or an issue ?
>>> I get certain email from a particular sender that have a header as >>> below, and, that display as below: >> >> (reply based on receiving the actual email itself offlist) Also please note that the original plaintext-only message display *does* display the desired message contents below all the CSS text. You might not have scrolled down far enough to see. >> If you click on "View as HTML" you will see the message (requires >> view_as_html plugin in 1.4.x). The message text is off center in SM >> version 1.5.2 due to a namespace clash in the CSS (which I will fix >> soon), but it's still readable. It displays perfectly in SM version >> 1.4.23. > > what's the 'best' version to use, 1.4.x rather than 1.5.x ? That's up to you. I personally prefer 1.4.x > is there some update procedure, or it it simple a matter of d/l new > version, installing to a new directory and, change/set http path/link ? There are some differences between 1.4 and 1.5, so I would recommend a more careful manual upgrade. - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] faulty email contents or an issue ?
On Tue, March 16, 2021 6:58 am, Voytek Eymont via squirrelmail-users wrote: > I get certain email from a particular sender that have a header as below, > and, that display as below: (reply based on receiving the actual email itself offlist) > am I correct to say it's sender's fault as mail has HTML only contents, > and, should included text/plain part ? Yes. If you click on "View as HTML" you will see the message (requires view_as_html plugin in 1.4.x). The message text is off center in SM version 1.5.2 due to a namespace clash in the CSS (which I will fix soon), but it's still readable. It displays perfectly in SM version 1.4.23. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] viewing message .eml attachment.
On Thu, March 18, 2021 12:43 pm, James B. Byrne wrote: > > > 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. Usually I download >>> and >>> extract using the tnef utility, but this time it says that 'Seems not >>> to >>> be a TNEF file'. >> >> It's a normal email message, just a text file with message headers and >> body. If it has the right mime type assigned in the parent message, >> SquirrelMail should handle it just fine. Or download it and open it in >> a >> text editor. >> >> > > First, I was inexact in my initial description. What I have is an .eml > attachment that is a message that was forwarded to me. I do not have the > original message. This is what Squirrelmail displays: [snip] > I can make out the headers even if they are all run together. But the > message > itself is in Base64 and this is not being translated into human readable > text. 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 formatted message. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] viewing message .eml attachment.
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. Usually I download and > extract using the tnef utility, but this time it says that 'Seems not to > be a TNEF file'. It's a normal email message, just a text file with message headers and body. If it has the right mime type assigned in the parent message, SquirrelMail should handle it just fine. Or download it and open it in a text editor. - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] faulty email contents or an issue ?
On Tue, March 16, 2021 6:58 am, Voytek Eymont via squirrelmail-users wrote:
> I get certain email from a particular sender that have a header as below,
> and, that display as below:
>
> am I correct to say it's sender's fault as mail has HTML only contents,
> and, should included text/plain part ?
It's really hard to know without seeing the unmolested message source.
Try sending a sanitized version as an attachment, or feel free to send the
original to me offlist (again, as an attachment please)
--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php
> thanks for any advice!
>
> they render OK on mobile, but, not in SM
>
> -
> You are using SquirrelMail version: 1.5.2 [SVN]
> The administrator installed the following plugins:
> none installed
>
>
>
> header is as so:
> --
> .
> MIME-Version: 1.0
> From: nore...@aaa.aaa.com
> To: voy...@b.bbb.com
> Date: Mon, 15 Mar 2021 23:44:04 +
> Subject: There is xxx.
> Content-Type: multipart/related; type="text/html";
> boundary=--boundary_7285_74b538b4-7819-40b0-80ad-a51581d538b5
> Message-ID:
> <010101783846715e-d3d12574-20de-48b0-9ed2-f971a755c889-000...@us-west-2.amazonses.com>
> X-OriginalArrivalTime: 15 Mar 2021 23:43:57.0824 (UTC)
> FILETIME=[11469800:01D719F5]
> X-SES-Outgoing:
> Feedback-ID:
> 1.us-west-2.jq0LT/01ANRfFMiHXGeSiNIleC9QhAgtglVJNuOnPkM=:AmazonSES
>
>
> displays in SM as so
> ---
>
> /* Mobile-specific Styles */
> @media only screen and (max-width: 660px) {
> table[class=w0], td[class=w0] { width: 0 !important; }
> table[class=w10], td[class=w10], img[class=w10] { width:10px !important; }
> table[class=w15], td[class=w15], img[class=w15] { width:10px !important; }
> table[class=w30], td[class=w30], img[class=w30] { width:10px !important; }
> table[class=w60], td[class=w60], img[class=w60] { width:10px !important; }
> table[class=w125], td[class=w125], img[class=w125] { width:80px
> !important; }
> table[class=w130], td[class=w130], img[class=w130] { width:55px
> !important; }
> table[class=w140], td[class=w140], img[class=w140] { width:90px
> !important; }
> table[class=w160], td[class=w160], img[class=w160] { width:180px
> !important; }
> table[class=w170], td[class=w170], img[class=w170] { width:100px
> !important; }
> table[class=w180], td[class=w180], img[class=w180] { width:80px
> !important; }
> table[class=w195], td[class=w195], img[class=w195] { width:80px
> !important; }
> table[class=w220], td[class=w220], img[class=w220] { width:220px
> !important; }
> table[class=w240], td[class=w240], img[class=w240] { width:180px
> !important; }
> table[class=w255], td[class=w255], img[class=w255] { width:185px
> !important; }
> table[class=w275], td[class=w275], img[class=w275] { width:135px
> !important; }
> table[class=w280], td[class=w280], img[class=w280] { width:135px
> !important; }
> table[class=w150], td[class=w150], img[class=w150] { width:150px
> !important; }
> table[class=w325], td[class=w325], img[class=w325] { width:95px
> !important; }
> table[class=w350], td[class=w350], img[class=w350] { width:70px
> !important; }
> table[class=w360], td[class=w360], img[class=w360] { width:140px
> !important; }
> table[class=w410], td[class=w410], img[class=w410] { width:180px
> !important; }
> table[class=w470], td[class=w470], img[class=w470] { width:200px
> !important; }
> table[class=w540], td[class=w540], img[class=w540] { width:270px
> !important; }
> table[class=w570], td[class=w570], img[class=w570] { width:280px
> !important; }
> table[class=w600], td[class=w600], img[class=w600] { width:300px
> !important; }
>
> #header td {display: block;}
> table[class*=hide], td[class*=hide], img[class*=hide], p[class*=hide],
> span[class*=hide] { display:none !important; }
> table[class=h0], td[class=h0] { height: 0 !important; }
> p[class=footer-content-left] { text-align: center !important; }
> #headline p { font-size: 30px !important; }
> .article-content, #left-sidebar{ -webkit-text-size-adjust: 90% !important;
> -ms-text-size-adjust: 90% !important; }
> .header-content, .footer-content-left {-webkit-text-size-adjust: 80%
> !important;
> -ms-text-size-adjust: 80% !important;}
> img { height: auto; line-height: 100%;}
> #footer span {display: block;}
> }
> /* Client-specific Styles */
> #outlook a { padding: 0; }/* Force Outlook to provide a "view in
> browser" button. */
> body { width: 100% !important; }
> .
>
-
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail not using port 465 for smtp although it is specified in config.php
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 server's submission service on port 25 (it's generally not). STARTTLS was added in version 1.4.23, so maybe your version is out of date. > 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. SquirrelMail does not ignore your settings. Maybe you have more than one SquirrelMail installation you are mixing up or your configuration settings were never saved. You're going to have to do more sleuthing; this is not normal behavior for SquirrelMail. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] RELAY needed in Sendmail for squirrelmail to be ableto send?
Please do not top-post. You can review the mailing list posting guidelines if you have questions about how to participate on our mailing lists. >>> >>> Hello and happy new year everyone. >>> I’ve been using Squirrelmail for a long time on 2 of my servers >>> currently >>> running Oracle Linux 6 with version 1.4.22. >> >> I advise upgrading to 1.4.23-svn >> >>> While doing some tests today, I noticed on my Sendmail server, which is >>> different from my web server where Squirrelmail is installed, that it >>> needs the following line in /etc/mail/access in order to be able to >>> send. >>> Connect:ip.squirrelmail RELAY >>> If I remove this line and regenerate access.db squirrelmail complaints >>> about not being able to run “/usr/sbin/sendmail -i -t etc, etc” >> >> That's because Sendmail on the mail server should not allow just anyone to >> relay mail freely through it. The access file is there to say that the >> server running SquirrelMail is trusted to relay mail from. >> >>> My options in config.php are the following: >>> $smtp_auth_mech = 'login'; >>> $imap_auth_mech = 'login'; >> >> This is all about your mail server setup, nothing to do with SquirrelMail. >> If you are requiring SASL login to send mail, then technically, the >> access file/permission on the mail server probably isn't needed, but in >> any case, SquirrelMail will just do what you tell it. >> >>> $smtp_sitewide_user = ''; >>> $smtp_sitewide_pass = ''; >>> $use_imap_tls = true; >>> $use_smtp_tls = true; >>> >>> One test I did was remove the RELAY entry in Sendmail access file and >>> use >>> valid user for fields $smtp_sitewide_user = ''; >>> $smtp_sitewide_pass = ''; >>> But the error is the same. >>> >>> Any ideas please? >> >> Read the logs on the mail server and review what your Sendmail relay >> and/or SASL authentication configuration (client requirements) are. After >> that, configure SquirrelMail to do whatever you choose to require on the >> Sendmail side. >> On Thu, January 7, 2021 9:41 am, David Carvalho wrote: > Hello and thanks for the reply. > I understand about the RELAY. I configured the server myself so that only > authenticated users could send through it. > All clients (windows mail, thunderbird, etc) can send when properly > authenticated. > From what I read, when the fields $smtp_sitewide_user = ''; > $smtp_sitewide_pass = ''; are null, the system should try to use the same > user/pass used in imap settings to be able to send. Yes, if you also have this: $smtp_auth_mech = 'login'; > If entering an existing valid user and password in those fields, shouldn’t > squirrelmail use them to authenticate? > Thanks and best regards. > Your logs should have the answers you need. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Unsafe Image Rules
On Wed, January 6, 2021 7:16 pm, "Andrés Chandía" wrote:
>
>
> El Mie, 6 de Enero de 2021, 20:05, "Andrés Chandía" escribió:
> ··
> ··
> ·· El Mie, 6 de Enero de 2021, 19:36, Paul Lesniewski escribió:
> ·· ··
> ·· ··
> ·· ·· On Wed, January 6, 2021 6:01 pm, "Andrés Chandía" wrote:
> ·· ··>
> ·· ··>
> ·· ··> Still finding some issues, now with the unsafe_image_rules plugin.
> ·· ··>
> ·· ··> If I activate
> ·· ··> this plugin when clicking the link to "See unsafe images" the
> entire email
> ·· ··> body
> ·· ··> desapears, clicking back the "hide unsafe images" shows the email
> body
> ·· ··> again.
> ·· ··
> ·· ·· http://squirrelmail.org/docs/admin/admin-11.html#ss11.1
> ·· ··
> ·· ··> If the plugin is not activated the "see unsafe images" works ok.
> ·· ··
> ·· ·· This makes no sense. If you deactivate the plugin, said feature
> will be
> ·· ·· gone. Maybe you have the plugin installed twice or something else
> quite
> ·· ·· mixed up.
> ·· ··
> ·· ··> SM 1.4.23 [SVN]
> ·· ··> Unsafe Image Rules Version 0.8
> ·· ··
> ··
> ··
> ··
> ·· It does make sense, I'm talking about the "View unsafe images" link
> that comes from
> ·· /src/read_body.php
Indeed, a bit hasty on my part.
> ·· Error: Call to undefined function eregi() in
> ·· /usr/share/squirrelmail/plugins/unsafe_image_rules/functions.php on
This is why reviewing the mailing list posting guidelines and including
all the information requested is important.
> in line 335 of
> /usr/share/squirrelmail/plugins/unsafe_image_rules/functions.php
> there was:
>
> while (eregi('(' . $Email_RegExp_Match . ')', $str, $hits)) {
>
> changing it to:
> while (preg_match('(' . $Email_RegExp_Match . ')', $str, $hits)) {
>
> solved the problem
That's the right fix.
-
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Unsafe Image Rules
On Wed, January 6, 2021 6:01 pm, "Andrés Chandía" wrote: > > > Still finding some issues, now with the unsafe_image_rules plugin. > > If I activate > this plugin when clicking the link to "See unsafe images" the entire email > body > desapears, clicking back the "hide unsafe images" shows the email body > again. http://squirrelmail.org/docs/admin/admin-11.html#ss11.1 > If the plugin is not activated the "see unsafe images" works ok. This makes no sense. If you deactivate the plugin, said feature will be gone. Maybe you have the plugin installed twice or something else quite mixed up. > SM 1.4.23 [SVN] > Unsafe Image Rules Version 0.8 -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] RELAY needed in Sendmail for squirrelmail to be able to send?
On Wed, January 6, 2021 5:14 pm, David Carvalho wrote: > > Hello and happy new year everyone. > I’ve been using Squirrelmail for a long time on 2 of my servers currently > running Oracle Linux 6 with version 1.4.22. I advise upgrading to 1.4.23-svn > While doing some tests today, I noticed on my Sendmail server, which is > different from my web server where Squirrelmail is installed, that it > needs the following line in /etc/mail/access in order to be able to send. > Connect:ip.squirrelmail RELAY > If I remove this line and regenerate access.db squirrelmail complaints > about not being able to run “/usr/sbin/sendmail -i -t etc, etc” That's because Sendmail on the mail server should not allow just anyone to relay mail freely through it. The access file is there to say that the server running SquirrelMail is trusted to relay mail from. > My options in config.php are the following: > $smtp_auth_mech = 'login'; > $imap_auth_mech = 'login'; This is all about your mail server setup, nothing to do with SquirrelMail. If you are requiring SASL login to send mail, then technically, the access file/permission on the mail server probably isn't needed, but in any case, SquirrelMail will just do what you tell it. > $smtp_sitewide_user = ''; > $smtp_sitewide_pass = ''; > $use_imap_tls = true; > $use_smtp_tls = true; > > One test I did was remove the RELAY entry in Sendmail access file and use > valid user for fields $smtp_sitewide_user = ''; > $smtp_sitewide_pass = ''; > But the error is the same. > > Any ideas please? Read the logs on the mail server and review what your Sendmail relay and/or SASL authentication configuration (client requirements) are. After that, configure SquirrelMail to do whatever you choose to require on the Sendmail side. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Set character environment
> Thanks Paul, latest svn stable version did the trick, eventhough I still > have two minor problems, > > 1. image buttons have desapeared, I can enable and disable the plugin but > icons don't show What image button? > 2. If my mail composition preference is the html format, when answering a > txt format received > mail the text from the original message is not recovered, I have to change > the setting... > > Default Email Composition Format: Plain Text > > to get the text from the message I'm answering into the response. > On the contrary, this does not happen with the mails that were sent to me > in html format. > > Some advice? Maybe follow the posting guidelines? You have to post details about what you installed and give us more to go on. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Set character environment
On Tue, December 29, 2020 2:54 pm, "Andrés Chandía" wrote: >> > Thanks for your advice Atoth, > I've found at least 4 patches in the thread you sent me, but I think you > refer to this one: > > quoted_printable_fix-1.4.x-version_3.diff > > I tried to apply it, but it always got rejected, so I checked the > implicated files > functions/i18n.php and functions/strings.php, and I have found that they > already had what the > patch was applying, exept that in file functions/strings.php there was a > section not included > which I included manually, but there was no imporvement anyway. This is always a bad sign and no one can really help you when it becomes that messy. > Actually as you can see in > this mail nor even what you wrote to me is recovered in the reply. > here are the packages I have installed: > > squirrelmail_1.4.23~svn20120406-2ubuntu1_all.deb This could easily be the problem. Please start over with a svn snapshot build from our downloads page instead. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php > squirrelmail-compatibility_2.0.16-1_all.deb > squirrelmail-decode_1.2-1ubuntu1_all.deb > squirrelmail-locales_1.4.18-20090526-1_all.deb > squirrelmail-lockout_1.7-2_all.deb > squirrelmail-logger_2.3.1-1_all.deb > squirrelmail-quicksave_2.4.5-1_all.deb > squirrelmail-secure-login_1.4-3_all.deb > squirrelmail-sent-confirmation_1.6-2_all.deb > squirrelmail-spam-buttons_2.3.1-1_all.deb > squirrelmail-viewashtml_3.8-3_all.deb > - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Set character environment
Please do not top post. > Thanks Paul, I have that already configured, I could save all my settings, > but things > don't go as expected anyway, for instance, for some messages the subject > or the sender or both > are not shown, I can not longer see the mails in the html view, only in > plain text (except for > the ones I send), and my address book is full of strange characters What version of SquirrelMail did you install? > Not sure what you're after, but you can start by setting SquirrelMail to > use > UTF8 in config/config.php > > $default_charset'?'? '?'? '?'? '?'?= > 'utf-8'; > $lossy_encoding'?'? '?'? '?'? '?'? = true; > > Though how this > plays out can depend if the charset you are using is > provided in UTF or not. > > > > > > > Hi there, not long ago I could finally set my server and squirrelmail to > work fine with > character encoding following a set of instructions... > > > Unfortunatelly something went wrong on my server and I've lost that > config, now I can not > find the instructions to set the character encoding environment again, if > you know what these > instructions could be, would you be so kind to send me the link to > them > > > thanks... > > > PS: is it not "internationalization" from the admin manual > > - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Set character environment
On Mon, December 28, 2020 4:29 pm, "Andrés ChandÃa" wrote: > > > Hi there, not long ago I could finally set my server and squirrelmail to > work fine with > character encoding following a set of instructions... Not sure what you're after, but you can start by setting SquirrelMail to use UTF8 in config/config.php $default_charset = 'utf-8'; $lossy_encoding= true; Though how this plays out can depend if the charset you are using is provided in UTF or not. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Modified Config_default.php | Can No Longer Send Mail
On Sat, August 1, 2020 7:47 pm, Orca Inbox wrote: > Hi Paul thanks for the response much appreciated. > > Here<https://termbin.com/r50x> is the log file for /var/log/maillog. I am > not certain if this is what you need. Not what I need, what *you* need. Seriously, *you* have to learn how to figure this stuff out. Indeed, this log file looks barren of most of the normal things you'd see in a functional mail server. I suggest you first make sure your mail server can send and receive email without using any mail client at all (use command line sendmail command or similar). Watch the log file in a different window when you do so: tail -f /var/log/maillog > PHP-Mapi instantiated 7,1,14,51822 That's a PHP extension for Exchange and I don't know why it would be "instantiating" over and over so quickly for an idle system. Doesn't look good to me. > Then my skilled friend said to check the webserver logs. Peculiar thing > for me is the logs are empty. Then that's another problem you should try to clear up first. > When I cat file -rwxrwxrwx jessemacdougall.ninja-error.log and > jessemacdougall.ninja-access.log the command goes through but nothing > outputs. This is the correct command: cat jessemacdougall.ninja-error.log > On Tue, July 28, 2020 5:04 am, Orca Inbox wrote: >> Problem: I edited /usr/share/squirrelmail/config/config_defaul.php for >> some esthetic changes when I should have edited >> /usr/share/squirrelmail/config/conf.pl. Now I can no longer send mail, >> I >> can receive mail. SquirrelMail was working fine before I made these >> changes<http://je...@jessemacdougall.com%20and%20jesse@macdougall.ninja%20can%20recieve%20mail%20in%20squirrelmail%20but%20can%20not%20send%20it.>. >> I reversed my changes but that didn't fix it. I can no longer send >> mail. >> I can receive it though. Here are the changes I >> made<http://%20https://docs.google.com/spreadsheets/d/10kWHDskwnFw2cdmDyE1mppDTN3fLnixuWN6M1l06ZBc/edit?usp=sharing> >> >> >> config_default.php clearly states to not edit the file and to edit >> conf.pl > > No, the configuration file you want is config.php, which is automatically > generated if you *run* conf.pl > >> | This is my fault. I apologize for wasting anyone's >> time.<http://conf.pl/> >> >> je...@jessemacdougall.com and jesse@macdougall.ninja can receive mail in >> SquirrelMail but can not send it. > > What you need to do is look in your logs and show the error that is > preventing this. That's the only way to hone in quickly on your problem, > especially when asking from help from other people. > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > http://squirrelmail.org/donate_paul_lesniewski.php > > > > > > >> The only thing I can think of is in line 35,41,61,95,106,695; I have a ; >> at the end of each line when the docs do not have the ;. I thought >> about >> removing the ; but I tend to break things faster then I build them so I >> thought I'd ask first. >> >> Needed Details >> SquirrelMail version = 1.4.23 >> Every plugin installed = None that I know of >> PHP Version = 5.4.16 >> Web server = Apache/2.4.6 (CentOS) >> IMAP server = ? >> SMTP server = ? >> OS = CentOS7 >> How software was installed = Came pre-installed >> Browsers tried = Firefox 68.6.0esr >> Any things that might make your install different = ? >> Bug report plugin: The requested URL >> /path-to-squirrelmail/src/configtest.php was not found on this server. >> >> Before You Ask<http://www.catb.org/~esr/faqs/smart-questions.html> >> >> 1. NA >> 2. NA >> 3. Read it >> 4. NA >> 5. I reverse the changed I made to the config_default .php file. No >> luck. I was surprised at this. I only chanced six variables so I >> thought if I changed variables back to original it would work. No dice. >> I can receive mail but can not send. I should have modified the >> conf.pl file like the file said. I f*^ked up. >> 6. I asked a skilled friend. He said to restore the >> config_default.php >> from the back up I made before I edited the config_default,php file. >> Problem was I was backing up my ~ not / so I was unable to restore the >> original file. So I looked up the source code >> <https://fossies.org/dox/squirrelmail-webmail-1.4.22/config__default_8php.html> >> and made changes back to original with no luck. Learning is fun. >> 7. NA >> >> I have learned to respect the instructions in
Re: [SM-USERS] Modified Config_default.php | Can No Longer Send Mail
On Tue, July 28, 2020 5:04 am, Orca Inbox wrote: > Problem: I edited /usr/share/squirrelmail/config/config_defaul.php for > some esthetic changes when I should have edited > /usr/share/squirrelmail/config/conf.pl. Now I can no longer send mail, I > can receive mail. SquirrelMail was working fine before I made these > changes<http://je...@jessemacdougall.com%20and%20jesse@macdougall.ninja%20can%20recieve%20mail%20in%20squirrelmail%20but%20can%20not%20send%20it.>. > I reversed my changes but that didn't fix it. I can no longer send mail. > I can receive it though. Here are the changes I > made<http://%20https://docs.google.com/spreadsheets/d/10kWHDskwnFw2cdmDyE1mppDTN3fLnixuWN6M1l06ZBc/edit?usp=sharing> > > > config_default.php clearly states to not edit the file and to edit conf.pl No, the configuration file you want is config.php, which is automatically generated if you *run* conf.pl > | This is my fault. I apologize for wasting anyone's > time.<http://conf.pl/> > > je...@jessemacdougall.com and jesse@macdougall.ninja can receive mail in > SquirrelMail but can not send it. What you need to do is look in your logs and show the error that is preventing this. That's the only way to hone in quickly on your problem, especially when asking from help from other people. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php > The only thing I can think of is in line 35,41,61,95,106,695; I have a ; > at the end of each line when the docs do not have the ;. I thought about > removing the ; but I tend to break things faster then I build them so I > thought I'd ask first. > > Needed Details > SquirrelMail version = 1.4.23 > Every plugin installed = None that I know of > PHP Version = 5.4.16 > Web server = Apache/2.4.6 (CentOS) > IMAP server = ? > SMTP server = ? > OS = CentOS7 > How software was installed = Came pre-installed > Browsers tried = Firefox 68.6.0esr > Any things that might make your install different = ? > Bug report plugin: The requested URL > /path-to-squirrelmail/src/configtest.php was not found on this server. > > Before You Ask<http://www.catb.org/~esr/faqs/smart-questions.html> > > 1. NA > 2. NA > 3. Read it > 4. NA > 5. I reverse the changed I made to the config_default .php file. No > luck. I was surprised at this. I only chanced six variables so I > thought if I changed variables back to original it would work. No dice. > I can receive mail but can not send. I should have modified the > conf.pl file like the file said. I f*^ked up. > 6. I asked a skilled friend. He said to restore the config_default.php > from the back up I made before I edited the config_default,php file. > Problem was I was backing up my ~ not / so I was unable to restore the > original file. So I looked up the source code > <https://fossies.org/dox/squirrelmail-webmail-1.4.22/config__default_8php.html> > and made changes back to original with no luck. Learning is fun. > 7. NA > > I have learned to respect the instructions in the config_default.php file, > which states clearly to edit the conf.pl for modification changes. > Learning the hard way. > > I read How to Ask Questions the Smart > Way<http://squirrelmail.org/docs/admin/admin-12.html>. > > Thank you for any responses they are greatly appreciated. Sorry again for > screwing this up. This is my bottleneck. > > Cheers, Jesse > > Jesse Mac Dougall > orcain...@aol.com - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] application/pdf not octet-stream for PDF attachments?
On Sun, June 28, 2020 1:14 pm, Voytek Eymont via squirrelmail-users wrote: > Hi, > > I'm running 1.5.2, all working well. when I get emails with PDF, usually, > they are "application/pdf" and open with PDF reader, > > BUT, some emails have them as "application/octet-stream", in which case > they attempt to open directly inside SM with PS characters/codes This was a bug that has been corrected in SVN. > is there any way to tell SM to always open all .pdf files with PDF reader > > I'm afraid my senders will keep sensing like they do... > > application/pdf These will open fine as-is. > application/octet-stream I can provide a plugin that will force SM to display these natively in-browser, or you can comment out the two lines in functions/mime.php after this: // IE does make use of mime content sniffing. Forcing a download // prohibit execution of XSS inside an application/octet-stream attachment But please read those comments carefully and consider that allowing the browser to load untrusted attachments can be dangerous. Same goes for the plugin I am offering. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Another HTML email oddity
Zsolt, On Tue, June 23, 2020 5:25 pm, 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 version is at state of 2019.09.04. Thanks for maintaining that, Zsolt. > I see logr14836 and r14838: > "Better HTML email content style containment" > and > "Even better HTML email content style containment" > > Can these changes cause the better behaviour? That will fix the earlier problem James was having, but this issue seems to be something else. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Another HTML email oddity
On Mon, June 22, 2020 3:02 pm, James B. Byrne via squirrelmail-users wrote: > I receive messages from e-bay whose message details contain this: > > From: eBay > Content-Type: multipart/mixed; > boundary="=_Part_17242949_169610758.1592739966714" > > --=_Part_17242949_169610758.1592739966714 > Content-Type: text/html;charset=UTF-8 > Content-Transfer-Encoding: quoted-printable > > But SM does not offer the option to display this as HTML. Instead I see > plain text that looks like this: Works for me (tm). First thing I'd suspect is your older/third-party SM version. We can't support forks or older versions and re-fix things that aren't broken in our code. PS - I didn't look at the content of your email; just saw that it worked and moved on. - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Another HTML email oddity
On Mon, June 22, 2020 3:02 pm, James B. Byrne via squirrelmail-users wrote: > I receive messages from e-bay whose message details contain this: > But SM does not offer the option to display this as HTML. Instead I see > plain > text that looks like this: I've never seen a case where SM doesn't handle such messages. If you want to forward one offlist I can try to have a look. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Need a bit of help getting Squirrelmail running on Centos 8
Jay, > 1. If the Apache Document Root is /www (current location), where should > Squirrelmail be installed to be accessible? It depends what URI you will use. If you want it as the main content for that host, e.g., https://example.com Then it has to be installed in /www or /www can be a symlink to the SquirrelMail source located elsewhere If the URI would be something like this: https://example.com/webmail Then it has to be installed in (or symlinked to) /www/webmail Of course, you can also do something like use the Apache Alias setting instead of symlinks, etc. etc. etc. The options are endless and none of this is unique to SquirrelMail. FWIW, SquirrelMail is often installed in /usr/share/squirrelmail and you can just symlink to it > 2. Instead of /www being document root, should I make it /var/www??? > Should it be something totally different? It depends entirely on the way you design your system architecture. > 3. If I do make /var/www (or the final answer for #2 above) document root, > where (directory) should Squirrelmail reside? See answer (1) and just prefix with /var SquirrelMail nor any other web content does not demand one document root over another. You should design and organize your web collateral in a way that makes sense to you and configure Apache accordingly. > 4. Is access to Squirrelmail, regardless of location, effected by selinux? > To get Squirrelmail working, do most people turn selinux 'off'? Don't turn off SELinux. That's bad advice propagated for years by people who can't take the time to learn how to configure its policies. If you don't place the files in a location that the OS understands as holding web media, you may have to inspect the SELinux labels/attributes on your files to make sure they are correct. You *can* temporarily disable SELinux to eliminate factors in your debugging, but it's just as easy to watch the audit log for AVC violations instead. Fix those and don't keep it disabled. > 5. Have I missed any important details that I need to know here??? Doesn't sound to me like you're watching your log files. They tell you everything you need to know. After that, you're better off asking for help in an Apache forum that probably will have more users with better expertise to help you. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php > Thanks for the answers. > > Jay > >> >> >> On Wed, June 17, 2020 12:32 am, Jay Hart wrote: >>> Good evening, >>> >>> I have not able able to run the http:///ip-addr/src/configtest.php >>> script, >>> nor access Squirrelmail. Looking for suggestions on what I >>> might have missed. >>> >>> I got squirrelmail installed in /usr/share/squirrelmail and >>> 'configured' >>> to work (using ./conf.pl). This setup below is about the same >>> setup on my Centos 6 box. I'm thinking my issue is more Apache >>> configuration related than Squirrelmail. >> >> This looks entirely like an Apache configuration problem. Watch your >> error *and* access logs and play with the URIs until you can find hints >> as >> to where it's going wrong. >> >> -- >> Paul Lesniewski >> SquirrelMail Team >> Please support Open Source Software by donating to SquirrelMail! >> http://squirrelmail.org/donate_paul_lesniewski.php >> >> >> >> >> - >> squirrelmail-users mailing list >> Posting guidelines: http://squirrelmail.org/postingguidelines >> List address: squirrelmail-users@lists.sourceforge.net >> List archives: http://news.gmane.org/gmane.mail.squirrelmail.user >> List info (subscribe/unsubscribe/change options): >> https://lists.sourceforge.net/lists/listinfo/squirrelmail-users >> > > - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Inline css renders squiremail headers illegible
On Wed, June 17, 2020 8:19 pm, James B. Byrne via squirrelmail-users wrote:
> 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;
> }
> table {
> border-collapse:collapse;
> border:0;
> }
> table td,
> table th {
> border-collapse:collapse;
> border:0 !important;
> margin-bottom: 1px !important;
> padding:0 !important;
> vertical-align: top !important;
> }
> a {
> color: #53BEE6;
> text-decoration: none;
> }
>
>
> Which, when the message is viewed in html, renders the Squirrelmail page
> heading links above the message body virtually invisible due to low
> contrast.
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 a copy of functions/mime.php out of our repository:
https://sourceforge.net/p/squirrelmail/code/HEAD/tree/branches/SM-1_4-STABLE/squirrelmail/functions/mime.php
Cheers,
--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php
-
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Need a bit of help getting Squirrelmail running on Centos 8
On Wed, June 17, 2020 12:32 am, Jay Hart wrote: > Good evening, > > I have not able able to run the http:///ip-addr/src/configtest.php script, > nor access Squirrelmail. Looking for suggestions on what I > might have missed. > > I got squirrelmail installed in /usr/share/squirrelmail and 'configured' > to work (using ./conf.pl). This setup below is about the same > setup on my Centos 6 box. I'm thinking my issue is more Apache > configuration related than Squirrelmail. This looks entirely like an Apache configuration problem. Watch your error *and* access logs and play with the URIs until you can find hints as to where it's going wrong. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Inline css renders squiremail headers illegible
On Wed, June 17, 2020 8:19 pm, James B. Byrne via squirrelmail-users wrote:
> 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;
> }
> table {
> border-collapse:collapse;
> border:0;
> }
> table td,
> table th {
> border-collapse:collapse;
> border:0 !important;
> margin-bottom: 1px !important;
> padding:0 !important;
> vertical-align: top !important;
> }
> a {
> color: #53BEE6;
> text-decoration: none;
> }
>
>
> Which, when the message is viewed in html, renders the Squirrelmail page
> heading links above the message body virtually invisible due to low
> contrast.
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.
-
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Inline css renders squiremail headers illegible
On Wed, June 17, 2020 8:19 pm, James B. Byrne via squirrelmail-users wrote:
> 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;
> }
> table {
> border-collapse:collapse;
> border:0;
> }
> table td,
> table th {
> border-collapse:collapse;
> border:0 !important;
> margin-bottom: 1px !important;
> padding:0 !important;
> vertical-align: top !important;
> }
> a {
> color: #53BEE6;
> text-decoration: none;
> }
>
>
> Which, when the message is viewed in html, renders the Squirrelmail page
> heading links above the message body virtually invisible due to low
> contrast.
Can you send an example to help busy/lazy developers take a look?
Thanks,
--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php
-
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Centos 8 and Squirrelmail
Jay, > Are the plugins mostly 'good to go' as well??? Anything to avoid at this > time? Many should work; but there are a lot that have new releases pending that I have not tended to; feel free to reach out if you find one is not working for you. Cheers, -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Centos 8 and Squirrelmail
> should any version of PHP work? Centos 8 may offer 7.2 or 7.3. Does > it matter? Should not matter. If you get PHP errors, please let us know. Cheers, -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Centos 8 and Squirrelmail
Hi Jay, On Thu, June 11, 2020 11:52 pm, Jay Hart wrote: > Good evening, > > LONG time user of Squirrelmail. 10+ years... Finally decided that my > Centos 6 server needs > retirement and am working on a Centos 8 box. I've been looking at webmail > clients but nothing > really appeals to me, keep coming back to Squirrelmail. > > So, my question is, can I use Squirrelmail on Centos 8 and is there > anything special I need to do? Should "just work" as long as you get a copy of 1.4.23-svn from the downloads page. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] preg_replace to be replaced by preg_replace_callback
On Wed, February 19, 2020 1:50 pm, Alfred Charles Stockton wrote:
> Apache2/Squirrelmail 1.4.23 [SVN] is giving me the following error
>
> [Wed Feb 19 15:37:38.632195 2020] [:error] [pid 955] [client
> 62.253.230.14:30063] PHP Warning: preg_replace(): The /e modifier is no
> longer supported, use preg_replace_callback instead in
> /usr/share/squirrelmail/functions/mime.php on line 716, referer:
> http://stockton.co.za/squirrelmail/src/compose.php?PG_SHOWALL=0&sort=0&startMessage=1&mailbox=INBOX&composenew=0&composesession=0&session=1&use_mailbox_cache=0&forward_as_attachment_init=1
>
> Line 716 in /usr/share/squirrelmail/functions/mime.php looks like
>
> $replace = preg_replace('/=([0-9a-f]{2})/ie',
> 'chr(hexdec("\1"))',$replace);
>
> Please tell me what it should look like.
Your copy of 1.4.23svn is somewhat outdated. We're still rebuilding our
website (where snapshots will be available again once it's online), but
you can always get a fresh copy of that file here:
https://sourceforge.net/p/squirrelmail/code/HEAD/tree/branches/SM-1_4-STABLE/squirrelmail/functions/mime.php
--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php
-
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Setting Up Mail Server Operation for CentOS Web Panel Web Hosting Control Panel on Amazon AWS Cloud
On Tue, February 25, 2020 3:37 pm, Turritopsis Dohrnii Teo En Ming wrote: > Subject: Setting Up Mail Server Operation for CentOS Web Panel Web Hosting > Control Panel on Amazon AWS Cloud Thanks, but I fail to see what this has to do with SquirrelMail? You don't even include it in your instructions. - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] fatal error running SM with php74 on FreeBSD-12.1
> Fatal error: Uncaught Error: Call to undefined function > session_set_cookie_params() in That is a PHP built-in function -- you need to determine why it has been removed or disabled in your environment. > We get the sme result with PHP72 and PHP73. SquirrelMail runs under PHP7. This issue points to a local configuration problem. > A similar SM bug is reported as being closed. See > https://sourceforge.net/p/squirrelmail/bugs/2847/ This is entirely unrelated. If you do a web search on the error message, I see a couple hints out there that could be helpful for you. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Reply-to-all no longer working in 1.4.23 and 1.5.2 on php 7
> let's take Anders' email from yesterday as an example -- it was: > > Subject: [SM-USERS] The latest version of Squirrelmail 1.5.2 will only > connect to MySQL-databases if I not change the default table names > From: "Anders Boholdt-Petersen" > > Date: Sat, August 10, 2019 23:50 > To: squirrelmail-users@lists.sourceforge.net > Priority: Normal You missed the reply-to header. Mailing lists like this one are configured so that replies are sent to the list on purpose. Reply-To tells the mail client to reply to the indicated address and to ignore the >From address. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php > So, a "reply to all" would be expected to write: > > To: "Anders Boholdt-Petersen" > > Cc: squirrelmail-users@lists.sourceforge.net > > But instead, it's addressed > > To: "Squirrelmail User Support Mailing List" > > > only. > > ## > > The complete header is (don't know which part needed, so copying all): > > Return-Path: > > Received: from mx1.mail.vrmd.de ([10.0.1.21]) > by h-0055.host.vrmd.de (Cyrus 2.5.11) with LMTPA; > Sat, 10 Aug 2019 23:52:18 +0200 > X-Sieve: CMU Sieve 2.4 > Envelope-to: jul-dez.2...@dipl-ing-kessler.de > Delivery-date: Sat, 10 Aug 2019 23:52:21 +0200 > Authentication-Results: mx1.mail.vrmd.de; dkim=fail (signature did not > verify) header.d=boholdt-petersen.dk; iprev=pass policy.iprev=216.105.38.7 > (lists.sourceforge.net); spf=pass (mx1.mail.vrmd.de: domain of > lists.sourceforge.net designates 216.105.38.7 as permitted sender) > smtp.mailfrom=squirrelmail-users-boun...@lists.sourceforge.net > Received-SPF: pass (mx1.mail.vrmd.de: domain of lists.sourceforge.net > designates 216.105.38.7 as permitted sender) client-ip=216.105.38.7; > envelope-from=squirrelmail-users-boun...@lists.sourceforge.net; > helo=lists.sourceforge.net; > Received: from lists.sourceforge.net ([216.105.38.7]) > by mx1.mail.vrmd.de with esmtps > (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) > (Exim 4.90_1) > (envelope-from ) > id 1hwZHg-000593-Ox > for jul-dez.2...@dipl-ing-kessler.de; Sat, 10 Aug 2019 23:52:21 +0200 > Received: from [127.0.0.1] (helo=sfs-ml-2.v29.lw.sourceforge.com) > by sfs-ml-2.v29.lw.sourceforge.com with esmtp (Exim 4.90_1) > (envelope-from ) > id 1hwZG2-0002bn-Fq; Sat, 10 Aug 2019 21:50:38 + > Received: from [172.30.20.202] (helo=mx.sourceforge.net) > by sfs-ml-2.v29.lw.sourceforge.com with esmtps > (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) > (envelope-from ) > id 1hwZFz-0002bb-FI > for squirrelmail-users@lists.sourceforge.net; Sat, 10 Aug 2019 > 21:50:35 + > DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; > d=sourceforge.net; s=x; > h=Content-Type:MIME-Version:Message-ID:Date:Subject: > To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: > > Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc > > :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: > List-Subscribe:List-Post:List-Owner:List-Archive; > bh=6W6W67RjOffmt+2AeT2mFa/WqKehk7fKf4FTDs2SzTc=; > b=kbwCToHt8Jxj29Ft5rkkeWa73A > > jVonCR/tWx8gzTxjNo38AUwUMdy+htWYVxZ1mL2kULZBUrhbORwG/oUph4u07zQEuCUwG5uwIWRL2 > MXAHZ9sKcZknfPwfdPJ7bfvMmaULhGMyb1r0jEsTcgjyJEz9hEJIIaVsmzc5kUEG4EiM=; > DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; > s=x > ; > > h=Content-Type:MIME-Version:Message-ID:Date:Subject:To:From:Sender:Reply-To > :Cc:Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: > > Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: > References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: > List-Owner:List-Archive; > bh=6W6W67RjOffmt+2AeT2mFa/WqKehk7fKf4FTDs2SzTc=; b=B > > tYHzDwZTazzJWQhgjPSVhW8Eyb1Bw2H3+i7vASkQ2Y5LE5/ZTbY+QYf3ZN6hLb1iupYcXDkeoC02p > > ut9sCVQrpiepn06/cCVh9TMOdjxTl2A5LAk6RoIkV1hZRxRfhB5mAVkGtpVSIb8lHqJs0N56hGDR/ > COIdpirysGxi3pEc=; > Received: from asmtp.unoeuro.com ([94.231.106.220]) > by sfi-mx-1.v28.lw.sourceforge.com with esmtps > (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) > id 1hwZFv-0014WZ-5E > for squirrelmail-users@lists.sourceforge.net; Sat, 10 Aug 2019 > 21:50:35 + > Received: from MiniNUCPC (87-49-146-177
Re: [SM-USERS] The latest version of Squirrelmail 1.5.2 will only connect to MySQL-databases if I not change the default table names
On Sun, August 11, 2019 10:12 am, Anders Boholdt-Petersen wrote: > Hi Paul > > ---Paul Lesniewski wrote on August 11, 2019 00:25--- >> SquirrelMail does not create database tables for you. You are >> responsible for doing that and the configuration lets you adapt the >> table and column names as necessary to your environment. > > 1. Is it a new option, that Squirrelmail not create the tables in > MySQL-databases (back in March 2018, I not means that I should create the > tables for Squirrelmail myself)? It's not an option -- SquirrelMail has never done that for you. > 2. Is it possible that configtest.php can be modified, so you see an error > if Squirrelmail not can find the tables in MySQL-databases? That's a morass that I don't think we'll wade into. There's plenty of different database engines out there and lots of ways to create tables. If you need just the basics, there is in fact a CREATE TABLE example at the top of functions/db_prefs.php in the source code. > It is a little confused that configtest.php first write that I fine > connect to MySQL-databases, but after that Squirrelmail not can find the > tables when I try to login. Connecting is not the same as accessing tables. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Reply-to-all no longer working in 1.4.23 and 1.5.2 on php 7
On 2019/08/10 6:43, jul-dez.2...@dipl-ing-kessler.de wrote: > Hi, > > I tested this on different systems (Ubuntu and Raspbian) each with PHP 7: > > Replying to an incoming email which was sent to more than one recipient > only puts sender's "from" info into "to" field, but no other recipients. > This happens regardless if clicking on "reply" or "reply all". > > So, you have to manually copy all other addresses into "to" / "cc" / "bcc" > if you want to reply to all. > > Is this the case on other installations, also? No, sounds like something particular to your environment or the message you are replying to. It might help if you provide sample (redacted) headers of the message you are replying to. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] The latest version of Squirrelmail 1.5.2 will only connect to MySQL-databases if I not change the default table names
On 2019/08/10 14:50, Anders Boholdt-Petersen wrote: > Hi everyone > > > > Today I have installed the latest developer version of Squirrelmail 1.5.2 > [SVN) from the Squirrelmail website. > > > > In connection with some tests, I installed Squirrelmail on two different > subdomains on my webhost remotely via FTP. One where Squirrelmail store > information about users etc. in folders on the webhost itself, and another > where Squirrelmail store the same information on an MySQL-database. The > first setup working fine. > > > > When I try to setup the database-information in Squirrelmail (via the > config.pl-file), I also try to change the default name on the database > table. For example I will install user preferences in a table with the name > newuserprefs instead of the default name, userprefs. > > > > Whatever I try, Squirrelmail will not create the tables. SquirrelMail does not create database tables for you. You are responsible for doing that and the configuration lets you adapt the table and column names as necessary to your environment. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Raspberry Pi and squirrelmail
On 2019/08/10 4:39, Alfred Charles Stockton wrote: > Within the last week Raspberry and apt decided to upgrade Squirrelmail on > my Raspbian server. > Where previous to this upgrade Squirrelmail worked fine now I find certain > emails appear as a blank line in the Squirrelmail index and others will > not display at all. This is not all the emails I receive just some. Please > tell me what I need to do to fix this. Could likely be that you need the patch given here: https://sourceforge.net/p/squirrelmail/bugs/2806/#f2f7/2c33 -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] PHP 7 support
On 2019/07/12 2:27, mar...@kottnet.net wrote: > Hello! From the section 1.1 Server Requirements [1] in the > documentation, it appears Squirrelmail does not support PHP 7, and when > I try to run Squirrelmail on PHP 7, I can barely sign in before various > kinds of errors appear. What's the status on support for PHP 7? As you found, version 1.4.23-svn is compatible with PHP 7. I've updated the docs. - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] configuring SquirrelMail Dovecot and wforced to display end user IP; auth_policy_server_url
Please try to use plain text formatted messages when sending to mailing
lists.
On 2019/04/12 7:16, Robert Kudyba wrote:
> > Thanks Paul! I tried the new code. Squirrelamil is definitely slower
> > with these options added.
>
> If you have metrics or profiling traces that quantify this, I'd love to
> see that. The added code does (should) not add all that much - it's
> just a single extra and very simple IMAP ID command. Did you use the
> configuration variable that disables response parsing?
>
>
> I have these logs, notice it takes over a minute to destroy the
> connection but perhaps that's normal?
No, that really doesn't tell much. Web server logs are better, but the
best is timing profile of the PHP requests. I still don't see any
impact of adding the ID command, inbox views for example are still
split-second fast, before and after. I seriously doubt this has caused
any problems unless you've configured Dovecot unusually.
> >>>Did you use the configuration variable that disables response parsing?
> Yes in /etc/squirrelmail/config_local.php I added:
> $imap_id_command_args = array('remote-host' => '###REMOTE ADDRESS###');
> $do_not_parse_imap_id_command_response = TRUE;
>
> > And still no source IP of end user but perhaps
> > there logs may shed a light? Or what should
> auth_policy_server_url be?
>
> The rest of your question is about Dovecot, it is not relevant to this
> list. I suggest first sniffing the IMAP connection to make sure the ID
> command with the IP address is being sent and acknowledged by Dovecot,
> then synchronizing your configuration and debugging that.
>
>
> Any tips on how to do that? Sniffing as in Wireshark?
Yes, or ngrep, etc
--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php
-
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail -- timestamp bug
> 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 from there. - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] [SM-DEVEL] Squirrelmail -- timestamp bug
On 2019/04/13 3:47, jan-jun.2...@dipl-ing-kessler.de wrote: > Hi all, > > it seems that I have found a little bug. > > Therefore I've done a recording, 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 shown is not plain text, but UNIX time > instead. > > Same when sending emails. This has been fixed and will show up in our next nightly snapshots, or get patches here: 1.4.23: https://sourceforge.net/p/squirrelmail/code/14819/ 1.5.2: https://sourceforge.net/p/squirrelmail/code/14818/ Thanks for letting us know. - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
