Alex Schroeder asked,
| Not one of this users emails are filtered out by
| procmail. I am using only one example now, to see wether anybody can
| give me a hint on what's going on.
|
| This is in my mailfolder:
| From uucp(_at_)news1(_dot_)gtn(_dot_)com Wed Jun 19 01:13:33 1996
| Return-Path: <uucp(_at_)news1(_dot_)gtn(_dot_)com>
| Received: from news1.gtn.com by rzusuntk.unizh.ch (4.1/SMI-4.1.9)
| id AA14059; Wed, 19 Jun 96 01:13:16 +0200
| Received: (from uucp(_at_)localhost) by news1.gtn.com (8.7.2/8.7.2) id
BAA04091 for a
| lex(_at_)zool(_dot_)unizh(_dot_)ch; Wed, 19 Jun 1996 01:04:20 +0200 (MET DST)
| Received: by gismo.gun.de (DUUCP vom 27.05.1996)
| with ZConnect; 18 Jun 1996 16:47:00 +0200
| From: herm(_at_)world(_dot_)gun(_dot_)de (Thorsten Hermes)
| X-Mailer: CrossPoint v3.11 R/A18744
| Message-Id: <6B717c5mA9B(_at_)herm(_dot_)world(_dot_)gun(_dot_)de>
| X-Gateway: ZCONNECT GF gismo.gun.de [DUUCP BETA vom 27.05.1996]
Notice: this user's From_ line and Return-Path: header say "uucp(_at_)forwarder"
instead of "real_logname(_at_)real_site" as given in the From: header.
| This is the rule that should apply (and does, for all other users):
|
| :0 cfh
| * ^Subject:.*ATLANTIS.*ADR.*SCHICK.*
| * !^Subject:.*Re:.*ATLANTIS.*
| * !^FROM_DAEMON
| * !^X-Loop: alex(_at_)zool(_dot_)unizh(_dot_)ch
| | (formail -r -A "Precedence: junk" -A "X-Loop:
alex(_at_)zool(_dot_)unizh(_dot_)ch";\
| cat $adressen) | $SENDMAIL -oi -t
|
| So that is the problem?
The problem is that "From .*uucp" matches ^FROM_DAEMON [perhaps
"Return-Path:.*uucp" does as well], so the !^FROM_DAEMON condition throws
out mail from this fellow. (Also, those trailing ".*"'s on your conditions
are unnecessary; regular expressions are not anchored by default the way
shell globbing patterns are.) He needs to supply a proper incoming From_
line when he feeds his mail to his provider so that the ISP won't add
"From uucp".