Mark Constable writes:
On 27/01/16 12:20, Sam Varshavchik wrote: > Use the full dig command. Is this two separate TXT records, or one > single TXT record with two strings. If google-site-verification is a > separate TXT record, it will definitely be ignored.Sorry, yes, it was 2 distinct TXT records... xxxx.com.au. 300 IN TXT "v=spf1 includes:spf.protection.outlook.com -all" xxxx.com.au. 300 IN TXT "google-site-verification=IlCUVOx... etc" > There are a bunch of nested includes here. Maybe one of them resulted > in a stalled DNS lookup, and this is configured to be treated as a > hard failure. The IP address looks fine to me. I think I see the problem, includes != include... v=spf1 includes:spf.protection.outlook.com -all should be... v=spf1 include:spf.protection.outlook.com -all The domain admin atxxxx.com.au has made a mistake setting up the TXT record. I hope you don't mind but while I am here would you/anyone mind giving me a reminder how to "whitelist" the above until they fix the TXT record?
This should be a matter of setting BOFHSPFHELO, BOFHSPFMAILFROM and BOFHSPFFROM to "off" in the smtpaccess file, for the connecting IP address.
pgpwPuqPEPLwk.pgp
Description: PGP signature
------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
