[Users] [Bug 2834] Filtering to a imap folder sometime fails to run

noreply at thewildbeast.co.uk noreply at thewildbeast.co.uk
Tue Jul 9 04:20:22 CEST 2013


--- Comment #2 from Daniel Mota Leite <higuita at gmx.net> ---
I have more information, but still need to do more tests

i finally manage to get a filtering log of not moved email:

[22:06:10] filtering message (incorporation)
            message file: /home/higuita/.claws-mail/tempfolder/processing/125
            Date: Mon, 08 Jul 2013 23:03:10 +0200
            From: Markus Weich <markus.weich at gmx.de>
            To: sfjro at users.sourceforge.net, aufs-users at lists.sourceforge.net
            Subject: Re: Cannot delete file as normal user
> message does not match
[22:06:10] processing rule 'aufs' [ header "Return-Path" matchcase
"aufs-users-bounces at lists.sourceforge.net" | to_or_cc matchcase
"aufs-users at lists.sourceforge.net" move "#imap/Local-imap/Linux/Software/aufs"
[22:06:10] checking if message matches [ header "Return-Path" matchcase
"aufs-users-bounces at lists.sourceforge.net" ]
[22:06:10] checking if message matches [ to_or_cc matchcase
"aufs-users at lists.sourceforge.net" ]
> message matches
[22:06:10] applying action [ move "#imap/Local-imap/Linux/Software/aufs" ]

So looking at this log, the message should be put in
#imap/Local-imap/Linux/Software/aufs ... yet, it show up in the

the filtering log don't show anything more and the claws cli output also don't
show any helpful message.

i will try next to run with --debug and monitor the network log next, but
either way, the problem doesn't seem to be in the filtering, but on the moving
of the message.

strangely the aufs messages seems to be special, as many of the not moved
messages are from this mailing list... yet other mailing never fail and some
aufs messages are moved successful.

finally, seems that only background fetch have the problem, every time i do a
manual fetch all seems to work.

i'm now using "3.9.2-dirty" , but its the 3.9.2 release

You are receiving this mail because:
You are the assignee for the bug.

More information about the Users mailing list