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
Thanks for your continued support on this idea, we don’t have any updates to report on the status of how we authenticate email addresses based on client domains, but any updates will be posted through this thread.
But, please continue providing your experiences with how the lack of this feature impacts your workflow.
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.
David Knappert commented
update? Having trouble with DMARC and shipstation....
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.
This is still a critical issue. I don't know how the priorities are managed at ShipStation but I would imagine that losing business for your customers would rank higher before you lose more customers. We know you use SendGrid for your emails. Just stop ignoring this issue and post an article to resolve this.
This is becoming more important to at least allow customers to add proper DKIM and SPF records for your sending servers. using DMARC tools messages from shipstation always fail SPF/DKIM checks
Adam Bierschenk Universal Athletic commented
I'm not sure if everyone who has posted will see this, but if so, has anyone found any work-arounds for this and still be able to implement DMARC w/reject policy?
Maxence Gélinas-Guy Dyze Design commented
Any update on this? This is definitely a must-have...