squirrelmail-users — SquirrelMail Users Mailing List

Re: [SM-USERS] Drop down menu and add button missing in Indexing Options

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

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

[SM-USERS] Drop down menu and add button missing in Indexing Options

[V. N. <nan...@ma...>]

Dear All,

  	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?

  	Many thanks in advance,
 	Nandagopal

===============================================================================
V. Nandagopal 				       Email: nan...@ma...
School of Mathematics			       Telephone: 22782672
Tata Institute of Fundamental Research	       Fax: 22804610/11
Homi Bhabha Road, Colaba, Bombay 400 005, India
================================================================================

[SM-USERS] bug report of "tnef_decoder" plugin

[anctop <an...@gm...>]

Hi,

It is found that the plugin package "tnef_decoder-1.0-1.4.0" contains
incompatibility with PHP 8.

On running "php -l functions.php", it returns

"PHP Fatal error: Array and string offset access syntax with curly
braces is no longer supported in functions.php on line 236".

This prevents the display of attachments list near the screen bottom
in SquirrelMail.

Regards,
anctop

Re: [SM-USERS] [SOLVED] User has one folder which is not sortable

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

On Fri, September 1, 2023 11:32, James B. Byrne via squirrelmail-users wrote:
> FreebSD-12.4
> SquirrelMail version 1.4.23 [SVN]
>
> We have one user that has one folder that does not display the sort select box
> for the columns displayed in the messages list.  Other folders for this user do
> not have this problem.  They have no recollection of having modified anything.
>
> Is this caused by a setting change somewhere?  If so, then where?
>
> Thanks,


The user had accidentally selected 'Threaded View' for that folder.


-- 
***          e-Mail is NOT a SECURE channel          ***
        Do NOT transmit sensitive data via e-Mail
   Unencrypted messages have no legal claim to privacy
 Do NOT open attachments nor follow links sent by e-Mail

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

[SM-USERS] User has one folder which is not sortable

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

FreebSD-12.4
SquirrelMail version 1.4.23 [SVN]

We have one user that has one folder that does not display the sort select box
for the columns displayed in the messages list.  Other folders for this user do
not have this problem.  They have no recollection of having modified anything.

Is this caused by a setting change somewhere?  If so, then where?

Thanks,


-- 
***          e-Mail is NOT a SECURE channel          ***
        Do NOT transmit sensitive data via e-Mail
   Unencrypted messages have no legal claim to privacy
 Do NOT open attachments nor follow links sent by e-Mail

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

Re: [SM-USERS] Deprecated: Creation of dynamic property Message::$header is deprecated

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

Hi Paul,

> Hi Paul, thanks so much for addressing this issue. I disabled PHP display
> > errors/warnings
>
> Yes, on production sites, you should never have error or notice display
> enabled. However, you should be *logging* all those things so you can be
> aware of any problems.
>

Yes, didn't realize it. I thought they were actual errors being reported.

> but if you're still actively able to fix issues that I
> > report, I will continue to test and reply with more info.
>
> We are always interested in any issues our users can identify!
>

Are you currently testing the latest snapshot against php-8.2, including
all the most common plugins?

Thanks,
Alex




>
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php
>
>
> >> > Any idea if this error/warning is fixed in the latest version?
> >>
> >> Deprecation notices are *not* errors.
> >>
> >> > *Deprecated*: Creation of dynamic property Message::$header is
> >> deprecated
> >> > in */usr/share/squirrelmail/class/mime/Message.class.php* on line
> >> *366*
> >>
> >> This should have been fixed as of a few minutes ago. Thanks for the
> >> report!
> >>
>
>
>
>
> -----
> squirrelmail-users mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squ...@li...
> 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] Deprecated: Creation of dynamic property Message::$header is deprecated

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

> Hi Paul, thanks so much for addressing this issue. I disabled PHP display
> errors/warnings

Yes, on production sites, you should never have error or notice display
enabled. However, you should be *logging* all those things so you can be
aware of any problems.

> but if you're still actively able to fix issues that I
> report, I will continue to test and reply with more info.

We are always interested in any issues our users can identify!

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


>> > Any idea if this error/warning is fixed in the latest version?
>>
>> Deprecation notices are *not* errors.
>>
>> > *Deprecated*: Creation of dynamic property Message::$header is
>> deprecated
>> > in */usr/share/squirrelmail/class/mime/Message.class.php* on line
>> *366*
>>
>> This should have been fixed as of a few minutes ago. Thanks for the
>> report!
>>

Re: [SM-USERS] Deprecated: Creation of dynamic property Message::$header is deprecated

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

Hi Paul, thanks so much for addressing this issue. I disabled PHP display
errors/warnings, but if you're still actively able to fix issues that I
report, I will continue to test and reply with more info.

Thanks so much,
Alex


On Tue, Aug 22, 2023 at 3:24 AM Paul Lesniewski <pa...@sq...>
wrote:

> > Any idea if this error/warning is fixed in the latest version?
>
> Deprecation notices are *not* errors.
>
> > *Deprecated*: Creation of dynamic property Message::$header is deprecated
> > in */usr/share/squirrelmail/class/mime/Message.class.php* on line *366*
>
> This should have been fixed as of a few minutes ago. Thanks for the report!
>
> --
> 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: squ...@li...
> 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] Deprecated: Creation of dynamic property Message::$header is deprecated

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

> Any idea if this error/warning is fixed in the latest version?

Deprecation notices are *not* errors.

> *Deprecated*: Creation of dynamic property Message::$header is deprecated
> in */usr/share/squirrelmail/class/mime/Message.class.php* on line *366*

This should have been fixed as of a few minutes ago. Thanks for the report!

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

[SM-USERS] Deprecated: Creation of dynamic property Message::$header is deprecated

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

Hi,
Any idea if this error/warning is fixed in the latest version?

*Deprecated*: Creation of dynamic property Message::$header is deprecated
in */usr/share/squirrelmail/class/mime/Message.class.php* on line *366*

I believe I'm using a version from Feb, 2023. This happens when opening or
reading a message. I'm using php-8.2.9.

   360                              if (!isset($msg)) {
   361                                  $msg = new Message();
   362                                  $hdr = new MessageHeader();
   363                                  $hdr->type0 = 'text';
   364                                  $hdr->type1 = 'plain';
   365                                  $hdr->encoding = '7bit';
   366                                  $msg->header = $hdr;
   367                              } else {
   368                                  $msg->header->type0 = 'multipart';
   369                                  $msg->type0 = 'multipart';
   370                                  while ($read[$i] == '(') {
   371
 $msg->addEntity($msg->parseBodyStructure($read, $i, $msg));
   372                                  }
   373                              }

Re: [SM-USERS] reporting bug of SquirrelMail 1.4.23-svn

[anctop <an...@gm...>]

On 01/08/2023, Paul Lesniewski <pa...@sq...> wrote:
>>>>>>>>> On Thu, July 27, 2023 9:57 pm, Paul Lesniewski wrote:
>>>>>>>>>>> I am writing to report an issue with SquirrelMail 1.4.23-svn.
>>>>>>>>>>> We have a Linux server with the following environment :
>>>>>>>>>>> 1. Apache/2.4.39 with OpenSSL/1.1.1l
>>>>>>>>>>> 2. PHP 7.3.4
>>>>>>>>>>> 3. squirrelmail-20190221_0201-SVN.locales.tar.bz2
>>>>>>>>>>> 4. Six SquirrelMail plugins
>>>>>>>>>>>     compatibility-2.0.16-1.0
>>>>>>>>>>>     html_mail-2.3-1.4
>>>>>>>>>>>     tnef_decoder-1.0-1.4.0
>>>>>>>>>>>     undelete-2.0-1.4.0
>>>>>>>>>>>     view_as_html-3.8
>>>>>>>>>>>     vlogin-3.10.2-1.2.7
>>>>>>>>>>> 5. access two IMAP servers
>>>>>>>>>>>     one runs "Panda IMAP 2010.417" (built from Alpine-2.26
>>>>>>>>>>> package)
>>>>>>>>>>>     one runs "Microsoft Exchange IMAP4"
>>>>>>>>>>> This copy of SquirrelMail works perfectly.
>>>>>>>>>>> Recently, we upgraded SquirrelMail to
>>>>>>>>>>> "squirrelmail-20230725_0200-SVN.stable.tar.bz2".
>>>>>>>>>>> Exactly the same configurations are applied to the new tree.
>>>>>>>>>>> The "<path to squirrelmail>/src/configtest.php" reports no
>>>>>>>>>>> error.
>>>>>>>>>>> Users login are successful but the right frame shows the
>>>>>>>>>>> following
>>>>>>>>>>> error
>>>>>>>>>>> :
>>>>>>>>>>> # Connect to Panda IMAP
>>>>>>>>>>>> ERROR: Bad or malformed request.
>>>>>>>>>>>> Query: FETCH 1,32 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>>>>>>>>> BODY.PEEK[HEADER.FIELDS
>>>>>>>>>>>> (Date To Cc From Subject X-Priority Importance Priority
>>>>>>>>>>>> Content-Type
>>>>>>>>>>>> )])
>>>>>>>>>>>> Server responded: Syntax error in header fields
>>>>>>>>>>> # Connect to Microsoft Exchange
>>>>>>>>>>>> ERROR: Bad or malformed request.
>>>>>>>>>>>> Query: FETCH
>>>>>>>>>>>> 23448:23449,23537,24173,24213,24402,24433,24452,24468,24505,24637,24673:24676
>>>>>>>>>>>> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS
>>>>>>>>>>>> (Date
>>>>>>>>>>>> To
>>>>>>>>>>>> Cc
>>>>>>>>>>>> From
>>>>>>>>>>>> Subject X-Priority Importance Priority Content-Type )])
>>>>>>>>>>>> Server responded: Command Argument Error. 11
>>>>>>>>>> I just enabled the "info" plugin, went to Options --> IMAP server
>>>>>>>>>> information, enabled the first three example commands, and
>>>>>>>>>> entered
>>>>>>>>>> a
>>>>>>>>>> cut-and-paste of the command from your report, adjusting the
>>>>>>>>>> requested
>>>>>>>>>> IDs
>>>>>>>>>> for my inbox count... as an example:
>>>>>>>>>> FETCH 1710:1712,1716 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>>>>>>> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority
>>>>>>>>>> Importance
>>>>>>>>>> Priority Content-Type )])
>>>>>>>>>> The server didn't have any problems with this command. Can you
>>>>>>>>>> please
>>>>>>>>>> use
>>>>>>>>>> the "info" plugin to further diagnose? Can you sniff the IMAP
>>>>>>>>>> traffic
>>>>>>>>>> for
>>>>>>>>>> an older instance that is working as well as the new installation
>>>>>>>>>> and
>>>>>>>>>> compare how the commands look different?
>>>>>>>>> You can also open up functions/imap_messages.php and find both
>>>>>>>>> instances
>>>>>>>>> of $extra_small_header_fields in the FETCH commands (approximately
>>>>>>>>> lines
>>>>>>>>> 750 and 752) and remove it and the space before it. There is a
>>>>>>>>> chance
>>>>>>>>> that
>>>>>>>>> your IMAP servers are being fussy about one extra space. If you
>>>>>>>>> can
>>>>>>>>> confirm that is the issue, I can issue a fix.
>>>>>>>>
>>>>>>>> Yes, removing $extra_small_header_fields for FETCH in
>>>>>>>> "functions/imap_messages.php" solves the problem immediately if no
>>>>>>>> plugin is used.
>>>>>>>>
>>>>>>>> When I put back the plugin "vlogin", users cannot login (in both
>>>>>>>> implementations).
>>>>>>>>
>>>>>>>> What other workaround is required ?
>>>>>>>
>>>>>>> Please first apply this patch and try it again "the right way" (you
>>>>>>> can
>>>>>>> also wait to grab the next nightly build tarball)
>>>>>>>
>>>>>>> https://sourceforge.net/p/squirrelmail/code/14991/
>>>>>>>
>>>>>>> Otherwise, the vlogin problem sounds unrelated and would need logs
>>>>>>> and
>>>>>>> further diagnosis.
>>>>>>
>>>>>> The patch does not help.
>>>>>
>>>> About your "official" patch, I am sorry to inform you that it really
>>>> does not work.
>>>> For the patch to work, the string "$extra_small_header_fields" must be
>>>> removed from the two FETCH lines, as you have said at the beginning.
>>>
>>> Did you apply the patch as given from the original unmodified file or do
>>> it by hand? There should not be any extra spaces in the resulting FETCH
>>> command. Can you please output the contents of
>>> $extra_small_header_fields
>>> just above where it is being used to ensure it is empty? You can do that
>>> with something such as:
>>> echo "<hr>extra_small_header_fields:<br>";
>>> var_dump($extra_small_header_fields); echo "<hr>";
>>
>> The patch was applied to the original "functions/imap_messages.php" file.
>>
>> Your codes are inserted just above the "if ($internaldate) {" block.
>> The output is :
>> | ----------------------------------------
>> | extra_small_header_fields:
>> | string(1) " "
>> | ----------------------------------------
>> | ERROR:
>> | ERROR: Bad or malformed request.
>> | Query: FETCH
>> 2375,2381,2385,2421,2448,2451,2454,2457,2463,2467,2469,2508,2510,2534,2547
>> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To
>> Cc From Subject X-Priority Importance Priority Content-Type )])
>> | Server responded: Syntax error in header fields
>
> Are you using a newer version of the Message Flags plugin? I'm not sure
> anyone should be populating $extra_small_header_fields
>
> In any case, I added one more safety against what you have shown here:
>
> https://sourceforge.net/p/squirrelmail/code/14992/
>
> Do you mind testing to ensure this closes the issue?
>
> Thanks for your help,
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php


Dear Paul,

As I have mentioned in my original post, our system is using six
plugins which do not include "Message Flags".
I have also checked the plugins directory and found that no file
mentions "$extra_small_header_fields".

The second patch eventually fixes the problem, even with all the
plugins in place.
Many thanks for your efforts.

I shall wait for the next snapshot for a clean installation.

Regards,
anctop


> -----
> squirrelmail-users mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squ...@li...
> 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] reporting bug of SquirrelMail 1.4.23-svn

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

>>>>>>>> On Thu, July 27, 2023 9:57 pm, Paul Lesniewski wrote:
>>>>>>>>>> I am writing to report an issue with SquirrelMail 1.4.23-svn.
>>>>>>>>>> We have a Linux server with the following environment :
>>>>>>>>>> 1. Apache/2.4.39 with OpenSSL/1.1.1l
>>>>>>>>>> 2. PHP 7.3.4
>>>>>>>>>> 3. squirrelmail-20190221_0201-SVN.locales.tar.bz2
>>>>>>>>>> 4. Six SquirrelMail plugins
>>>>>>>>>>     compatibility-2.0.16-1.0
>>>>>>>>>>     html_mail-2.3-1.4
>>>>>>>>>>     tnef_decoder-1.0-1.4.0
>>>>>>>>>>     undelete-2.0-1.4.0
>>>>>>>>>>     view_as_html-3.8
>>>>>>>>>>     vlogin-3.10.2-1.2.7
>>>>>>>>>> 5. access two IMAP servers
>>>>>>>>>>     one runs "Panda IMAP 2010.417" (built from Alpine-2.26
>>>>>>>>>> package)
>>>>>>>>>>     one runs "Microsoft Exchange IMAP4"
>>>>>>>>>> This copy of SquirrelMail works perfectly.
>>>>>>>>>> Recently, we upgraded SquirrelMail to
>>>>>>>>>> "squirrelmail-20230725_0200-SVN.stable.tar.bz2".
>>>>>>>>>> Exactly the same configurations are applied to the new tree.
>>>>>>>>>> The "<path to squirrelmail>/src/configtest.php" reports no
>>>>>>>>>> error.
>>>>>>>>>> Users login are successful but the right frame shows the
>>>>>>>>>> following
>>>>>>>>>> error
>>>>>>>>>> :
>>>>>>>>>> # Connect to Panda IMAP
>>>>>>>>>>> ERROR: Bad or malformed request.
>>>>>>>>>>> Query: FETCH 1,32 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>>>>>>>> BODY.PEEK[HEADER.FIELDS
>>>>>>>>>>> (Date To Cc From Subject X-Priority Importance Priority
>>>>>>>>>>> Content-Type
>>>>>>>>>>> )])
>>>>>>>>>>> Server responded: Syntax error in header fields
>>>>>>>>>> # Connect to Microsoft Exchange
>>>>>>>>>>> ERROR: Bad or malformed request.
>>>>>>>>>>> Query: FETCH
>>>>>>>>>>> 23448:23449,23537,24173,24213,24402,24433,24452,24468,24505,24637,24673:24676
>>>>>>>>>>> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS
>>>>>>>>>>> (Date
>>>>>>>>>>> To
>>>>>>>>>>> Cc
>>>>>>>>>>> From
>>>>>>>>>>> Subject X-Priority Importance Priority Content-Type )])
>>>>>>>>>>> Server responded: Command Argument Error. 11
>>>>>>>>> I just enabled the "info" plugin, went to Options --> IMAP server
>>>>>>>>> information, enabled the first three example commands, and
>>>>>>>>> entered
>>>>>>>>> a
>>>>>>>>> cut-and-paste of the command from your report, adjusting the
>>>>>>>>> requested
>>>>>>>>> IDs
>>>>>>>>> for my inbox count... as an example:
>>>>>>>>> FETCH 1710:1712,1716 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>>>>>> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority
>>>>>>>>> Importance
>>>>>>>>> Priority Content-Type )])
>>>>>>>>> The server didn't have any problems with this command. Can you
>>>>>>>>> please
>>>>>>>>> use
>>>>>>>>> the "info" plugin to further diagnose? Can you sniff the IMAP
>>>>>>>>> traffic
>>>>>>>>> for
>>>>>>>>> an older instance that is working as well as the new installation
>>>>>>>>> and
>>>>>>>>> compare how the commands look different?
>>>>>>>> You can also open up functions/imap_messages.php and find both
>>>>>>>> instances
>>>>>>>> of $extra_small_header_fields in the FETCH commands (approximately
>>>>>>>> lines
>>>>>>>> 750 and 752) and remove it and the space before it. There is a
>>>>>>>> chance
>>>>>>>> that
>>>>>>>> your IMAP servers are being fussy about one extra space. If you
>>>>>>>> can
>>>>>>>> confirm that is the issue, I can issue a fix.
>>>>>>>
>>>>>>> Yes, removing $extra_small_header_fields for FETCH in
>>>>>>> "functions/imap_messages.php" solves the problem immediately if no
>>>>>>> plugin is used.
>>>>>>>
>>>>>>> When I put back the plugin "vlogin", users cannot login (in both
>>>>>>> implementations).
>>>>>>>
>>>>>>> What other workaround is required ?
>>>>>>
>>>>>> Please first apply this patch and try it again "the right way" (you
>>>>>> can
>>>>>> also wait to grab the next nightly build tarball)
>>>>>>
>>>>>> https://sourceforge.net/p/squirrelmail/code/14991/
>>>>>>
>>>>>> Otherwise, the vlogin problem sounds unrelated and would need logs
>>>>>> and
>>>>>> further diagnosis.
>>>>>
>>>>> The patch does not help.
>>>>
>>> About your "official" patch, I am sorry to inform you that it really
>>> does not work.
>>> For the patch to work, the string "$extra_small_header_fields" must be
>>> removed from the two FETCH lines, as you have said at the beginning.
>>
>> Did you apply the patch as given from the original unmodified file or do
>> it by hand? There should not be any extra spaces in the resulting FETCH
>> command. Can you please output the contents of
>> $extra_small_header_fields
>> just above where it is being used to ensure it is empty? You can do that
>> with something such as:
>> echo "<hr>extra_small_header_fields:<br>";
>> var_dump($extra_small_header_fields); echo "<hr>";
>
> The patch was applied to the original "functions/imap_messages.php" file.
>
> Your codes are inserted just above the "if ($internaldate) {" block.
> The output is :
> | ----------------------------------------
> | extra_small_header_fields:
> | string(1) " "
> | ----------------------------------------
> | ERROR:
> | ERROR: Bad or malformed request.
> | Query: FETCH
> 2375,2381,2385,2421,2448,2451,2454,2457,2463,2467,2469,2508,2510,2534,2547
> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To
> Cc From Subject X-Priority Importance Priority Content-Type )])
> | Server responded: Syntax error in header fields

Are you using a newer version of the Message Flags plugin? I'm not sure
anyone should be populating $extra_small_header_fields

In any case, I added one more safety against what you have shown here:

https://sourceforge.net/p/squirrelmail/code/14992/

Do you mind testing to ensure this closes the issue?

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

Re: [SM-USERS] reporting bug of SquirrelMail 1.4.23-svn

[anctop <an...@gm...>]

On 30/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>
>
> On Sun, July 30, 2023 5:19 am, anctop wrote:
>> On 30/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>>>
>>> On Sat, July 29, 2023 5:41 am, anctop wrote:
>>>> On 29/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>>>>> Please bottom-post to keep context...
>>>>>
>>>>>> On 28/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>>>>>>>
>>>>>>> On Thu, July 27, 2023 9:57 pm, Paul Lesniewski wrote:
>>>>>>>>> I am writing to report an issue with SquirrelMail 1.4.23-svn.
>>>>>>>>> We have a Linux server with the following environment :
>>>>>>>>> 1. Apache/2.4.39 with OpenSSL/1.1.1l
>>>>>>>>> 2. PHP 7.3.4
>>>>>>>>> 3. squirrelmail-20190221_0201-SVN.locales.tar.bz2
>>>>>>>>> 4. Six SquirrelMail plugins
>>>>>>>>>     compatibility-2.0.16-1.0
>>>>>>>>>     html_mail-2.3-1.4
>>>>>>>>>     tnef_decoder-1.0-1.4.0
>>>>>>>>>     undelete-2.0-1.4.0
>>>>>>>>>     view_as_html-3.8
>>>>>>>>>     vlogin-3.10.2-1.2.7
>>>>>>>>> 5. access two IMAP servers
>>>>>>>>>     one runs "Panda IMAP 2010.417" (built from Alpine-2.26
>>>>>>>>> package)
>>>>>>>>>     one runs "Microsoft Exchange IMAP4"
>>>>>>>>> This copy of SquirrelMail works perfectly.
>>>>>>>>> Recently, we upgraded SquirrelMail to
>>>>>>>>> "squirrelmail-20230725_0200-SVN.stable.tar.bz2".
>>>>>>>>> Exactly the same configurations are applied to the new tree.
>>>>>>>>> The "<path to squirrelmail>/src/configtest.php" reports no error.
>>>>>>>>> Users login are successful but the right frame shows the following
>>>>>>>>> error
>>>>>>>>> :
>>>>>>>>> # Connect to Panda IMAP
>>>>>>>>>> ERROR: Bad or malformed request.
>>>>>>>>>> Query: FETCH 1,32 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>>>>>>> BODY.PEEK[HEADER.FIELDS
>>>>>>>>>> (Date To Cc From Subject X-Priority Importance Priority
>>>>>>>>>> Content-Type
>>>>>>>>>> )])
>>>>>>>>>> Server responded: Syntax error in header fields
>>>>>>>>> # Connect to Microsoft Exchange
>>>>>>>>>> ERROR: Bad or malformed request.
>>>>>>>>>> Query: FETCH
>>>>>>>>>> 23448:23449,23537,24173,24213,24402,24433,24452,24468,24505,24637,24673:24676
>>>>>>>>>> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date
>>>>>>>>>> To
>>>>>>>>>> Cc
>>>>>>>>>> From
>>>>>>>>>> Subject X-Priority Importance Priority Content-Type )])
>>>>>>>>>> Server responded: Command Argument Error. 11
>>>>>>>> I just enabled the "info" plugin, went to Options --> IMAP server
>>>>>>>> information, enabled the first three example commands, and entered
>>>>>>>> a
>>>>>>>> cut-and-paste of the command from your report, adjusting the
>>>>>>>> requested
>>>>>>>> IDs
>>>>>>>> for my inbox count... as an example:
>>>>>>>> FETCH 1710:1712,1716 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>>>>> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority
>>>>>>>> Importance
>>>>>>>> Priority Content-Type )])
>>>>>>>> The server didn't have any problems with this command. Can you
>>>>>>>> please
>>>>>>>> use
>>>>>>>> the "info" plugin to further diagnose? Can you sniff the IMAP
>>>>>>>> traffic
>>>>>>>> for
>>>>>>>> an older instance that is working as well as the new installation
>>>>>>>> and
>>>>>>>> compare how the commands look different?
>>>>>>> You can also open up functions/imap_messages.php and find both
>>>>>>> instances
>>>>>>> of $extra_small_header_fields in the FETCH commands (approximately
>>>>>>> lines
>>>>>>> 750 and 752) and remove it and the space before it. There is a
>>>>>>> chance
>>>>>>> that
>>>>>>> your IMAP servers are being fussy about one extra space. If you can
>>>>>>> confirm that is the issue, I can issue a fix.
>>>>>>
>>>>>> Yes, removing $extra_small_header_fields for FETCH in
>>>>>> "functions/imap_messages.php" solves the problem immediately if no
>>>>>> plugin is used.
>>>>>>
>>>>>> When I put back the plugin "vlogin", users cannot login (in both
>>>>>> implementations).
>>>>>>
>>>>>> What other workaround is required ?
>>>>>
>>>>> Please first apply this patch and try it again "the right way" (you
>>>>> can
>>>>> also wait to grab the next nightly build tarball)
>>>>>
>>>>> https://sourceforge.net/p/squirrelmail/code/14991/
>>>>>
>>>>> Otherwise, the vlogin problem sounds unrelated and would need logs and
>>>>> further diagnosis.
>>>>
>>>> The patch does not help.
>>>
>>> More specifically, it does help with your IMAP problem but not the
>>> vlogin
>>> one, right?
>>>
>>>> In fact, if "vlogin" is used, then user authentication fails with or
>>>> without the patch :
>>>>> ERROR
>>>>> Unknown user or password incorrect.
>>>>> Go to the login page
>>>>
>>>> It seems that the "vlogin" plugin is not compatible with the new
>>>> snapshot.
>>>> Should I submit the file "plugins/vlogin/data/config.php" for diagnosis
>>>> ?
>>>
>>> Turn on $vlogin_debug and start gathering information about what the
>>> actual error is and what the plugin is doing to usernames versus what
>>> the
>>> IMAP server expects to get. You can also start with a default
>>> configuration file and change one thing at a time.
>>
>> Firstly I must apologize for making a false report about "vlogin".
>> By turning on $vlogin_debug, I find that the login failure was due to
>> setting a wrong value to $sendmailVirtualUserTable.
>> This problem is now fixed.
>>
>> About your "official" patch, I am sorry to inform you that it really
>> does not work.
>> For the patch to work, the string "$extra_small_header_fields" must be
>> removed from the two FETCH lines, as you have said at the beginning.
>
> Did you apply the patch as given from the original unmodified file or do
> it by hand? There should not be any extra spaces in the resulting FETCH
> command. Can you please output the contents of $extra_small_header_fields
> just above where it is being used to ensure it is empty? You can do that
> with something such as:
> echo "<hr>extra_small_header_fields:<br>";
> var_dump($extra_small_header_fields); echo "<hr>";
>
> Thanks for your help.
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php


Dear Paul,

The patch was applied to the original "functions/imap_messages.php" file.

Your codes are inserted just above the "if ($internaldate) {" block.
The output is :
| ----------------------------------------
| extra_small_header_fields:
| string(1) " "
| ----------------------------------------
| ERROR:
| ERROR: Bad or malformed request.
| Query: FETCH 2375,2381,2385,2421,2448,2451,2454,2457,2463,2467,2469,2508,2510,2534,2547
(FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To
Cc From Subject X-Priority Importance Priority Content-Type )])
| Server responded: Syntax error in header fields

Regards,
anctop


> -----
> squirrelmail-users mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squ...@li...
> 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] reporting bug of SquirrelMail 1.4.23-svn

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

On Sun, July 30, 2023 5:19 am, anctop wrote:
> On 30/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>>
>> On Sat, July 29, 2023 5:41 am, anctop wrote:
>>> On 29/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>>>> Please bottom-post to keep context...
>>>>
>>>>> On 28/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>>>>>>
>>>>>> On Thu, July 27, 2023 9:57 pm, Paul Lesniewski wrote:
>>>>>>>> I am writing to report an issue with SquirrelMail 1.4.23-svn.
>>>>>>>> We have a Linux server with the following environment :
>>>>>>>> 1. Apache/2.4.39 with OpenSSL/1.1.1l
>>>>>>>> 2. PHP 7.3.4
>>>>>>>> 3. squirrelmail-20190221_0201-SVN.locales.tar.bz2
>>>>>>>> 4. Six SquirrelMail plugins
>>>>>>>>     compatibility-2.0.16-1.0
>>>>>>>>     html_mail-2.3-1.4
>>>>>>>>     tnef_decoder-1.0-1.4.0
>>>>>>>>     undelete-2.0-1.4.0
>>>>>>>>     view_as_html-3.8
>>>>>>>>     vlogin-3.10.2-1.2.7
>>>>>>>> 5. access two IMAP servers
>>>>>>>>     one runs "Panda IMAP 2010.417" (built from Alpine-2.26
>>>>>>>> package)
>>>>>>>>     one runs "Microsoft Exchange IMAP4"
>>>>>>>> This copy of SquirrelMail works perfectly.
>>>>>>>> Recently, we upgraded SquirrelMail to
>>>>>>>> "squirrelmail-20230725_0200-SVN.stable.tar.bz2".
>>>>>>>> Exactly the same configurations are applied to the new tree.
>>>>>>>> The "<path to squirrelmail>/src/configtest.php" reports no error.
>>>>>>>> Users login are successful but the right frame shows the following
>>>>>>>> error
>>>>>>>> :
>>>>>>>> # Connect to Panda IMAP
>>>>>>>>> ERROR: Bad or malformed request.
>>>>>>>>> Query: FETCH 1,32 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>>>>>> BODY.PEEK[HEADER.FIELDS
>>>>>>>>> (Date To Cc From Subject X-Priority Importance Priority
>>>>>>>>> Content-Type
>>>>>>>>> )])
>>>>>>>>> Server responded: Syntax error in header fields
>>>>>>>> # Connect to Microsoft Exchange
>>>>>>>>> ERROR: Bad or malformed request.
>>>>>>>>> Query: FETCH
>>>>>>>>> 23448:23449,23537,24173,24213,24402,24433,24452,24468,24505,24637,24673:24676
>>>>>>>>> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date
>>>>>>>>> To
>>>>>>>>> Cc
>>>>>>>>> From
>>>>>>>>> Subject X-Priority Importance Priority Content-Type )])
>>>>>>>>> Server responded: Command Argument Error. 11
>>>>>>> I just enabled the "info" plugin, went to Options --> IMAP server
>>>>>>> information, enabled the first three example commands, and entered
>>>>>>> a
>>>>>>> cut-and-paste of the command from your report, adjusting the
>>>>>>> requested
>>>>>>> IDs
>>>>>>> for my inbox count... as an example:
>>>>>>> FETCH 1710:1712,1716 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>>>> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority
>>>>>>> Importance
>>>>>>> Priority Content-Type )])
>>>>>>> The server didn't have any problems with this command. Can you
>>>>>>> please
>>>>>>> use
>>>>>>> the "info" plugin to further diagnose? Can you sniff the IMAP
>>>>>>> traffic
>>>>>>> for
>>>>>>> an older instance that is working as well as the new installation
>>>>>>> and
>>>>>>> compare how the commands look different?
>>>>>> You can also open up functions/imap_messages.php and find both
>>>>>> instances
>>>>>> of $extra_small_header_fields in the FETCH commands (approximately
>>>>>> lines
>>>>>> 750 and 752) and remove it and the space before it. There is a
>>>>>> chance
>>>>>> that
>>>>>> your IMAP servers are being fussy about one extra space. If you can
>>>>>> confirm that is the issue, I can issue a fix.
>>>>>
>>>>> Yes, removing $extra_small_header_fields for FETCH in
>>>>> "functions/imap_messages.php" solves the problem immediately if no
>>>>> plugin is used.
>>>>>
>>>>> When I put back the plugin "vlogin", users cannot login (in both
>>>>> implementations).
>>>>>
>>>>> What other workaround is required ?
>>>>
>>>> Please first apply this patch and try it again "the right way" (you
>>>> can
>>>> also wait to grab the next nightly build tarball)
>>>>
>>>> https://sourceforge.net/p/squirrelmail/code/14991/
>>>>
>>>> Otherwise, the vlogin problem sounds unrelated and would need logs and
>>>> further diagnosis.
>>>
>>> The patch does not help.
>>
>> More specifically, it does help with your IMAP problem but not the
>> vlogin
>> one, right?
>>
>>> In fact, if "vlogin" is used, then user authentication fails with or
>>> without the patch :
>>>> ERROR
>>>> Unknown user or password incorrect.
>>>> Go to the login page
>>>
>>> It seems that the "vlogin" plugin is not compatible with the new
>>> snapshot.
>>> Should I submit the file "plugins/vlogin/data/config.php" for diagnosis
>>> ?
>>
>> Turn on $vlogin_debug and start gathering information about what the
>> actual error is and what the plugin is doing to usernames versus what
>> the
>> IMAP server expects to get. You can also start with a default
>> configuration file and change one thing at a time.
>
> Firstly I must apologize for making a false report about "vlogin".
> By turning on $vlogin_debug, I find that the login failure was due to
> setting a wrong value to $sendmailVirtualUserTable.
> This problem is now fixed.
>
> About your "official" patch, I am sorry to inform you that it really
> does not work.
> For the patch to work, the string "$extra_small_header_fields" must be
> removed from the two FETCH lines, as you have said at the beginning.

Did you apply the patch as given from the original unmodified file or do
it by hand? There should not be any extra spaces in the resulting FETCH
command. Can you please output the contents of $extra_small_header_fields
just above where it is being used to ensure it is empty? You can do that
with something such as:
echo "<hr>extra_small_header_fields:<br>";
var_dump($extra_small_header_fields); echo "<hr>";

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

Re: [SM-USERS] reporting bug of SquirrelMail 1.4.23-svn

[anctop <an...@gm...>]

On 30/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>
> On Sat, July 29, 2023 5:41 am, anctop wrote:
>> On 29/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>>> Please bottom-post to keep context...
>>>
>>>> On 28/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>>>>>
>>>>> On Thu, July 27, 2023 9:57 pm, Paul Lesniewski wrote:
>>>>>>> I am writing to report an issue with SquirrelMail 1.4.23-svn.
>>>>>>> We have a Linux server with the following environment :
>>>>>>> 1. Apache/2.4.39 with OpenSSL/1.1.1l
>>>>>>> 2. PHP 7.3.4
>>>>>>> 3. squirrelmail-20190221_0201-SVN.locales.tar.bz2
>>>>>>> 4. Six SquirrelMail plugins
>>>>>>>     compatibility-2.0.16-1.0
>>>>>>>     html_mail-2.3-1.4
>>>>>>>     tnef_decoder-1.0-1.4.0
>>>>>>>     undelete-2.0-1.4.0
>>>>>>>     view_as_html-3.8
>>>>>>>     vlogin-3.10.2-1.2.7
>>>>>>> 5. access two IMAP servers
>>>>>>>     one runs "Panda IMAP 2010.417" (built from Alpine-2.26 package)
>>>>>>>     one runs "Microsoft Exchange IMAP4"
>>>>>>> This copy of SquirrelMail works perfectly.
>>>>>>> Recently, we upgraded SquirrelMail to
>>>>>>> "squirrelmail-20230725_0200-SVN.stable.tar.bz2".
>>>>>>> Exactly the same configurations are applied to the new tree.
>>>>>>> The "<path to squirrelmail>/src/configtest.php" reports no error.
>>>>>>> Users login are successful but the right frame shows the following
>>>>>>> error
>>>>>>> :
>>>>>>> # Connect to Panda IMAP
>>>>>>>> ERROR: Bad or malformed request.
>>>>>>>> Query: FETCH 1,32 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>>>>> BODY.PEEK[HEADER.FIELDS
>>>>>>>> (Date To Cc From Subject X-Priority Importance Priority
>>>>>>>> Content-Type
>>>>>>>> )])
>>>>>>>> Server responded: Syntax error in header fields
>>>>>>> # Connect to Microsoft Exchange
>>>>>>>> ERROR: Bad or malformed request.
>>>>>>>> Query: FETCH
>>>>>>>> 23448:23449,23537,24173,24213,24402,24433,24452,24468,24505,24637,24673:24676
>>>>>>>> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date
>>>>>>>> To
>>>>>>>> Cc
>>>>>>>> From
>>>>>>>> Subject X-Priority Importance Priority Content-Type )])
>>>>>>>> Server responded: Command Argument Error. 11
>>>>>> I just enabled the "info" plugin, went to Options --> IMAP server
>>>>>> information, enabled the first three example commands, and entered a
>>>>>> cut-and-paste of the command from your report, adjusting the
>>>>>> requested
>>>>>> IDs
>>>>>> for my inbox count... as an example:
>>>>>> FETCH 1710:1712,1716 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>>> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority
>>>>>> Importance
>>>>>> Priority Content-Type )])
>>>>>> The server didn't have any problems with this command. Can you please
>>>>>> use
>>>>>> the "info" plugin to further diagnose? Can you sniff the IMAP traffic
>>>>>> for
>>>>>> an older instance that is working as well as the new installation and
>>>>>> compare how the commands look different?
>>>>> You can also open up functions/imap_messages.php and find both
>>>>> instances
>>>>> of $extra_small_header_fields in the FETCH commands (approximately
>>>>> lines
>>>>> 750 and 752) and remove it and the space before it. There is a chance
>>>>> that
>>>>> your IMAP servers are being fussy about one extra space. If you can
>>>>> confirm that is the issue, I can issue a fix.
>>>>
>>>> Yes, removing $extra_small_header_fields for FETCH in
>>>> "functions/imap_messages.php" solves the problem immediately if no
>>>> plugin is used.
>>>>
>>>> When I put back the plugin "vlogin", users cannot login (in both
>>>> implementations).
>>>>
>>>> What other workaround is required ?
>>>
>>> Please first apply this patch and try it again "the right way" (you can
>>> also wait to grab the next nightly build tarball)
>>>
>>> https://sourceforge.net/p/squirrelmail/code/14991/
>>>
>>> Otherwise, the vlogin problem sounds unrelated and would need logs and
>>> further diagnosis.
>>
>> The patch does not help.
>
> More specifically, it does help with your IMAP problem but not the vlogin
> one, right?
>
>> In fact, if "vlogin" is used, then user authentication fails with or
>> without the patch :
>>> ERROR
>>> Unknown user or password incorrect.
>>> Go to the login page
>>
>> It seems that the "vlogin" plugin is not compatible with the new
>> snapshot.
>> Should I submit the file "plugins/vlogin/data/config.php" for diagnosis ?
>
> Turn on $vlogin_debug and start gathering information about what the
> actual error is and what the plugin is doing to usernames versus what the
> IMAP server expects to get. You can also start with a default
> configuration file and change one thing at a time.
>
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php


Dear Paul,

Firstly I must apologize for making a false report about "vlogin".
By turning on $vlogin_debug, I find that the login failure was due to
setting a wrong value to $sendmailVirtualUserTable.
This problem is now fixed.

About your "official" patch, I am sorry to inform you that it really
does not work.
For the patch to work, the string "$extra_small_header_fields" must be
removed from the two FETCH lines, as you have said at the beginning.

Regards,
anctop


> -----
> squirrelmail-users mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squ...@li...
> 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] reporting bug of SquirrelMail 1.4.23-svn

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

On Sat, July 29, 2023 5:41 am, anctop wrote:
> On 29/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>> Please bottom-post to keep context...
>>
>>> On 28/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>>>>
>>>> On Thu, July 27, 2023 9:57 pm, Paul Lesniewski wrote:
>>>>>> I am writing to report an issue with SquirrelMail 1.4.23-svn.
>>>>>> We have a Linux server with the following environment :
>>>>>> 1. Apache/2.4.39 with OpenSSL/1.1.1l
>>>>>> 2. PHP 7.3.4
>>>>>> 3. squirrelmail-20190221_0201-SVN.locales.tar.bz2
>>>>>> 4. Six SquirrelMail plugins
>>>>>>     compatibility-2.0.16-1.0
>>>>>>     html_mail-2.3-1.4
>>>>>>     tnef_decoder-1.0-1.4.0
>>>>>>     undelete-2.0-1.4.0
>>>>>>     view_as_html-3.8
>>>>>>     vlogin-3.10.2-1.2.7
>>>>>> 5. access two IMAP servers
>>>>>>     one runs "Panda IMAP 2010.417" (built from Alpine-2.26 package)
>>>>>>     one runs "Microsoft Exchange IMAP4"
>>>>>> This copy of SquirrelMail works perfectly.
>>>>>> Recently, we upgraded SquirrelMail to
>>>>>> "squirrelmail-20230725_0200-SVN.stable.tar.bz2".
>>>>>> Exactly the same configurations are applied to the new tree.
>>>>>> The "<path to squirrelmail>/src/configtest.php" reports no error.
>>>>>> Users login are successful but the right frame shows the following
>>>>>> error
>>>>>> :
>>>>>> # Connect to Panda IMAP
>>>>>>> ERROR: Bad or malformed request.
>>>>>>> Query: FETCH 1,32 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>>>> BODY.PEEK[HEADER.FIELDS
>>>>>>> (Date To Cc From Subject X-Priority Importance Priority
>>>>>>> Content-Type
>>>>>>> )])
>>>>>>> Server responded: Syntax error in header fields
>>>>>> # Connect to Microsoft Exchange
>>>>>>> ERROR: Bad or malformed request.
>>>>>>> Query: FETCH
>>>>>>> 23448:23449,23537,24173,24213,24402,24433,24452,24468,24505,24637,24673:24676
>>>>>>> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date
>>>>>>> To
>>>>>>> Cc
>>>>>>> From
>>>>>>> Subject X-Priority Importance Priority Content-Type )])
>>>>>>> Server responded: Command Argument Error. 11
>>>>> I just enabled the "info" plugin, went to Options --> IMAP server
>>>>> information, enabled the first three example commands, and entered a
>>>>> cut-and-paste of the command from your report, adjusting the
>>>>> requested
>>>>> IDs
>>>>> for my inbox count... as an example:
>>>>> FETCH 1710:1712,1716 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority
>>>>> Importance
>>>>> Priority Content-Type )])
>>>>> The server didn't have any problems with this command. Can you please
>>>>> use
>>>>> the "info" plugin to further diagnose? Can you sniff the IMAP traffic
>>>>> for
>>>>> an older instance that is working as well as the new installation and
>>>>> compare how the commands look different?
>>>> You can also open up functions/imap_messages.php and find both
>>>> instances
>>>> of $extra_small_header_fields in the FETCH commands (approximately
>>>> lines
>>>> 750 and 752) and remove it and the space before it. There is a chance
>>>> that
>>>> your IMAP servers are being fussy about one extra space. If you can
>>>> confirm that is the issue, I can issue a fix.
>>>
>>> Yes, removing $extra_small_header_fields for FETCH in
>>> "functions/imap_messages.php" solves the problem immediately if no
>>> plugin is used.
>>>
>>> When I put back the plugin "vlogin", users cannot login (in both
>>> implementations).
>>>
>>> What other workaround is required ?
>>
>> Please first apply this patch and try it again "the right way" (you can
>> also wait to grab the next nightly build tarball)
>>
>> https://sourceforge.net/p/squirrelmail/code/14991/
>>
>> Otherwise, the vlogin problem sounds unrelated and would need logs and
>> further diagnosis.
>
> The patch does not help.

More specifically, it does help with your IMAP problem but not the vlogin
one, right?

> In fact, if "vlogin" is used, then user authentication fails with or
> without the patch :
>> ERROR
>> Unknown user or password incorrect.
>> Go to the login page
>
> It seems that the "vlogin" plugin is not compatible with the new snapshot.
> Should I submit the file "plugins/vlogin/data/config.php" for diagnosis ?

Turn on $vlogin_debug and start gathering information about what the
actual error is and what the plugin is doing to usernames versus what the
IMAP server expects to get. You can also start with a default
configuration file and change one thing at a time.

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

Re: [SM-USERS] reporting bug of SquirrelMail 1.4.23-svn

[anctop <an...@gm...>]

On 29/07/2023, Paul Lesniewski <pa...@sq...> wrote:
> Please bottom-post to keep context...
>
>> On 28/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>>>
>>> On Thu, July 27, 2023 9:57 pm, Paul Lesniewski wrote:
>>>>> I am writing to report an issue with SquirrelMail 1.4.23-svn.
>>>>> We have a Linux server with the following environment :
>>>>> 1. Apache/2.4.39 with OpenSSL/1.1.1l
>>>>> 2. PHP 7.3.4
>>>>> 3. squirrelmail-20190221_0201-SVN.locales.tar.bz2
>>>>> 4. Six SquirrelMail plugins
>>>>>     compatibility-2.0.16-1.0
>>>>>     html_mail-2.3-1.4
>>>>>     tnef_decoder-1.0-1.4.0
>>>>>     undelete-2.0-1.4.0
>>>>>     view_as_html-3.8
>>>>>     vlogin-3.10.2-1.2.7
>>>>> 5. access two IMAP servers
>>>>>     one runs "Panda IMAP 2010.417" (built from Alpine-2.26 package)
>>>>>     one runs "Microsoft Exchange IMAP4"
>>>>> This copy of SquirrelMail works perfectly.
>>>>> Recently, we upgraded SquirrelMail to
>>>>> "squirrelmail-20230725_0200-SVN.stable.tar.bz2".
>>>>> Exactly the same configurations are applied to the new tree.
>>>>> The "<path to squirrelmail>/src/configtest.php" reports no error.
>>>>> Users login are successful but the right frame shows the following
>>>>> error
>>>>> :
>>>>> # Connect to Panda IMAP
>>>>>> ERROR: Bad or malformed request.
>>>>>> Query: FETCH 1,32 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>>> BODY.PEEK[HEADER.FIELDS
>>>>>> (Date To Cc From Subject X-Priority Importance Priority Content-Type
>>>>>> )])
>>>>>> Server responded: Syntax error in header fields
>>>>> # Connect to Microsoft Exchange
>>>>>> ERROR: Bad or malformed request.
>>>>>> Query: FETCH
>>>>>> 23448:23449,23537,24173,24213,24402,24433,24452,24468,24505,24637,24673:24676
>>>>>> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To
>>>>>> Cc
>>>>>> From
>>>>>> Subject X-Priority Importance Priority Content-Type )])
>>>>>> Server responded: Command Argument Error. 11
>>>> I just enabled the "info" plugin, went to Options --> IMAP server
>>>> information, enabled the first three example commands, and entered a
>>>> cut-and-paste of the command from your report, adjusting the requested
>>>> IDs
>>>> for my inbox count... as an example:
>>>> FETCH 1710:1712,1716 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance
>>>> Priority Content-Type )])
>>>> The server didn't have any problems with this command. Can you please
>>>> use
>>>> the "info" plugin to further diagnose? Can you sniff the IMAP traffic
>>>> for
>>>> an older instance that is working as well as the new installation and
>>>> compare how the commands look different?
>>> You can also open up functions/imap_messages.php and find both instances
>>> of $extra_small_header_fields in the FETCH commands (approximately lines
>>> 750 and 752) and remove it and the space before it. There is a chance
>>> that
>>> your IMAP servers are being fussy about one extra space. If you can
>>> confirm that is the issue, I can issue a fix.
>>
>> Yes, removing $extra_small_header_fields for FETCH in
>> "functions/imap_messages.php" solves the problem immediately if no
>> plugin is used.
>>
>> When I put back the plugin "vlogin", users cannot login (in both
>> implementations).
>>
>> What other workaround is required ?
>
> Please first apply this patch and try it again "the right way" (you can
> also wait to grab the next nightly build tarball)
>
> https://sourceforge.net/p/squirrelmail/code/14991/
>
> Otherwise, the vlogin problem sounds unrelated and would need logs and
> further diagnosis.
>
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php


Dear Paul,

The patch does not help.
In fact, if "vlogin" is used, then user authentication fails with or
without the patch :
> ERROR
> Unknown user or password incorrect.
> Go to the login page

It seems that the "vlogin" plugin is not compatible with the new snapshot.
Should I submit the file "plugins/vlogin/data/config.php" for diagnosis ?

Regards,
anctop


>>>>> We then replicate the SquirrelMail installation on another server :
>>>>> 1. Apache/2.4.56 OpenSSL/3.1.0
>>>>> 2. PHP 8.1.17
>>>>> 3. squirrelmail-20230725_0200-SVN.stable.tar.bz2
>>>>> 4. no SquirrelMail plugins
>>>>> This copy of SquirrelMail has the same problem as described above.
>>>>> Please kindly advise.
> -----
> squirrelmail-users mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squ...@li...
> 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] reporting bug of SquirrelMail 1.4.23-svn

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

Please bottom-post to keep context...

> On 28/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>>
>> On Thu, July 27, 2023 9:57 pm, Paul Lesniewski wrote:
>>>> I am writing to report an issue with SquirrelMail 1.4.23-svn.
>>>> We have a Linux server with the following environment :
>>>> 1. Apache/2.4.39 with OpenSSL/1.1.1l
>>>> 2. PHP 7.3.4
>>>> 3. squirrelmail-20190221_0201-SVN.locales.tar.bz2
>>>> 4. Six SquirrelMail plugins
>>>>     compatibility-2.0.16-1.0
>>>>     html_mail-2.3-1.4
>>>>     tnef_decoder-1.0-1.4.0
>>>>     undelete-2.0-1.4.0
>>>>     view_as_html-3.8
>>>>     vlogin-3.10.2-1.2.7
>>>> 5. access two IMAP servers
>>>>     one runs "Panda IMAP 2010.417" (built from Alpine-2.26 package)
>>>>     one runs "Microsoft Exchange IMAP4"
>>>> This copy of SquirrelMail works perfectly.
>>>> Recently, we upgraded SquirrelMail to
>>>> "squirrelmail-20230725_0200-SVN.stable.tar.bz2".
>>>> Exactly the same configurations are applied to the new tree.
>>>> The "<path to squirrelmail>/src/configtest.php" reports no error.
>>>> Users login are successful but the right frame shows the following
>>>> error
>>>> :
>>>> # Connect to Panda IMAP
>>>>> ERROR: Bad or malformed request.
>>>>> Query: FETCH 1,32 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>>> BODY.PEEK[HEADER.FIELDS
>>>>> (Date To Cc From Subject X-Priority Importance Priority Content-Type
>>>>> )])
>>>>> Server responded: Syntax error in header fields
>>>> # Connect to Microsoft Exchange
>>>>> ERROR: Bad or malformed request.
>>>>> Query: FETCH
>>>>> 23448:23449,23537,24173,24213,24402,24433,24452,24468,24505,24637,24673:24676
>>>>> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To
>>>>> Cc
>>>>> From
>>>>> Subject X-Priority Importance Priority Content-Type )])
>>>>> Server responded: Command Argument Error. 11
>>> I just enabled the "info" plugin, went to Options --> IMAP server
>>> information, enabled the first three example commands, and entered a
>>> cut-and-paste of the command from your report, adjusting the requested
>>> IDs
>>> for my inbox count... as an example:
>>> FETCH 1710:1712,1716 (FLAGS UID RFC822.SIZE INTERNALDATE
>>> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance
>>> Priority Content-Type )])
>>> The server didn't have any problems with this command. Can you please
>>> use
>>> the "info" plugin to further diagnose? Can you sniff the IMAP traffic
>>> for
>>> an older instance that is working as well as the new installation and
>>> compare how the commands look different?
>> You can also open up functions/imap_messages.php and find both instances
>> of $extra_small_header_fields in the FETCH commands (approximately lines
>> 750 and 752) and remove it and the space before it. There is a chance
>> that
>> your IMAP servers are being fussy about one extra space. If you can
>> confirm that is the issue, I can issue a fix.
>
> Yes, removing $extra_small_header_fields for FETCH in
> "functions/imap_messages.php" solves the problem immediately if no
> plugin is used.
>
> When I put back the plugin "vlogin", users cannot login (in both
> implementations).
>
> What other workaround is required ?

Please first apply this patch and try it again "the right way" (you can
also wait to grab the next nightly build tarball)

https://sourceforge.net/p/squirrelmail/code/14991/

Otherwise, the vlogin problem sounds unrelated and would need logs and
further diagnosis.

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


>>>> We then replicate the SquirrelMail installation on another server :
>>>> 1. Apache/2.4.56 OpenSSL/3.1.0
>>>> 2. PHP 8.1.17
>>>> 3. squirrelmail-20230725_0200-SVN.stable.tar.bz2
>>>> 4. no SquirrelMail plugins
>>>> This copy of SquirrelMail has the same problem as described above.
>>>> Please kindly advise.

Re: [SM-USERS] reporting bug of SquirrelMail 1.4.23-svn

[anctop <an...@gm...>]

Dear Paul,

Yes, removing $extra_small_header_fields for FETCH in
"functions/imap_messages.php" solves the problem immediately if no
plugin is used.

When I put back the plugin "vlogin", users cannot login (in both
implementations).

What other workaround is required ?

Regards,
anctop


On 28/07/2023, Paul Lesniewski <pa...@sq...> wrote:
>
> On Thu, July 27, 2023 9:57 pm, Paul Lesniewski wrote:
>>> I am writing to report an issue with SquirrelMail 1.4.23-svn.
>>> We have a Linux server with the following environment :
>>> 1. Apache/2.4.39 with OpenSSL/1.1.1l
>>> 2. PHP 7.3.4
>>> 3. squirrelmail-20190221_0201-SVN.locales.tar.bz2
>>> 4. Six SquirrelMail plugins
>>>     compatibility-2.0.16-1.0
>>>     html_mail-2.3-1.4
>>>     tnef_decoder-1.0-1.4.0
>>>     undelete-2.0-1.4.0
>>>     view_as_html-3.8
>>>     vlogin-3.10.2-1.2.7
>>> 5. access two IMAP servers
>>>     one runs "Panda IMAP 2010.417" (built from Alpine-2.26 package)
>>>     one runs "Microsoft Exchange IMAP4"
>>> This copy of SquirrelMail works perfectly.
>>> Recently, we upgraded SquirrelMail to
>>> "squirrelmail-20230725_0200-SVN.stable.tar.bz2".
>>> Exactly the same configurations are applied to the new tree.
>>> The "<path to squirrelmail>/src/configtest.php" reports no error.
>>> Users login are successful but the right frame shows the following error
>>> :
>>> # Connect to Panda IMAP
>>>> ERROR: Bad or malformed request.
>>>> Query: FETCH 1,32 (FLAGS UID RFC822.SIZE INTERNALDATE
>>>> BODY.PEEK[HEADER.FIELDS
>>>> (Date To Cc From Subject X-Priority Importance Priority Content-Type
>>>> )])
>>>> Server responded: Syntax error in header fields
>>> # Connect to Microsoft Exchange
>>>> ERROR: Bad or malformed request.
>>>> Query: FETCH
>>>> 23448:23449,23537,24173,24213,24402,24433,24452,24468,24505,24637,24673:24676
>>>> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc
>>>> From
>>>> Subject X-Priority Importance Priority Content-Type )])
>>>> Server responded: Command Argument Error. 11
>> I just enabled the "info" plugin, went to Options --> IMAP server
>> information, enabled the first three example commands, and entered a
>> cut-and-paste of the command from your report, adjusting the requested
>> IDs
>> for my inbox count... as an example:
>> FETCH 1710:1712,1716 (FLAGS UID RFC822.SIZE INTERNALDATE
>> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance
>> Priority Content-Type )])
>> The server didn't have any problems with this command. Can you please use
>> the "info" plugin to further diagnose? Can you sniff the IMAP traffic for
>> an older instance that is working as well as the new installation and
>> compare how the commands look different?
> You can also open up functions/imap_messages.php and find both instances
> of $extra_small_header_fields in the FETCH commands (approximately lines
> 750 and 752) and remove it and the space before it. There is a chance that
> your IMAP servers are being fussy about one extra space. If you can
> confirm that is the issue, I can issue a fix.
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php
>
>>> We then replicate the SquirrelMail installation on another server :
>>> 1. Apache/2.4.56 OpenSSL/3.1.0
>>> 2. PHP 8.1.17
>>> 3. squirrelmail-20230725_0200-SVN.stable.tar.bz2
>>> 4. no SquirrelMail plugins
>>> This copy of SquirrelMail has the same problem as described above.
>>> Please kindly advise.
> -----
> squirrelmail-users mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squ...@li...
> 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] reporting bug of SquirrelMail 1.4.23-svn

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

On Thu, July 27, 2023 9:57 pm, Paul Lesniewski wrote:
>> I am writing to report an issue with SquirrelMail 1.4.23-svn.
>>
>> We have a Linux server with the following environment :
>>
>> 1. Apache/2.4.39 with OpenSSL/1.1.1l
>> 2. PHP 7.3.4
>> 3. squirrelmail-20190221_0201-SVN.locales.tar.bz2
>> 4. Six SquirrelMail plugins
>>     compatibility-2.0.16-1.0
>>     html_mail-2.3-1.4
>>     tnef_decoder-1.0-1.4.0
>>     undelete-2.0-1.4.0
>>     view_as_html-3.8
>>     vlogin-3.10.2-1.2.7
>> 5. access two IMAP servers
>>     one runs "Panda IMAP 2010.417" (built from Alpine-2.26 package)
>>     one runs "Microsoft Exchange IMAP4"
>>
>> This copy of SquirrelMail works perfectly.
>>
>>
>> Recently, we upgraded SquirrelMail to
>> "squirrelmail-20230725_0200-SVN.stable.tar.bz2".
>> Exactly the same configurations are applied to the new tree.
>> The "<path to squirrelmail>/src/configtest.php" reports no error.
>> Users login are successful but the right frame shows the following error
>> :
>>
>> # Connect to Panda IMAP
>>> ERROR: Bad or malformed request.
>>> Query: FETCH 1,32 (FLAGS UID RFC822.SIZE INTERNALDATE
>>> BODY.PEEK[HEADER.FIELDS
>>> (Date To Cc From Subject X-Priority Importance Priority Content-Type
>>> )])
>>> Server responded: Syntax error in header fields
>>
>> # Connect to Microsoft Exchange
>>> ERROR: Bad or malformed request.
>>> Query: FETCH
>>> 23448:23449,23537,24173,24213,24402,24433,24452,24468,24505,24637,24673:24676
>>> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc
>>> From
>>> Subject X-Priority Importance Priority Content-Type )])
>>> Server responded: Command Argument Error. 11
>
> I just enabled the "info" plugin, went to Options --> IMAP server
> information, enabled the first three example commands, and entered a
> cut-and-paste of the command from your report, adjusting the requested IDs
> for my inbox count... as an example:
>
> FETCH 1710:1712,1716 (FLAGS UID RFC822.SIZE INTERNALDATE
> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance
> Priority Content-Type )])
>
> The server didn't have any problems with this command. Can you please use
> the "info" plugin to further diagnose? Can you sniff the IMAP traffic for
> an older instance that is working as well as the new installation and
> compare how the commands look different?

You can also open up functions/imap_messages.php and find both instances
of $extra_small_header_fields in the FETCH commands (approximately lines
750 and 752) and remove it and the space before it. There is a chance that
your IMAP servers are being fussy about one extra space. If you can
confirm that is the issue, I can issue a fix.

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


>> We then replicate the SquirrelMail installation on another server :
>>
>> 1. Apache/2.4.56 OpenSSL/3.1.0
>> 2. PHP 8.1.17
>> 3. squirrelmail-20230725_0200-SVN.stable.tar.bz2
>> 4. no SquirrelMail plugins
>>
>> This copy of SquirrelMail has the same problem as described above.
>>
>>
>> Please kindly advise.
>
>

Re: [SM-USERS] reporting bug of SquirrelMail 1.4.23-svn

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

> I am writing to report an issue with SquirrelMail 1.4.23-svn.
>
> We have a Linux server with the following environment :
>
> 1. Apache/2.4.39 with OpenSSL/1.1.1l
> 2. PHP 7.3.4
> 3. squirrelmail-20190221_0201-SVN.locales.tar.bz2
> 4. Six SquirrelMail plugins
>     compatibility-2.0.16-1.0
>     html_mail-2.3-1.4
>     tnef_decoder-1.0-1.4.0
>     undelete-2.0-1.4.0
>     view_as_html-3.8
>     vlogin-3.10.2-1.2.7
> 5. access two IMAP servers
>     one runs "Panda IMAP 2010.417" (built from Alpine-2.26 package)
>     one runs "Microsoft Exchange IMAP4"
>
> This copy of SquirrelMail works perfectly.
>
>
> Recently, we upgraded SquirrelMail to
> "squirrelmail-20230725_0200-SVN.stable.tar.bz2".
> Exactly the same configurations are applied to the new tree.
> The "<path to squirrelmail>/src/configtest.php" reports no error.
> Users login are successful but the right frame shows the following error :
>
> # Connect to Panda IMAP
>> ERROR: Bad or malformed request.
>> Query: FETCH 1,32 (FLAGS UID RFC822.SIZE INTERNALDATE
>> BODY.PEEK[HEADER.FIELDS
>> (Date To Cc From Subject X-Priority Importance Priority Content-Type )])
>> Server responded: Syntax error in header fields
>
> # Connect to Microsoft Exchange
>> ERROR: Bad or malformed request.
>> Query: FETCH
>> 23448:23449,23537,24173,24213,24402,24433,24452,24468,24505,24637,24673:24676
>> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc
>> From
>> Subject X-Priority Importance Priority Content-Type )])
>> Server responded: Command Argument Error. 11

I just enabled the "info" plugin, went to Options --> IMAP server
information, enabled the first three example commands, and entered a
cut-and-paste of the command from your report, adjusting the requested IDs
for my inbox count... as an example:

FETCH 1710:1712,1716 (FLAGS UID RFC822.SIZE INTERNALDATE
BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance
Priority Content-Type )])

The server didn't have any problems with this command. Can you please use
the "info" plugin to further diagnose? Can you sniff the IMAP traffic for
an older instance that is working as well as the new installation and
compare how the commands look different?

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


> We then replicate the SquirrelMail installation on another server :
>
> 1. Apache/2.4.56 OpenSSL/3.1.0
> 2. PHP 8.1.17
> 3. squirrelmail-20230725_0200-SVN.stable.tar.bz2
> 4. no SquirrelMail plugins
>
> This copy of SquirrelMail has the same problem as described above.
>
>
> Please kindly advise.

[SM-USERS] reporting bug of SquirrelMail 1.4.23-svn

[anctop <an...@gm...>]

Hi,

I am writing to report an issue with SquirrelMail 1.4.23-svn.

We have a Linux server with the following environment :

1. Apache/2.4.39 with OpenSSL/1.1.1l
2. PHP 7.3.4
3. squirrelmail-20190221_0201-SVN.locales.tar.bz2
4. Six SquirrelMail plugins
    compatibility-2.0.16-1.0
    html_mail-2.3-1.4
    tnef_decoder-1.0-1.4.0
    undelete-2.0-1.4.0
    view_as_html-3.8
    vlogin-3.10.2-1.2.7
5. access two IMAP servers
    one runs "Panda IMAP 2010.417" (built from Alpine-2.26 package)
    one runs "Microsoft Exchange IMAP4"

This copy of SquirrelMail works perfectly.


Recently, we upgraded SquirrelMail to
"squirrelmail-20230725_0200-SVN.stable.tar.bz2".
Exactly the same configurations are applied to the new tree.
The "<path to squirrelmail>/src/configtest.php" reports no error.
Users login are successful but the right frame shows the following error :

# Connect to Panda IMAP
> ERROR: Bad or malformed request.
> Query: FETCH 1,32 (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS
> (Date To Cc From Subject X-Priority Importance Priority Content-Type )])
> Server responded: Syntax error in header fields

# Connect to Microsoft Exchange
> ERROR: Bad or malformed request.
> Query: FETCH
> 23448:23449,23537,24173,24213,24402,24433,24452,24468,24505,24637,24673:24676
> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc From
> Subject X-Priority Importance Priority Content-Type )])
> Server responded: Command Argument Error. 11


We then replicate the SquirrelMail installation on another server :

1. Apache/2.4.56 OpenSSL/3.1.0
2. PHP 8.1.17
3. squirrelmail-20230725_0200-SVN.stable.tar.bz2
4. no SquirrelMail plugins

This copy of SquirrelMail has the same problem as described above.


Please kindly advise.

Re: [SM-USERS] MFA/2FA support?

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

Hi Paul,

On Wed, May 10, 2023 at 10:23 PM Paul Lesniewski <pa...@sq...>
wrote:

> > Is there any chance some sort of software-based MFA is supported?
>
> Depends what factors you need to implement.  The Login Authentication
> plugin supports SSO, and I have an unpublished plugin that's meant to
> implement more generic factors but currently only supports SMS messaging
> via an API such as Twilio's.
>

That would work. I was thinking of something like FreeOTP, but some SMS
solution would also be okay.

I'd love to try it, if you think it's stable enough.

Thanks,
Alex


>

Re: [SM-USERS] MFA/2FA support?

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

> Is there any chance some sort of software-based MFA is supported?

Depends what factors you need to implement.  The Login Authentication
plugin supports SSO, and I have an unpublished plugin that's meant to
implement more generic factors but currently only supports SMS messaging
via an API such as Twilio's.

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

[SM-USERS] MFA/2FA support?

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

Hi,

Is there any chance some sort of software-based MFA is supported?

Thanks,
Alex