[kdepim-users] [Probably found] Re: Please check your maildir stores for 1-byte sized files

Sat May 4 11:55:45 BST 2013

Am Freitag, 3. Mai 2013, 09:30:15 schrieb O. Sinclair:
> On 02/05/2013 20:47, Martin Steigerwald wrote:
> > Am Donnerstag, 2. Mai 2013, 17:34:05 schrieb Martin Steigerwald:
> >> Hi!
> >> 
> >> I stumpled over what I think is a possible data loss again with
> >> my most recent, I think pretty simple setup with KMail and filter
> >> configuration from scratch:
> >> 
> >> Bug 319226 - produces 1-byte-sized files on failed move attempts
> >> while filtering http://bugs.kde.org/319226
> >> 
> >> I saw it produce three more of these 1-byte-sized files
> > 
> > […]
> > 
> >> I still hope its just happening for me and its somehow related to
> >> filter rules, but please sanity check your maildir stores.
> > 
> > I suspect its really something with my filter rules, particularily
> > the CRM114 spam filtering integration rules I made.
> > 
> > So it may really just happen to me.
> > 
> > I removed those CRM114 rules now and will see what happens.
> > 
> > Still it would be reassuring to hear from some POP3 users that they
> > do not have one byte sized files in their local maildirs while
> > using (local) filtering themselves.
> 
> I find none and I have been using CRM114 though it seems to be botched
> in Kubuntu 13.04 (not first time, worked nicely in 12.10 though). Have
> also removed CRM114 as it simply does not seem to work..

Thanks!

Can you recall the exact filter fules you used?

I think it would be helpful to compare them with the ones I have posted to the 
bug report above.

After having switched of my CRM114 spam filter rules I did not see further one-
byte sized files. So I´d like to find out whats different with your rules.

I am quite sure my CRM114 on Debian Sid with still crm114 package version 
20100106-3 works just fine. It did so a week ago with KMail 1. It never 
produced one-byte sized files or other erratic results as far as I can see.

For comparison on list here are my CRM114 filter rules. On looking at the filter 
rules while pasting them here, I found a possible issue with them explaining 
what I was seeing. But still, I´d like to compare with your filter rules, 
before trying again, as its quite tedious to restore crunched mails from POP3 
server.

Pipe through crm114 to find if its spam:

[Filter #0]
Applicability=1
AutomaticName=false
ConfigureShortcut=false
ConfigureToolbar=false
Enabled=true
Icon=system-run
StopProcessingHere=false
ToolbarName=crm114: Auf Spam prüfen
accounts-set=akonadi_pop3_resource_0
action-args-0=crm -u ~/.crm114 mailreaver.crm
action-name-0=filter app
actions=1
apply-on=check-mail,manual-filtering
contentsA=262144
fieldA=<size>
funcA=less-or-equal
identifier=BfESlQkyajcYUgNg
name=crm114: Auf Spam prüfen
operator=or
rules=1

Set status of mails crm114 marked in rule #0 to spam and filter them to spam 
folder:

[Filter #1]
Applicability=0
AutomaticName=false
ConfigureShortcut=true
ConfigureToolbar=false
Enabled=true
Icon=system-run
StopProcessingHere=true
ToolbarName=crm114: Spam ausfiltern
action-args-0=Lokale Ordner/Papierkorb/Spam
action-args-1=P
action-name-0=transfer
action-name-1=unset status
actions=2
apply-on=check-mail,manual-filtering
contentsA=SPAM.*
contentsB=^[2345]
fieldA=X-CRM114-Status
fieldB=X-GMX-Antispam
funcA=regexp
funcB=regexp
identifier=5t65LS2QA9PYTGUe
name=crm114: Spam ausfiltern
operator=or
rules=2

Filter mails crm114 marked as unsure to unsure folder:

[Filter #2]
Applicability=0
AutomaticName=false
ConfigureShortcut=false
ConfigureToolbar=false
Enabled=true
Icon=system-run
StopProcessingHere=true
ToolbarName=crm114: Unsicher ausfiltern
action-args-0=Lokale Ordner/Papierkorb/Unsicher
action-name-0=transfer
actions=1
apply-on=check-mail,manual-filtering
contentsA=UNSURE
fieldA=X-CRM114-Status
funcA=contains
identifier=ui7f6pceYEB2uWgx
name=crm114: Unsicher ausfiltern
operator=or
rules=1

And add the send manual filters for telling crm114 whether a mail is spam or 
good. I had them at the end cause with apply-on=manual-filtering and 
StopProcessingHere=true any Ctrl+J ended on them and other mailing list based 
filters after it did not work. Now, after having looked at my original KMail-1 
based filters again, I think I´d just omit uncheck "apply-on=manual-filtering" 
option.

[Filter #39]
Applicability=0
AutomaticName=false
ConfigureShortcut=true
ConfigureToolbar=true
Enabled=true
Icon=mail-mark-notjunk
StopProcessingHere=true
ToolbarName=crm114: Als Gut einstufen
accounts-set=akonadi_pop3_resource_0,akonadi_maildir_resource_0
action-args-0=H
action-args-1=crm -u ~/.crm114 mailreaver.crm --good
action-args-2=rm -u ~/.crm114 mailreaver.crm

GOSH! That rm -u should be a "crm", a copy and paste error. I think I noticed 
an error like this and fixed it.

That might explain what I am seeing.

action-name-0=unset status
action-name-1=execute
action-name-2=filter app
actions=3
apply-on=manual-filtering
identifier=XOzgjB9dqty8V2Zn
name=crm114: Als Gut einstufen
operator=all
rules=0

Still that filter was after all mailing list based filters and the one-byte 
sized files where sorted into mailing lists by previous filters which have 
StopProcessingHere.

I will look at newer revisions of my filter rules.

And well, I also had one-byte sized files with imported filter rules from 
KDEPIM-1, which were not having this "rm" in it. Just checked it.

But still:

merkaba:/tmp> echo "test" > test
merkaba:/tmp> LANG=C rm -u test
rm: invalid option -- 'u'
Try 'rm --help' for more information.
merkaba:/tmp#1> cat test
test
merkaba:/tmp>

So if Akonadi pipes the mail through rm -u, it should get back "rm: invalid 
option -- 'u'
Try 'rm --help' for more information."

or something like that.

Well, that could somehow have lead to a one byte sized file.

[Filter #40]
Applicability=0
AutomaticName=false
ConfigureShortcut=true
ConfigureToolbar=true
Enabled=true
Icon=application-exit
StopProcessingHere=true
ToolbarName=crm114: Als Spam einstufen
accounts-set=akonadi_pop3_resource_0,akonadi_maildir_resource_0
action-args-0=P
action-args-1=crm -u ~/.crm114 mailreaver.crm --spam
action-args-2=Lokale Ordner/Papierkorb/Spam
action-args-3=crm -u ~/.crm114 mailreaver.crm
action-name-0=unset status
action-name-1=execute
action-name-2=transfer
action-name-3=filter app
actions=4
apply-on=manual-filtering
identifier=k2iC48NCVtfkNKe3
name=crm114: Als Spam einstufen
operator=all
rules=0

If need be I can also post the old KMail-1 based filter rules, I have an export 
here. But right now whats more interesting would be to know the difference 
between your working rules and my producing 1-byte sized files sometimes rules.

I am pretty sure crm114 doesn´t produce these one-byte sized responses, as it 
did work well basically unaltered for years.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users