> This I can confirm at any rate. All rcpt plugins get called after the
> client has sent the RCPT TO: line but before qpsmtpd has acknowledged that
> the rcpt is valid or not. Otherwise what would be the point...
So i would need to send the current (not already processed) recipient also
to the config plugin to be able to do per-user config.
> The problem you are going to have to deal with is the complex relationship
> between different behaviors when you have multiple recipients for the same
> message:
For a rcpt plugin this is not a problem. It is a problem for a datapost
plugin.
> It would almost be better to fork the message handling after the rcpt
> phase and effectively do a single delivery for each rcpt.
This would solve it for a datapost plugin. However, if some recipients
decide to accept the mail (according to plugin configuration) and some do
not, i can not reject the message at the SMTP level, but have to silently
drop it for some recipients.
However most people today filter Spam after accepting the mail and drop
spam silent too, so i don't see this as much of a problem. I've made the
observation that it might even be a bad idea to reject spam at SMTP (instead
of just saying "250 Ok" and dropping it), as i have seen retries for such
rejected spam (which adds to unnecessary traffic).
-kju
--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks
