Version: KMAIL1.5 (using KDE KDE 3.1.1) Installed from: RedHat RPMs OS: Linux Hello! When kmail try a smtp connection to a "Merak Mail server", if the server return this: 220-mail.BlahBlah.fr ESMTP BlahBlah Mail Server; Sun, 20 Jul 2003 17:42:40 +0100 220-********************************************************************* 220-* BlahBlah Secure Mail Server * 220-* * 220-* All connections are logged! * 220-* This server employs anti-virus and antis-pam technology * 220 ********************************************************************* The smtp connection fail because it check the last line, and not the first. Thank you for your very good work. Denis Moinel
Perhaps the response from the server is in a bad format. The RFC821 doesn't be very precise on this multiline format. (sorry for my english.)
RFC 2821 doesn't clarify much either, but it says that the official domain name must be the first word after the 220 code (I'd say it's the first line). The thing is, it also lists the Greeting line with "220 " in ABNF.
RFC2821 Says this: _________________ The format for multiline replies requires that every line, except the last, begin with the reply code, followed immediately by a hyphen, "-" (also known as minus), followed by text. The last line will begin with the reply code, followed immediately by <SP>, optionally some text, and <CRLF>. As noted above, servers SHOULD send the <SP> if subsequent text is not sent, but clients MUST be prepared for it to be omitted. For example: 123-First line 123-Second line 123-234 text beginning with numbers 123 The last line In many cases the SMTP client then simply needs to search for a line beginning with the reply code followed by <SP> or <CRLF> and ignore all preceding lines. In a few cases, there is important data for the client in the reply "text". The client will be able to identify these cases from the current context. __________________ Others SMTP clients like "MS outlook*, Eudora, The bat..." work fine in this configuration.
That's why it's confusing. The RFC says there might be a few cases in which important data is in the "text". The 220 reply is one of those cases. But it does not say whether the important data should be in the first line or the one with the space (the last). It is my understanding of the RFC that it's the first line.
hrm... is the original poster SURE that it is the multiline 220 reply that cuases the problem? and if so, what makes you think that? what is the exact error msg that KMail gives you in the error dialog? the reason i ask is that looking at the SMTP code in 3.1, it doesn't actually parse the 220 reply at all. all it does is recv it and then make sure that it starts with a valid number. it then immediately goes into the EHLO/HELO exchange.. would it be possible to get a complete log of the client/server exchange using a tool like ethereal or some other (readable) TCP dumper?
Created attachment 2340 [details] ethereal capture hello. When the provider remove the multiline reply, kmail work fine. I have make others tests: The error msg is: Reponse SMTP recue non valable: "*****************" you can find in attachement a capture of error message (jpeg) and a complete ethereal log made with ethereal 0.9.8 You can also make tests on email testkmail@moinel.org smtp server : mail.moinel.org pop3 server :mail.moinel.org If need, I can give you a valid password for the tests (in private)
Info: the attachement "ethereal capture" is a tgz archive.
Please check with 3.2 alpha. Works for me (which means I can use "check what the server supports" in KMail's configure dialog and the result (debug output from the slave) looks kosher.
*** Bug 62477 has been marked as a duplicate of this bug. ***
Works for me.
*** Bug 72955 has been marked as a duplicate of this bug. ***