Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Duncan B. (duncanpresidium.org)
Date: Thu Sep 10 2009 - 11:25:22 CDT
Just a quick config question, which I'm not too sure how to achieve.
I'd like to enable recipient domain validation, which I've partly done (at
the data stage), however if you then enter another "rcpt to" after the
data command failed, it'll allow it through. E.g.
220 relay4.post.newnet.co.uk ESMTP
mail from: <duncannewnet.co.uk>
250 2.1.0 Ok
rcpt to: <sgaggthsighoaghoga.org>
250 2.1.5 Ok
450 4.1.2 <sgaggthsighoaghoga.org>: Recipient address rejected: Domain
rcpt to: <sgsgagsgagsgzzzzz.org>
250 2.1.5 Ok
354 End data with <CR><LF>.<CR><LF>
I assume this is because my "smtpd_recipient_resrictions" doesn't have
Here is the config:
relay4# postconf -n | grep restriction
smtpd_client_restrictions = sleep 3, reject_unauth_pipelining
smtpd_data_restrictions = reject_multi_recipient_bounce,
smtpd_helo_restrictions = reject_non_fqdn_helo_hostname,
smtpd_sender_restrictions = reject_non_fqdn_sender,
The list of CIDR IP ranges to relay for is in the mynetworks variable,
so I can't do the recipient domain verification in "smtpd_recipient_restrictions"
because I need "permit_mynetworks", so that my networks can relay through
the box! permit_mynetworks skips the other checks for those networks.
So, how do I make mynetworks exempt from the smtpd_recipient_restrictions,
yet make mynetworks able to relay through the box?