Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert replyTo address to lowercase when sending e-mail via Send API v3.1 #28

Open
patryk-marcin-zielinski opened this issue Oct 3, 2019 · 3 comments

Comments

@patryk-marcin-zielinski
Copy link

We are sending e-mail through your Send API v3.1 (https://api.mailjet.com/v3.1/send) using Java Client. We have a mailbox in mailjet in which we want to receive an e-mail and we post them to our application by Parse API. When we send e-mail we set replyTo address to:
<MAILJET_EMAIL_ID>+<SOME_ID>@parse-in1.mailjet.com. What we observe that MAILJET_EMAIL_ID contains upper/lower case letters, number and special characters like -, but when the recipient receives an e-mail replyTo address is all lowercase. So when the recipient replies the mail doesn't go to our mailbox and no endpoint is fired. When I manually fix MAILJET_EMAIL_ID to properly cases and sent e-mail than I can observe that mail is in our mailjet mailbox and endpoint is fired.

@kira4ka
Copy link

kira4ka commented Oct 25, 2019

Have the same problem.

@patryk-marcin-zielinski
Copy link
Author

@kira4ka Quick partial solution to the problem is verifying your own domain(sub-domain) and provide custom mail address with lower cases: https://dev.mailjet.com/email/guides/parse-api/
It won't solve the problem if you use <SOME_ID> mix cases there but it will solve problem that your endpoint is not fired.

@kira4ka
Copy link

kira4ka commented Oct 28, 2019

@patryk-marcin-zielinski, thank you for the quick work around, but in our case the endpoint is fired. But <SOME_ID> is encrypted and then encoded with base64. To work well our endpoint needs to decode and then decrypt the string.
When this part is set to lowercase it become impossible to decode it back to then decrypt, as we are getting "Bad base 64" error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants