Hi guys, I have upgraded to Exchange 2013 (Flawless procedure I have to say, well done MS) and have noticed and reaped its benefits. One thing I have lost out on though is the ability to use Forefront (as its discontinued). After trying my best to deal with anti spam and all of this nonsense, I thought about if its possible to introduce a second Exchange serve rin my environment as an Exchange 2010 Server (Co-existence) and then to reintroduce forefront on it as it will act the Front end server, which will link to he back-end server (Exchange 2013) so my users reap the benefits of both. Just would like an opinion and some direction on whether this is possible or practical, and if there is any documentation on co-existence between the two version as I struggled to find any Many Thanks, Shahrad

Hi Shahrad Looks like you want to use Exchange 2010 with Forefront for Anti-spam & Anti-Malware. I would Not bring in Exchange 2010 into your new Exchange 2013 infrastructure. Exchange 2013 has a good Anti-Spam & Anti-Malware build in. Exchange 2013 Anti-Spam and Anti-Malware Protection Fred Chamanara | Advanced Agile Technology LLC | Hire us | please mark "Propose As Answer" if helpful.

I would be inclined to accept that except its not catching spam and where we used to get none, we now get minimum 30-40 spam, even though all of our malware providers like spamhaus and spamcop are all brought in with the same settings!!! Any other food for thought, maybe Im missing something: Things I have done: Enable anti-spam Enable Spamhaus, Spamcop, PBSL & UEC.. Anything else, with rejection threshold and junk threshold set levels too?

This should shed some light on Spam Confidence Level Threshold for you. Fred Chamanara | Advanced Agile Technology LLC | Hire us | please mark "Propose As Answer" if helpful.

Hi Shahrad, We can't install Exchange 2007 or Exchange 2010 in a forest that's been prepared for Exchange 2013 but hasn't been prepared for Exchange 2007 or Exchange 2010. If you want to install Exchange 2007 or Exchange 2010 in a forest, do not prepare that forest for Exchange 2013. REfer to: http://technet.microsoft.com/en-us/library/jj150489(v=exchg.150).aspxFiona Liao TechNet Community Support

Thanks for the post guys, @Fional_Liao : message recieevd it cant be done. okay, thank you @Fred: For now I guess I am going to adjust the thresholds to be more stringent. Do you run an on-premises exchange server? Would be nice to know what your settings are as a comparison Referring this for help btw: http://www.allspammedup.com/2010/06/configuring-exchange-server-2010-anti-spam-settings-for-individual-mailboxes/ I know its for 2010 but same context applies. Many Thanks,

Yes Exchange 2013 On-Premises has good Anti-spam & Anti-Malware build in. I am using On-Premises too. The link has good settings.Fred Chamanara | Advanced Agile Technology LLC | Hire us | please mark "Propose As Answer" if helpful.

Ok I have changed my settings. I noticed my junk threshold was on 5, when default is 4, not sure why. Changed it back, lets see how this works over next few days. Also I have applied CU1 to Exch 2013. I will come back on here and let you guys know for sure. Thanks for suggestions amigos!

Sorry for the double post however I thought I should post my findings thus far: After setting the thresholds and applying CU1 to exchange 2013 at the regular times I would get spam, nothing spam-related comees through ( A success so far!) I noticed in the EAC that next to the "Block Relay" there is an option there to block Spoofed email, something I did not see before (could be that I missed it) and this when update was applied was turned on. At any rate since the combination of your suggestions and CU1 it seems to be holding its own so far. Resolution: 1.) Find out who changed the default setting in the company, and kill him, and revert it back :) 2.) Apply CU1 to Exchange 2013, seems to have affected performance and Spam so far for me. IF I don't reply here again it means problem solved. Thanks very much guys, Kind regards,

Well been running it now for some time. Anti spam with providers don't seem to be doing much to guard this off, I set up transport rules so they set the SCL Level but to no avail either, has MS just lost its grip on Anti-spam since exchange 2010 or am I missing something else I can do???