We safe listed the listserver here.  We've had tickets with MS; they are aware of the issue, but do not seem to see it as a big deal.  Safe listing works (mostly) for us.  Here.  If you were at another institution, safelisting someone else's listserver might seem kind of odd.  But that is what we are recommending.  Whether other mail admins do this, I cannot say.  

I have suggested MS reach out to the vendors and see if they can resolve this together.  Of course, the contacts are not from tech support, they will have to be between developers, so even if this is done, I do not see an early solution.

We encountered this on the Office 365 Discussion List (UCDAVIS).  I believe they use Mailman.  I had an interesting "discussion" (I am told I was shouting) as I asked if "uga.edu" should designate "ucdavis.edu" as authorized to send mail as "uga.edu".  It had been a long day, and the tech sup guy did not deserve it.

    
________________________________________
From: LISTSERV Site Administrators' Forum <[log in to unmask]> on behalf of Helmke,Richard A <[log in to unmask]>
Sent: Thursday, March 16, 2017 4:08 PM
To: [log in to unmask]
Subject: Re: Help needed to troubleshoot Exchange 365 fraud detection error

I mentioned that I had opened a Microsoft support ticket on this 'fraud detection' issue.  I got a phone call today closing the ticket.  They were very nice, but essentially told me that O365's new "Email Safety Tips" feature noted that a mailing list user who posts a note to an off campus server and then receives a copy of that original message from the mailing list (Sender: the list server host and From: the original poster) trips the mechanism to mark the message with the fraud detection warning.  Basically it was a "works as designed" response.

I was given two steps to perform.


  1.   Login to the O365 Portal > Click Admin > Click Security & Compliance > Click Threat Management > Click Mail filtering > Click Edit Default Spam filter policy > Click the drop down for Spam & Bulk actions > Uncheck Safety Tips > Click Save
  2.  Use Microsoft feedback link to comment on my desire to see a change in this feature at http://office365.uservoice.com/

In my case this will involve fielding dozens or hundreds of complains about the interaction of O365 and LISTSERV and helping remote clients contact their site O365 administrators about the wisdom of turning off Microsoft's Email Safety Tips.

If you are also having trouble with these fraud detection warnings, I would suggest that you also open an Office 365 support ticket to let them know how wide spread this feature affects their clients.

Good luck,
-Rich Helmke


________________________________

To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

############################

To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1