Rich Kulawiec wrote:
So let me modify these as follows and see if this is any better:
(1) LHS (left-hand-side) rules
Present to list-owner for disposition as done today, but mark it
prominently as noreply address, almost certainly a forgery.
(2) sender rules
Present to list-owner for disposition as done today, but mark it
prominently as probable phish.
Granted, in both cases, the message still has be to processed, but
perhaps marking it (both on the Subject line and inside the
message body) will make it easier/faster for list-owners to deal with.
Referring back to your original idea where you wanted the messages
refused at SMTP time, it seems that what you really want is for
messages that match your rules to be discarded. You can use
header_filter_rules for this, but maintaining them would be a pain.
If I were trying to do it, I would use the KNOWN_SPAMMERS list in
mm_cfg.py. For example just listing a few of yours
KNOWN_SPAMMERS = [
('from', '^(.*[\s])?do-not-reply@'),
('from', '^(.*[\s])[EMAIL PROTECTED]([\s].*)?'),
]
This list applies installation wide and will discard any message to a
list or list-owner address that contains a matching header.
The entries are 2-tuples ('a', 'b') where a is the case-insensitive
name of a header and b is a Python regexp to match case-insensitively
against the values of all headers of that type in the message.
This doesn't address mail to the other (e.g., -request or -bounces)
list addresses, but it's a start, and using KNOWN_SPAMMERS frees you
from maintaining rules per list.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
