I haven't had time to sit and poke at the offending mail server to see
if they react to the reply to: or the from: header. I'll have to mess
with that this weekend when traffic is lower on lour lists.
On Wed, 2006-02-22 at 14:35 +0900, Stephen J. Turnbull wrote:
Matthew == Matthew Thompson
On 2/21/06 3:27 PM, Matthew Thompson [EMAIL PROTECTED] wrote:
I have a mailing list with users subscribed from two particular domains,
call them nice.com and naughty.com. The security czars are naughty.com
have decided that inbound email with naughty.com in the From address
cannot possibly
On 2/21/06 3:27 PM, Matthew Thompson [EMAIL PROTECTED] wrote:
I have a mailing list with users subscribed from two particular domains,
call them nice.com and naughty.com.
By the way, almost any domain whose name one invents for purposes like this
exists.
nice.com has existed since 1992 (or
Mark == Mark Sapiro [EMAIL PROTECTED] writes:
Mark The logical place to do all this is
Mark Mailman/Handlers/CookHeaders.py.
I don't understand this recommendation. Why not use a separate
Handler in either the global pipeline (if it's an organizational
installation) or the
Stephen J. Turnbull wrote:
Mark == Mark Sapiro [EMAIL PROTECTED] writes:
Mark The logical place to do all this is
Mark Mailman/Handlers/CookHeaders.py.
I don't understand this recommendation. Why not use a separate
Handler in either the global pipeline (if it's an organizational
Matthew Thompson wrote:
I was looking for a way that we could automatically add the sender's
name or email address to the message to make this more fool-proof. I
would prefer to add it to the subject line to make sorting in the mail
client meaningful but adding it to the message body would be
Matthew == Matthew Thompson [EMAIL PROTECTED] writes:
Matthew I have a mailing list with users subscribed from two
Matthew particular domains, call them nice.com and naughty.com.
Matthew The security czars are naughty.com have decided that
Matthew inbound email with naughty.com
