Hi,

If you look at your Configure > Email > Settings page, you can check to see the mail account displayed for "Store Email". It's a little easier than querying the database :)

However, from the error message above, it looks like you might need to contact Comcast.



Please keep us updated.

Katie

Hi,

Along the same line that I discovered, is your "Store Email" the same address as your "Email Server Configuration" log-in details (SMTP Username on my configuration)?

If they are different, I had to permit my primary email address in Gmail to "Send From" a different address that we are specifying in the "Store Email" field.

-Jeff

Just following back to your note "The Contact Us Form initiates an email to send from the customer..... the form is trying to send an email from the domain the user entered in the email field in the form."

Someone please correct me otherwise, but I don't believe that's how it is working. I can initiate a message on our contact form with a bogus email address and the Contact Message email arrives in my email inbox. It looks to me like the AC store is sending the email from the "Store Email" and just showing the contents of the Contact Form. I don't know that the customer's email address is relevant at all at this stage.

-Jeff

This is working for me as well. We just upgraded to version 9.0.3.

Hi Jeff. We have removed the Contact Form at this point and redirected it to an about us page that contains an email button with a more traditional mailto: reference. That is most likely what you are seeing now. Unfortunately we cannot afford to have these emails just get lost in the void and so we're having to move back to a more dependable method, even if site visitors tend not to use it as much. I'd love to find a solution for this but all roads are leading nowhere at this point, I'm sorry to say.

This issue is caused by how Able populates the email header after the contact-us form is submitted.

When Able populates the header, they are setting the FROM address of the email to be the shopper's email address. Most likely this was done based on the presumption that the merchant could simply click reply to that contact-us email and respond directly to the shopper.



However, most major email servers/providers will not permit a FROM address on a new email that does not match the email of the account used to authenticate their email server.

For example, let's say my SMTP server settings are configured to log into my mail server using 'foo@payne.com'. Many mail providers will not allow the store to send an email with the FROM value of anything other than 'foo@payne.com'. Bigger systems such as Comcast, ZOHO and Office365 all have strict requirements such as this to reduce spam.

What Able should be doing is populating the 'ReplyToList' with the shopper email instead of the FROM address. Email clients such as Outlook will use the REPLY-TO value of the email if one was specified when the email was sent. So the end goal of making it easy for merchants to reply to contact-us forms is still achieved.

The FROM address should always be set to match the SMTP username configured in the Able store settings. This is the only way to get many of the major email servers to accept email from an external source such as an Able website. Even then, it can be a challenge. For example, there are additional challenges when trying to use an Office365 account to send emails from an Able store.

Every email provider is different. And the rules are changing. Some providers that permitted it before, no longer do. Often without any advance warning. So you can literally wake up one day to find none of your store emails will go out.

Some providers offer a workaround. Others simply don't care. Office365 is the WORST to work with, and of course is wildly popular.

Regular store transaction emails are indeed constructed differently in the code.