|
Jeremy,
I'm not sure if you refer to the "Authorized TO" whitelist, or to the new feature present in SpamFilter v4.2.
If the question is for the "Authorized TO", this section of our manual for the following parameter in the SpamFilter.ini file should provide the answer:
;If the "AuthorizedTO" whitelist is used to specify the list of valid email addresses that can be accepted, by default SpamFilter will terminate a connection when the remote server specifies an invalid address in the RCPT TO command. You can use the following option to disable this forced disconnect, and cause SpamFilter to simply reject the invalid recipient, and continue to accept additional ones DisconnectOnNonAuthorizedTO=true
If you're referring to the new feature in SpamFilter v4.2 that checks to ensure your destination SMTP server accepts the recipients, placing "on hold" the remote server while this check is being made, then the behavior should be straightforward. If one or more of the recipients is not accepted by your mail server, SpamFilter will deliver the email to the valid recipients, but will also output a 500 error code to the remote server to inform it the email was not delivered successfully. The 500 error code will include in its description a list of the email addresses that were not delivered.
-------------
Roberto Franceschetti
http://www.logsat.com" rel="nofollow - LogSat Software
http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP
|