Version: (using KDE KDE 3.5.7) Installed from: Ubuntu Packages OS: Linux I've just run into something annoying when using kmail to try to send mail. I had just authored an e-mail and hit send, but nothing happened. The statusbar didn't indicate any attempt to send at all. I got no error message, nothing. It just wouldn't send. A day later I sent my e-mail through webmail, then noticed in kmail my smtp settings weren't set to "default". After setting it to default sending worked again just fine. I would have expected either a warning or something when attempting to send without any set to default or something. Anyway, just something I noticed that'd be nice to get fixed in kde 4.
>A day later I sent my e-mail through webmail, then noticed in kmail my smtp settings weren't set to "default". What exactly do you mean here? What did you set to "default"?
On Wednesday 13 June 2007 9:52:14 am Thomas McGuire wrote: [bugs.kde.org quoted mail] I hit the "Set Default" button on the kmail accounts settings page, sending tab. Note, I only have one smtp account in that screen. Jeremy
Well, you probably set some option there which was wrong, for example setting the "default send method" to "Send Later". Unless you find out the exact setting that caused the problem, we can only assume that you misconfigured KMail. So please find out what setting caused this problem or close this bug report.
On Wednesday 13 June 2007 10:09:21 am Thomas McGuire wrote: [bugs.kde.org quoted mail] I see, I will see what setting caused the problem. However if I click send queued messages and kmail cant/wont send them I thought it should tell me why or something. I'll see what I can figure out settings wise. Thanks, Jeremy
I'm pretty sure I've seen this in the past. If you have no smtp accounts marked as a default, then sending silently fails; messages simply sit in your outbox forever. at least that's what I remember....
Allen, you are right. I confused the "set as default" and the "defaults" buttons, sorry. So this is the same as in bug 133912. *** This bug has been marked as a duplicate of 133912 ***