[sylpheed:36533] Re: Mail filters don't work reliably

Thu Mar 9 05:13:23 JST 2017

Hi,

sorry for the big delay...

Here are the two log files. As I described in my last mail, each log
should contain a message bypassing the filter:

> When the first message bypassed the filter, I quit Sylpheed, and
> started it again in debug mode. I clicked on the INBOX with that
> message, and so it automatically fetched new mails again (this happens
> when you click on an INBOX in Sylpheed). It fetched only one, namely
> the second message which bypassed the filter. Then I quit Sylpheed
> again, and restarted it in debug mode. Selecting the two messages and
> applying the filters manually via "Tools/Filter selected messages"
> worked fine.

In any case, the first (big) log file should contain (at least) one
such message.

Unfortunately, I have problem identifying the message within the log
file. When I view the source code of the first message, at the top it
says:

Received: (qmail 3203 invoked from network); 1 Mar 2017 12:34:56 -0000

I thought that number 3203 would identify the mail on my mail server,
but it does not appear in the log.

Sometimes in the log there's a line like:
[13:30:18] IMAP4> 30805 UID FETCH 1:* (UID FLAGS)

Here, 30805 looks like it identified the mail. But I guess that in turn
does not appear in the message source...

Does anybody have a suggestion where I could go from here?

Thanks!

Merlin

On Wed, 1 Mar 2017 16:34:54 +0100
Merlin Büge <merlinbuege at web.de> wrote:

> 
> So, it just happened again today two times in row, with these two
> messages:
> https://lists.debian.org/debian-user/2017/03/msg00012.html
> https://lists.debian.org/debian-user/2017/03/msg00013.html
> 
> As usual, I still had Sylpheed checking my mails every 5 minutes.
> I started Sylpheed via 'sylpheed --debug > sylpheed.log on 24/02/2017.
> In the meanwhile my laptop was suspended several times (always
> suspend-to-RAM), and the last resume from suspend was about 10 hours
> before the two mails bypassed the filter.
> 
> When the first message bypassed the filter, I quit Sylpheed, and
> started it again in debug mode. I clicked on the INBOX with that
> message, and so it automatically fetched new mails again (this happens
> when you click on an INBOX in Sylpheed). It fetched only one, namely
> the second message which bypassed the filter. Then I quit Sylpheed
> again, and restarted it in debug mode. Selecting the two messages and
> applying the filters manually via "Tools/Filter selected messages"
> worked fine.
> 
> 
> From the first big log:
> (Note that the last 1400 lines start a few minutes before the two
> messages were received.)
> 
> $ tail -n 1400 sylpheed_debug_log_from_20170224_to_20170301.log |
> grep filter inc_remote_account_mail(): filtering IMAP4 INBOX
> filter_junk_rule_create: junk folder: #mh/Mailbox/junk
> inc_remote_account_mail(): INBOX: 0 new, 0 filtered
> inc_remote_account_mail(): filtering IMAP4 INBOX
> filter_junk_rule_create: junk folder: #mh/Mailbox/junk
> inc_remote_account_mail(): INBOX: 0 new, 0 filtered
> inc_remote_account_mail(): filtering IMAP4 INBOX
> filter_junk_rule_create: junk folder: #mh/Mailbox/junk
> inc_remote_account_mail(): INBOX: 0 new, 0 filtered
> Writing filter configuration...
> 
> 
> From the second log:
> 
> $ cat sylpheed_debug_log_20170301.log | grep filter
> Reading filter configuration...
> Reading /home/merlin/.sylpheed-2.0/filter.xml
> Writing filter configuration...
> 
> 
> I'm somehow uncomfortable with posting the full log here, as it may
> contain various sensitive information. I will post them after editing.
> 
> Normally, when I filter catches a message, the following appears in
> my log (in fact this cought a message from the debian-user ML just 10
> minutes before them two bypassing my filter):
> 
> filter-log: filter_match_header_cond: HEADER [Cc], str_value:
> [debian-user] filter-log: filter_apply_msginfo: rule [debian lists]
> matched filter_action_exec(): move: dest_folder = #imap/- at -/Debian
> 
> As you can see this did not appear in the above log excerpt.
> 
> 
> Please tell me if I should provide more information! (Logs are coming)
> 
> 
> Thanks!
> 
> Merlin
> 
> 
> 
> 
> 
> 
> On Sat, 25 Feb 2017 02:46:18 +0100
> Merlin Büge <merlinbuege at web.de> wrote:
> 
> > On Sat, 25 Feb 2017 12:02:47 +1100
> > Keith Bainbridge <keithrbau at gmail.com> wrote:
> > 
> > > G'day all
> > > 
> > > If this only happens when sylpheed starts, what happens if you
> > > turn off the 'Download mail at start up' option?
> > 
> > For me, it does not only happen when sylpheed starts up. Also, I
> > don't have the option 'Download mail at start up' enabled (and
> > never had).
> > 
> > But I have sylpheed checking for new mails every 5 minutes. I will
> > try to disable that option once I reproduced the issue.
> > 
> > 
> > Regards,
> > 
> > Merlin
> > 
> > 
> > > 
> > > 
> > > 
> > > Keith Bainbridge
> > > 
> > > 0447667468
> > > 
> > > keithrbau at gmail.com
> > > 
> > > Sent from my APad
> > > 
> > > On 25 Feb 2017 11:40, "Merlin Büge" <merlinbuege at web.de> wrote:
> > > 
> > > On Fri, 24 Feb 2017 17:27:36 -0600
> > > Rich Coe <rcoe at wi.rr.com> wrote:
> > > 
> > > <snip>
> > > 
> > > > I agree that the easiest way to diagnose the issues is to look
> > > > at the debug messages when it happens.
> > > 
> > > I'm running Sylpheed now from CLI via 'sylpheed --debug >
> > > sylpheed.log' and waiting for the issue to appear again.
> > > 
> > > 
> > > > I have some early created rules that matched only
> > > > {From}/{To}/{CC} based on username like your debian-user.  All
> > > > my later rules, which I may have created with the 'create
> > > > filter rule Automattically' feature, and then edited, include
> > > > the full email address: {From} {contains}
> > > > someuser at some.host.com This also prevents filtering out false
> > > > postives if some one has 'debian-user' as some other part of
> > > > the {From} or {To} field.
> > > 
> > > Good idea.
> > > 
> > > 
> > > > Another nice thing about the 'create Automattically' feature is
> > > > when you pick a different field than the one the tool picked, it
> > > > auto-fills the value in.  A number of lists use the {List-Id}
> > > > attribute, which makes it nicer to match from the mail list than
> > > > listing multiple entries for {To}, {CC}, {From}, etc.
> > > 
> > > Thanks a lot. I didn't know about the 'List-Id' header field.
> > > After diagnosing the current filter issue I'll use that.
> > > 
> > > 
> > > > Another thing to try is to look at the failing message with the
> > > > View>Message Source option, and also pull up the filter rules
> > > > View>from
> > > > {sylpheed-home}/filter.xml and see if any of the rules from the
> > > > top down match something before your 'debian-user' or some other
> > > > rule.
> > > 
> > > I did that, and -- despite my rules being set up kind of sloppy,
> > > e.g. 'someuser' instead of 'someuser at domain.tld' -- the filter
> > > logic itself seems not to be the problem here.
> > > 
> > > I'm curious about what the debug log will give.
> > > 
> > > 
> > > Regards,
> > > 
> > > Merlin
> > > 
> > > 
> > > 
> > > --
> > > Merlin Büge <merlinbuege at web.de>
> > 
> > 
> > -- 
> > Merlin Büge <merlinbuege at web.de>
> 
> 
> -- 
> Merlin Büge <merlinbuege at web.de>

-- 
Merlin Büge <merlinbuege at web.de>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sylpheed_debug_log_20170301_big_clean.log
URL: <http://www.sraoss.jp/pipermail/sylpheed/attachments/20170308/464eff34/attachment-0002.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sylpheed_short_clean.log
URL: <http://www.sraoss.jp/pipermail/sylpheed/attachments/20170308/464eff34/attachment-0003.ksh>