+++ This bug was initially created as a clone of Bug #489648 +++ Running a not-very-recent trunk build... Today, every few minutes, I get a pair of Alert dialogs. The first says: > Alert > COPY failed The second says: > Alert > The current command did not succeed. The mail server responded: [ALERT] COPY failed. I suspect that these are coming from the mail filters' attempts to copy messages to other folders. These alerts really trouble me because: 1) They do not tell me any useful information such as: - the name of the server on which the copy operation failed - the name of the destination folder to which the copy was being attempted - the name of the source folder from which the copy was being attempted - anything about the mail message itself, subject, From, date ... nothing - what has happened to the message as a result of the failure. Lost? left in some source folder? If these failures are indeed happening as a result of message filters attempting to move messages to other folders, then there should be a message in the filter log saying - a filter action failure occurred - what filter was trying to execute, - what message it was trying to copy - what happened to the message (e.g. left in Inbox, or something) These useless alerts are chicken little, saying "the sky is falling", but providing no information that can be used for any purpose. This bug is NOT asking that the underlying cause of the alerts be fixed. Bug 489648 is for that. This bug is about making the alerts informative and useful. One should not need to take extra steps, rerunning the program with extra environment variables set to set an informative statement of the information outlined above.
aceman/filterman, do you think this is still an issue?
I don't know, I do not use IMAP so I have never seen this. But I'd expect if the copy is produced via a filter, it may be quite difficult to show anything filter related in the message. I'd assume the filter just copies the messages locally and then some new async task uploads them to the server, which may not have enough info how the messages got into that folder in the first place. But I could be wrong. Also notice bug 489648 is closed. Even if the message is not related to filters, it should be improved, but I don't know what myself (as I do not use IMAP). I don't know what it should tell the user to do.
You need to log in before you can comment on or make changes to this bug.