🚀 go-pugleaf

In article <694.UUL1.3#5131@mvac23.UUCP> thomas@mvac23.UUCP (Thomas Lapp) writes:
>fenner@postscript.cs.psu.edu (Bill Fenner) writes:
>
>> Mail went into a black hole (no
>> bounce, no warnings, no nothing):     62   (34%)
>> 
>
>In the case of mvac23, I have it set up so that it doesn't automatically
>bounce messages which are addressed to non-existant accounts.  It goes
>into a failure bin, which I check every so often and manually "fix",
>since it is usually a munge of a good address.  So rather than
>frustrating someone with a bounce, I try to get the mail delivered.

	IMHO this is bogus.  Why not just bounce the message and have the
user fix his address?  What is so "frustrating" about it?  If the
addresses get munged, then it's a matter of either informing the user
or fixing whatever software is munging the address.
	Note I'm not against the postmaster manually fixing bounced
mail and redelivering it, but I think it should be done _in addition_
to an automatic bounce, not in place of.  What if you go on vacation?

--Dave
-- 
System Administrator, Population Research Institute    barr@pop.psu.edu
#define ENOTTY          25              /* Not a typewriter */