After the limit is reached, spamdyke rejects every extra recipient with a temporary rejection code. A well-behaved SMTP server will send the message anyway, then retry delivery to the recipients that failed. Whether it retries them separately or tries to deliver the remaining recipients in a single batch is entirely up to the remote server. The remote server should never retry delivery to the recipients that were accepted.
There is a small chance that a message could have so many recipients that subsequent retries cannot deliver them all before the message bounces. For example, if a message had 500 recipients and spamdyke only accepted 5 at a time, the remote server may only retry 10 times before the message bounces. In that case, 50 recipients would get the message, 450 would not. The risk exists, but it is small. Most SMTP servers handle this situation gracefully. Of course, user mail clients typically do not handle recipient rejection correctly at all. Most mail clients will completely abort delivery if any error messages are seen. For this reason, you should make sure all of your users are authenticating before you enforce a maximum number of recipients. -- Sam Clippinger Greg Cirelle Enterprises wrote: > When the max recipients value is reached, does > the remote server get told to retry one at a time > or some such thing, or does the delivery fail with > only email addresses up to the max recipient value > getting the email? > > best > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
