asked on

Messages stuck in que

I have about 6 domains that are stuck in que for an exchange 2010 sp1 update 6 server on Windows 2008 R2 Server. The rest of the emails are flowing fine. Verified not being blocked because we are blacklisted by mxtool. Changed external dns and restarted transport services. No go. All roles are on one server. Using hub transport to send and receive messages. It is also virtualized on VMware 5.1 esxi host.
logs.docx

R--R

Check for IP blacklist.
Check for reverse dns record for your domain.

dns8268

ASKER

I checked with mxtoobox.com to see if it was blacklisted and wasn't. Reverse DNS query also is working.
mail.sparboe.com. A IN 7200 42ms 66.103.181.30

Hypercat (Deb)

What error message appears in the Queue Viewer in the EMS for those domains? Are you using external DNS servers on the Exchange server, or through DNS forwarders?

Just to determine if it is a DNS issue, try adding the correct IP addresses for the MS servers for those domains to the local HOSTS file on the Exchange server and see if that allows the email to go out.

dns8268

ASKER

The error is LastError : 451 4.4.0 Primary target IP address responded with: "554 vanguard.verizonwireless.com." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.

Using External DNS on Exchange Server.

Tried adding the dns on the local host for one of the stuck ques, but didn't help

Dan Arseneau

Also check to see if they are possibly all using the same gateway service...ie. MessageLabs, Postini, etc.

dns8268

ASKER

Not sure how to find that out except to phone all of them to find out. Is there a different way?

Dan Arseneau

I see you're going through mxlogic. I would speak to them...have them do some traces.

dns8268

ASKER

Only incoming mail is going through mxlogic, outgoing doesn't use a smart host.

Dan Arseneau

Then that may be part of your issue. All mail environments are not created equal. The message is received by mxlogic, so if a reversedns lookup is performed, they'll receive a different value; they'll get the value of Exchange box (NAT). Not all domains do reverse lookups, which explains the seemingly randomness of the problem.

Dan Arseneau

...hmmm. I just did a SMTP test and it's reporting that you may be an open relay.

dns8268

ASKER

I just did an open relay test and it said port 25 was closed on 66.103.181.30

dns8268

ASKER

I have our ISP providing a reverse lookup for mail.sparboe.com , shouldn't that take care of the reverse look up? If not do you have a solution

Dan Arseneau

My test was on MXlogic

208.65.145.2 resolves to mxl145v2.mxlogic.net

Have you put in a SPF record? This will help for most issues.

http://www.openspf.org/FAQ/Examples

dns8268

ASKER

Been really digging and I think the 6 domains use iron port filtering and we apparently have a score of -2.2 and they are blocking our mail. I assume we go under that and it flows and then above and it stops, It would explain why it is sporatic. Anyway we can get whitelisted with Ironport?

ASKER CERTIFIED SOLUTION

Dan Arseneau

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

dns8268

ASKER

I changed our outgoing email to go through MXLogic as well and boom, mail flowed. We were paying for it anyway and not using it.