Bug 294140

Summary:	KMail gives strange error after sending IMAP/SMTP mail
Product:	[Applications] kmail2	Reporter:	francescm <francesc.montserrat>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	francesc.montserrat, montel
Priority:	NOR
Version:	4.8
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description francescm 2012-02-15 11:33:59 UTC

Version:           4.8 (using KDE 4.8.0) 
OS:                Linux

This error was initially files as bug 284539, but still persists, apprently...

I had some small difficulties last week with my Akonadi server (accidentally deleted some MySQL files). However, with the help of one of the forum members I had that solved. Of course, KMail needed re-configuring after this incident. Ever since, whenever I send a mail, I get the following error message:

[QUOTE]
Kmail: sending email failed: Sending succeeded but failed to finalize message. Unknown error. (no items found)
[/QUOTE]

The strange thing is that KMail actually DOES manage to send the complete mail but keeps the mail in the outbox. The sent mail arrives without any discernible errors, but a copy (I assume) is kept in the outbox and reported to be unable to be "finalized", whatever that may mean...it's not that it's hindering me in any way, but I wonder every time whether the mail has actually been sent or not.

Reproducible: Always

Steps to Reproduce:
Send mail, any mail...form KMail

Actual Results:  
mail is sent, described error message shows, mail is saved in outbox and stays there

Expected Results:  
not show the error message, and remove mail from outbox

Comment 1 Laurent Montel 2012-02-16 09:01:56 UTC

"Kmail: sending email failed: Sending succeeded but failed to finalize message.
Unknown error. (no items found)"
are your sure from message ? I can't find this message in source code

Comment 2 francescm 2012-02-17 10:30:28 UTC

Dear Laurent,

Yes, I'm sure this is the message that is given when I send a mail. 
Moreover, for one reason or the other KMail now also starts mailing 
random people constantly (wihtout me doing anything), but with empty 
messages, using the outgoing smtp server (a gmail account) as a sender 
address and not my work mail address.

I REALLY like Kontact for the functionalities it has, but at the moment 
I use Thunderbird to mail, because I do not want my colleagues to 
receive three, four, five empty messages from me, from another account.
Again, I REALLY like KMail, but Thunderbird has never given me ANY 
problem, while Kontacvt starts to annoy me a bit.

I hope you/somebody at KDE might be able to help me with this. Please go 
easy, I'm quite new to Linux :)

best regards,
Francesc

On 02/16/2012 10:01 AM, Laurent Montel wrote:
> https://bugs.kde.org/show_bug.cgi?id=294140
>
>
> Laurent Montel<montel@kde.org>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |montel@kde.org
>
>
>
>
> --- Comment #1 from Laurent Montel<montel kde org>   2012-02-16 09:01:56 ---
> "Kmail: sending email failed: Sending succeeded but failed to finalize message.
> Unknown error. (no items found)"
> are your sure from message ? I can't find this message in source code
>

Comment 3 francescm 2012-02-21 08:30:12 UTC

Dear Laurent, 

Not to breathe down your neck, but do you have any news on the abovementioned bug ? I have tried KMail again, and the error message is still given. I was just wondering if anything was known...

Comment 4 Denis Kurz 2016-09-24 18:22:42 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 5 Denis Kurz 2017-01-07 22:31:44 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.