Bug 31194 - fetchmail fails to download mail. Might be an openssl issue
Summary: fetchmail fails to download mail. Might be an openssl issue
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-26 11:48 CET by GG HH
Modified: 2022-11-27 18:04 CET (History)
3 users (show)

See Also:
Source RPM: fetchmail-6.4.24-3.mga9.src.rpm
CVE:
Status comment:


Attachments

Description GG HH 2022-11-26 11:48:35 CET
When downloading my mails, i get the following errors

$ fetchmail -vvv pop.orange.fr
fetchmail: 6.4.24 querying pop.orange.fr (protocol POP3) at Sat Nov 26 11:11:23 2022: poll started
Trying to connect to 80.12.24.15/995...connected.
fetchmail: Loaded OpenSSL library 0x30000050 newer than headers 0x30000020, trying to continue.
fetchmail: OpenSSL reported: error:030000A9:digital envelope routines::unknown option
fetchmail: OpenSSL reported: error:0700006D:configuration file routines::module initialization error
fetchmail: pop.orange.fr: SSL connection failed.
fetchmail: socket error while fetching from XXXXXX@pop.orange.fr

$ cat ~/.fetchmailrc
set postmaster "XXXXX"
set bouncemail
set properties ""
poll pop.orange.fr with proto POP3
        user account1               there with password mypassword    is XXXXX here options ssl
        user account2               there with password mypassword    is XXXXX here options ssl
poll YYYY with proto POP3
...

It is worth noting that the failure only occurs for the first account which is tried and a workaround is to duplicate it in the config file
        user account1               there with password mypassword    is XXXXX here options ssl
        user account1               there with password mypassword    is XXXXX here options ssl
        user account2               there with password mypassword    is XXXXX here options ssl
(as if the openssl error shown in the message was a wrongly managed warning message which only occurs during init)

Version-Release number of selected component (if applicable):
$ rpm -q fetchmail openssl lib64openssl3 lib64openssl-devel
fetchmail-6.4.24-3.mga9
openssl-3.0.5-2.mga9
lib64openssl3-3.0.5-2.mga9
lib64openssl-devel-3.0.5-2.mga9
GG HH 2022-11-26 11:49:02 CET

CC: (none) => boulshet

Comment 1 Lewis Smith 2022-11-26 20:31:31 CET
Thank you for the detailed report.
Can you post the log for one of your workaround duplicate accounts to the same e-mail account, for comparison?

Assigning initially to NicolasL who looks best for fetchmail.
CC'ing luigi and ns80 for their (SSL) view. They might suggest more useful diagnostics.

Assignee: bugsquad => mageia
CC: (none) => luigiwalser, nicolas.salguero

Comment 2 GG HH 2022-11-26 22:48:35 CET
here it is.

$ fetchmail pop.orange.fr
[...]
fetchmail: OpenSSL reported: error:030000A9:digital envelope routines::unknown option
fetchmail: OpenSSL reported: error:0700006D:configuration file routines::module initialization error
fetchmail: pop.orange.fr: SSL connection failed.
fetchmail: socket error while fetching from account1@pop.orange.fr
fetchmail: Query status=2 (SOCKET)
fetchmail: No mail for account1 at pop.orange.fr
[...]

Please look at the last line which is the same account as the first one - which failed - are 'both' related to those lines in my config file described in the report 
        user account1               there with password mypassword    is XXXXX here options ssl
        user account1               there with password mypassword    is XXXXX here options ssl

regards
Comment 3 GG HH 2022-11-27 17:58:25 CET
well, the issue is no longer met.
I made no modification on my system but removing an old an no longer used kernel. That's strange.

It might have been a server side issue... or not.

Closing, i will reopen if it occurs again.

thanks

Resolution: (none) => INVALID
Status: NEW => RESOLVED

Comment 4 GG HH 2022-11-27 18:04:25 CET
Actually looking a bit further, a cron task updated fetchmail to 6.4.34-1.mga9

i assume something has been fixed upstream :-)

thanks

Resolution: INVALID => FIXED


Note You need to log in before you can comment on or make changes to this bug.