> I also changed the per-user feature to only take effect if the > message has a single recipient.
Perhaps it would be useful to give people the option of only accepting one recipient per SMTP transaction? This seems a bit messy/inefficient, we don't do it ourselves, but I've heard from at least one QP user with a big installation that has had success with this; anything after the first (accepted) recipient is simply deferred, so the sending MTA is forced to send messages to multiple recipients with one transaction per recipient. This would allow people to always take advantage of per-user spam rules, if they wished. I should note that our installation does institute a higher recipient limit (since we queue once per recipient we were running into problems with client timeouts being reached while waiting for our response to the DATA command...) and sending MTA's have generally obeyed this, but it has generated some questions from sending organizations as their queued take a little longer to empty out, especially in the case where our clients are doing outbound filtering. ...Actually, if it was also possible to turn of SA scanning on relay-allowed transactions, then it would perhaps be reasonable to make it a one-inbound-recipient limit rather than simply a one-recipient limit. For inbound mail it's much less common to have a whole lot of recipients in a single transactions. -Jared
