Emails stack on queue when using MX record


When I'm using MX record associated with the recipient domain on send connectors I see in the queue viewer some emails that are stacked for a long time (It seems that are junk emails), and if I change the send connector to use a smart host sender the emails are immediately transferred

Any idea why it's happening because I received emails and not send, the way it is not moved from the queue immediately when I'm using MX record?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Is the MX record pointing to an IP address instead of an A record maybe?

Also be sure to perform an open relay test against that exchange server ( or another helpfull article in that regard is .
compx_itAuthor Commented:
I'm not anderstood your quetion, maybe I'll be more clear, when i'm saying MX record I meen on the delivery option.
I attach a screenshot for example
Forget about the mx record question for now, i'll come back to it when needed. For now, can you perform the test below and let us know the outcome?

(From From the remote client, follow these steps:
Click Start, click Run, type telnet, and then click OK.
At the Telnet command prompt, type set local_echo, and then press ENTER.
At the Telnet command prompt, type open sbs-IP-address 25, and then press ENTER (where sbs-IP-address is the external public IP address of the Small Business Server computer).

The output is similar to the following:
220 server.smallbusiness.local Microsoft ESMTP MAIL Service, Version: 5.0.2195.4905 ready at "date" -0500
Note The "Version" reference may vary, depending on the version of Small Business Server.
Type ehlo, and then press ENTER (where anydomain is not the Small Business Server computer's e-mail domain. Make sure that the last line is:
250 OK
Type mail, and then press ENTER (where youremail@anydomain is an SMTP address that is not hosted on the Small Business Server computer). Make sure that the result is:
250 2.1.0 OK
Type rcpt, and then press ENTER (where user@spam is not your e-mail domain). Make sure that the result is one of the following two responses:
550 5.7.1 Unable to relay for


250 2.1.5
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

First, in the queue, really try to get the details of all those email (at least check from: and to:, read subject to get more sense of it). It could be real emails from your users, or it could be out of office replies. It could also be NDR's.

Next, find out WHY it's in the queue. Are they non-existent email addresses? Or are they going to real addresses?
If they're non-existent, it's only logical it's in the queue.
If they're going to real addresses, find out if you're on a blacklist.
compx_itAuthor Commented:

I figure out that the emails that are stuck on qeueu are with no sender adress: From Address: <>

Any idea how to fix it, i'm thinknig the problrm is with the spam software, i'm using third part software for spam, not edge.
What about the To: address ? What about the subject?
compx_itAuthor Commented:
Identity: WIN-2012-1\586\58884001628226
Subject: ‏‏לא ניתן למסירה: [SPAM] My photo
Internet Message ID: <ae8044a0-403d-41e2-89a3-2defd1789ed2@WIN-2012-1.mail.local>
From Address: <>
Status: Ready
Size (KB): 101
Message Source Name: DSN
Source IP:
SCL: -1
Date Received: 01/04/2015 16:23:35
Expiration Time: 03/04/2015 16:23:35
Last Error:
Queue ID: WIN-2012-1\586
Recipients:;2;2;[{LRT=};{LED=};{FQDN=};{IP=}];0;CN=575,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mail,DC=local;0
Just to be sure, is  your email domain
In that case, it's due to the user accompanya29 not existing (and the other emails probably have some random username as well)

If is NOT your email, it means some spammer sent it to your email domain (but with a non-existent user), then your mail server want to send it back telling the user "this user doesn't exist", but since spammers don't use real email addresses, it will now be in the queue.
The only way to solve this is to NOT use non-delivery reports for spam, or if it's not available in the spam settings, then you should disable it globally (but normal users making typos, will also NOT get an NDR).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
compx_itAuthor Commented:
Thanks for your help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.