On 02/09/10 16:13, RGBall wrote:
Greg Trounson wrote:
Hi Rich,
I'm not sure what you mean. The only criteria change was at the
recommendation of someone on this list trying to help with my problem.
No matter. Perhaps I was reading more into what you wanted to do than
was necessary.
There is nothing wrong with the regexp part of
* ^FROM(_dot_)*[\(_dot_)(_at_)]my\(_dot_)domain\(_dot_)com
except that if the message happens to have a header like
From tinkerbell.my.domain.com Wed 18-Sep-2010 ...
along with
From: nobody(_at_)someplaceelse(_dot_)com
you are going to get a match you don't want. This is what the verbose
log would tell you because you'll get to see what is matching.
Hi,
I see what's been happening now.
I've since added a couple more criteria, but here is the log entry for
one of the offending messages:
procmail: Unlocking "/home/user1/.lockmail"
procmail: [21485] Thu Sep 2 13:12:00 2010
procmail: No match on "^X-Loop:
user1(_at_)division\(_dot_)my\(_dot_)domain\(_dot_)com"
procmail: Match on "^FROM(_dot_)*[\(_dot_)(_at_)]my\(_dot_)domain\(_dot_)com"
procmail: Match on !
"^From:(_dot_)*(_at_)division\(_dot_)my\(_dot_)domain\(_dot_)com"
procmail: Match on ! "^Subject.*Re:"
procmail: Match on ! "^Subject.*confidential"
procmail: Executing "formail,-A,X-Loop:
user1(_at_)division(_dot_)my(_dot_)domain(_dot_)com"
procmail: Assigning "LASTFOLDER=/usr/sbin/sendmail -oi
user2(_at_)division(_dot_)my(_dot_)domain(_dot_)com"procmail: Locking "/home/user1/Maildir/.lock"
procmail: Executing
"/usr/sbin/sendmail,-oi,user2(_at_)division(_dot_)my(_dot_)domain(_dot_)com"
procmail: Assigning
"LASTFOLDER=/home/user1/Maildir/new/1283389920.21485_3.server"procmail:
Unlocking "/home/user1/Maildir/.lock"
procmail: Notified comsat:
"user1(_at_)0:/home/user1/Maildir/new/1283389920.21485_3.server"
From bounce-debian-user=user1=division(_dot_)my(_dot_)domain(_dot_)com(_at_)lists(_dot_)debian(_dot_)org
Thu Sep 2 13:12:00 2010
Subject: What's the Debian way of disabling suspend to disk?
Folder: /home/user1/Maildir/new/1283389920.21485_3.server
5511
So procmail is seeing the line:
From
bounce-debian-user=user1=division(_dot_)my(_dot_)domain(_dot_)com(_at_)lists(_dot_)debian(_dot_)org
, which doesn't actually appear anywhere in the message file itself, and
is enough to match "^FROM(_dot_)*[\(_dot_)(_at_)]my\(_dot_)domain\(_dot_)com". The fact this didn't
show up in the message header was confusing me, and I now see why the
colon after the field name is necessary in these rules. I've since
implemented the recommended changes and it all works now.
Thanks Rich and Michelle,
Greg
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)de
http://mailman.rwth-aachen.de/mailman/listinfo/procmail