Email Authentication based on Client Domain

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.

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.

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.

Need I echo the other 31 comments? How is this still an issue years later?

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.

Hi, this is still an important need! Please address.

Sendgrid can do this for you as they do it for other businesses such as ours. Upvote +1

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.

All our emails from Shipstation are quarantined because we moved to DMARC p=quarantine a while ago. The lack of support for SPF and DKIM records at Shipstation is a HUGE problem and affects every one of our clients. We loose trust with our clients, and we spend extra money on customer support. Both are not acceptable.

When DMARC is enabled on our domain, Shipstation notification emails are effectively turned into SPAM 100% of the time in whatever inbox they land. This being a 3 year old issue makes it look like Shipstation 1) does not care 2) has no expertise in solving a simple issue with massive impact to their entire user base. As of 2020 there is no phone support (really!) and email support is pretty useless.

Our delivery emails are going to SPAM because of SPF and DKIM failured of you sending on our behalf.

Wow, this thread has been going on since 2016, and in 4 years, Ship Station hasn't implemented basic healthy email sending infrastructure practices?

BUMP. please!

Looks like you are getting about 2 comments of users who want this feature every month (and that's just the users that are going out of their way to comment and post, many more would like to see this feature, pretty pretty please!).

'+1 - three years later this is still missing. I’d understand for a free service but SS is paid platform, can we please push this along?

For what it’s worth I ended up building my own email notifications because the deliverability on these was so unacceptable.

Yes. Please. Deliverability. Email deliverability and verification has moved forward since Shipstation started, time for an upgrade to get with the times. Bump, bump, bump.

Yep, I have to reply to my customers daily, "please check your spam for tracking." I shouldn't have to do that. I get tracking emails from other retailers when I order online. It's sad to be ignored like this.

It's basically to the point where your product doesn't offer email notifications for shipments. I mean if they aren't being delivered, then you don't offer this feature. So perhaps in the product feature matrix where it says "Automatic shipping confirmation e-mail to customers" just change the check mark to a question mark. Perhaps EVERYONE HERE should fill out a support ticket and link to this post.

I don't know WHY this still isn't a feature. Due to the lack of this simple feature, we are soon going to be having a Shiopify App send out tracking instead of ShipStation. We need to ensure that our emails get delivered and ShipStation is actively hindering this. Because of ShipStation, and ONLY ShipStation, I am forced to set our DMARC policy to none. I would far prefer it be set to Quarantine, but I don't have a choice in the matter. Even the Shopify apps that send emails on our behalf provide us with the necessary records to fully authenticate the emails they send for us. This is the least you could do to improve email delivery. If you really want to take it a step further, you would give us the ability to configure ShipStation to send emails directly from our own mail servers.

That is the crux: "Because of ShipStation, and ONLY ShipStation, I am forced to set our DMARC policy to none. I would far prefer it be set to Quarantine, but I don't have a choice in the matter." Virtually every other service that is sending email on our behalf has SPF or DKIM record settings available.

This bug report (yes, it’s a bug report) honestly makes me wonder if ShipStation is a zombie company. If they aren’t working on this big of an issue, what are they actually doing?

'@David Lots of these tickets make me think this. We are actively exploring other shipping options, you can't be a software company and be this utterly unresponsive for years to basic things and expect to grow forever.

Wow! Look at how many people are following this thread to respond quickly at the small activity I started. I think I might post a screenshot of this thread to their social media and tag the, perhaps that will get their attention! I also ended up using Zapier to make custom email notifications connecting through API. You would think they could have at least done that and made it a plug and play zapier integration. Let's see if they respond when this gets more attention. If you're following, throw another comment on here, Let's keep bumping this.

I just tweeted at them (and Shippo, Ordero, ShippingEasy, etc.) and asked if any of those companies are able to develop this feature and take care of their customers. Let's see if we get any traction with that. I encourage you all to send a tweet to them. You can re-use this one: @ShipStation @shipstationhelp has a non-existent support for their customer requests. What other companies are out there that respond to their customers' needs and wants? @goshippo @ShippingEasy @ordoro ? Can any of you develop this feature? (http://feedback.shipstation.com/forums/330429-product-feedback-fresh-ideas/suggestions/11618976-email-authentication-based-on-client-domain?tracking_code=3a781beaefe1df51d941256a048ff655)