OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: 554 Client host rejected Access denied

From: Victor Duchovni (Victor.DuchovniMorganStanley.com)
Date: Tue Mar 04 2008 - 22:23:37 CST


On Tue, Mar 04, 2008 at 10:49:34PM -0500, Brian Carroll wrote:

> smtp inet n - y - - smtpd
> -o cleanup_service_name=pre-cleanup
> 465 inet n - y - - smtpd
> -o cleanup_service_name=pre-cleanup
> smtps inet n - y - - smtpd
> -o smtpd_tls_wrappermode=yes
> -o smtpd_sasl_auth_enable=yes
> -o smtpd_client_restrictions=permit_sasl_authenticated,reject
> -o cleanup_service_name=pre-cleanup

The "smtps" service is by default port 465 in most /etc/services files,
does yours differ? This Postfix configuration should not start because
master is unable to rebind the "smtps" port already used by the "465"
service.

This said, if "smtps" is NOT port 465 on your machine, and the sender
is connecting to the smtps port and not using SASL auth, you would
get the log message you report.

You are also using chroot jails for your smtpd(8) daemons, this is an
advanced setting, not recommended for most users not prepare to trouble
shoot any resulting issues (this one is not a chroot problem).

Your log message corresponds to either "reject" in smtpd_client_restrictions
or a "REJECT" RHS in an access(5) table used via "check_client_access".

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomopostfix.org?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.