Bug 8579 - kmail won't send e-mail after upgrade
Summary: kmail won't send e-mail after upgrade
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords: PATCH, Triaged, UPSTREAM
Depends on:
Blocks:
 
Reported: 2013-01-02 18:16 CET by David Walser
Modified: 2013-11-22 16:54 CET (History)
3 users (show)

See Also:
Source RPM: kdepim4-4.8.5-1.2.mga2.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2013-01-02 18:16:07 CET
After upgrading my dad's machine from Mageia 1 to Mageia 2 a couple days ago, he was unable to send e-mails, as they would just get stuck in the Outbox.

Checking ~/.xsession-errors, I saw this error message:
kmail2(####)/kdepimlibs (mailtransport): Could not access Outbox.

where the #### was a PID.  After some Googling, I think it's this bug:
https://bugs.kde.org/show_bug.cgi?id=254388

It sounds like there's a fix in SVN for it.

I also found a workaround, running the command "akonadictl restart" allowed the mails to be sent.  That was mentioned in the last comment of these bugs:
https://bugs.kde.org/show_bug.cgi?id=252114
https://bugs.kde.org/show_bug.cgi?id=290774

I also found a couple other workaround suggestions that involve "akonadiconsole" but I don't know what that is.  One was to restart the Mail Dispatcher Agent, and the other was to remove the MTA and readd it:
https://bugs.kde.org/show_bug.cgi?id=192046
http://forums.gentoo.org/viewtopic-p-6717593.html

So far, the "akonadictl restart" workaround seems to only be needed once, as it is working now, even after a reboot.
David Walser 2013-01-02 18:16:15 CET

CC: (none) => nicolas.lecureuil

David Walser 2013-01-02 18:16:21 CET

CC: (none) => balcaen.john

Comment 1 David Walser 2013-01-07 17:28:58 CET
Had another problem sending e-mail yesterday morning.  Hitting Send would just cause the whole composer window to get grayed out, but the message would not be sent or copied to the Outbox.  Logging out of KDE and back in fixed it.  These messages appeared in ~/.xsession-errors around the time of the problem (I changed the domain name of our isp):

Query failed: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." 
QStringList Akonadi::NepomukSearch::search(const QString&) Calling blockingQuery() failed! 
akonadi_pop3_resource_0(2761)/kio (KIOJob) KIO::TransferJob::slotData: mimeType() not emitted when sending first data!; job URL = KUrl("pop3://walser%40our-isp.net@pop.our-isp.net:110/index") data size = 0 
akonadi_pop3_resource_0(2761)/kio (KIOJob) KIO::TransferJob::slotData: mimeType() not emitted when sending first data!; job URL = KUrl("pop3://walser%40our-isp.net@pop.our-isp.net:110/uidl") data size = 0 
akonadi_pop3_resource_0(2761)/kio (KIOJob) KIO::TransferJob::slotData: mimeType() not emitted when sending first data!; job URL = KUrl("pop3://walser%40our-isp.net@pop.our-isp.net:110/download/") data size = 0
Samuel Verschelde 2013-09-05 16:02:46 CEST

Keywords: (none) => PATCH, Triaged, UPSTREAM
CC: (none) => stormi
Assignee: bugsquad => nicolas.lecureuil

Comment 2 Manuel Hiebel 2013-10-22 12:20:44 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 3 David Walser 2013-11-22 16:54:08 CET
Closing this now due to Mageia 2 EOL.

http://blog.mageia.org/en/2013/11/21/farewell-mageia-2/

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


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