Xero - beautiful accounting software

Xero Business Help Center

Xero Business Community

Community > Feature Requests >

Email Send As @company-name.com not message-service@post.xero.com

Started by Chris Neophytou -   in Feature Requests | Not planned

Email Send As @company-name.com (not message-service@post.xero.com)

The new feature: http://blog.xero.com/2013/06/more-control-over-your-emails/
introduced on June 17 2013 has introduced the mandatory display of message-service@post.xero.com from outbound emails.

A feature in line with the proposal would:
- improve user corporate branding adding value to their business
- resolve the potential for confustion and save time to explain the reason for a strange email
- save user customer goodwill thereon
- improve user-Xero trust

I expect the full brunt of the update to hit Xero support circa 1st July when users normally send out auto-emails. If Xero could resolve this by then that would be fantastic.

useful related posts:
Relevant Community post here: Email Settings - Using Company SMTP Server for sending.
Cheers, Brittany
Official Xero Reply
To reiterate what Andrew said earlier, there were issues when sending invoices by impersonating email addresses. By sending your invoices from the message-service address, there’s a much higher chance of them being delivered. Whatsmore, the subject line will always say who the email has come from, and you can set the email address that you’d like replies to come to.

We’re not planning to change how this works, but hopefully this helps you all with understanding why we do this now.

Matt Oldfield (Community Manager)  

Best Reply as chosen by Brittany H (Community Manager)
@all - as promised, we've just finished writing up a document, to help explain how emails are sent from Xero and to address the concerns several of you have raised on this thread. Note that while we have no immediate plans to make any updates to this area, we are not ruling out future enhancements.

Also, regarding the NDR bug - this has now been fixed, apologies for the issues this has caused.

Andrew Tokeley (Xero Staff)