[GH-ISSUE #2856] Mailgun EU API support #2050

New issue

Closed

opened 2026-02-27 03:00:33 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 03:00:33 +03:00

Owner

Originally created by @GrillGuth on GitHub (May 1, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2856

Originally assigned to: @h3o66 on GitHub.

User Story

As a EU located administrator, I want the "mailgun"-alert feature to support their EU API so that the feature is GDPR [1] compliant.

Basic info

Command: [alert]

Further Information

Due to the GDPR [1] "mailgun" is offering a separate API for EU clients utilising EU based server infrastructure [2]. Only this API is GDPR compliant. Therefore, LinuxGSM should support this API.

Ultimately, LinuxGSM should provide a config entry called "mailgunapiregion" as part of the "# Mailgun Email Alerts" section. Options for this entry should be "us" (default) for the US API-endpoint and "eu" for the EU API-endpoint. Another approach could be the entry "mailguneuapi" with the options "0" (default) and "1" to avoid confusion for users outside the US or the EU.

The EU API is available through: api.eu.mailgun.net [3].
Therefore, "https://api.eu.mailgun.net/v3/${mailgundomain}/messages" should be used instead of "https://api.mailgun.net/v3/${mailgundomain}/messages" when the EU option is selected.

Originally created by @GrillGuth on GitHub (May 1, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2856 Originally assigned to: @h3o66 on GitHub. ## User Story As a EU located administrator, I want the "mailgun"-alert feature to support their EU API so that the feature is GDPR [[1]](https://eur-lex.europa.eu/eli/reg/2016/679/oj) compliant. ## Basic info * **Command:** [alert] ## Further Information Due to the GDPR [[1]](https://eur-lex.europa.eu/eli/reg/2016/679/oj) "mailgun" is offering a separate API for EU clients utilising EU based server infrastructure [[2]](https://www.mailgun.com/blog/we-have-a-new-region-in-europe-yall/). Only this API is GDPR compliant. Therefore, LinuxGSM should support this API. Ultimately, LinuxGSM should provide a config entry called "mailgunapiregion" as part of the "# Mailgun Email Alerts" section. Options for this entry should be "us" (default) for the US API-endpoint and "eu" for the EU API-endpoint. Another approach could be the entry "mailguneuapi" with the options "0" (default) and "1" to avoid confusion for users outside the US or the EU. The EU API is available through: api.eu.mailgun.net [[3]](https://documentation.mailgun.com/en/latest/api-intro.html#mailgun-regions). Therefore, "https://api.eu.mailgun.net/v3/${mailgundomain}/messages" should be used instead of "https://api.mailgun.net/v3/${mailgundomain}/messages" when the EU option is selected. ## Further Reading [[1] https://eur-lex.europa.eu/eli/reg/2016/679/oj](https://eur-lex.europa.eu/eli/reg/2016/679/oj) [[2] https://www.mailgun.com/blog/we-have-a-new-region-in-europe-yall/](https://www.mailgun.com/blog/we-have-a-new-region-in-europe-yall/) [[3] https://documentation.mailgun.com/en/latest/api-intro.html#mailgun-regions](https://documentation.mailgun.com/en/latest/api-intro.html#mailgun-regions)

kerem

2026-02-27 03:00:33 +03:00

closed this issue
added the
type: feature

info: alerts
labels

kerem commented

2026-02-27 03:00:34 +03:00

Author

Owner

@h3o66 commented on GitHub (Sep 14, 2020):

Hi @GrillGuth
could you maybe test the connected PR for mailgun ?

To change the region to eu add mailgunapiregion="eu" to the common or server config.

@h3o66 commented on GitHub (Sep 14, 2020): Hi @GrillGuth could you maybe test the connected PR for mailgun ? To change the region to eu add `mailgunapiregion="eu"` to the common or server config.

kerem commented

2026-02-27 03:00:34 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 21, 2021):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Sep 21, 2021): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.