You might ask them if they'll let you use one of their servers as a smarthost until it gets sorted out.
From: Steve Szabo [mailto:steve...@gmail.com] Sent: Monday, April 12, 2010 1:09 PM To: MS-Exchange Admin Issues Subject: Re: 4.4.2 Connection Dropped When I was on the phone with them, that issue really did not come up. I think the problem is more that the rDNS record disappeared. \\Steve// On Mon, Apr 12, 2010 at 1:52 PM, Campbell, Rob <rob_campb...@centraltechnology.net<mailto:rob_campb...@centraltechnology.net>> wrote: Any chance Verizon mistakenly published that Class C you're in as being a dynamic / DHCP range? From: Steve Szabo [mailto:steve...@gmail.com<mailto:steve...@gmail.com>] Sent: Monday, April 12, 2010 12:47 PM To: MS-Exchange Admin Issues Subject: 4.4.2 Connection Dropped We are having a serious problem sending mail out from our Exchange server. We have Exchange 2007, fully patched, running on Server 2003 R2, again, fully patched. The problem started Thursday when it was noted that some e-mail was not going out, but sitting in the queues. The message give was ""421 4.4.2 Connection dropped.' Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts." A check showed that we were listed on an RBL, NOMOREFUNN which apparently blocks whole ranges of IP addresses--checking showed that the whole class C network we are part of was blocked by them. I applied for a removal of the block, but it never happened, and now that RBL is timing out when I try to check it using MXToolbox, but I can reach it manually, and, despite the requests, it still shows us as being on the list. Their complaint is "washdc.fios.verizon.net<http://washdc.fios.verizon.net>. Dynamic IP or generic rDNS". It does appear that there is a generic rDNS right now, which there did not used to be. I have talked to Verizon about getting this fixed, but I do not think this is the source of the problem, since whether the mail goes through is a hit or miss affair. I do not believe that NOMOREFUNN is a widely used RBL, and do not think it is a source of the problem, however, it may be that the rDNS is. Am I going the right way with this, or am I barking up the wrong tree and fixing the rDNS will not fix the problems we are having? -- \\Steve// ************************************************************************************************** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ************************************************************************************************** -- \\Steve// ************************************************************************************************** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. **************************************************************************************************
