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.
1 year goes by, anniversary today guys ... update? this is 101 type stuff for SaaS!
Jake Willard StoreYourBoard commented
This is an industry standard feature! Email deliverability is severely impacted without this. Please get this added asap.
We are getting more and more complaints from AOL and Yahoo customers that they don't receive the tracking emails. We really need a solution for better authenticated emails then just adding an SPF record. (SPF we use is include:email.shipstation.com)
This has been a long standing issue and I don't understand why. It's fairly easy to set up and have all clients post a DMARC record saying that ShipStation is legitimate. It worries me that after 2 years you have not been able to find resources to work on this project...
Mark SMP Logistics commented
many emails ending up in spam, pls add SPF/DKIM support, the basics, common!
Sebastian Wolff Materia Collective LLC commented
This continues to impact deliverability. AOL and other servers have begun throttling ShipStation IPs, resulting in undelivered emails. "Destination deferred - Email was deferred due to the following reason(s): [IPs were throttled by recipient server] (attempt #12)"
I tested ShipStations email deliverability using www.mail-tester.com and our emails are coming in at a 4.4/10 score. Our email deliverability is severely impacted by this poor rating and, as other commenters in this thread have pointed out, other web applications offer SPF configuration. Hopefully SS will add this feature soon.
A flaw with everything coming from ShipStation is that we are all on the hook if an email provider decides some emails are spam. The entire domain being blacklisted means none of us can get emails into the inbox of our customers.
It could happen. Occurs with enough other services we used where someone before us got the domain blacklisted.
Sebastian Wolff Materia Collective LLC commented
This is important to us as well. Are SPF and DKIM signatures on the roadmap? Deliverability is impacted by not having this option.
This is an industry standard feature offered by almost all of our services that send emails on our behalf. Why is ShipStation so far behind the curve on this one?
Wade Cool Pet Stuff LLC commented
We view this as extremely important and want it ASAP too. Not offering this is not keeping up with the times. We have SPA set to strict and use a DKIM record as there's too many spammers/scammers out there spoofing legit emails (we found a spammer spoofing our email address long ago, which led to us to start using strict SPA + DKIM as we certainly don't want to wrongly be accused of spamming, end up on blacklists, etc).
Obviously we also want the professional appearance of emails actually coming from our domain and not displayed as "via shipstation".
Brian King Superlative Events commented
SPF and DKIM signatures are needed. It's expected and ensures deliverability and consistency of branding across our communications with clients.
Cloud Alchemist commented
100% agree this is a necessary feature. More Info from Mailchimp: http://kb.mailchimp.com/accounts/email-authentication/about-email-authentication
Jean-Francois Hardy Backcountry Chai commented
This would be great to help with inboxing of communication from us to clients
Erin Willis Fluence Bioengineering commented
I would really like to see this feature enabled as well.
I agree with James. While I don't mind the "via Shipstation.com" additon on our company emails, when we do 3rd party fulfillment, we like the branding to match the seller. Most of our brands are okay with the addition of our company URL as the sending domain, so I think this would be a great solution for everyone.
Jeff Ruhle Moonshine Distiller commented
It would be great if ShipStation could send emails from our web server. Right now, emails appear as "from" us, but then in clients like Gmail, it says "via shipstation.com." It just seems a lot less professional.... Also it seems that a lot of these emails get caught up in spam boxes, so sending the email straight from our servers might help considerably on that front as well.