From: Borja Marcos (borjamsarenet.es)
Date: Tue Aug 28 2007 - 05:59:54 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I'm trying to tune a couple of servers that use the sbl-xbl RBL list.
They are holding a lot of simultaneous connections, and I've seen
that the worst are connections started from bots listed in XBL.

Looking at the configuration parameters I see that decreasing
smtpd_hard_error_limit would help the server to kick the connection
immediately (right after the RCPT-TO and access denied error), but
unfortunately a non-existant recipient counts as a hard error as
well, as "hard error" means "non-deliverable, don't retry".

Is it possible to rethink this policy? I think that the "hardness
level" of a non-existant recipient should be different than an
authorization error.

Would it be possible to either add a new error cathegory or to add a
configuration parameter to restrictions so that they can specify a
"sever connection" directive?

This is mostly a design decision rather than a quick patch.

Best regards,

Borja.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFG1AAxULpVo4XWgJ8RAr2vAKCtpQ3y9yLhvWZJW6WswY4TK9vK+QCfQZIM
DI7xYI6+YuDPrqGRxaCMdyA=
=skzG
-----END PGP SIGNATURE-----

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]