Exchange 2013 SP1 all roles installed on 1 server in server 2012 hyper-v. Our queue is filled with spam that comes from <some id)@ourdoamin and goes to some unknown user on an unknown domain. We shouldnt use builtin recipient filtering due to multi role on 1 server (according to technet article). So my question is what are our options to combat our queue problem? Here is a link to a exchange forum with the same question. I only link it here so you can see the queue and the associated header:

Featured Links*

I think the more important question is, why are you not separating the roles like you should be? How many users do you have, and why are you running everything on one server? Is this your only Exchange server in your org?

I think the more important question is, why are you not separating the roles like you should be? How many users do you have, and why are you running everything on one server? Is this your only Exchange server in your org?

That's an easy one, don't have the resources/capital for MS servers. Most are Linux servers but we do have 1 MS server that does Remote Desktop services. Less than 10 users at the moment but we will be adding more users as time passes. Yes it is the only exchange server. Can you separate roles after designating all roles to a server?