Email Settings - Custom sending domain security SPF;Dkim;Dmarc
With the implementation of Google and Yahoo email security please enable the ability to send out invoice, quotes and statements using our own domain.
We are seeing more emails that are sent from within Xero being flagged as Spam or put in Quarantine, especially if the recipient is using Outlook 365.
Xero needs to implement the ability to send from Xero from our own domain.
Please furnish us with SPF sending ip/include host name and DKIM certificate. This will reduce the number of email blocked/junkmail, and increase the security of mail sending.

-
Kyle Spence commented
I have successfully implemented DMARC for many organizations. SPF alignment is not necessary if you have DKIM alignment! Your teams can still use a return-path pointing to Xero (to get bounce backs, NDRs, etc), we just need a custom DKIM signature to use a custom From: domain. This is essential to modern verification, you can also make it very clear to organizations that using a custom From: domain relieves your support team of any assistance to email issues.
At the very least let us use a SMTP relay... We NEED a custom From: domain. Xero has already implemented DMARC and BIMI, let us too! This is a necessity that is 5 years overdue.
-
Wajeeha Bhatti commented
Email address to send Sales invoices from xero is coming as:
messaging-service@post.xero.com.
My client wants to change it to his email i.e. Custom sending domain security
Please can you add this change, because it is causing confusion to my client's customers. -
Alex Graham commented
ridiculous that this feature doesn't exist - several clients complain that they don't trust quotes or invoices not coming from a company email address and flag them as spam
-
Ben Fairless commented
This appears to be a relatively basic feature that all other accounting platforms have. I don’t understand why this is so hard to implement.
-
Brendan Carmichael commented
Lack of mail authentication support (SPF/DKIM/DMARC) is significant enough for me to strongly recommend against Xero to anyone considering it.
-
Nicole Reilly commented
As a partner, this issue is a major blocker to my recommending Xero as a solution for my clients over other accounting software.
All have this feature except Xero!
Late Payments are bad enough for business, without this unneccessary extra hurdle.
-
MAHCA Treasurer commented
This is critical since email security is getting tighter. Just allow us to put in smtp parameters and use those.
-
Marc Paquin commented
I am surprised that this is not possible. I received recently confirmation from multiple clients that they did not receive a quote or invoice when I sent them via Xero. This is impacting our business and sales cycles.
-
Shashwat Singh commented
Send all your xero emails from your own domain in just 2 mins. Watch demo : https://www.youtube.com/watch?v=MNsvdL-ppls (No need for multiple tools, relay systems, or complicated setup)
Contact : https://www.xeroemail.com.
-
akshay Singh commented
I think this can help: https://www.youtube.com/watch?v=QaIJw5M2rGE&t=1s (Very simple to use, takes just 5 mins to setup and it takes care of the rest). Sends all your xero emails from your own domain.
-
Michael Pepera commented
I'm having significant problems getting my invoices submitted to a large corporation whose IT department has no intention of whitelisting Xero's email server.
It is absolutely unacceptable that Xero has stated that they have no intention of implementing this feature. We pay a subscription service so that Xero can continually update the product and maintain compliance with industry security and accounting requirements.
-
Jake Cormier commented
So many of our invoices are going to spam now, because Xero stupidly uses one email address for sending out all their customers invoices across the world. So if one xero customer abuses this and gets labeled as spam, we all suffer.
Xero absolutely needs to make this a priority.
-
Victoria Buyers commented
+1
Please resolve this to stop invoice emails going to the junk folder. -
Kevin Gallagher commented
Agreed on this. We are starting to get rejected invoice emails from some of our customers. They have no reason to recognize a Xero domain name.
-
Chris Foottit commented
Why hasn't this happened yet?!
-
Daryl Leigh commented
This is very important!!!
-
Mike Baptiste commented
This is a HUGE issue for us. AOL and Yahoo constantly block our Xero emails (directly impacting our ability to get paid because clients never see the invoice) All our other systems like Hubspot, Zendesk, etc send using our domain and a specified email address (ar@domain.com etc). We just add the appropriate SPF and DKIM CNAME records and it works great. They ALWAYS get emails from Zendesk. But from Xero? Depends who their email is with. I realize it's easy to say this is an issue with AOL/Yahoo because the Xero emails ARE spf/dkim compliant. But they get blocked anyway and it's the only system we have this issue with.
For people that choose to use Xero to send the email - you should include the bounce error in the notification emails that a Xero email bounced. It's impossible to troubleshoot. It's usually a typo,but we've had a few instances that the email address was 100% correct - but still bounced. We had no idea why.
-
Chris Apperley commented
Bit of a no brainer really
-
Jeremy Cooper commented
+1 - Please, We are an IT Comapany and our own software is flagging the emails as impersonation, The messaging-service@post.xero.com email has been flagged as spam in many systems because anyone, Even scammers, can purchase a xero subscription and send invoices to whoever they want
-
Edward Kay commented
+1 (more if I could)
It seems many company firewalls are now explicitly marking messages from messaging-service@post.xero.com as spam, or in some cases deleting them without even reaching the recipient's inbox. I have examples of both from my clients. This is despite the Xero address passing SPF / DKIM / DMARC checks.
PLEASE give us the option to set up DKIM records on our own domains so we can authorise Xero to send email using our own domains.