Email Authentication based on Client Domain

It would be great if ShipStation could send emails from our web server. Right now, emails appear as "from" us, but then in clients like Gmail, it says "via shipstation.com." It just seems a lot less professional.... Also it seems that a lot of these emails get caught up in spam boxes, so sending the email straight from our servers might help considerably on that front as well.

I agree with James. While I don't mind the "via Shipstation.com" additon on our company emails, when we do 3rd party fulfillment, we like the branding to match the seller. Most of our brands are okay with the addition of our company URL as the sending domain, so I think this would be a great solution for everyone.

More info from Mandrill: https://mandrill.zendesk.com/hc/en-us/articles/205582727-Can-I-customize-the-Return-Path-bounce-address-used-for-my-emails-

I would really like to see this feature enabled as well.

This would be great to help with inboxing of communication from us to clients

100% agree this is a necessary feature. More Info from Mailchimp: http://kb.mailchimp.com/accounts/email-authentication/about-email-authentication

SPF and DKIM signatures are needed. It's expected and ensures deliverability and consistency of branding across our communications with clients.

We view this as extremely important and want it ASAP too. Not offering this is not keeping up with the times. We have SPA set to strict and use a DKIM record as there's too many spammers/scammers out there spoofing legit emails (we found a spammer spoofing our email address long ago, which led to us to start using strict SPA + DKIM as we certainly don't want to wrongly be accused of spamming, end up on blacklists, etc). Obviously we also want the professional appearance of emails actually coming from our domain and not displayed as "via shipstation".

This is an industry standard feature offered by almost all of our services that send emails on our behalf. Why is ShipStation so far behind the curve on this one?

This is important to us as well. Are SPF and DKIM signatures on the roadmap? Deliverability is impacted by not having this option.

A flaw with everything coming from ShipStation is that we are all on the hook if an email provider decides some emails are spam. The entire domain being blacklisted means none of us can get emails into the inbox of our customers. It could happen. Occurs with enough other services we used where someone before us got the domain blacklisted.

I tested ShipStations email deliverability using www.mail-tester.com and our emails are coming in at a 4.4/10 score. Our email deliverability is severely impacted by this poor rating and, as other commenters in this thread have pointed out, other web applications offer SPF configuration. Hopefully SS will add this feature soon.

This continues to impact deliverability. AOL and other servers have begun throttling ShipStation IPs, resulting in undelivered emails. "Destination deferred - Email was deferred due to the following reason(s): [IPs were throttled by recipient server] (attempt #12)"

many emails ending up in spam, pls add SPF/DKIM support, the basics, common!

This has been a long standing issue and I don't understand why. It's fairly easy to set up and have all clients post a DMARC record saying that ShipStation is legitimate. It worries me that after 2 years you have not been able to find resources to work on this project...

We are getting more and more complaints from AOL and Yahoo customers that they don't receive the tracking emails. We really need a solution for better authenticated emails then just adding an SPF record. (SPF we use is include:email.shipstation.com)

This is an industry standard feature! Email deliverability is severely impacted without this. Please get this added asap.

1 year goes by, anniversary today guys ... update? this is 101 type stuff for SaaS!

June 26, 2018 Today I rise to join the chorus of voices requesting either a)SPF/DKIM records or b) the ability to send outgoing email from our own email accounts. This weekend we had multiple emails from two different countries use our domain. With threats like that I can't wait for ShipStation. We are rejecting mail that fails our DMARC tests which includes email that is sent by mx.tds.net. For the moment, I'm figuring out a work-around so that our customers aren't left in the dark. How does this "impact my workflow"? It impacts our end-customers and our production team as they will no longer receive any notifications from ShipStation.

Our company, like so many below, requires this feature to prevent confusion by our customers and reduce spam flagging for our domain. WHEN will DKIM and DMARC capabilities be rolled into Shipstation email servers?

You guys HAVE to fix this. We're not far now from a world where incorrectly configured email deliverability is equal to zero email sending capability. Imagine offering shipstation with no ability to send out shipment status and tracking emails to your customer's customers. That's very close to what you have now without the ability to include your mail servers in our SPF records. Very, very low hanging fruit to fix this with a huge win. Put one devops person on this for one weekend and it's all good. Please get this done.

This is still an issue in December of 2018. After reviewing the DMARC failure reports, it appears that ShipStation is using the SendGrid system, so I've implemented their SPF & DKIM steps: https://sendgrid.com/docs/glossary/dkim/ https://sendgrid.com/docs/glossary/spf/ Will see if this improves our deliverability issues with ShipStation emails without leaving our domain wide-open.

2019 checking in... and these now-standard email security practices are sorely needed in ShipStation and are overdue. We are relatively new customers to ShipStation and are otherwise satisfied, but I can only ignore the ShipStation failures in my DMARC reports for so long.

We also can't implement DMARC rejection due to shipstation emails not supporting SPF/DKIM. We've had customers complain these emails aren't delivered or go to spam. We're looking into alternatives for shipstation due to this issue--if a portion of our customers aren't notified of their shipments, that's pretty unacceptable to us. Honestly, the fact that this ticket has been open without any serious comment when this could be set up in an afternoon is pretty maddening. As someone said, this is SaaS 101, a basic thing that's expected, and its integration into sendgrid is widely documented, several people have shared the links for you!

Any updates on this? It's been 3 years and it's honestly ridiculous that this is not supported yet. It is really important to improve deliverability of our emails from ShipStation and maintain our professional appearance. Get this verification feature added ASAP, please!