Email Authentication based on Client Domain
We want the FROM address set to our domain so that 'via Shipstation.com' does not appear on gmail. We also want to include your spf/senderId records in our spf/senderId records, have the email signed with our DKIM key and have the links use our subdomain instead of email.shipstation.com.
Here's how this works on a few of the major ESPs:
This will significantly improve deliverability and professional appearance.
VP of Marketing Technology
I’ve posted the following response to our ShipStation community thread and want to also share here for transparency:
Thank you for your candor with your feedback. We definitely understand and appreciate that the lack of responsiveness on this specific issue has been frustrating. We are working internally to improve how we review and respond to feedback so this doesn’t keep occurring in the future. And we apologize for failing to meet our users’ expectations around this feedback. We will do better and changes are already happening.
Our product team is investigating how to implement a workable solution for this that will not impact other existing functionality and properly uses the notification service that’s embedded in ShipStation. There are really two issues here that need to be addressed and they don’t affect all users equally:
Spam – ensuring the notification makes it to your user without getting filtered to their spam folder or blocked entirely.
Domain validation – which validates that you own and control the domain your email is coming from (there are some additional considerations here about what level of control should be implemented within ShipStation around these email settings – this is where the SPF/DKIM/DMARC/etc details come in).
Because of ShipStation’s level of configurability, we also have to consider the impact any change will cause to the experience of many different types of users. If a change is made available universally, and there are additional settings or configuration options that must be included to accommodate the change, how will this affect the experience of users at different levels? Could it potentially cause a mis-configuration to break notifications entirely? If we don’t implement the change universally, what’s the criteria used to determine this?
As of now, these are a few of the questions our product team is looking at (though there are many more). This change is still in the discovery phase and is not part of the upcoming sprint cycle of development work happening in April. We hope to have some decisions made around this by the end of the month and we’ll update this thread at that time.
In the meantime, we recommend what was suggested early on this thread – remove your email address from your stores’ Branding tab and allow ShipStation to send notification emails from tracking at shipstation dot com. If you have something in the Branding tab’s Company field, that will be used as the display value for the FROM field in your customers’ inboxes.
Thank you again for your input and patience.
I just signed up for shipstation (still in trial) and my heart sank when I found out I can't validate the emails via DKIM and SPF. What's going on, why isn't this an option? This is an essential item.
Matthew Nocifora Bright Brain commented
Sendgrid can do this for you as they do it for other businesses such as ours. Upvote +1
Hi, this is still an important need! Please address.
Jason Cox Lazarus Naturals commented
Has this ever been addressed? It's not best practice to be forced to configure the DMARC record with p=none so customers are able to receive notifications.
Jason Lathrop Tektonic Candles commented
Need I echo the other 31 comments? How is this still an issue years later?
How is this still "under review"? This is a common setting on any application sending email on your behalf. ActiveCampaign, MailChimp they all have the option to generate SPF and DMARC records.
emails from Shipstations are failing DMARC , please provide SPF record and allow customer to update DKIM settings. Its been 3 year and there is no update.
So, this is still not working? I’m guessing I’ll have to start getting tracking back to our store and handle shipment emails there so we can make sure they’re going out correctly and as deliverable as possible.
No updates from Shipstation since 2017 on this issue. Its now 2020.
I've given up on this and stopped allowing shipstation to "Send as" from my company in order to:
A) Actually have mail arrive and not get tagged as spam
B) Have my DMARK/DKIM monitoring tools not go nuts about someone else sending under my company's email without authorization.
All Yahoo based email domains are giving us problems because of the lack of DKIM from outgoing mail from shipstation.. C'mon shipstation this issue was brought up 4 years ago and is getting worse every year!
Kevin Schmitt GearUP Sports commented
Stunning that this hasn't been implemented yet.
PopShadow Decals PopShadowDecals commented
All our emails are landing in customer's spam, due to higher restrictions and spam prevention.
Please consider this.
Sholom Chazanow LIV- Swiss Watches commented
This really needs to be done, I can not believe we are still asking for this in 2020
Casey Liu Eduporium commented
Is there any update about this or any workaround? Email is a huge part of the customer experience and currently with Shipstation shipment notifications are falling short.
Anyone switch over to another Shipping Software? We love Shipstation but emails send via Shipstation are being marked as spam by Google. Customers are frustrated when they don't know when their orders have shipped because they didn't receive an email. We can't keep working like this.
David Knappert commented
update? Having trouble with DMARC and shipstation....
Hi there. I saw this thread a while back and implemented a solution. We noticed the emails for years were coming through o1.email.shipstation.com (for many years), and so we added an entry in spf record: a:o1.email.shipstation.com
This entry immediately improved the deliverability of our email. After using it for a while now with less complaints and calls for tracking information etc, we figured we'd share with you.
Avi Webberman Dropps commented
We would also very much appreciate having SPF/DKIM support. The lack of reliable email deliverability is a significant concern for us.
David Dellanave Dellanave Imports commented
It's really good that you allow us to send notification emails from our email domain, but at this point in time it's almost useless without proper SPF and DMARC records. GMail places a giant yellow warning box above the email saying it might be fake. Most people will delete it and maybe even mark it as spam. This will algorithmically harm ALL email from the same domain, so you're possibly crippling someone's business because this simple feature isn't implemented. As an example, please see ConvertKit's verified domain implementation.
This feature request is 3 years old and probably 5 years overdue.
When can we expect this critical feature to be implemented?
Gene Kagan Lola & Sophie commented
@admin come on guys... We love ShipStation overall but your canibalizing your customers' email deliverability with this basic, basic requirement missing from your platform. Can you at least chime in and provide us with some sort of update to if we should continue to wait this out? Thank you.