• Resolved deeveedee

    (@deeveedee)


    After upgrading from WooCommerce 2.6.14 to WooCommerce 3.0.5, new order notifications are not being sent. I use the Postman SMTP plugin version 1.7.2. Postman SMTP logs show that the difference between e-mails sent by WC 2.6.14 and WC 3.0.5 is that WC 3.0.5 is adding a ‘Reply-To’ e-mail address field that was not added by WC 2.6.14. This ‘Reply-To’ field is blank when orders are paid by PayPal (even though the PayPal Gateway ‘From’ address is configured) and Postman SMTP flags the blank ‘Reply-To’ address as an e-mail validation error.

    The work-around is to check the “Disable e-mail validation” checkbox in Postman SMTP (Postman SMTP Settings -> All Settings -> Message Tab) so that Postman SMTP ignores the blank ‘Reply-To’ email address.

    Since it appears that the ‘Reply-To’ address is not the same as the ‘From’ address, where should the ‘Reply-To’ Address be configured in WooCommerce 3.0.5 and should the ‘Reply-To’ address be separately configured for each payment gateway?

    Thank you for a great plugin and for your great support.

    • This topic was modified 6 years, 11 months ago by deeveedee.
    • This topic was modified 6 years, 11 months ago by deeveedee.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Mike Jolley (a11n)

    (@mikejolley)

    Checked on github – reply-to is set correctly our side. Added a check to ensure the data is there, but if that PR does not work for you you’ll need to see what is setting it outside of WooCommerce.

    Thread Starter deeveedee

    (@deeveedee)

    @mikejolley – thank you very much. I will retest with the next version of WooCommerce. I don’t require the customer’s name/e-mail for PayPal orders but do require the customer’s name/e-mail when paid by check. I unset the name and e-mail order fields for PayPal orders and leave them set for orders paid by check. Since you’re generating the Reply-To from the order fields, I understand why the behavior I’m seeing is different for the PayPal and Check payment gateways.

    What I still don’t understand is why this wasn’t a problem with WC 2.6.14 and is now a problem with WC 3.0.5.

    Thanks again for your help and great support.

    Thread Starter deeveedee

    (@deeveedee)

    @mikejolley – I looked throught the WooCommerce changelog and see that “Reply-to” was added to admin e-mails in WC 3.0.0, so this explains why everything worked for me in 2.6.14 when the customer’s name and e-mail were not present in my WooCommerce billing fields.

    If I understand the change that you added after 3.0.5 (to ensure that “the data is there”), I believe that should fix the problem I’m observing. WooCommerce should only add Reply-to to the admin e-mail header if the billing name and billing e-mail address are populated (leaving Reply-to completely out of the e-mail header if the billing fields are not set).

    Thank you.

    Thread Starter deeveedee

    (@deeveedee)

    This issue (described in detail below) is now fixed by WooCommerce 3.0.6. Thank you @mikejolley!

    Details about this error and the fix:
    When using Postman SMTP (PS) plugin version 1.7.2 with e-mail validation enabled, WooCommerce (WC) 3.0.0-3.0.5 would not send new order notifications if the customer name and e-mail billing fields were empty (which would happen if the name and billing fields are “unset” via the woocommerce_checkout_fields filter). PS would throw an ‘invalid Reply-to’ error. This happened, because WC would insert the text ‘Reply-to’ in the e-mail header without a Reply-to address. The work-around when using PS and WC was to disable PS e-mail validation.

    WooCommerce 3.0.6 added a check, so that the Reply-to field is only added to the e-mail header if the customer name and e-mail billing fields are populated. As a result of this WC 3.0.6 fix, Postman SMTP 1.7.2 will nolonger throw an ‘invalid Reply-to’ error if the customer billing fields are not populated.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘New order notification e-mails not sent after upgrade from 2.6.14 to 3.0.5’ is closed to new replies.