The server which talking to eop should be on the spf.If you listserv directly sending to eop, then the connecting up should be on spf. Or route via the mailrelay which I believe would be already on spf.Is this article still the most current on how to get ListServ to work with O365 and not have messages being sent go into Junk?
https://www.lsoft.com/news/techtipLSV-issue3-2015.asp
Our ListServ is running on Windows and is on the Intranet of our organization, which has switched to using O365 for email. We currently use an SMTP relay. Messages that go to external addresses are fine, as the ListServ's domain has an SPF record that contains the ESAs, but if a message comes From the organization's main domain, from O365 to the ListServ, and the subscribers have a mailbox on the org's main domain (in O365), the messages takes a direct route to the microsoft production server and EOP, so the SPF check fails, and ironically internal mail, going to the listserv, then sent back to internal mail, gets tossed into subscriber's junk folders.
I'm not an exchange server engineer/Office 365 admin/engineer. I'm just going based on what our engineer is telling me.If anyone has more up to date suggestions on how to work with O365 (cloud) from an internal ListServ, please let me know.Krista Landon
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