General Feedback

← Tell Us What You Think

What do you think of our email service? This is the spot for good, bad, or neutral feedback about our main product.
You can also leave feedback on specific features like Inbound Routing, Message Event Logs, or Email Analytics.
If you have feedback that you believe requires an immediate response, don’t post here. Submit a support ticket or email help@mailgun.com. Feel free to interact with other users if you agree, disagree, or found a solution to their feedback.

Please be courteous of others and upvote if you believe strongly enough in an idea!

What feedback do you have for our email service?

My feedback about Mailgun's email service is...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

Fix email tracking with SSL websites

Using email tracking with SSL website prevents user to perform the action with Google Chrome.
If you use SSL with HSTS, it triggers big warning in Chrome when the user click on the link http://cl.ly/image/0A373O2r3539

Email tracking in mailgun is performed by replacing links in email by a custom subdomain setup in the admin panel, ie email.domain.com which as to be configured as a CNAME for mailgun.org.

Chrome will try to access httpS://email.domain.com which will fail because the underlying server is mailgun.org and not domain.com's server.

Proposed Solution:
Instead of pointing email.domain.com => mailgun.org, configure your server for https://email.domain.com and redirect every request (with parameters) to https://mailgun.org/$requestedURI.
Then the usual mailgun tracking system can track click and redirect to the right domain.com url.

This could be easily done if there was a way to override the mailgun admin panel check for the CNAME record, ie a checkbox "I've setup a forwarding subdomain to mailgun.org"

A degrated version would be to have links replaced by https://mailgun.org/click?ID but this would probably harm deliverability for mail coming from domain.com (and not mailgun.org)

More info on SSL HSTS: http://en.wikipedia.org/wiki/HTTPStrictTransport_Security

Using email tracking with SSL website prevents user to perform the action with Google Chrome.
If you use SSL with HSTS, it triggers big warning in Chrome when the user click on the link http://cl.ly/image/0A373O2r3539

Email tracking in mailgun is performed by replacing links in email by a custom subdomain setup in the admin panel, ie email.domain.com which as to be configured as a CNAME for mailgun.org.

Chrome will try to access httpS://email.domain.com which will fail because the underlying server is mailgun.org and not domain.com's server.

Proposed Solution:
Instead of pointing email.domain.com => mailgun.org, configure your server for https://email.domain.com and…

149 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

25 comments · Analytics · Flag idea as inappropriate… · Delete… · Admin →

planned · AdminChris Farmer (Product Manager, Mailgun) responded

Hi all,

This has been added to our 2021 roadmap, with an initial expected delivery of H1.

Don't see your idea?

General Feedback

What feedback do you have for our email service?

Fix email tracking with SSL websites

Feedback