On Fri May 8 2009 06:38:44 Charles Marcus wrote:
> I thought that since the check was under smtpd_recipient_restrictions
> that all of those checks would be applied before the recipient was
> 'validated'... apparently that assumption was incorrect and the
> source of my problem...
Well, they ARE, but you're confusing your MX host. Sometimes you tell
it, "CMarcus is a valid user," other times, the opposite. There's no
good way, from your end, to tell them, "CMarcus is a valid user, unless
the sender is Rik."
As Sahil said, the only responsible way to do this is at the edge MX,
because backscatter could result. Don't make your MX host send bounces.
If your provider offers this as a feature, you can do it on that end.
If not, I wouldn't bother. (I wouldn't, anyway, since this does not
scale well. I think it's better to deal with user/personal issues at
the user level, rather than at the MTA.)
> So, would moving the check above 'reject_unauth_destination' fix
> this? Or is there some other way to force postfix to perform all of
> these checks before validating a recipient?
Recipient validation is a boolean. You're wanting to add conditions.
That's probably not going to work, and it could cost you some real
mail.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
