New Exchange 2013 unknown messages in queue

Just a quick run down. Just deployed a new Exchange 2013 SP1 no CU just straight SP1 on Server 2012 R2. There is only 1 server here so the exchange is also on the Active Directory. We also have only 1 name on our certificate which is remote.ourdomain.com.
-Also note we have a spam filter in the cloud before it reaches our exchange server and I don't have any spam filtering turned on, on the server itself.
-MXToolbox says we are not an open relay.

On to the problem. I know straight out of the box exchange 2013 is not configured ideally. I noticed when i went to the exchange toolbox and checked the queue viewer i saw a bunch of messages from address "<>". So I cleared out a bunch of them and they seem to slowly come back over time.

The Receive Connectors I did not touch they are default from the server install.

The Send Connectors I created 1 entry on the..
*delivery it is using "MX record associated with recipient domain"
*scoping under address space i have 1 entry "type=SMTP  FQDN=* cost=1" under source server our only server is selected and at the bottom is FQDN which I have left blank.

I've tried many google searches and not found much information regarding this except for older exchange servers, which seemed easier to setup.
LVL 1
easyworksAsked:
Who is Participating?
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.

AlanConsultantCommented:
Hi Easyworks,

I see these too on an SBS 2011 / Exchange 2010 setup (since it is SBS, it is also Exchange on the DC).

I speculate that they are read receipts from spam, possibly where a user has 'read' the spam via a preview window (not sure on that part).

Whenever I see them in the queue, I just delete them (no NDR).

I have never had any queries or complaints from any user saying they are missing or failing to get through to a correspondent.

HTH,

Alan.
0
easyworksAuthor Commented:
I would like to prevent the mesages from showing up in the queue viewer. I am assuming these messages are trying to send out.

Identity: Server2012\3290\1563368095779
Subject: Undeliverable: Alert:You currently-have $200 in-Groupon Rewards-to-Spend! Claim Here
Internet Message ID: <85c5191d-f4c6-438d-905a-265c20f2ff75@Server2012.mydomain.local>
From Address: <>
Status: Ready
Size (KB): 14
Message Source Name: DSN
Source IP: 255.255.255.255
SCL: -1
Date Received: 4/23/2015 8:20:31 PM
Expiration Time: 4/25/2015 8:20:31 PM
Last Error:
Queue ID: Server2012\3290
Recipients:  YourNewCoupons@save.yourallnew-couponrewards.us;2;2;[{LRT=};{LED=};{FQDN=};{IP=}];0;CN=SomeSite Send,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=domain,DC=local;0
queu-viewer.jpg
0
AlanConsultantCommented:
Hi Easyworks,

I guess you could use something like this:

Get-Message -Queue "ServerName\QueueName" -ResultSize Unlimited | where{$_.SenderName -eq "<>" } | Remove-Message -WithNDR $False

Open in new window


It does risk being a blunt instrument though - not something I would recommend.

Personally, I'd rather look at it manually and delete myself since the items sitting in the queue don't seem to cause any issues.

Assuming that is what you want, you could run that once a day or week or whatever suits.

Alan.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

easyworksAuthor Commented:
Resolved this by installing the built in anti spam features and blocking blank senders from the server. Even though we have a cloud base spam filter still needed to turn something on the server itself for people trying to spam us directly.
0

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
AlanConsultantCommented:
Hi Easyworks,

Glad you got it sorted.

Please can you outline in more detail what you did (turned on) so that those who follow can get a working solution to their problem too.

Thanks,

Alan.
0
easyworksAuthor Commented:
Resolved own problem.
0
AlanConsultantCommented:
Yes, I understand that, but I was asking if you could outline in more detail *how* you solved the problem, so that other users that search and find your (solved) question, also find an answer, rather than just a statement that you worked it out.

Thanks,

Alan.
0
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
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.