Bug 195423

Summary: Unable to send mail with a spamhaus enabled sever
Product: [Applications] kmail Reporter: Dalibor Karlović <dado>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version: 1.11.3   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Dalibor Karlović 2009-06-06 10:34:45 UTC
Version:           1.11.3 (using KDE 4.2.3)
OS:                Linux
Installed from:    Fedora RPMs

I'm using qmail with rblsmtpd using spamhaus.org. My SMTP setup is:

TLS
SMTP-AUTH
CRAM-MD5
Store password (if it matters)

When sending mail, I get:

Sending failed:
Invalid SMTP response (0) received.
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:
 my.transport

which wasn't really helpful. What was weird is that it worked at work, but not from home. So, I tried to telnet to my host's 25 and keep getting:

451 http://www.spamhaus.org/query/bl?ip=X.X.X.X

where X.X.X.X is my current IP. Reading spamhaus' info:

"Important: If you are using any normal email software such as Outlook, Entourage, Thunderbird, Apple Mail, and you are being blocked by this Spamhaus PBL listing when you try to send email, the reason is simply that you need to turn on "SMTP Authentication" in your email software settings (Tools : Accounts : Properties : Outgoing Mail Server : check "My server requires authentication")."

If I disable rblsmtpd, kmail sends mail just fine. So, the problem is: either my server is misconfigured (possible, it was done through Plesk) or Kmail doesn't handle this case well. In any case, that error message mentioned could use a facelift, it didn't give me much to go on.
Comment 1 Dalibor Karlović 2009-06-11 20:14:08 UTC
It was indeed a misconfigured server which I've confirmed by installing Thunderbird. The difference is, Thunderbird gave me the content of the error message it got from the SMTP right inside the error message it displayed to me so I knew right away it was something wrong there.