I have not perused the source, yet, but it looks like this answers my
earlier question.
2002-05-17 Mr. Sam <mrs...@courier-mta.com>
tcpd/tcpd.c (doallowaccess): Code cleanup.
courier/submit.C (getrcpts): Fix failure to inject a bounce message when
the original message had corrupted MIME content.
Thanks, Sam...
Jerry
-----Original Message-----
From: cour...@lists.sourceforge.net
[mailto:cour...@lists.sourceforge.net]On Behalf Of Jerry
Amundson
Sent: Friday, May 31, 2002 12:50 PM
To: Courier-Users
Subject: [courier-users] BOFHBADMIME wrap and dsn?
Just upgraded to Courier 0.38.1 (what a breeze, but I digress :-), mostly to
provide BOFHBADMIME functionality.
Now that I've see it in action, I'm wondering if I can have my cake and eat
it too. Can the wrapped message be delivered, but also have an
RFC-compliance message bounced to the sender? I was thinking of some kind of
maildrop, reformail/autoreply combination... with a reply along the lines of
"Your message has been delivered, but you really should fixed your broken
software". I hate to let the senders get off too easily...
Thoughts on doing this?
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
5 messages in net.sourceforge.lists.courier-usersRE: [courier-users] BOFHBADMIME wrap ...
