Share your challenges, collaborate with others, and let us hear you!

← Product Feedback & Fresh Ideas

Email Authentication based on Client Domain

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

166 votes
Vote
Sign in Sign in with ShipStation
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
jfredley shared this idea  ·   ·  Admin →
under review  ·  AdminShipStation (Product Owner, ShipStation) responded  · 

Hey, @all

Thanks for your continued support on this idea, we don’t have any updates to report on the status of how we authenticate email addresses based on client domains, but any updates will be posted through this thread.

But, please continue providing your experiences with how the lack of this feature impacts your workflow.

Show previous admin responses (1)

31 comments

Sign in Sign in with ShipStation
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Chris and Julie Colotti StitchTek Services, LLC commented  · 

    This is becoming more important to at least allow customers to add proper DKIM and SPF records for your sending servers. using DMARC tools messages from shipstation always fail SPF/DKIM checks

  • Adam Bierschenk Universal Athletic commented  · 

    I'm not sure if everyone who has posted will see this, but if so, has anyone found any work-arounds for this and still be able to implement DMARC w/reject policy?

  • Eric Bender The Tooth Bank commented  · 

    An updates on this @admin? It's been quite some time - would like to have consistent branding and more importantly email deliverability. Emails send via shipstation are being marked as spam by Google. "Be careful with this message, Could not verify that it actually came from domain.com. Avoid clicking links, downloading attachments, or replying with personal information. +report spam or "looks safe"" <-- This is impacting our workflow - our customers don't trust our emails.

  • Joey Halderman Theory Printing & Graphics commented  · 

    I am also needing SPF support. I am definitely looking into other services for shipping at this point. The only option I have found for emails not to be marked as spoofed is to remove my email from the BCC / Delivery email box and that isn't a good solution. I would like these emails to come from my domain and also It helped to be BCC'd on these. This is pretty frustrating. C'mon Shipstation!

  • Steven Hull CMS, Inc. commented  · 

    You are sending thousands of emails an hour for all us merchants. These DMARC SPF rejected email do not bounce back to your server. So this is adding hundreds of extra phone calls and email from customers to merchants asking for tracking and delivery notices.

    We have not been interested in your competitors because Shipstation is so good, but this problem may make us rethink rejecting them flat out. This will be my first question to them.

    SO PLEASE FIX

  • Sunho Choi Simple Shapes commented  · 

    My email was recently flagged as spam by google because of shipstation emails. This should be an absolute priority as I am thinking of moving to another platform that will support proper SPF/DKIM records.

  • calebcbe commented  · 

    We really need this feature. Do we have any type of status update? This was posted sooo long ago.

  • David Benedetti Cathouse LLC commented  · 

    +1 for SPF/DKIM support... Email deliverability from shipstation is really rough at the moment...

  • Koos Vis @ Diamond Hoof Care Ltd. commented  · 

    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!

  • bt-admin commented  · 

    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.

  • benji-calpetrx commented  · 

    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?

  • Kevin Schmitt GearUP Sports commented  · 

    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.

  • Drew commented  · 

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

  • Jake Willard StoreYourBoard commented  · 

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

  • tmadmin commented  · 

    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)

  • mhalpin commented  · 

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

  • Mark SMP Logistics commented  · 

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

  • Sebastian Wolff Materia Collective LLC commented  · 

    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)"

  • cablesandsensors commented  · 

    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.

← Previous 1

Product Feedback & Fresh Ideas: Customers & Email Communication

Categories

Feedback and Knowledge Base

(thinking…)