FYI, we did see more delivery issues to 98.139.171.245 for other Yahoo! hosted
email domains, with our email server logging:
(98.139.171.245) said in response to MAIL FROM (451 4.3.2 Internal
error reading data)
I saw first one at 10:30 am and last one was 7:36 pm (U.S. Central), so it's
possible that that it's not over.
Frank
-----Original Message-----
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of frnk...@iname.com
Sent: Tuesday, May 03, 2016 12:38 PM
To: mailop@mailop.org
Subject: [mailop] Humor of the day
When connecting to this email host ....
telnet 98.139.171.245 25
Trying 98.139.171.245...
2016 May 3 12:17:20 10.18.120.197 BCMSDK - unit 0 L3_ENTRY_IPV6_UNICAST
entry 1487 parity error
2016 May 3 12:17:20 10.18.120.197 BCMSDK - Unit 0: mem:
2103=L3_ENTRY_IPV6_UNICAST blkoffset:9
2016 May 3 12:17:20 10.18.120.197 BCMSDK - Unit 0: CACHE_RESTORE:
L3_ENTRY_IPV6_UNICAST[2103] blk: ipipe0 index: 1487 : [0][0]
Connected to 98.139.171.245.
Escape character is '^]'.
220 mta1014.biz.mail.bf1.yahoo.com ESMTP ready
HELO node5.premieronline.net
250 mta1014.biz.mail.bf1.yahoo.com
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
