> At a guess it's something to do with your SPF record. > What domain are you sending from when you get the problems? Is the SPF record > for that domain set up to allow sending through the Office365 account?
Thanks Paul, OL2016 connects via IMAP to Office365 registered with a domain, but most outgoing messages are actually sent via POP using domain2. I had tried connecting the domain2 accounts to Office365, and even changing the DNS pointers to Office365, but the result was messages going out as "Sent by [email protected] on behalf of [email protected]" which was in many ways worse. Sending VIA POP avoids that on-behalf-of issue, but creates another one. I'll take a look at SPF - https://technet.microsoft.com/en-us/library/dn789058(v=exchg.150).aspx Scott -----Original Message----- From: mailop [mailto:[email protected]] On Behalf Of Paul Smith Sent: Thursday, January 5, 2017 10:24 AM To: [email protected] Subject: Re: [mailop] False positive on spoofing On 05/01/2017 16:06, Scott E Bonacker CPA wrote: > Since upgrading to a new laptop with OEM Win10x64, and OL2016 connected to an > Office365 account, I have also been sending messages to various lists via POP > using a domain different than the one registered with Office365. That has > resulted in false positive alerts when messages are distributed by some > systems - the alert below was inserted by LISTSERV-TCP/IP release 16.0. > Interestingly, msgs distributed by Yahoo Groups don't get a similar alert. > Is there anything a user can do to avoid creating false-positives like this, > or is this just a fact of life now? At a guess it's something to do with your SPF record. What domain are you sending from when you get the problems? Is the SPF record for that domain set up to allow sending through the Office365 account? _______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
