Skip to contentSkip to conversation

Mail troubles at hermes.sistina.com[208.210.145.141]?

linux-lvm Michael Tokarev 2 participants 2 messages Aug 22, 2001

lore
Share & tools
lore
#0 lore raw

I'm sorry for sending this message to list.

Today morning I noticied that our mailserver rejected some mails from hermes.sistina.com due to invalid (non-FQDN) SMTP HELO argument (this is not rfc-compilant, and our mailserver configured to reject such a misconfigured clients).

I sent a notice to [email protected] about this issue, hoping it will be resolved soon. But that my message still in our mailqueue, with a message:

(host hermes.sistina.com[208.210.145.141] said:
451 Cannot check <[email protected]> at this time - please try later)

So Sistina also have no valid postmaster address that is also required by RFC? This way, it will end up on rfc-ignorant.org's blacklist shortly! ;)

Now I whitelisted this IP address (it was once whitelisted here already, due to reverse-DNS problem that seems gone now), so I hope to receive some mails from there from now on (if I was't unsubscribed authomatically due to constant bounces, as our mailserver rejected about 15 messages destined to me).

Something wrong with Sistina's mailserver, and needs to be fixed soon.

Regards,
Michael.

#1 lore raw
Quoted 3 lines · Michael Tokarev

Today morning I noticied that our mailserver rejected some mails from hermes.sistina.com due to invalid (non-FQDN) SMTP HELO argument

Thanks for bringing this to our attention!
Our sysadmin team has now fixed this particular problem.

Quoted 4 lines

451 Cannot check <[email protected]> at this time - please try later)
So Sistina also have no valid postmaster address that is also required by RFC?

No - what you saw was of course a *transient* error as the error code starts with a 4 not a 5 (see the RFC).

There *is* a postmaster address, but there was a transient problem affecting certain deliveries, including messages sent to the postmaster address, but not the list addresses.

Again, I believe this is also now resolved, but do let us know if you notice any more problems!

Alasdair

Signature · 1 line
[email protected]