Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 4 of 4

Thread: Store email not working correctly

  1. #1
    neverenoughauto is offline Junior Member
    Join Date
    Aug 2010
    Posts
    3

    Default Store email not working correctly

    EMail Test and Configuration

    Receipt Email Failed:
    ·Mail Error occurred - Exception=Mailbox unavailable. The server response was: #5.1.0 Address rejected (removed)


    New Order Notification Email Successful



    it will send emails to our domain (Example: sales@mystorefront.com) hence the "New Order Notification Email Successful" but it will not email anything else @gmail.com, @yahoo.com etc

    I have exhausted Google searches, forum searches and have not figured this out

    Our email is hosted through GoDaddy but our domain is hosted through ASP.NET/Vortx

    I am using smtp.secureserver.net as the Mail Server DNS (which I was told was correct before) no SSL or username/password, advanced settings are all the same

    I am not a developer of any sort so my knowledge is limited on all this any help is grateful

    thanks

  2. #2
    medsupply is offline Senior Member
    Join Date
    Jul 2011
    Posts
    99

    Default

    I am having exactly the same issue. Does anybody know the answer to this?

    Thx!

  3. #3
    Skriver is offline Senior Member
    Join Date
    Apr 2012
    Posts
    188

    Default

    It is probably sending the email from an alias on the server. Check your DNS and create a mail.domain.com and point your MX record to that address. It may fix the issue.

  4. #4
    ghinfl is offline Junior Member
    Join Date
    Apr 2013
    Posts
    1

    Default same issue

    I am also having the same problem with same server and this worked in previous version of aspdotnetstorefront not hosted by aspdotnetstorefront. Did the last solution work for anyone?