451.4.4.0 Primary target Ip address responded with "421.4.4.2 Connection dropped due to SocketError "Attempted failover to alternate host, but taht did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.
and I receive some e-mail error.
Delivery is delayed to these recipients or groups:
This message hasn't been delivered yet. Delivery will continue to be attempted.
The server will keep trying to deliver this message for the next 1 days, 19 hours and 46 minutes. You'll be notified if the message can't be delivered by that time.
Do you have a reverse lookup for your MX record configured publicly? Some of these domains will not accept mail from a domain that they cannot do a reverse lookup on.
_____________________________
Ibrahim Benna - Microsoft Exchange MVP Forum Moderator Navantis
I'm getting this right now too. Here's the situation.
Two - Exchange 2010 SP1 Servers in a DAG Both send connectors have the same thing mail.domain.com instead of their actual host names. I setup a pool on the F5 and a virtual server with all ports working. I changed the NAT forwarding to the virtual server (exchange server pool) for failover.
Now emails are being marked as spam because the rDNS doesn't match the host name of the computer sending the mail. The MX record points to mail.domain.com but the outgoing mail is coming from server1.domain.com or server2.domain.com
We added CNAME records on the external DNS server for server1.domain.com and server2.domain.com to point the server names to the mail.domain.com host record/server.
We're still getting outgoing mails blocked by other companies.
HELP!!!
< Message edited by ptireland -- 21.Sep.2011 6:41:11 PM >
Do you acquire a about-face lookup for your MX almanac configured about? Some of these areas will not acquire mail from a area that they cannot do a about-face lookup on.
Do you acquire a about-face look up for your MX almanac configured about? Some of these areas will not acquire mail from a area that they cannot do a about-face look up on.
ok, wow, this one was not fun. I called MS opened a ticket. they turned on verbose smtp logging (done in the registry). after looking at the log file the MS mail flow expert did this: set-sendconnector IgnoreSTARTTLS true (that's not the exact syntax, but that's what we did)
bingo, all queues emptied out! our error was: 421.4.4.2 connection dropped due to socketerror. I hope people with the same error find this thread!
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2010] >> General >> 421.4.4.2 connection dropped due to socketerror 
421.4.4.2 connection dropped due to socketerror - 
RE: 421.4.4.2 connection dropped due to socketerror - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
