Bug 185934 - KMail almost always says it can't send (even though it can)
Summary: KMail almost always says it can't send (even though it can)
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.11.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-02 10:05 UTC by Mark Summerfield
Modified: 2015-04-12 10:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Summerfield 2009-03-02 10:05:54 UTC
Version:           1.11.0 (using 4.2.00 (KDE 4.2.0), 4.2.0-15.fc10 Fedora)
Compiler:          gcc
OS:                Linux (i686) release 2.6.27.15-170.2.24.fc10.i686

Most times when I try to send an email I get an error message box:

Sending failed:
smtp.googlemail.com
The message will stay in the 'outbox' folder until you either fix the problem (e.g. a broken address) or remove the message from the 'outbox' folder.
The following transport was used:
 googlemail

This happens when there is no problem at all with the email I'm sending as proved by the fact that if I do File|Send almost always the message is sent. (Sometimes I get the error message box again, but that's rare.)
Comment 1 Jaime Torres 2009-03-07 12:43:26 UTC
My gmail smtp server is smtp.gmail.com not smtp.googlemail.com, And I've never seen this message.
Comment 2 Mark Summerfield 2009-03-08 08:32:41 UTC
In the UK we use googlemail not gmail; I believe this is because gmail was already taken. But in any case what difference does it make? I've been using the exact same setup for several years with prior versions of KMail & only since Fedora switched to this new version of KMail has this problem arisen.
Furthermore KMail is simply giving an incorrect error. If I try sending the message again, it gets sent (usually at the first retry, sometimes at the second), so the error message is spurious. Of course it may be that the new KMail is using a shorter timeout?
Comment 3 Laurent Montel 2015-04-12 10:20:21 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.