Remove (or merge) Elastic email Unsubscribe

I’m not sure personally, you’d need another engineer to confirm. Perhaps @zogstrip knows.

The only unsubscribe route we have takes an “unsubscribe key” as parameter.

But we do support webhooks for our other recommended email services. I’m open to a PR adding support for Elastic Email :wink:

3 Likes

As far as I understand, that would only partially solve the problem because if users re-subscribed to mails from their Discourse profile, this would fail (they’d need to resubscribe with ElasticMail). I’m not sure there is a good solution to this :frowning:

4 Likes

@allu Is it possible to hide the address though? I don’t mind having the unsubscribe button but the address of my elasticmail account shows everytime an email is sent.

1 Like

+1 for removing address from footer. Is there any way to do it at least?
@Majedsam did you manage to remove it?

What a bummer. It really looks like you can’t send a single email through elastic email without an unsubscribe link at the bottom. (In my case, they’re also adding my address. But I haven’t investigated whether the address can be removed).

In any case, I think this should disqualify elastic email as an officially recommended email provider for discourse. It’s unusable like that. And 30 minute install wont work if you have to go back and reconfigure your email…

4 Likes

What’s that? You should be able to run ./discourse-setup again and just enter new mail settings.

1 Like

Well, yes. Or just edit the app.yml and rebuild (which takes time). And what takes even more time is setting up a mailgun account and setup the DNS records accordingly.

3 Likes

I see. My setup script configures mallgun, and if you use digital ocean’s dns servers, the dns and mallgun activation.

I’m with Hetzner and Google domains…

Anyway, my point was just that I see no reason why elasticemail is on the list. It’s misleading.

Looks like mailgun is the only way to go if you want free emails for a smaller forum…

1 Like

Mallgun is what I recommend, actually, require, for my $99 desk customers.

1 Like

Can you remove it if you pay for the service, at least?

no, you can’t, is mandatory.

I asked them if I misunderstood something and here is what they answered:

All email sent through the account requires an Elastic Email {unsubscribe} merge tag. You can learn how to add this link to your emails here: https://elasticemail.com/support/user-interface/unsubscribe/#Unsubs

Additional information regarding this is located here: https://elasticemail.com/resources/templates/merge-fields/

If you do not add an {unsubscribe} tag to your emails, our system will automatically place an “UNSUBSCRIBE” link at the bottom of your email.

All email is also required to have your profile’s physical address information. Please see details here:
https://elasticemail.com/resources/account/email-compliance-merging…

If you would like to customize the placement or formatting of this information you can use the merge tag {accountaddress}.

6 Likes

Although it’s an old subject, let me let here a solution for other people searching the answer to the question. You can change the unsubscribe link adding a merge field or the link. Something like
{unsubscribe:{unsubscribe_link}} (where unsubscribe_link is the merge field) or
{unsubscribe: http://yourdomain.com/unsusbscribe_or_something_similar/ }

Source: https://elasticemail.com/resources/guides/unsubscribe/

3 Likes

Is there a general unsubscribe link which can be used with cookies then?

Why do people still keep trying to use Elasticmail? Could it be because it is still being offically recommended?

3 Likes

Personal i don’t use anymore, but yes for me that was the reason

Yes I chose it because it was recommended and it sent the most email for free out of the recommended services. After discovering there is no clear way for EE to communicate bounce info to Discourse, I plan on making the switch to Mailgun.

EE should be removed from the recommended services IMO due to it not fully integrating with Discourse like the others do. Or at the very least a disclaimer should be added next to the recommendation.

3 Likes

Ran into this same issue over last two months and now regretting using Elastic Email without knowing this limitation.

Just created a pull request for this:

4 Likes