Email Authentication based on Client Domain

Email deliverability is a huge issue. It's a headache and unprofessional having to tell people, "Hey check your spam, our shipping partner won't update their email sending capabilities so all of the emails we send you look like spam." What other shipping platforms support this functionality?

We've added the IP address range that's sending the emails and hope that our delivery will improve... We shall see.

'@GPZ: Care to share the IP range? Thanks.

It doesn't really look like anyone is paying attention to this thread. It's actually so easy to fix, i can't believe we're being ignored.

'@Alan Attridge Myshroom Deedum LLC we're watching our DMARC reports and basing the SPF IP entries off of what we see. We've just recently started this, so a bit of time will tell if it works or not. Seeing as SS uses sendgrid for the tracking notification emails, it's that range that's needed. I personally don't like to many IP address entries in SPF, but it's a necessary "evil" at this time due to the way SS does this. I'll report back on my findings.

Just ended up here trying to fix a problem that was my fault. Surprised to see its something that Shipstation could be actively improving on.

We left ShipStation over this issue, this week. Best of luck to those sticking around for this.

What are you using now @Jason?

Is there any solution on this issue?

We have implemented DMARC as part of an initiative to secure our brands and domains. Unfortunately, email delivery to our customers may be impacted if domain authentication is not available. We have worked with our other vendors to generate DKIM keys to prevent spoofing of our domains. This would be a great feature for you to provide us with.

I've just started evaluating Shipstation. Lol. Basic fail. I have a perfectly good AWS SES dispatch confirmation with tracking code from a Woocommerce plugin. Every single evaluation point so far is worse than what I have now.

'@Christo what do you use now? I'm open to switching platforms since nothing is keeping me here.

Seriously? 4 years between replies from SS? Gmail rejects all emails from ShipStation now. Not in spam folder, just blocked.

Yesterday it got worse; or better depending on your perspective? Status: 4.4.7 notices piling up in our customer support system. 100's of email delay notices streaming through since yesterday. At least we can confirm all the customers that have been complaining of no ship notice are justified. Does anyone have recommendations for a replacement that is not a zombie app? Endicia was our backup but now they're just more of the same. We can't wait another 4 years for basic maintenance let alone innovation. ShipStation used to make us happy (using 5+ years). That has not happened for quite some time.

Kudos to @lunacoffee for bringing up this very important issue recently in the Community Forums. And also kudos to @nick for providing a very useful, though not ideal and hopefully temporary, workaround: "remove your email address from your store setup page" and the "customer will get the email." https://community.shipstation.com/t5/ShipStation-Features/Why-sending-email-without-a-verified-sender-domain-is-dangerous/m-p/569/highlight/true#M154

What is ShipStation's Sendgrid SPF Record? Per Sendgrid: https://sendgrid.com/docs/ui/account-and-settings/spf-records/ --- Each SendGrid account gets a unique SPF TXT record to authenticate their outbound mailings. An example of such a record is: v=spf1 include:u123456.wl.sendgrid.net -all --- If you can tell us what to use in place of "u123456.wl" that will help. Doing a TXT record lookup on shipstation.com it looks like it should be: "u877888.wl139.sendgrid.net" We have that in place, but many gmail and yahoo users do not get their tracking emails. If you can provide a setting to send the emails as "tracking@shipstation.com" but set a Reply-To field on those emails to our store emails that would allow the emails to be sent from a valid server and customer could still reply to us with question. Thank You, Rich

I was reminded to come back to this thread after getting an email from ShipStation bragging about SMS support: "You asked, we listened" Turns out SMS notifications have 152 votes and we're sitting here with 283 votes and 92 comments on a mission critical feature and you're still twiddling your thumbs. ShipStation is a zombie company.

Hello! We are actively working with our email notification partner to update the email notification process in ShipStation. We’ve taken your comments into consideration to help plan for how any new processes will be implemented. When we've solidified a plan, we'll update the status of this idea to Planned.

6 years this has been waiting...

You guys are using SendGrid, right? Domain authentication of a platform's clients is a totally routine thing for them. I'm struggling to understand how this is taking so long unless ShipStation simply doesn't care. Do we really have to explain the critical importance of email deliverability and advocate for it for years? Let's address the fundamentals before we devote resources to superfluous features.

Prospective client - can't believe this isn't available, I've been having to test out of my junk folder which is just ridiculous. All our other vendors are provide spf info so that this is a non-issue...

'@Shipstation - You have a feature request from six years ago which you put into the "consideration queue" long after it became critically important. While you consider that, a LOT of us are going to consider the results of a google search for "shipstation alternatives". Branding is important. Email authentication is important. Having emails coming from @Shipstation.com shatters the illusion for clients. Develop this. Enough is enough.

No text available