After Hal Wine made this suggestion:
| > Given pattern:
| > >* ^Subject: .*ATLANTIS.*ZEITUNG.*
| > the line:
| > >Subject: atlantis zeitung
| > would not match if the character after the colon (:) was a tab.
| > There's no reason not to write the pattern as:
| > * ^Subject:.*ATLANTIS.*ZEITUNG
Alex Schroeder answered,
| I did that, but still this one message will not be processed. I am at
| loss, since again other messages have been processed. Looking at my
| log file though, their header was always "ATLANTIS ZEITUNG" and not
| "atlantis zeitung" as in this problematic mail.
Are you trying a verbose logfile? Maybe there is something else not match-
ing, though your only other condition was * !^FROM_DAEMON and I can't see why
that would be problem with the sample headers you showed us.
| Another thought: my version is procmail v2.91 1993/07/02 - perhaps it
| is a bug? perhaps "case independent" means that the lower case rules
| get translated to upppercase for a match - but if the target is
| lowercase and the rule uppercase, there will never be a match?
Well, that is the way less works (lower-case characters in a search expres-
sion will be matched by capitals in the text but capitals in the search ex-
pression will be matched only by capitals in the text), but I've never found
that in procmail. Without the `D' flag case in the expression doesn't matter
and with it both upper and lower cases must be matched exactly.
Give it a try: see if changing the condition to
* ^Subject:.*atlantis.*zeitung
will successfully catch this writer's mail as well as that from people who
send the subject in all caps.