Fair question -- none of our infrastructure uses 10.15.194.x. In any offline 
thread someone else believes this is a Dell device (based on the "EMC").

Frank 

-----Original Message-----
From: mailop <mailop-boun...@mailop.org> On Behalf Of Brandon Applegate via 
mailop
Sent: Thursday, June 04, 2020 7:50 PM
To: mailop@mailop.org
Subject: Re: [mailop] Strange information upon SMTP connection to icloud email 
server

On Thu, Jun 4, 2020 at 8:20 PM Frank Bulk via mailop <mailop@mailop.org> wrote:
>
> I was reviewing the details on an email deliverability error and I saw the
> following recorded by our "check script" when connecting to an icloud.com MX
> record:
> ===============================================
> Trying 17.57.154.7...
>
> Connected to 17.57.154.7.
>
> Escape character is '^]'.
>
> 2020 Jun  4 18:20:48 10.15.194.199 message repeated 82 times: [ BCMSDK -
> unit 0 MMU subblock 12   reg EMC_ERROR_1 field
> EMC_CSDB_2_UPPER_BUFFER_UNCORRECTED_ERROR(value = 0x8000000) has  MMU parity
> error]
> 2020 Jun  4 18:20:49 10.15.194.199 BCMSDK - unit 0 MMU subblock 12   reg
> EMC_ERROR_1 field EMC_CSDB_2_UPPER_BUFFER_UNCORRECTED_ERROR(value =
> 0x8000000) has MMU parity error
>
>
> Timeout connecting to '17.57.154.7'
> connecting to an icloud.com MX record
> ===============================================
>

Wow, looks like maybe a NIC error message (I’m guessing this based on
the “BCMSDK” - Broadcom SDK ?) “bled over” into the smtp connection ?
How does that even happen ?  Some sort of TCP offload on the host tied
in a knot ?

Dumb question - forgive me in advance - this wouldn't be from
something on your side (i.e. your monitoring box) ?  I guess if
10.15.194.199 isn't one of your IP's internally the answer would be
no...

_______________________________________________
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

Reply via email to