On Tue, 8 Aug 2000, Eric Hilding wrote:
Is there a limitation to the number of conditions that can
be put in a particular recipe? I've been trying all sorts
of things to axe <anything(_at_)xx(_dot_)com> that is unauthorized but
stuff keeps slipping through...like this bogus wall street
journal subscription by a forgerer:
Received: from zen2-exds (qmailr(_at_)zen2-exds(_dot_)strategy(_dot_)com
[216.35.219.133])
by winery.garlic.com (8.10.0/8.10.0) with SMTP id e78I8w517962
for <xxx(_at_)xx(_dot_)com>; Tue, 8 Aug 2000 11:08:59 -0700
Received: (qmail 2340 invoked from network); 8 Aug 2000 17:46:33 -0000
Received: from unknown (HELO wasdc-ebse012.strategy.com) (10.60.49.96)
by 10.60.80.106 with SMTP; 8 Aug 2000 17:46:33 -0000
Received: from mail pickup service by wasdc-ebse012.strategy.com with
Microsoft
SMTPSVC;
Tue, 8 Aug 2000 13:42:50 -0400
Eric,
Rather than sending fragments of altered headers, why not send a complete
set of headers with unaltered information? It makes it easier to provide
answers to what you want (anti-list sub from what I see) and possibly in
an alternative method than you are asking. I.e.:
:0:
* ^FROM_DAEMON
* (Series of exclusion lines for lists you do sub to)
forged-list-sub
--
Drugs may be the road to nowhere, but at least they're the scenic
route!
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail