I agree, but this firewall in question is at Microsoft. Securence, our server, does not refuse connections. The "450 4.4.316” error is from a Microsoft server, not Securence.
Michael at Microsoft has been helping, but, so far, the Microsoft network techs are unable to comprehend that Securence isn’t sending the 450 error. So, has anyone else experienced this issue? > On Oct 4, 2018, at 8:53 AM, Greg Robinson <[email protected]> wrote: > > Sounds like a firewall config issue: > > https://social.technet.microsoft.com/Forums/en-US/ef63dcb2-b814-4638-964c-ef5fc75612df/message-delayed-with-450-44316-connection-refused?forum=onlineservicesexchange > > <https://social.technet.microsoft.com/Forums/en-US/ef63dcb2-b814-4638-964c-ef5fc75612df/message-delayed-with-450-44316-connection-refused?forum=onlineservicesexchange> > > https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges?redirectSourcePath=%252fen-us%252farticle%252fOffice-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#BKMK_EXO > > <https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges?redirectSourcePath=%252fen-us%252farticle%252fOffice-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#BKMK_EXO> > > > -Greg > > -----Original Message----- > Date: Wed, 3 Oct 2018 22:00:52 +0000 > From: Michael Wise <[email protected] > <mailto:[email protected]>> > To: Ryan Krueger <[email protected] <mailto:[email protected]>>, > "[email protected] <mailto:[email protected]>" > <[email protected] <mailto:[email protected]>> > Subject: Re: [mailop] Anyone else seeing EOP/O365 unable to connect > when delivering? > Message-ID: > > <bl0pr00mb0291a553ba647e680a694c1d80...@bl0pr00mb0291.namprd00.prod.outlook.com > > <mailto:bl0pr00mb0291a553ba647e680a694c1d80...@bl0pr00mb0291.namprd00.prod.outlook.com>> > > Content-Type: text/plain; charset="utf-8" > > > > Are you doing any form of Greylisting? > > Why do you throw the 450 4.4.316 error in the first place? > > Aloha, > Michael. > -- > Michael J Wise > Microsoft Corporation| Spam Analysis > "Your Spam Specimen Has Been Processed." > Got the Junk Mail Reporting > Tool<http://www.microsoft.com/en-us/download/details.aspx?id=18275 > <http://www.microsoft.com/en-us/download/details.aspx?id=18275>> ? > > > > -----Original Message----- > From: mailop <[email protected] <mailto:[email protected]>> > On Behalf Of Ryan Krueger > Sent: Wednesday, October 3, 2018 2:27 PM > To: [email protected] <mailto:[email protected]> > Subject: [mailop] Anyone else seeing EOP/O365 unable to connect when > delivering? > > > > We have had multiple customers finding EOP and O365 getting messages delayed > when delivering to our servers. Our customers have noted we are not the only > destination experiencing this behavior, it seems it is not isolated to > Securence. > > > > The behavior is that EOP/O365 servers get a connection refused error when > connecting to our servers. The error is “450 4.4.316 Connection refused > [Message=Socket error code 10061]…”. This happens for a while and the > messages eventually deliver. Delay times range from a few minutes to over an > hour, though not all messages experience this behavior. > > > > Our software doesn’t have the capability to refuse a connection (we write it > all), our servers are not under heavy load, our load balancers are not under > heavy load, our load balancers are showing no errors, we are unable to even > see the attempted connections. This appears like a networking issue. > > > > One of our customer’s business partner has opened a ticket at Microsoft but > experienced difficult and slow support. The support tech simple says the > other side is refusing the connection, the end. Not helpful. It has been > escalated but this has been even slower and tedious. > > > > Does anyone else see this issue? Is there anyone at Microsoft that is able > to look into this? > > > > -Ryan > > Securence Engineer > > [email protected] <mailto:[email protected]><mailto:[email protected] > <mailto:[email protected]>> > > _______________________________________________ > > mailop mailing list > > [email protected] <mailto:[email protected]><mailto:[email protected] > <mailto:[email protected]>> > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchilli.nosignal.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fmailop&data=02%7C01%7Cmichael.wise%40microsoft.com%7C336f10bd3b8b41f8bbf808d6297834af%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636741993590750384&sdata=A%2Bj%2B5s2EoRxD7NbENPszSlvUen3XWb6lgxWXsO%2FnhSE%3D&reserved=0 > > <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchilli.nosignal.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fmailop&data=02%7C01%7Cmichael.wise%40microsoft.com%7C336f10bd3b8b41f8bbf808d6297834af%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636741993590750384&sdata=A%2Bj%2B5s2EoRxD7NbENPszSlvUen3XWb6lgxWXsO%2FnhSE%3D&reserved=0> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <https://chilli.nosignal.org/cgi-bin/mailman/private/mailop/attachments/20181003/b98c222a/attachment-0001.html > > <https://chilli.nosignal.org/cgi-bin/mailman/private/mailop/attachments/20181003/b98c222a/attachment-0001.html>> > > ------------------------------ > > Message: 3 > Date: Thu, 4 Oct 2018 08:45:58 +0000 > From: Benjamin BILLON <[email protected] <mailto:[email protected]>> > To: "[email protected] <mailto:[email protected]>" <[email protected] > <mailto:[email protected]>> > Subject: [mailop] Is SenderID deprecated? > Message-ID: > > <he1pr0602mb3435cb10e9fb9da2ebdcbdcbb4...@he1pr0602mb3435.eurprd06.prod.outlook.com > > <mailto:he1pr0602mb3435cb10e9fb9da2ebdcbdcbb4...@he1pr0602mb3435.eurprd06.prod.outlook.com>> > > Content-Type: text/plain; charset="utf-8" > > The RFC 4406 is not obsolete, only experimental. > > In the past, Hotmail/Live heavily relied on it, but it's not even visible in > Outlook's headers anymore (advantageously replaced by DKIM, and DMARC). So > Hotmail's out. > > Microsoft Exchange servers also used it, but it's not clear it's still the > case. > The article > https://docs.microsoft.com/en-us/exchange/antispam-and-antimalware/antispam-protection/sender-id?view=exchserver-2019 > > <https://docs.microsoft.com/en-us/exchange/antispam-and-antimalware/antispam-protection/sender-id?view=exchserver-2019> > says "basically unchanged from Exchange Server 2010", which kind of scares > me. But the page also says it checked the "RECEIVED SMTP header", so > basically the HELO/EHLO; it mentions the PRA, but it's not the definition I > knew (nor what's in the RFC): "The IP address of the authorized sending > server is referred to as the purported responsible address (PRA).". > In short, I don't understand this article and I'm glad I'm not administrating > an Exchange server right now. > > In my _opinion_, only old (non-updated) Exchange servers might reject or > consider negatively emails with missing SenderID record in their sending > domains, so it _should_ be ok to stop setting up these records. > > Dear Microsoft folks around there, what's the status of it from your > perspective? > > Cheers, > -- > Benjamin > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <https://chilli.nosignal.org/cgi-bin/mailman/private/mailop/attachments/20181004/50e23bcd/attachment.html > > <https://chilli.nosignal.org/cgi-bin/mailman/private/mailop/attachments/20181004/50e23bcd/attachment.html>> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > mailop mailing list > [email protected] <mailto:[email protected]> > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > <https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop> > > > ------------------------------ > > End of mailop Digest, Vol 132, Issue 8 > ************************************** > _______________________________________________ > mailop mailing list > [email protected] > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
