Andrew,

After reviewing the issues, we potentially had several hundred O365 sites that might be affected.  This number discouraged us from attempting to rewrite all the addresses for these domains.

 

LSoft provided us with a DKIM enabled LISTSERV.  We think it helps, but we still see a frequent number of ‘fraud detection’ warnings with DKIM signing and inclusion in the SPF records of the sending host and the recipient’s host.

 

Still working the problem.  I submitted an O365 support ticket (and suggest that others should too) to let Microsoft that we aren’t happy.

-Rich

 

From: LISTSERV Site Administrators' Forum [mailto:[log in to unmask]] On Behalf Of Andrew Bosch
Sent: Thursday, March 2, 2017 11:27 AM
To: [log in to unmask]
Subject: Re: Help needed to troubleshoot Exchange 365 fraud detection error

 

So how is the testing progressing for the workaround? Is there an estimated release date for the fix?

 

Andrew

 

 

From: LISTSERV Site Administrators' Forum [mailto:[log in to unmask]] On Behalf Of Helmke,Richard A
Sent: Wednesday, December 7, 2016 10:12 AM
To: [log in to unmask]
Subject: Re: Help needed to troubleshoot Exchange 365 fraud detection error

 

While LSoft is developing a workaround for this O365 bug/feature, we are starting to experiment with adding our O365 sites' domains to DEBUG_DMARC_REWRITE (in go.user).  This applies LSoft's DMARC sender rewrite to these domains.  An initial test looks hopeful.

-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, 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, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1