On 9/1/2016 9:32 AM, Aaron Richton wrote: > On Thu, 1 Sep 2016, Dave Brockman wrote: > >> For Example: >> > > That's just base64, use e.g. openssl enc -d -base64 which gives:
Thanks for that!
> Reporting-MTA: dns;BAY004-OMC3S15.hotmail.com
> Received-From-MTA: dns;NAM02-CY1-obe.outbound.protection.outlook.com
> Arrival-Date: Wed, 31 Aug 2016 06:30:48 -0700
>
> Final-Recipient: rfc822;tmanr...@wdef.com
> Action: delayed
> Status: 4.4.7
> Will-Retry-Until: Fri, 2 Sep 2016 06:30:54 -0700
>
> Final-Recipient: rfc822;rmccl...@wdef.com
> Action: delayed
> Status: 4.4.7
> Will-Retry-Until: Fri, 2 Sep 2016 06:30:54 -0700
>
> (somehow I'd guess that you are aware of the delays. Perhaps the final
> permfail will have more details, if you're lucky? Or perhaps network
> investigation looking critically at
Yes, those are attached to Delay NDR's that state:
This is an automatically generated Delivery Status Notification.
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
Delivery to the following recipients has been delayed.
tmanr...@wdef.com
rmccl...@wdef.com
Nothing useful here :(
> $ dig BAY004-OMC3S15.hotmail.com. +short
> 65.54.190.153
>
> would help. I can ping that IP -- can you?)
The mail server in question can, by IP address and FQDN.
I cannot see a connection attempt from that IP address in SMTP logs,
however. Running a capture on the firewall logs now.
Thank you for looking!
Regards,
dtb
signature.asc
Description: OpenPGP digital signature
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
