Xibo Community Emails

The automated Xibo Community summary emails (and likely others) are landing in my junk folder, and that’s probably the case for subscribers to O365 and other major providers because the sender domain can’t be validated against either MX or SPF:

Authentication-Results: spf=none (sender IP is 108.61.221.71)
 smtp.mailfrom=xibo.org.uk; <redacted_domain>.com; dkim=none (message not signed)
 header.d=none;<redacted_domain>.com; dmarc=none action=none
 header.from=xibo.org.uk;compauth=fail reason=001
Received-SPF: None (protection.outlook.com: xibo.org.uk does not designate
 permitted sender hosts)

Your MX records for xibo.org.uk refer to Google’s mail servers, but it looks like these are being sent from your own infrastructure. You might want to set up an SPF record for xibo.org.uk like you have for springsignage.com:

springsignage.com.      10089   IN      TXT     "v=spf1 mx ip4:108.61.221.71/32 include:spf.mailjet.com include:_spf.google.com include:_spf.elasticemail.com ~all"

Thanks for your message. You’re quite correct that that’s an oversight and it should be resolved for you now.

If you could, please update your SPF records with the allowed IP address. All of the Xibo Community summary emails end up in quarantine for me:

| [

Received-SPF](RFC 4408 - Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1) Fail (protection.outlook.com: domain of xibo.org.uk does not designate 2001:19f0:7402:363:5400:ff:fe01:650a as permitted sender) receiver=protection.outlook.com; client-ip=2001:19f0:7402:363:5400:ff:fe01:650a; helo=smtp.springsignage.com;

Thank you!

Thanks for bringing this to our attention. I’ve added the IPV6 address now too so that should resolve itself once caches expire.

1 Like