Email Authentication based on Client Domain

'+1 for SPF/DKIM support... Email deliverability from shipstation is really rough at the moment...

We really need this feature. Do we have any type of status update? This was posted sooo long ago.

My email was recently flagged as spam by google because of shipstation emails. This should be an absolute priority as I am thinking of moving to another platform that will support proper SPF/DKIM records.

You are sending thousands of emails an hour for all us merchants. These DMARC SPF rejected email do not bounce back to your server. So this is adding hundreds of extra phone calls and email from customers to merchants asking for tracking and delivery notices. We have not been interested in your competitors because Shipstation is so good, but this problem may make us rethink rejecting them flat out. This will be my first question to them. SO PLEASE FIX

I am also needing SPF support. I am definitely looking into other services for shipping at this point. The only option I have found for emails not to be marked as spoofed is to remove my email from the BCC / Delivery email box and that isn't a good solution. I would like these emails to come from my domain and also It helped to be BCC'd on these. This is pretty frustrating. C'mon Shipstation!

An updates on this @admin? It's been quite some time - would like to have consistent branding and more importantly email deliverability. Emails send via shipstation are being marked as spam by Google. "Be careful with this message, Could not verify that it actually came from domain.com. Avoid clicking links, downloading attachments, or replying with personal information. +report spam or "looks safe"" <-- This is impacting our workflow - our customers don't trust our emails.

Any update on this? This is definitely a must-have...

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?

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

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 needs to become a feature like 2 years ago at this point. I'm blown away that there is no proper DKIM / SPF records through ShipStation. This will lead to your customers emails ending up in THEIR customer's spam folders after some time has passed. PLEASE add support for this basic necessity ShipStation

'@other users. What alternative shipping software should I consider. This lack of innovation and attention to customer requests is leading me to look toward viable alternatives that allow for proper emaol signatures, DKIM SPF, etx.

We definitely need this.

'@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.

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?

We would also very much appreciate having SPF/DKIM support. The lack of reliable email deliverability is a significant concern for us.

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.

update? Having trouble with DMARC and shipstation....

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.

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.

This really needs to be done, I can not believe we are still asking for this in 2020

All our emails are landing in customer's spam, due to higher restrictions and spam prevention. Please consider this.

Stunning that this hasn't been implemented yet.

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!

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.