DMARC, SPF & DKIM settings - Email deliverability

We are experiencing the same issue.  We have contacted support and are waiting on a reply.

Welcome to the 8 year old problem.

https://community.shipstation.com/t5/Orders-Shipment-Management/Email-Authentication-based-on-Client-Domain/idi-p/7502/page/9

I'll share our fix to this dated problem.

Delete your company email from the branded tab (you can leave everything else, website, logo, phone, etc). Create a new template for both tracking confirmations and delivered confirmations (copy from default). Edit these new templates to remove the email field and enter a static value (your email @ your domain). Save.  Change the default email templates to use these newly created templates. Save. Emails are still branded, and emails are delivered.

While this solves the DEMARC deliverability issues caused by ShipStation effectively spoofing your domain, there are still problems with this.  If a customer hits "reply" to either the tracking or the delivery confirmation, it will bounce as tracking@shipstation.com is a no-reply address.  However, at least they are delivered, its a clean and branded email looking as though it is from your company, and the email contact is in the body of the email.

In my opinion that is not really a solution because you lose connection with your customers as the reply back is to Ship Station.  You are better off finding another way to send the emails. Ship Station failed to fix this in time after years of customers saying this was an issue.  They were warned of this.  It is old news when Google and Yahoo eventually said they were going to force Dmarc.

This month Gmail and Yahoo Mail have both implemented more rigorous email verification requirements... so expect even more customers not to get tracking emails.

https://blog.google/products/gmail/gmail-security-authentication-spam-protection/

It doesn't get much dumber than Shipstation not fixing this in the years and years it's been complained about.. and it's about to get critical with the changes this month.

This is a perfect example of the fact that ShipStation devs don't listen to customer input. Along with all the negative feedback about the new layout, then more recently the new order page layout, not to mention simple fixes that could be implemented into products, these order emails should be looked at by ShipStation as a CRUCIAL feature that should be addressed immediately. 

Given the lack of documentation and Shipstation not feeling this is an important issue to inform their customers about, I will be looking into other alternatives to Shi*tstation.

We are also now waiting for a fix. Due to the issues around spam, and with Google and Yahoo's dmarc requirements, I am seeing that our shipstation, via sendgrid are getting quarantined. We have an spf record with sendgrid, why can't they provide a dkim record. As far as I can see, this is the only thing needed. I hope someone from Shipstation is actually monitoring this thread.

Good luck if you think Ship Station will fix anything. 

According to them it is "fixed" for now - if you use tracking@shipstation.com as the sender, which you can't switch to without talking to support, from my experience. 

They switched me over and now the emails are getting delivered. That doesn't solve the issue of the customer trying to reply to the email, of course, but they do get delivered. They are supposedly working on this as well.

See Erin's final note on the last page of this 8 year old thread, before she "closed" the thread by disabling replies.

https://community.shipstation.com/t5/Orders-Shipment-Management/Email-Authentication-based-on-Client-Domain/idi-p/7502/page/9

This is not a fix because customers cannot respond to the email.  tracking@shipstation.com  should have always been working.  It is there own domain.  This is Ship Station pretending they fixed something when they did not.

I wrote to Shipstation support and this is the answer I got which confirms what Start_Haus and others said:
 
our engineering team is aware of these coming requirements and is working on a solution. More communications to come. Our default email address tracking@shipstation.com is DMARC-compliant, so the merchant can remove their email address from the Branding tab in their store settings to ensure immediate compliance.

I wrote back asking specifically where to change it and what happens if a person replies to this email.

This is still an issue. No updates from Shipstation devs since Jan 31 2024, and they have been locking threads on this issue in an attempt to make it look like it's not a problem.

• 8 year old thread with 160 posts started in 2016: https://community.shipstation.com/t5/Orders-Shipment-Management/Email-Authentication-based-on-Client-Domain/idi-p/7502/page/16#comments
• 3 year old thread: https://community.shipstation.com/t5/ShipStation-Features/Why-sending-email-without-a-verified-sender-domain-is-dangerous/m-p/520
• 3 month old thread: https://community.shipstation.com/t5/ShipStation-Features/New-Email-Delivery-Requirements-for-Yahoo-and-Gmail/m-p/21995
• All recently locked by Shipstation staff to prevent discussion

What is going on @Manager-Erin ? It's crazy that this simple, integral aspect of the shipping service we pay for is functionally broken and has been for years. It's far worse as of Feb 2024 now with GMAIL/Yahoo's stricter authentication policies.

At absolute minimum, in the short term, Shipstation needs to change tracking emails sent out to come from noreply@shipstation.com. As is, it is not clear to our customers that they shouldn't reply to tracking emails since they go into the void. Including an option for a banner notice at the top of the emails that that email address can't receive replies would also be good.

(Alternately, Shipstation could forward us the email if a customer replies to the tracking@shipstation.com emails.)

In addition, in Selling Channels > Store Setup > Branding > Email it should have a warning explaining that you should leave the box blank because if you enter your own domain email right now, it will likely go to spam or be rejected due to DKIM authentication issues.

To actually fix the problem, the Shipstation devs need to implement a legitimate CUSTOM MAIL FROM solution. This problem has been known, but unresolved for 8+ years, meanwhile the developers spent time redesigning the interface multiple times. It's past time to make this a priority.

It is definitely possible for a 3rd party service like Shipstation to be authorized to send mail from our custom domain, for example, here are the instructions Amazon AWS has for setting a "CUSTOM MAIL FROM" with their service: https://docs.aws.amazon.com/ses/latest/dg/mail-from.html - but Shipstation needs to set this up on their end first.

Take a look at this thread started by Manager-Erin and please reply there with your thoughts.

• ShipStation DMARC Compliance - ShipStation Community

What are people doing who operate a dropshipping business? we dropship for many customers and we have been using their personal or business emails in the branding section and in bcc for notifications. Will emails no longer be delivered for notifications now if i can verify every single email and domain? Will orders stop coming into SS so we can send out the order? if anyone has more info on what can be done please let me know. I have no idea how i would go about verifying every email and domain for customers we ship for.