postfix-us...@tja-server.de schrieb:
/dev/rob0 wrote:
But as far as i can tell, this is already quite late in
processing the mails!
Why do you think so?
I seem to remember, that the recipient code technically is called later
- after all headers and maybe even data has been read by the server.
From your URLs, i found the text again, that made be think this way:
In
http://www.postfix.org/postconf.5.html#smtpd_reject_unlisted_recipient i
found the following text:
########
Other restrictions that are valid in this context:
[...]
SMTP command specific restrictions described under
smtpd_sender_restrictions or smtpd_recipient_restrictions. When sender
or recipient restrictions are listed under smtpd_helo_restrictions, they
have effect only with "smtpd_delay_reject = yes", so that
$smtpd_helo_restrictions is evaluated at the time of the RCPT TO command.
########
So, it seems that using "check_recipient_access" as argument to
"smtpd_helo_restrictions" would reject mails more early than using the
same for "smtpd_recipient_restrictions", or?
In summary:
smtpd_recipient_restrictions = check_recipient_access ...,
would reject later then
smtpd_helo_restrictions = check_recipient_access ...,
So, for getting aways that spam as early as possible,
"smtpd_helo_restrictions" would be better than
"smtpd_recipient_restrictions".
Or not?
