On Tue, Aug 26, 2003 at 03:56:30PM -0400, Damian Gerow wrote:
Thus spake Scott Wiersdorf (scott(_at_)perlcode(_dot_)org) [26/08/03 15:43]:
On Tue, Aug 26, 2003 at 10:05:45PM +0300, Brock Rozen wrote:
I'm using procmail as my local mailer, and when a user hits a quota limit
now it returns a "550 5.0.0 <xxx(_at_)xxx(_dot_)com>... Can't create
output" message.
<snip>
By not logging at all, stderr will be written back to the MTA,
allowing sendmail to generate a more "true" error bounce.
Erm... Is there any way to log *and* provide a valid bounce? I may be
reaching here, but last I checked, logging was seen as a Good Thing. I'd
rather suffer with mystical bounces that completely disable logging.
I'm just giving my observations of how it appears to work (a co-worker
and I dug pretty deep in the source to find this behavior; a few
trusses and lots of logging revealed this behavior).
Unfortunately, I don't have any more help than this. I agree that it
would be nice to do both (maybe write your log to a named pipe that is
a tee to a logfile and stderr?), but I haven't thought much more about
it beyond that.
Scott
--
Scott Wiersdorf
scott(_at_)perlcode(_dot_)org
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail