ok, thank a lot, it seems to solve my problem. Now how postmaster get
noticed about the fact one SASL authentication was rejected? If postmaster
doesn't get noticed and take an action, it will happen indefinitelly. How
postmaster get noticed?
Thanks
David
----- Original Message -----
From: "Wietse Venema" <[email protected]>
To: "Postfix users" <[email protected]>
Sent: Wednesday, August 26, 2009 10:43 AM
Subject: Re: smarthost issue
Ing. Davy Leon:
Hi all
I have a postfix 2.3.3 running on Centos 5.3. Postfix delivers
mail through an authenticated smarthost based on a per user
authentication. Everything works fine until some smarthost's
account get blocked for some brute force attack or something. The
fact is that any mail from that user who's account is blocked at
the smarthost can't be delivered and is bounced back to the user
with some mail delivery error as soon as postfix try to deliver
it once.
My point is, how can I make this message that postfix couldn't
deliver just stay around in queue for longer time and be retried
everytime queue is processed, and postmaster be noticed about the
problem to solve it wich is simple though the smarthost's web
page. I want the end-user never gets aware of the problem.
See: http://www.postfix.org/postconf.5.html#smtp_sasl_auth_soft_bounce
Wietse
smtp_sasl_auth_soft_bounce (default: yes)
When a remote SMTP server rejects a SASL authentication request
with a
535 reply code, defer mail delivery instead of returning mail as
unde-
liverable. The latter behavior was hard-coded prior to Postfix
version
2.5.
Note: the setting "yes" overrides the global soft_bounce parameter,
but
the setting "no" does not.
Example:
# Default as of Postfix 2.5
smtp_sasl_auth_soft_bounce = yes
# The old hard-coded default
smtp_sasl_auth_soft_bounce = no
This feature is available in Postfix 2.5 and later.
