Bug 4422 - Message retrieval does not intitiate
Summary: Message retrieval does not intitiate
Status: RESOLVED WORKSFORME
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Folders/IMAP (show other bugs)
Version: 3.17.3
Hardware: PC Linux
: P3 major
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2020-12-15 18:16 UTC by claws-mail-bugs
Modified: 2020-12-15 19:02 UTC (History)
0 users

See Also:


Attachments

Description claws-mail-bugs 2020-12-15 18:16:17 UTC
Several mechanisms were used to initiate a download, and Claws Mail makes no attempt:

* clicked the "Get Mail" pulldown followed by the account

* right-clicked the account >> "check for new messages"

* Message >> Recieve >> <account>

* configured the account to check for new mail every minute

* enabled "'Get Mail' checks for new messages on the account" in the configs

* selected the account in the lower right of the main window

* configuration >> change current account >> <account>

* triggered offline mode then went back online

There is no error, yet the network log shows no attempts to connect to the IMAP server.

I've also seen this problem on a POP3 account (IIRC after a few failed attempts to authenticate).  Restarting Claws Mail did nothing, but then the next day (after a reboot) the POP3 account started working.  But the IMAP account at hand has never before connected, and "Get Mail" is dead (no failure message, yet no results).
Comment 1 claws-mail-bugs 2020-12-15 19:02:31 UTC
The workaround in this case is to "rebuild folder tree", which I only found out because it was suggested by a C-M veteran.  I think what happened was I initially set the account up to use Tor and the service provider is very Tor hostile.  So the initial connection was refused, and C-M never created a folder tree.

It's quite strange (and absurd) that once the account is created without subfolders, C-M is dead in the water-- incapable of attempting a retrieval.  And  worse: it does not reattempt to create the folders and also gives no dialog or feedback indicating that there's a problem.  It just ignores the user, giving no indicative output even in --debug mode.

This has to change.  I personally won't get stung again but I'm sure others will.  It could probably also happen if they enter the wrong password in the initial setup.  I'm calling it major because availability of the most essential function to the apps existance is compromised, or apparently so as far as the user knows.

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