Kmail will not send mail via smtp (not sendmail protocol). It worked previous to installing KDE 3.2.0. It recieves fine. No Errors are produced, it looks like it sent the email, goes to outbox, then sentbox. But never goes to destination. Mozilla mail works fine, sending & receiving. Used: tcpdump -x -X -v -s 0 port 25 and host 12.222.148.04 to produce output of smtp connection and including. Reproducible: Always Steps to Reproduce: 1. Start kmail or kmail -composer 2. Create email and send. 3. Goes to outbox, then sentbox. Looks like went out to destination. 4. Never gets to destination address. Actual Results: Email never goes arrives at destination. Expected Results: For email to go to server via smtp protocol and arrive at destination. Looking at the output of the tcpdump and comparing it to the mozilla mail output find these things: 1) a smtp RSET is being sent when using kmail. So mail gets canceled. 2) you will see a smtp response of 354 in both. So it server is ack that ready to receive the email. 3) a smtp QUIT is being send when using mozilla mail. So it terminates correctly. 4) in kmail smtp MAIL.FROM does not include the SIZE= . It does in mozilla mail and another kmail that I have checked. 5) #4 above looks like it might be the problem. Not sure though, cause why would it not send the size and and also send a RSET if that was the problem. You would think a RSET would have been sent earlier or an error produced. 6) checked the kmail tcpdump for all smtp codes. No error codes (except for RSET) are being produced, so as far as kmail is concerned it sent the mail. Using: Qt: 3.3.0 KDE: 3.2.0 KMail: 1.6
Created attachment 27517 [details] tcpdump of kmail smtp output This is the kmail output of smtp which fails.
Created attachment 27518 [details] tcpdump of smtp mozilla mail This works and email is sent to destination.
Oh, forgot. Have recompiled: kdelibs, kdepim, qt several times and hasn't helped.
I'll test this tonight, but I use the same ISP as you (insightbb.com) and have never had a problem.
Thanks Caleb. I don't think it is the isp though. Works in mozilla and windows. Kmail isn't sending the SIZE= in MAIL.FROM (if that is the problem) and is sending the RSET (doesn't seem to be coming from the isp). It looks like something in kde, but I have exhausted all my ideas.
As a sanity check, did you try deleting the Sending configuration entry in KMail, then create a new one?
New I forgot to mention something. :( Sorry. Have done so much forgot some of the details. Let's see: 1) Deleted kmailrc and restarted kmail, creating identities,... again. 2) Deleted .kde3.2 folder and did same again. 3) Replaced kmailrc with one that worked and recreated the identities,... 4) Compared basic setting in Configure Kmail to another kmail setup and to the Mozilla that worked to make sure had setup correctly. Think that covers it. Will delete just the sending configuration and try again though. Need to cover my bases.
Retested: 1) Just to make sure. Removed any old kmailrc files found in ~/ . They were: ~/.kde3.1.old/share/config/kmailrc ~/.kde3.2/share/config/kmailrc~ ~/Desktop/Trash/kmailrc ~/.kde3.old/share/config/kmailrc ~/.kde.olddave/share/config/kmailr So removed them. Restarted kmail. Did notice one change: A) This time while watching the tcpdump it still sent a RSET, but this time isp answered with 250.ok, then kmail sent a QUIT. That didn't happen before on the previous test. So does seem like something new. 2) To further the above test. Moved all the old .kde folders that had already renamed to a temp folder and deleted them from ~/ . They had already been renamed as: .kde.backup .kde.olddave .kde2.old .kde3.1.old .kde3.old Then deleted the send information from Kmail. Restarted and same thing: ie (RSET, 250.ok, then QUIT) 3) Then to finalize this test. Deleted kmailrc left in ~/.kde3.2/share/config and recreated the account. Same thing again. :(
After doing a little research. Thinking might need to look into kio_smtp.so . So going to try remerging kdebase to recomile it and see if fixes problem.
Remerging kdebase 3.2.0 doesn't appear to have helped either.
One additional thing noticed on the output. The tcpdump of kmail shows that just before the RSET that the server didn't respond with a 'id' (think message recipt). Mozilla does and another kmail does (slightly different than the mozilla one though). Maybe because kmail isn't getting a recipt it resets the connection?
I would recommend filing a bug at bugs.kde.org...sounds like an issue deep in the code.
Will do Caleb.
I confirm this bug. I just installed KDE 3.2.1 and in my case kmail doesn't send any packet out at all, it just immediately says "Failed to send (some) queued messages". Previous kmail version (from KDE 3.2.0) was working with no problems at all. I didn't see any mention on bugs.kde.org, did you already submit it Decibels?
Yes I did: http://bugs.kde.org/show_bug.cgi?id=77853 Did you look at the tcpdump of kmail on here? In this particular case. It smtp (or I guess kio_smtp) is sending a RSET. The only thing can figure so far is that in MAIL.FROM it isn't sending a size. ??? Not sure at this moment if it. Mainly because, why would it do that if it send it with no SIZE and doesn't look like the server is complaining. So don't know. Tried getting debug output from kio_smtp, (emerged kdebase and kdepim) with debug enabled and everything seems to output debug code, but kio_smtp. And this is on a system that works. So seem unable to find a way to produce anymore debug code as to what is happening except for the tcpdump. According the doc I found (seems sparse out there in kdeland how to debug), you should be able to produce it with kdebugdialog and 7112 [kio_smtp], but kdebugdialog will never give me 7112 or kio_smtp under any other number for that matter. At my end. Can't do much if you can't debug.
Also, Note, there is NO Error produced with this problem having. Lot of times kmail will not send a message if another message is in outbox and won't go. I find this if I bounce a message sometimes and it won't send. It blocks any others from sending also. Have to delete the offending message. Check your tcpdump the way I did and see what your output is.
Maybe a stupid one, but do you have any 3.1 libraries laying around? In this case, what does your KDEDIRS variable contain? (it should only contain /usr), KDEDIR should contain /usr/kde/3.2
FIXED!!! Thanks. Here is what it was. You lead me into looking further. I was actually working on this for someone else. I have kde 3.2.1, they had 3.2.0 After looking at the /etc/env.d files. Deleted some old 49kdepaths-3.1.4 and 49kdepaths-3.1 they had laying around there. No help. Checked the 99kde-env and it said: KDEDIRS=/usr CONFIG_PROTECT=/usr/share/config My 3.2.1 system though had: KDEDIRS=/usr/kde/3.1 CONFIG_PROTECT=/usr/share/config So would appear they had it correct, mine worked fine and had already unmerged all kde's less than 3.2.1 ??? Tried changing theirs to same as mine and nogo. Don't know why mine was like that. Everything works?? Then thought already told them to unmerge all kde's less than 3.2.0. Checked and was still there, so unmerged them. Another weird thing was that I unmerged mine in one swoop. I had to unmerge each kde package individually on theirs. emerge --unmerge \<kde-3.2.0 Did that for kdelibs, kdebase, kdepim,.... all the kde stuff. Had them send a email with kmail while watched the tcpdump. Knew it was going to work the minute saw it. Sent a SIZE with MAIL.FROM this time and no RSET send. Email was sent to them, also sent one to me and went thru also. So works, it was having 3.1.4 still installed that was the problems !! Now to the question why didn't my /etc/env.d/99kde-env contain the correct information? I unmerged kde's less than 3.2.0 when first installed it cause it doesn't play nice with previous kde versions. Looked at a few post on the forum and couldn't decide which was correct way to have it, so opted to change both ours to: KDEDIRS=/usr/kde/3.2:/usr CONFIG_PROTECT=/usr/share/config I would close this bug out, but not sure I am allowed to. Plus don't know if you want to look into why the env was not changed correctly.
Great, btw. just unmerging the kde package will not unmerge anything usefull as the kde package does not provide files. Unfortunately you really need to unmerge all kde packages manually using "emerge -P kdelibs" etc. Btw. A grep on KDEDIR in my /etc/env.d gives the following working result: /etc/env.d/56kdedir-3.1.5:KDEDIR=/usr/kde/3.1 /etc/env.d/57kdedir-3.2.1:KDEDIR=/usr/kde/3.2 /etc/env.d/99kde-env:KDEDIRS=/usr the startkde script does correct the KDEDIR variable when starting kde.
