Email Authentication based on Client Domain

[james35]

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: http://login.mg2mail.com/help/Content/Listrak_Manual/Branding%20Settings.htm https://mandrill.zendesk.com/hc/en-us/articles/205582387-How-to-Set-up-Sending-Domains https://sendgrid.com/docs/Glossary/email_authentication.html This will significantly improve deliverability and professional appearance. Best Regards, James Fredley VP of Marketing Technology FilterEasy

[GoFishMedia]

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-sende...

[sales3]

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

[david8]

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.

[feedback]

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.

[david8]

6 years this has been waiting...

[dakota]

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.

[allen]

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

[allen1]

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

[northwell]

This is a minimum standard. It's been 6 years with no deployment. Incredibly disappointed.