Bug 323858 - Reveive error message after successfully sending email
Summary: Reveive error message after successfully sending email
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 4.11
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-21 19:31 UTC by Edward Reiss
Modified: 2017-01-07 21:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Edward Reiss 2013-08-21 19:31:01 UTC
When I sent email via a DAVMail relay, the message is sent successfully but I receive the following message:

TAG: Store failed, server replied: A000134 BAD Command Argument Error. 11 

The "Sent Mail" folder for the identity used for the DAVMail relay is set to the local folders Sent-Mail folder.

If I disable the sent mail folder within the identity, I get the following error:

Failed to store result in item. Item query returned empty result set

This worked flawlessly before the upgrade to 4.11 from 4.10.

Reproducible: Always

Steps to Reproduce:
1. Create message
2. Send message
3. Receive notifications of successfully sent message along with error UNLESS sent mail folder is disabled, in which case only an error message is sent even though the message was successfully sent.
Actual Results:  
Receive errors regarding successfully sent message.

Expected Results:  
No error messages.

This was an upgrade from KDE 4.10.
Comment 1 Denis Kurz 2016-09-24 18:20:47 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 2 Denis Kurz 2017-01-07 21:30:23 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.