[Mimedefang] MIMEDefang - "Bounce" when really a SMTP rejection.

Fri Aug 20 14:23:58 EDT 2010

Can we finally fix this mis-naming too?  Globally change anything using the word "bounce" to "reject" since what really happens is an SMTP rejection.

Of course, we would alias "action_bounce()" to "action_reject()" for a few releases for backwards compatibility.
-------------- next part --------------
/usr/src/mimedefang-2.71/Changelog:919: * mimedefang-filter.5.in: Clarified description of action_bounce.
/usr/src/mimedefang-2.71/Changelog:1014:        we bounce the message and log an error at LOG_CRIT importance.
/usr/src/mimedefang-2.71/Changelog:1908:        Sample filter now calls action_bounce() for viruses and
/usr/src/mimedefang-2.71/Changelog:2034:        and bounce the message if there are more than $MaxMIMEParts parts.
/usr/src/mimedefang-2.71/Changelog:2745:        return true for action_bounce, action_tempfail AND action_discard.
/usr/src/mimedefang-2.71/Changelog:2754:        of using action_bounce().
/usr/src/mimedefang-2.71/Changelog:2797:        to test if something earlier on has bounced or tempfailed message.
/usr/src/mimedefang-2.71/Changelog:2916:        * mimedefang.pl.in (action_bounce): Add newline to end of
/usr/src/mimedefang-2.71/Changelog:3286:        * mimedefang.pl.in: Changed "bounce" action to continue processing
/usr/src/mimedefang-2.71/Changelog:3287:        remaining parts of the message and only bounce at the end.
/usr/src/mimedefang-2.71/README:42:bounce messages (something impossible to do with procmail-based
/usr/src/mimedefang-2.71/README.SECURITY:27:5) You may use action_bounce, but use it with care.  You may wish to
/usr/src/mimedefang-2.71/README.SECURITY:28:test the sender address first.  (For example, don't bounce a message
/usr/src/mimedefang-2.71/contrib/graphdefang-0.9/event/sendmail/sympa_outgoing:12:# Bounce
/usr/src/mimedefang-2.71/contrib/graphdefang-0.9/event/sendmail/sympa_outgoing:14:#Jun 10 18:46:57 hdnetwork sendmail[21944]: h5A7KMT19430: to="| /home/sympa/bin/bouncequeue todaysverse-kjv at maillists.heartlight.org", ctladdr=todaysverse-kjv-owner at maillists.heartlight.org (8/0), delay=16:26:16, xdelay=00:00:01, mailer=prog, pri=4890100, dsn=2.0.0, stat=Sent
/usr/src/mimedefang-2.71/contrib/graphdefang-0.9/event/sendmail/sympa_outgoing:42:      } elsif ($text =~ m/^\S+: to=.*?bouncequeue (\S+?)\", ctladdr=(\S+) .*?, mailer=prog, .*?, stat=Sent.*?$/) {
/usr/src/mimedefang-2.71/contrib/graphdefang-0.9/event/sendmail/sympa_outgoing:45:                      $event = "bounce";
/usr/src/mimedefang-2.71/examples/suggested-minimum-filter-for-windows-clients:180:     action_bounce("MIME type message/partial not accepted here");
/usr/src/mimedefang-2.71/examples/suggested-minimum-filter-for-windows-clients:222:     action_bounce("MIME type message/partial not accepted here");
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:91:.B action_bounce
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:432:MIMEDefang machine will be forced to generate a bounce message when
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:509:for messages with more than that many parts, and the message is bounced.
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1155:.B action_bounce($reply, $code, $dsn)
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1160:make sense for a bounce, they are replaced with "554" and "5.7.1"
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1163:\fBaction_bounce\fR merely makes a note that the message is to
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1164:be bounced; remaining parts are still processed.  If
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1165:\fBaction_bounce\fR is called for more than one part, the mail is
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1166:bounced with the message in the final call to \fBaction_bounce\fR.
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1168:\fBaction_bounce\fR if you want to keep a copy of the offending part.
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1169:Note that the message is not bounced immediately; rather, remaining
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1170:parts are processed and the message is bounced after all parts have
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1173:Note that despite its name, \fBaction_bounce\fR does \fInot\fR generate
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1174:a "bounce message".  It merely rejects the message with an SMTP
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1178:\fBaction_bounce()\fR may cause the sending relay to generate spurious
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1179:bounce messages if the sender address is faked.  This is a particular
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1181:better to bounce a virus than to silently discard it.  It's almost
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1595:are going to bounce it if it is on four or more, you can set $answers_wanted
/usr/src/mimedefang-2.71/mimedefang-filter.5.in:1689:Returns true if any of \fBaction_tempfail\fR, \fBaction_bounce\fR or
/usr/src/mimedefang-2.71/mimedefang-protocol.7.in:198:Bounce (reject) the message with the specified SMTP reply code, DSN code
/usr/src/mimedefang-2.71/mimedefang.c:1735:         /* Bounce */
/usr/src/mimedefang-2.71/mimedefang.pl.in:1138:#  True if message has been rejected (with action_bounce or action_tempfail);
/usr/src/mimedefang-2.71/mimedefang.pl.in:1144:     defined($Actions{'bounce'})   ||
/usr/src/mimedefang-2.71/mimedefang.pl.in:1481:# %PROCEDURE: action_bounce
/usr/src/mimedefang-2.71/mimedefang.pl.in:1493:sub action_bounce ($;$$) {
/usr/src/mimedefang-2.71/mimedefang.pl.in:1495:    return 0 if (!in_message_context("action_bounce"));
/usr/src/mimedefang-2.71/mimedefang.pl.in:1502:    $Actions{'bounce'}++;
/usr/src/mimedefang-2.71/mimedefang.pl.in:2289:     action_bounce("Unable to stream message");
/usr/src/mimedefang-2.71/mimedefang.pl.in:2337:         action_bounce("Unable to stream message");
/usr/src/mimedefang-2.71/mimedefang.pl.in:5890: # Message is too complex; bounce it
/usr/src/mimedefang-2.71/mimedefang.pl.in:5891: action_bounce("Message contained too many MIME parts.  We do not accept such complicated messages.");
/usr/src/mimedefang-2.71/tests/parts/action_bounce.bin:1:Should cause message to be bounced.
/usr/src/mimedefang-2.71/tests/test-filter:159:    if ($lc_fname =~ /action_bounce/) {
/usr/src/mimedefang-2.71/tests/test-filter:160: return action_bounce("Bounce test");
/usr/src/mimedefang-2.71/tests/test-msg-2:27:Content-Type: APPLICATION/octet-stream; name="action_bounce.bin"
/usr/src/mimedefang-2.71/tests/test-msg-2:31:Content-Disposition: attachment; filename="action_bounce.bin"
/usr/src/mimedefang-2.71/mimedefang.pl:1138:#  True if message has been rejected (with action_bounce or action_tempfail);
/usr/src/mimedefang-2.71/mimedefang.pl:1144:        defined($Actions{'bounce'})   ||
/usr/src/mimedefang-2.71/mimedefang.pl:1481:# %PROCEDURE: action_bounce
/usr/src/mimedefang-2.71/mimedefang.pl:1493:sub action_bounce ($;$$) {
/usr/src/mimedefang-2.71/mimedefang.pl:1495:    return 0 if (!in_message_context("action_bounce"));
/usr/src/mimedefang-2.71/mimedefang.pl:1502:    $Actions{'bounce'}++;
/usr/src/mimedefang-2.71/mimedefang.pl:2289:        action_bounce("Unable to stream message");
/usr/src/mimedefang-2.71/mimedefang.pl:2337:            action_bounce("Unable to stream message");
/usr/src/mimedefang-2.71/mimedefang.pl:5890:    # Message is too complex; bounce it
/usr/src/mimedefang-2.71/mimedefang.pl:5891:    action_bounce("Message contained too many MIME parts.  We do not accept such complicated messages.");
/usr/src/mimedefang-2.71/mimedefang-filter.5:91:.B action_bounce
/usr/src/mimedefang-2.71/mimedefang-filter.5:432:MIMEDefang machine will be forced to generate a bounce message when
/usr/src/mimedefang-2.71/mimedefang-filter.5:509:for messages with more than that many parts, and the message is bounced.
/usr/src/mimedefang-2.71/mimedefang-filter.5:1155:.B action_bounce($reply, $code, $dsn)
/usr/src/mimedefang-2.71/mimedefang-filter.5:1160:make sense for a bounce, they are replaced with "554" and "5.7.1"
/usr/src/mimedefang-2.71/mimedefang-filter.5:1163:\fBaction_bounce\fR merely makes a note that the message is to
/usr/src/mimedefang-2.71/mimedefang-filter.5:1164:be bounced; remaining parts are still processed.  If
/usr/src/mimedefang-2.71/mimedefang-filter.5:1165:\fBaction_bounce\fR is called for more than one part, the mail is
/usr/src/mimedefang-2.71/mimedefang-filter.5:1166:bounced with the message in the final call to \fBaction_bounce\fR.
/usr/src/mimedefang-2.71/mimedefang-filter.5:1168:\fBaction_bounce\fR if you want to keep a copy of the offending part.
/usr/src/mimedefang-2.71/mimedefang-filter.5:1169:Note that the message is not bounced immediately; rather, remaining
/usr/src/mimedefang-2.71/mimedefang-filter.5:1170:parts are processed and the message is bounced after all parts have
/usr/src/mimedefang-2.71/mimedefang-filter.5:1173:Note that despite its name, \fBaction_bounce\fR does \fInot\fR generate
/usr/src/mimedefang-2.71/mimedefang-filter.5:1174:a "bounce message".  It merely rejects the message with an SMTP
/usr/src/mimedefang-2.71/mimedefang-filter.5:1178:\fBaction_bounce()\fR may cause the sending relay to generate spurious
/usr/src/mimedefang-2.71/mimedefang-filter.5:1179:bounce messages if the sender address is faked.  This is a particular
/usr/src/mimedefang-2.71/mimedefang-filter.5:1181:better to bounce a virus than to silently discard it.  It's almost
/usr/src/mimedefang-2.71/mimedefang-filter.5:1595:are going to bounce it if it is on four or more, you can set $answers_wanted
/usr/src/mimedefang-2.71/mimedefang-filter.5:1689:Returns true if any of \fBaction_tempfail\fR, \fBaction_bounce\fR or
/usr/src/mimedefang-2.71/mimedefang-protocol.7:198:Bounce (reject) the message with the specified SMTP reply code, DSN code