Sam Varshavchik writes: > > Alessandro Vesely writes: > > > Sam, may I ask if filters are going to be redesigned one day? In this > > case it would seem more polite to sprout two control files, similarly > > to what is being done with 200 recipients... > > I don't follow you. Splitting the message internally is not going to change > the fact that there's a single DATA transaction, which is the root of the > problem.
Yes, then it would produce bounces. In general, let's say that there are two options to block a message after content filtering. A: reject the body after it has been received, B: accept it but produce a bounce later. A saves the burden to send out bounces, but requires that all recipients agree on the filter's response. (412 responses allow to drive remote servers into sending such homogeneous sets of recipients as needed - some clients fail to obey to 412s.) B should be the preferred choice for relay clients; it would avoid the need to run a second server for relaying. I don't think that implementing B would be worth per se, but (when | if) filters are redesigned. In the latter case it would be worth to account for filters that drop or resubmit messages, to classify filters so that they are not invoked in a random order, to possibly allow rcptfilters to specify which filters they want and what possible alterations of the message would they be interested in. In that scenario, option B is handy: it extends the subset of the message lifecycle where filtering can be applied. Last and least, option B also avoids letting the remote server learn who whitelists who, which some might consider sensible info. ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
