Scratch previous comment -- bounces are going to individual senders, not to list
(because
headers are not rewritten, which is a good thing, I suppose). I'll add a filter
myself for
my host.
"Aaron L. Meehan" wrote:
> My mail to [EMAIL PROTECTED] bounced, so I malleted them into
> badmailfrom-
I think unsubscribing them is probably unnecessary, but blocking their 'bounce'
messages at
the list server would probably be smart.
"Aaron L. Meehan" wrote:
> My mail to [EMAIL PROTECTED] bounced, so I malleted them into
> badmailfrom--they are kind enough to send their bounces with a
> non-nu
Quoting Peter van Dijk ([EMAIL PROTECTED]):
> And my previous message about a broken mailer generated a bounce from
> *another* broken mailer...
>
> - Forwarded message from Mail Delivery Subsystem <[EMAIL PROTECTED]>
>-
My mail to [EMAIL PROTECTED] bounced, so
Yep, same thing here. I think someone (probably <[EMAIL PROTECTED]>,
since it appears in the bounces tough the original message was no addressed
to said individual) has a mail forwarder that gags with semicolon separated
addresses in the To: field.
Armando
And my previous message about a broken mailer generated a bounce from
*another* broken mailer...
- Forwarded message from Mail Delivery Subsystem <[EMAIL PROTECTED]> -
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 23018 invoked from netw
