[Remops] Antani remailer SMTP changes (original thread in APAS)

[Marco A. Calamari]

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

I summarize here the reasons and corrective actions
that cause broken chains and dropped mail for Antani
remailer, as well as the apparent lack of answer by me,

Antani domain has a primary SMTP that doesn't use SORBS
and a secondary one, owned by another organization with
a different policy, that started to use it some months
ago.

Primary SMTP has a different hostname, in HELO messages,
that the MX hostname. This is allowed by the RFC.

It seems that some SMTP, including ones used by Dingo and
Panta, started to drop connection if MX name and HELO
name differs. This is *not allowed* by RFC, albeit is a 
common but IMHO wrnog reaction to some kind of spamming.
Their SMTP dropped to secondary SMTP and were stopped by
SORBS, being on a dynamic IP.

For the same reason they had error messages trying to
write to me. It is wrong to define me "a non
answering remop" if the sender had the evidence
I never received his or her messages; more if this
is due to a stupid, non RFC conforming, limitation
of his SMTP.

To cope with this, we changed HELO hostname to match
MX one, and arrange for a different, non SORBSed
backup MX

One more problem arose; the ping message catched
by nilsimsa, triggered by a sudden batch of ping
due to unknow reason (batch processing of an SMTP
queue of held messages by the previos remailer
in chain ?).

Manually observing the rules file allow to catch
this for Panta & Dingo pings. Is Reliable a more
aggressive pinger that Echolot ? This problem
usually arise only from Reliable pingers.

Antani admin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDjXPUqIOZDSyGL5cRAm6JAKCADJtALRzBgBQQEoBbL/yMThM+JgCePPp9
uKesT2fxb+6cWDaXPXgfaKk=
=acgi
-----END PGP SIGNATURE-----