OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
RE: reject_non_fqdn_hostname question

From: Joey (JoeyWeb56.Net)
Date: Thu Jul 05 2007 - 08:31:20 CDT


> -----Original Message-----
> From: owner-postfix-userspostfix.org [mailto:owner-postfix-
> userspostfix.org] On Behalf Of Rene van Hoek
> Sent: Thursday, July 05, 2007 9:03 AM
> To: postfix-userspostfix.org
> Subject: Re: reject_non_fqdn_hostname question
>
> Jorey Bump wrote:
> > Rene van Hoek wrote:
> >
> >> Check are evaluated in the order they appear.
> >> Do something like this (postconf -n ouput):
> >>
> >> smtpd_recipient_restrictions = permit_sasl_authenticated
> >> reject_unauth_destination permit_mynetworks
> >> reject_invalid_helo_hostname
> >> reject_non_fqdn_helo_hostname reject_non_fqdn_sender
> >> reject_non_fqdn_recipient reject_unknown_sender_domain
> >> reject_unknown_recipient_domain
> >
> > Be careful. You might not want to exempt your users from
> > reject_non_fqdn_sender, reject_unknown_sender_domain, or
> > reject_unknown_recipient_domain. This will help prevent typos or
> other
> > types of garbage.
> >
> Yes, you are right. So, you mean this:
>
> smtpd_recipient_restrictions =
> reject_non_fqdn_sender
> reject_non_fqdn_recipient
> reject_unknown_sender_domain
> reject_unknown_recipient_domain
> permit_sasl_authenticated
> reject_unauth_destination
> permit_mynetworks
> reject_invalid_helo_hostname
> reject_non_fqdn_helo_hostname

Thanks to everyone for the FAST responses.

I moved the reject_non_fqdn_hostname below auth & my networks and it seems
to have resolved the error.

        permit_mynetworks,
        permit_sasl_authenticated,
        reject_non_fqdn_hostname,

Should I also add these below reject_non_fqdn_hostname or is this redundant?

reject_invalid_helo_hostname
reject_non_fqdn_helo_hostname

Thanks!

Joey