Hi
There are no reasons to worry about old Exchange onPrem servers spam filters as
nobody relies on them anymore.
We stopped issuing filter updates two years ago and the filter itself stopped
receiving new features well before that.
+1 to what Paul said
but the best reason for a non-spam friendly infra owner to enforce outbound
limits is to not become a target for hackers.
For example, on Mike's IPs attempted traffic spiked from 1-3 mails/day to 21k
on Aug 18th towards Microsoft alone and, depending on the spam list,
Sorry for the confusion but "protection.outlook.com" refers to O365 inbound,
which is mail directed to Office365 business subscribers, not the consumer side
of the house (outlook.com/hotmail/msn/live/ note that custom domains exist in
outlook.com consumer business too)
The enterprise side
Indeed the abuse@ aliases in ms are inspected by automation and different
topics get different treatment. Child porn reports for example do have a goal
of being 100% reviewed. Bullying, piracy, brand, domains, phish, lots of topics
out there.
At the other side of the spectrum there are one
Michael, the two sample accounts you sent privately had no safesenders at all.
We have some tech that rescues junk senders that are frequently read, and junks
inboxed senders that get no reads etc. this will make panel users differ from
the larger population if for example the panel automation
On this topic, Office 365 EAI support got very positive adoption
https://blogs.technet.microsoft.com/exchange/2017/12/27/eai-support-announcement/
It seems non-ASCII emails and domain names will get more and more popular
___
mailop mailing list
One approach is to have the landing page for the unsubscribe include another
confirmation action/button. This way a GET of the page for security inspection
will not trigger the actual removal from the list
> On Mar 1, 2018, at 3:36 PM, "mailop-requ...@mailop.org"
>
ot having any
explicit emails or spoofs, etc. This is actually also good signal as it tells
us (and you) that this user really does not want that mail.
Regards,
Mihai Costea
O365 Information Protection
Message: 1
Date: Thu, 14 Dec 2017 11:11:47 +0100
From: Stefano Bagnara <mai...@bago.o
