-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Robert,
| From 217.26.52.23: | Trying 62.2.95.11... | Connected to mx.hispeed.ch. | Escape character is '^]'. | 220 mx.hispeed.ch ESMTP Sendmail 8.12.6/8.12.6/tornado-1.0; Thu, 29 Jan | 2004 15:53:30 +0100 | | From 217.26.52.15: | Trying 62.2.95.11... | telnet: connect to address 62.2.95.11: Connection timed out | | | So your statement sounds kind of incomplete to me... Have you | implemented other 'protection' mechanisms?
in case you don't understand Markus' statement: You're doing it the wrong way. If my mailserver wants to connect to mx.hispeed.ch it does not get a connection, therefore it keeps the mails in its queue (by default 1 week for qmail), retries and retries, because it thinks that it might get a connection sometime.
Now the users think their mails have been succesfully delivered because they won't receive a bounce mail until the mail expires in the queue (1 week). Quite frankly, that sucks.
Doing it the right way would mean accepting the connection and sending back an error such as
~ 451 Your mailserver has been blocked, please see http://url/to/policy.html for more information
That would bounce immediately and the error message is verbose enough for sysadmins to understand what's going on.
My server is blocked. You'll get a call from me tomorrow.
Please be a good net citizen and do it the right way.
daniel
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAJ78ES2WJ/hBy2k8RAoVrAJ9AW9sgAMULdDV3UMM78462QyIrBgCeJ4uE IvPtfZqgzXaD2tlqB5RZXqU= =dpXZ -----END PGP SIGNATURE----- ---------------------------------------------- [EMAIL PROTECTED] Maillist-Archive: http://www.mail-archive.com/swinog%40swinog.ch/
