Hide Forgot
I'm using an IMAP service from SpamExperts, where suspected spam is sorted into a folder named CAUGHT. For false negative spam, I must move those messages to a write-only folder, named RELEASE. This has worked in the past. With the latest Evolution released for Fedora 23, I get error messages, and moving fails (message remains in CAUGHT folder). I cannot say exactly which version was first to show the regression. I have been experiencing this for a while, but I was too busy to report it earlier, sorry. These are the versions I have currently installed: evolution-3.18.5.2-1.fc23.x86_64 evolution-data-server-3.18.5-1.fc23.x86_64 evolution-ews-3.18.5-1.fc23.x86_64 evolution-help-3.18.5.2-1.fc23.noarch
I forgot to mention: It works fine with Thunderbird.
Thanks for a bug report. This might be related to yours upstream bug [1], which had been fixed quite some time ago. I created a write-only folder on my Dovecot server and I can successfully copy a message into it using the current development version. I cannot select it, a warning about the folder being write-only is shown in the UI, but the message copy succeeds there. Running evolution as: $ CAMEL_DEBUG=imapx:io evolution shows that the SELECT fails here: > [imapx:A] I/O: 'A00010 SELECT write-only' > [imapx:A] I/O: 'A00010 NO [NOPERM] Permission denied (0.000 secs).' but when I try to copy a message into that folder I receive: > [imapx:A] I/O: 'A00017 SELECT write-only' > [imapx:A] I/O: '* OK [CLOSED] Previous mailbox closed. > A00017 NO [NOPERM] Permission denied (0.000 secs).' > [imapx:A] I/O: 'A00018 APPEND write-only (\SEEN) "13-Nov-2007 15:39:23 +0000" {3844+}' > [imapx:A] I/O: 'Return-Path: ..... > .... > [imapx:A] I/O: '' > [imapx:A] I/O: 'A00018 OK Append completed (0.009 secs).' That is, could you capture a debugging log from the time when you try to copy a message into the write-only folder and paste/attach it here, please? The command will be the same as above: $ CAMEL_DEBUG=imapx:io evolution and it's enough when you wait for the automatic update to finish and copy only the part which begins before you start the copy and ends after the operation is over, while I expect you'd see a similar lines as I pasted above. Copying here an exact error message from the UI will be appreciated too. [1] https://bugzilla.gnome.org/show_bug.cgi?id=740627
Thanks for the instructions. I'll do as soon as I'll receive another false-negative spam.
(In reply to Kai Engert (:kaie) from comment #3) > Thanks for the instructions. I'll do as soon as I'll receive another > false-negative spam. Finally, today, I have new false messages that I can use to test. I started with tracing as instructed. I attempted to move one of the messages "from Caught to Release". This first attempt worked fine, without errors: [imapx:A] I/O: '* OK Still here' [imapx:A] I/O: '' [imapx:A] I/O: 'DONE' [imapx:A] I/O: '' [imapx:A] I/O: 'A00063 OK Idle completed.' [imapx:A] I/O: 'A00066 SELECT Release' [imapx:A] I/O: '* OK [CLOSED] Previous mailbox closed. A00066 NO [NOPERM] Permission denied (0.000 + 0.000 secs).' [imapx:A] I/O: 'A00067 SELECT Caught (QRESYNC (1440088293 9503 6706:6776 (1,45,63 6706,6750,6768)))' [imapx:A] I/O: '* FLAGS (\Answered \Flagged \Deleted \Seen \Draft unknown-0 unknown-1 unknown-2 $has_cal unknown-3) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft unknown-0 unknown-1 unknown-2 $has_cal unknown-3 \*)] Flags permitted. * 71 EXISTS * 0 RECENT * OK [UNSEEN 54] First unseen. * OK [UIDVALIDITY 1440088293] UIDs valid * OK [UIDNEXT 6777] Predicted next UID * OK [HIGHESTMODSEQ 9503] Highest A00067 OK [READ-WRITE] Select completed (0.000 + 0.000 secs).' [imapx:A] I/O: 'A00068 UID MOVE 6765 Release' [imapx:A] I/O: '* VANISHED 6765 A00068 OK [HIGHESTMODSEQ 9504] Move completed (0.009 + 0.000 secs).' [imapx:A] I/O: 'A00069 STATUS Release (MESSAGES UNSEEN UIDVALIDITY UIDNEXT HIGHESTMODSEQ)' [imapx:A] I/O: 'A00069 NO [NOPERM] Permission denied (0.000 + 0.000 secs).' Then I attempted to move the second message, same folders. This time it failed. UI error: Error while Moving messages into folder Release. Error moving messages: No mailbox selected (0.000 + 0.000 secs). Log: [imapx:A] I/O: 'A00070 UID STORE 6759,6764 +FLAGS.SILENT (\SEEN)' [imapx:A] I/O: '* 54 FETCH (UID 6759 MODSEQ (9505)) * 59 FETCH (UID 6764 MODSEQ (9505)) A00070 OK Store completed (0.278 + 0.000 secs).' [imapx:A] I/O: 'A00071 SELECT Release' [imapx:A] I/O: '* OK [CLOSED] Previous mailbox closed. A00071 NO [NOPERM] Permission denied (0.000 + 0.000 secs).' [imapx:A] I/O: 'A00072 UID MOVE 6764 Release' [imapx:A] I/O: 'A00072 BAD No mailbox selected (0.000 + 0.000 secs).'
Thanks for the update. I can reproduce it too. I didn't realize it's the second attempt, I always tried only once. It makes sense now too.
I made the change upstream and assigned it to the previously mentioned: https://bugzilla.gnome.org/show_bug.cgi?id=740627
Thank you. Can the fix be easily applied to Fedora 23? Or should I work around by always restarting evolution, when necessary? Will this be fixed in Fedora 24? Thanks
(In reply to Kai Engert (:kaie) from comment #7) > Can the fix be easily applied to Fedora 23? Yes, here's a scratch build with it: http://koji.fedoraproject.org/koji/taskinfo?taskID=14011493 > Or should I work around by always restarting evolution, when necessary? Easier to switch to a different folder on that same account and then back. > Will this be fixed in Fedora 24? Of course. Once 3.20.3 is released, which is planned on the June 6th, then it'll be added as an update for Fedora 24.
(In reply to Milan Crha from comment #8) > (In reply to Kai Engert (:kaie) from comment #7) > > Can the fix be easily applied to Fedora 23? > > Yes, here's a scratch build with it: > http://koji.fedoraproject.org/koji/taskinfo?taskID=14011493 I confirm the fix works, thanks a lot!