Bug 1892126 - Upgraded from Fedora 32 to 33 - Claws Mail could not queue message
Summary: Upgraded from Fedora 32 to 33 - Claws Mail could not queue message
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: claws-mail
Version: 33
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Michael Schwendt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-28 00:57 UTC by Edward
Modified: 2020-10-28 11:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-28 11:43:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot showing error (8.81 KB, image/png)
2020-10-28 00:57 UTC, Edward
no flags Details

Description Edward 2020-10-28 00:57:08 UTC
Created attachment 1724661 [details]
Screenshot showing error

Description of problem:

Cannot send email after upgrading to Fedora 33. Getting error message that it could not queue message. There are Queue folders showing for each account.

Version-Release number of selected component (if applicable):

3.17.8

How reproducible:

Upgraded Fedora to 33. Launched Claws Mail after upgrade process completed. Attempted to send e-mail, error appeared that it could not queue the message.


Actual results:

Claws Mail could not queue message.


Expected results:

Claws Mail should have queued message and sent it.


Additional info:

Screenshot of error attached.

Comment 1 Michael Schwendt 2020-10-28 07:21:58 UTC
You need to tell a lot more than that. I've been using the same Claws Mail successfully with F33, and it's the same version as released for F32/F31. There is no reason to assume that F33 would be the culprit. It would be a wise idea to discuss such symptoms on a mailing-list before opening a ticket.

Start with launching "claws-mail -d > cmdebug.txt", send a test email, and perhaps the captured debug output gives a hint already.

Comment 2 Edward 2020-10-28 11:43:26 UTC
The issue was resolved on my own. Thank you.


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