I've been maintaining a majordomo (1.92) list and from time to time
one of the recipients addresses on the net is bogus, and it sends
the error message back to majordomo ...
In the example below, a Ccmail system bounced the mail back, and
because it didn't use "Postmaster" in the From field, majordomo
happily sent it back to the list... which proceeded to bounce, and
got send back to the list, and got redistributed, and ... ad naseum...
My question is - what is the best way to deal with this? 1.92
checks for the user postmaster - but that is no good, since ccmail sites
use the local site admin's name..
I considered adding '/User \S+ is not defined/' to the administriva
checks, but I want to avoid making changes that won't be in later
versions - so this problem won't come back.
I'd like to add "Errors-to: email@example.com" to the mail
headers, but 1.92 only supports Reply-To: ... (again I could add this,
but I want to avoid modifying majordomo for maintenance reasons..)
Thoughts? Is this addresses in 1.93? (I haven't checked the change list,
and until now 1.92 has been working without a hitch..)
Here's some of the headers from a sample CC: Mail return message..
(headers changed to protect the non-existant..)
> Date: Fri, 10 Feb 95 10:00:40
> From: Jane_Doe@somehost.company.com
> X-ccAdmin: admin@netcomsv
> Message-Id: <9501107924.AA792439240@somehost.company.com>
> To: firstname.lastname@example.org
> Subject: cc:Mail UUCPLINK 2.0 Undeliverable Message
> Resent-From: email@example.com
> X-ccAdmin: admin@somehost
> X-Mailing-List: <firstname.lastname@example.org> archive/latest/49
> X-Loop: email@example.com
> Precedence: list
> Resent-Sender: firstname.lastname@example.org
> User somehost!someuser is not defined
> Original text follows