PSE-L(_at_)mail(_dot_)professional(_dot_)org (Professional Software
Engineering) writes:
At 01:06 AM 2/16/98 -0600, Brad Knowles wrote:
[domain portion of major ISP Message-IDs matching domain of ISP]
What about mailing lists? Especially those run as entries in
/etc/aliases?
Do you know any MSN users who have /etc/aliases access *ON MSN* ? AOL? etc?
You misunderstand: if I create an alias here that says:
something: fred(_at_)aol(_dot_)com, guenther(_at_)gac(_dot_)edu
and then someone(_at_)aol(_dot_)com sends a message to
something(_at_)gac(_dot_)edu, the
message that goes to fred(_at_)aol(_dot_)com will have an envelope and header
sender of someone(_at_)aol(_dot_)com, even though the message is coming to the
aol
machines from solen.gac.edu.
...
Besides, proper handling of a remailed message on a mailing list is to have
the list add "Resent-Message-ID:" with a list-generated Message-ID. The
original Message-ID is retained. Look at your procmail messages as an
example.
Relatively few mailing lists use Resent- headers. Most generate a
completely new message header with new message-id, preserving only a
few headers from the original message (typically From: and the
recipient headers, but not always). Both methods are RFC compliant.
[in another message you had said]
I'd replace [a-z] with [A-Za-z] just to be on the complete side (otherwise
the first message with an uppercase letter in there is going to slip
through). Also, I might double up the numerics on either end (for "2 or
more" : "[0-9][0-9]+"), if this is a characteristic of the messages, though
I agree that I'd be unlikely to get messages with addressing matching the
basic format, so why bother narrowing the match?
Unless you've turned on case sensitive matching, adding "A-Z" to the
character class is pointless. As for narrowing the condition, I would
suggest doing so, then seeing if any get through.
Philip Guenther