Kevin Schmitt GearUP Sports

My feedback

  1. 185 votes
    Vote
    Sign in Sign in with ShipStation
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    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.

    Kevin Schmitt GearUP Sports supported this idea  · 
    An error occurred while saving the comment
    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.

  2. 29 votes
    Vote
    Sign in Sign in with ShipStation
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Hey @Kris, thanks for bringing this up! You’re right about logging out of your Windows user will not allow ShipStation Connect to run. This is something we’re reviewing for the future. For now, we’d like to hear from others on this before moving forward.

    An error occurred while saving the comment
    Kevin Schmitt GearUP Sports commented  · 

    I'm voting for Connect-as-a-Service. As an Enterprise subscriber we have ShipStation connected (no pun) on more than a handful of computers. As we are a Microsoft AD shop we don't have assigned users on each system. Having Connect running as a service on the machine would help us greatly as it wouldn't be user-dependent.
    I've been told that only the computer connected to the local resources has to have Connect installed. I've also been told that all computers that need to use network resources have to have it installed. Which is it? I'd prefer to only install it on the directly connected machine and use it as a server for the other workstations.
    Thank you ShipStation for listening to your users.

Feedback and Knowledge Base