Roy,

We have double-checked the code to see the order in which events occur, and they are as follows.

• All settings in INI file and local lists are loaded, including alternative routes for local domain list
• SMTP port is opened and incoming connections are accepted
• Mail in queue is processed for delivery

I tried to replicate the problem by having an smtp stress tool send mass emails to SpamFilter with the SpamFilter shut off. The emails are for a domain that has an alternate destination smtp address and port in the domain list. As soon as it incoming conns are accepted, SpamFilter did route them to the alternate domain, not the primary listed under the main settings tab.

Are you absolutely sure that it is not behaving as it should, and that ALL emails are being redirected to the main smtp server? If you're using a build earlier than .122, we just made available on the website the public build .122, could you see if the problem occurs with that as well?

Roberto Franceschetti
LogSat Software

You are correct on this one, we were able to duplicate it. When there are multiple recipients, the email is forwarded "as-is" to the destination server for the domain of the first recipient. This is because SpamFilter is sending the message as it arrives.

If it arrives as an email with all the recipients specified using multiple RCPT TO, this is how they are delivered, to one destination smtp server with multple RCTP TOs. If it arrives as one separate email for each recipient, SpamFilter will send one single email per recipient to the appropriate (the correct one in this case since there is only one) destination smtp server.

Different SMTP servers can send mail to multiple reicipients in both ways, either with one single transmission specifying multiple RCPT TOs in one session, or as separate sessions each with one RCPT TO. SpamFilter simply duplicates this behavior. Changing it is not going to be easy and simple, but we'll see what we can do.

Roberto Franceschetti
LogSat Software