Re: Problem delivering to yahoo

Hello Rob,

Am 28.10.2019 um 16:50 schrieb Rob Berendt <rob@xxxxxxxxx>:

Message header:
https://code.midrange.com/1202ac4fe8.html

Unimportant in this context.

The actual message was limited to:
[WARNING: ATTACHMENT UNSCANNED]Failure Notice
NONDELIVERY@xxxxxxxxxxxxxxxxxxxx
Mon 10/28/2019 10:38 AM
To: Rob Berendt <rob@xxxxxxxxx>
1 attachments (3 KB)
test from gdihq;

Hmm. Not exactly helpful. I was hoping for some "mailer-daemon" bounce. Usually, the plain response from the denying server is contained there.

This "Cisco Cloud Content Security Management Virtual Appliance" (AKA: Cisco Ironport Mail Appliance) is the last relay and sending outbound mail to Yahoo, then?

When I send to yahoo I get a reply to my work account

And that's the senseless message from above?

Maybe you can check with the guys managing the Ironport, I know that it has extensive logging and with correct time these should be able to look up the mail transaction. The reply from yahoo's incoming mail relay is what I need to help finding a solution.

Maybe others are right about reverse DNS. My guess would be that the domain part of the sending mail address from the i LPAR seems invalid to Yahoo lately for unknown reasons, because it's (usually) not known for outside DNS. (I wonder how it worked before, then.)

Instead of just guessing I propose to find facts. Especially since you told, it worked before.

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc