Version: 1.9.6 (using KDE 3.5.6, Kubuntu (edgy) 4:3.5.6-0ubuntu1~edgy1) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.17-10-generic Everytime i want to send an mail over smtp i get this message from kmail. Sending failed: Internal Error Please send a full bug report at http://bugs.kde.org Unhandled error condition. Please send a bug report. 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 protocol was used: myaccount@mysmtp.xx The passwords/settings were doublechecked. Thank you for your help and time Jan Simbera
Does this happen for all all mails or for one specific mail? Does the mail have an attachment? In that case it might be the same as in bug #97917.
All mails, with or without attachments. Tried several smtp account. All the same.
Server: smtp.seznam.cz I am using: Kubuntu 6.10 Kernel: 2.6.17-10-generic Kde: 3.5.6 from deb http://kubuntu.org/packages/kde-latest edgy main Kmail send account setting: Port: 25 Requires auth: Yes Encryption: none Auth Method: Plain I get asked for the password, after that the Internal error message shows up. It doesn't matter if i press File >> Send Queued Messages or right click on the outbox and use the popup menu. I don't know what other information would be reliable. Tell me if needed. Thanks
Created attachment 19994 [details] My Kmailrc
I don't know if my problem falls under this but I get a similar message when trying to send mail via my ISP's SMTP server. The error message that I get says something about "SASL(-4): no mechanism available". This began happening after upgrading from KDE 3.5 (Mandriva 2008.1) to 4.1 (Mandriva 2009.0).
Jan, do you still have the problem with the current KDE version (4.3) ? @comment #5: your problem seems to be something different, as you do not get the internal error message.
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!