Long story short: EOP sucks. From: [email protected] [mailto:[email protected]] On Behalf Of xyz Sent: Monday, July 28, 2014 10:09 PM To: [email protected] Subject: [Exchange] Change in cloud EOP support?
Greetings, Just a heads up and wondering if anyone else has seen new MS support polices yet? EXCHANGE 2010 SP2 RU3 1200 faculty/staff users. We converted from Cloud FOPE to EOP in January 2014 per MS indicating I had to do this within 30 days or no more email delivery. I did this months ago ( a few issues conversion issues which MS resolved ) but all has been working with NO changes: UNTIL 7/23/14 - when we had a flood of user calls with all kinds of SPAM coming into our on premise EXCHANGE 2010 servers from numerous users. As many know with EOP, the quarantine message now can come daily, vs EOP where it was 3 days. Checking with numerous users, no one I spoke with has even had a quarantine message since this problem started so the EOP quarantine process seems to be broken. I opened a ticket with Premier Support and included a couple of clips below with the response. Hard to understand, but summary I was told that the only way to currently deal with SPAM is to inform all 1200 users how to submit SPAM emails on an individual basis to the MS SPAM link. I was told that no one at MS is able to access our EOP other than the SPAM group and that they only deal with the individual SPAM submission, not our EOP. To be fair to MS, they did send me this link to create new transport rules. http://technet.microsoft.com/en-us/library/jj837173(v=exchg.150).aspx Not sure I want to make major changes to production and why we would want this stuff going into on premise, rather than being quarantined and since they have to be hands off, not sure if they will help if something breaks. Anyway, clips below from TAM and Premier support. Thank you Dana Per Premier Support: ##### Hi Dana, Thanks for your patience. This is sort of a canned response but if you were previously a FOPE client and have worked with us on that service, there have been a few changes to how you deal with spam under EOP and O365. Previously we were able to take your samples and direct them to the anti spam team. This is no longer the case per se, as you must now use the spam submission tool for outlook and/or the manual option. Please see this link, http://technet.microsoft.com/en-us/library/jj200769(v=exchg.150).aspx, it will explain how to do it. Now, that being said, I do have the ability to work with the team directly if needed. At this point it is best to recommend that you send me a few of the same examples that you submit via the tool. Please put the raw .msg files in a zip (3-4 of them) and I will take a look. Make sure that your users are not forwarding them to you but rather attaching them so the original headers are retained. There is not much I can do but make recommendations based on the contents of the email themselves, only the anti spam team can now make changes to the edge servers other than the options in the EAC which you can turn on and off (we no longer have access to client interfaces like we did in the previous product due to new privacy laws in the US). If you can send me the samples, I'd be happy to assist, but make sure the same samples are submitted to the anti spam team so that if I have to escalate to them, the submissions are already there waiting. Per Our TAM: ### I haven't run into this until now but from the engineer's response, it is quite clear that due to new privacy laws in the US, the engineers no longer have access to the client interfaces. You should definitely work with the engineer to get him some examples of SPAM you are receiving but also make sure you submit the SPAM examples with that tool to the ant-spam team since they are the ones who can make changes on the edge servers if changes are required.
