Lindsay Haisley writes:
Sam deals with this by having Courier preemptively back out on the receiving end if it finds that content analysis is enabled for the exchange between the sender and one of the recipients and not for the sender and another of the recipients. In this case, Courier never makes it to the DATA exchange and the SMTP session is aborted for all recipients.
No, not quite. What happens is that the other recipients are turned down with a temporary 4xx error. In this manner, the recipient list gets divided into the subset that has filtering enabled, and the other subset that does not. The status of the message's first recipient determines which subset gets a 4xx. If the first recipient does not filter, other recipients that do not filter get accepted, the remaining ones that have filtering enabled get a 4xx. If the first recipient has filtering enabled, other recipients that also have filtering enabled are accepted, the remaining ones that do not filter get a 4xx.
The recipients in the same subset as the first recipients are processed accordingly. The sender takes the 4xx-ed recipients, all in the other subset, and will try to resend the message to those recipients at a later time. In this manner, an arbitrary set of a single message's recipients gets clumsily divided into two separate subsets.
Note that this applies to the localmailfiltering API only. This is not applicable to the courierfilter API.
pgptPd98EI3oh.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
