On Mon, 10 Sep 2007 the voices made Peter J. Holzer write:
> That forces smtp-forward to be the last plugin in the rcpt hook, because
> any later plugin could return a 5xx (or worse, a 4xx) error to the
> client while the backend has already accepted the recipient.
>
> Since a large percentage of the recipients doesn't exist IME, the check
> for existing recipients should be (one of) the first, not the last.
It should, if it's possible, but if it isn't an option then how about a
compromise along the lines of having it both first and last; you have the
simplicity of a smpt-forward(ish) plugin at the end, but it also caches
relevant responses so that it can identify nonexistent recipients for the next
X (72?) hours as one of the first plugins?!?
I'm not saying that it's the most beautiful solution one could imagine, but it
might do wonders for "normal" people using a packaged qpsmtpd and not enough
time/knowhow to tinker with settings/plugins...
/Tony
--
"Generally speaking, taunting mentally unstable people is a bad idea."
