Bug 279303 - KMail2 can't send any email from any account
Summary: KMail2 can't send any email from any account
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 1.99.0
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 15:58 UTC by Christian Trippe
Modified: 2012-01-28 18:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Trippe 2011-08-03 15:58:11 UTC 
Version:           1.99.0 (using KDE 4.7.0) 
OS:                Linux

Trying to sent an email with Kmail2 from KDE 4.7 does not work. The mail only goes to the outbox folder. I get no error message. This worked fine with kmail2 from KDE 4.6.

I use the mysql driver for akonadi.

A similar/the same bug was reported at https://bugzilla.novell.com/show_bug.cgi?id=709262 where the report there says it would work for him when having 
[%General]
Driver=QSQLITE3
in ~/.config/akonadi/akonadiserverrc

Reproducible: Always

Steps to Reproduce:
Try to sent an email with kmail2 from KDE 4.7. I can reproduce this with old and new configurations for a smtp server.

Actual Results:  
kamil2 does not sent mails but only moves them to the outbox folder.

Expected Results:  
kmail2 sending mails

OS: Linux (x86_64) release 2.6.37.6-0.7-desktop
Compiler: gcc
Comment 1 Christian Trippe 2011-08-05 16:04:11 UTC 
I could reproduce this for some time, even reboots did not help. But after having restarted the "Mail Dispatcher Agent" once, it still works after a reboot.
So feel free to close the bug if you wish.
Comment 2 mattm3a 2011-08-25 17:38:52 UTC 
After upgrading KDE 4.6.0 to 4.7.0, I encountered the same behavior of mail collecting in the outbox without being sent. 

How did you restart the Mail Dispatcher Agent?
Comment 3 mattm3a 2011-08-25 19:25:47 UTC 
This seems to have corrected itself after reboot.
Comment 4 Victor Mataré 2011-09-20 12:34:49 UTC 
Bug #276077 is probably related...
Comment 5 Christian Trippe 2012-01-28 18:51:37 UTC 
I never had this problem again.