Version: (using KDE KDE 3.5.1) Installed from: Compiled From Sources Compiler: gcc 3.4.5 OS: Linux When attempting to send through an exim SMTP server which supports NTLM and requires AUTH, I get the following error: Sending failed: Authorization failed, An error occured during authentication: SASL(-5): bad protocol / cancel: server didn't issue valid NTLM challenge authentication not supported 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. I have just tested the account in Outlook and Outlook Express with their respective SPA checkboxes ticked. They both work fine. From the Exim debug log, it appears that Kmail simply gives up midway through: 30177 Connection request from 71.113.119.162 port 60522 30177 search_tidyup called 12221 host in rfc1413_hosts? yes (matched "*") 12221 doing ident callback 30177 1 SMTP accept process running 30177 Listening... 12221 ident connection to 71.113.119.162 failed: Connection refused 12221 sender_fullhost = [71.113.119.162] 12221 sender_rcvhost = [71.113.119.162] 12221 Process 12221 is handling incoming connection from [71.113.119.162] 12221 checking for IP options 12221 no IP options found 12221 host in host_lookup? yes (matched "*") 12221 looking up host name for 71.113.119.162 12221 DNS lookup of 162.119.113.71.in-addr.arpa (PTR) succeeded 12221 IP address lookup yielded pool-71-113-119-162.sttlwa.dsl-w.verizon.net 12221 gethostbyname looked up these IP addresses: 12221 name=pool-71-113-119-162.sttlwa.dsl-w.verizon.net address=71.113.119.162 12221 checking addresses for pool-71-113-119-162.sttlwa.dsl-w.verizon.net 12221 71.113.119.162 OK 12221 sender_fullhost = pool-71-113-119-162.sttlwa.dsl-w.verizon.net [71.113.119.162] 12221 sender_rcvhost = pool-71-113-119-162.sttlwa.dsl-w.verizon.net ([71.113.119.162]) 12221 set_process_info: 12221 handling incoming connection from pool-71-113-119-162.sttlwa.dsl-w.verizon.net [71.113.119.162] 12221 host in host_reject_connection? no (option unset) 12221 host in sender_unqualified_hosts? no (option unset) 12221 host in recipient_unqualified_hosts? no (option unset) 12221 host in helo_verify_hosts? no (option unset) 12221 host in helo_try_verify_hosts? no (option unset) 12221 host in helo_accept_junk_hosts? no (option unset) 12221 SMTP>> 220 a.msa.seattleserver.com ESMTP Exim 4.54 Tue, 07 Mar 2006 17:13:45 +0000 12221 Process 12221 is ready for new message 12221 smtp_setup_msg entered 12221 SMTP<< EHLO [192.168.0.100] 12221 sender_fullhost = pool-71-113-119-162.sttlwa.dsl-w.verizon.net ([192.168.0.100]) [71.113.119.162] 12221 sender_rcvhost = pool-71-113-119-162.sttlwa.dsl-w.verizon.net ([71.113.119.162] helo=[192.168.0.100]) 12221 set_process_info: 12221 handling incoming connection from pool-71-113-119-162.sttlwa.dsl-w.verizon.net ([192.168.0.100]) [71.113.119.162] 12221 host in pipelining_advertise_hosts? yes (matched "*") 12221 host in auth_advertise_hosts? yes (matched "*") 12221 host in tls_advertise_hosts? no (end of list) 12221 SMTP>> 250-a.msa.seattleserver.com Hello pool-71-113-119-162.sttlwa.dsl-w.verizon.net [71.113.119.162] 12221 250-SIZE 52428800 12221 250-PIPELINING 12221 250-AUTH PLAIN LOGIN CRAM-MD5 NTLM 12221 250 HELP 12221 SMTP<< AUTH NTLM TlRMTVNTUAABAAAABwIAAAAAAAAgAAAAAAAAACAAAAA= 12221 SMTP>> 334 NTLM supported That's where the log stops, and I get the error in KMail. I can create a testing account if you need one.
A workaround is to use http://ntlmaps.sourceforge.net/ at least for konqueror it works fine.
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.