Re: reporting bug of SquirrelMail 1.4.23-svn

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 29/07/2023, Paul Lesniewski <paul@xxxxxxxxxxxxxxxx> wrote:
> Please bottom-post to keep context...
>
>> On 28/07/2023, Paul Lesniewski <paul@xxxxxxxxxxxxxxxx> 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: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxxx
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users



[Index of Archives]     [Video For Linux]     [Yosemite News]     [Yosemite Photos]     [gtk]     [KDE]     [Cyrus SASL]     [Gimp on Windows]     [Steve's Art]     [Webcams]

  Powered by Linux