Wrong "Reply to" issue in version 1.3.6.0

[namph81]

I have just updated to new version 1.3.6.0. However, it has problem with “Reply to” value. I have set an email in "Reply to" when create a campaign, but it does not affect to sent emails.

Detail scenario:
---------------------------------------------------
My email service url: www.mydomain.com
Delivery server: Amazon SES SMTP with sender email is set to info@mydomain.com
When create a new campaign, I set "Reply to" to "abc@otherdomain.com".
User receive my email, then reply, it goto info@mydomain.com, not abc@otherdomain.com
---------------------------------------------------
My delivery server is SES SMTP.
And I don’t use force reply-to in the delivery server settings.

Now I had to rollback to old version temporary and it work fine.
Definitely there is problem with 1.3.6.0.

 

[frm.mwz]

I have just updated to new version 1.3.6.0. However, it has problem with “Reply to” value. I have set an email in "Reply to" when create a campaign, but it does not affect to sent emails.

Detail scenario:
---------------------------------------------------
My email service url: www.mydomain.com
Delivery server: Amazon SES SMTP with sender email is set to info@mydomain.com
When create a new campaign, I set "Reply to" to "abc@otherdomain.com".
User receive my email, then reply, it goto info@mydomain.com, not abc@otherdomain.com
---------------------------------------------------
My delivery server is SES SMTP.
And I don’t use force reply-to in the delivery server settings.

Now I had to rollback to old version temporary and it work fine.
Definitely there is problem with 1.3.6.0.

Latest version is 1.3.6.2
However, the From/Reply-To address problem is covered here
https://forum.mailwizz.com/threads/issues-on-mailer.1928
https://forum.mailwizz.com/threads/dkim-signing-is-failed.1921
and you will find in the latter also a new file for swiftmailer taking care of the From/Reply-To problem (MailerSwiftMailer.php.zip)

Not sure if there are any additional problems re From/Reply-To due to amazonSES-specifics.
Hope that works for you

 

[twisted1919]

@namph81 - i just tested this now in the dev version with a test campaign and it worked fine for me, so if indeed there was an issue with this, it has been fixed and next version will be fine.