# Mailgun alternative

**URL:** <https://forum.ghost.org/t/mailgun-alternative/29428>\
**Category:** Ideas\
**Created:** [April 5, 2022, 5:37pm UTC](https://forum.ghost.org/t/mailgun-alternative/29428 "2022-04-05T17:37:43Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexgoldman68](https://avatars.discourse-cdn.com/v4/letter/a/439d5e/32.png) [@alexgoldman68](https://forum.ghost.org/u/alexgoldman68)\
**Post date:** [April 5, 2022, 5:37pm UTC](https://forum.ghost.org/t/mailgun-alternative/29428/1 "2022-04-05T17:37:43Z")

</div>

Is there any plan to provide alternate methods for sending emails?

Having a lot of issues with Mailgun, and additionally their high prices.

Would be nice to have more than one option.

---

<div class="post-metadata">

**Author:** ![nicgentile](https://avatars.discourse-cdn.com/v4/letter/n/71e660/32.png) [@nicgentile](https://forum.ghost.org/u/nicgentile)\
**Post date:** [September 28, 2022, 11:15am UTC](https://forum.ghost.org/t/mailgun-alternative/29428/2 "2022-09-28T11:15:14Z")

</div>

I’m still new to Ghost, and I really like it. Have gone from zero hits to paid subscribers and a following in under a month. Still surprised by all that. The only Achilles heel is Mailgun. No idea why it’s the only one when they have such terrible service and support.

There needs a different plan. Right now I am going with Mailchimp + Zapier so there are no statistics coming into Ghost and for such a well-built platform, that just feels wrong.

If the mantra of “no bullshit” stands, then Mailgun should not be the only provider, regardless of the fact that Ghost does not benefit from this. It’s just a terrible service ruining a fantastic product.

---

<div class="post-metadata">

**Author:** ![saiunes](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/saiunes/32/21538_2.png) [@saiunes](https://forum.ghost.org/u/saiunes)\
**Post date:** [January 13, 2023, 11:52pm UTC](https://forum.ghost.org/t/mailgun-alternative/29428/3 "2023-01-13T23:52:33Z")

</div>

apart from using mailgun, i believe it will be nice to add ses as a second option

---

<div class="post-metadata">

**Author:** ![DustinG](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/dusting/32/26622_2.png) [@DustinG](https://forum.ghost.org/u/DustinG)\
**Post date:** [June 16, 2023, 12:32pm UTC](https://forum.ghost.org/t/mailgun-alternative/29428/4 "2023-06-16T12:32:44Z")

</div>

Being required to use Mailgun is possibly the biggest problem with Ghost. Too many emails end up marked as spam, they no longer offer a free pricing tier, and their price plans are expensive, and their customer service is bad.

---

<div class="post-metadata">

**Author:** ![Cathy\_Sarisky](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cathy_sarisky/32/25750_2.png) [@Cathy\_Sarisky](https://forum.ghost.org/u/Cathy_Sarisky)\
**Post date:** [June 17, 2023, 12:33am UTC](https://forum.ghost.org/t/mailgun-alternative/29428/5 "2023-06-17T00:33:49Z")

</div>

Mailgun has a pay as you go plan. It isn’t advertised, but you can downgrade to it at the end of your trial, and it’s super cheap.

> **[How does PAYG billing work?](https://help.mailgun.com/hc/en-us/articles/360048661093-How-does-PAYG-billing-work-)**
>
> Mailgun offers a Pay-As-You-Go (PAYG) billing model via our Flex plan, which allows you to only pay for the messages you send in any given month with no subscription fee. Pricing is $1.00 per thous...

It’s first 1000 messages/month free, then $1/1000 messages.

Aside: Do you have stats about another bulk mail provider having better deliverability? Genuinely curious. Everything I understand about bulk email delivery is that it’s hard. When I ran my first email server, 20+ years ago, it was pretty easy to turn it on and send email from it. Now? I’m glad it’s not my job.

Ultimately, the Ghost team has decided that supporting an additional email option is not a priority. You can read more about that here: [Why do I have to set up Mailgun for newsletters?](https://ghost.org/docs/faq/mailgun-newsletters/)

---

<div class="post-metadata">

**Author:** ![Matt\_P](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/matt_p/32/18629_2.png) [@Matt\_P](https://forum.ghost.org/u/Matt_P)\
**Post date:** [June 19, 2023, 5:47am UTC](https://forum.ghost.org/t/mailgun-alternative/29428/6 "2023-06-19T05:47:24Z")

</div>

Deliverability has a lot more to do with the sending domain, the sender, and the list receiving the emails than it does with Mailgun or any other provider. Mailgun is at least conscious of warming up and keeping their sending IPs off of spam blacklists. If your emails are hitting the spam folder, the sender & their habits are the problem more often than not.

---

<div class="post-metadata">

**Author:** ![Anuga](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/anuga/32/26530_2.png) [@Anuga](https://forum.ghost.org/u/Anuga)\
**Post date:** [October 14, 2023, 4:01pm UTC](https://forum.ghost.org/t/mailgun-alternative/29428/7 "2023-10-14T16:01:40Z")

</div>

Mailgun for internal newsletter? No no no…

Imagine being a billion dollar company, and choosing to use Ghost as a internal, eller external, blog platform.  
Your running your own web/db/proxy/cache servers and your own mailservers.  
But you must use a external third party for newsletter sendouts, cause the developers of Ghost, wants you to use, Mailgun…

No no no… ;)

---

<div class="post-metadata">

**Author:** ![barnabynagy](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/barnabynagy/32/28464_2.png) [@barnabynagy](https://forum.ghost.org/u/barnabynagy)\
**Post date:** [January 17, 2024, 9:16pm UTC](https://forum.ghost.org/t/mailgun-alternative/29428/8 "2024-01-17T21:16:44Z")

</div>

Mailgun is the worst email provider I used so far and their support sucks! Please add other options like sendgrid or others!

See below:

 ![CleanShot 2024-01-17 at 15.14.23](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/3X/a/7/a7247a21868085cdf0d788bc283cc135560216bd.png)

 ![CleanShot 2024-01-17 at 15.14.33](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/3X/b/2/b2c46cca3d50e62d27a4280c3be79330b2a00c80.png)

 ![CleanShot 2024-01-17 at 15.14.53](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/3X/2/1/21929725dbb0296561148eee4ed79f46f2628184.png)

 ![CleanShot 2024-01-17 at 15.15.06](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/3X/e/4/e4afa660edb3ffad0d4610c821bf494f8c0a0704.png)

Please add other options!

---

<div class="post-metadata">

**Author:** ![block](https://avatars.discourse-cdn.com/v4/letter/b/839c29/32.png) [@block](https://forum.ghost.org/u/block)\
**Post date:** [January 27, 2024, 11:40am UTC](https://forum.ghost.org/t/mailgun-alternative/29428/9 "2024-01-27T11:40:46Z")

</div>

Not gonna happen anytime soon I’m afraid. They have other priorities. For now, Mailgun works pretty good for me, but I had to spend some time chatting with the support to let them whitelist my account.

---

<div class="post-metadata">

**Author:** ![ratchet](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/ratchet/32/28632_2.png) [@ratchet](https://forum.ghost.org/u/ratchet)\
**Post date:** [January 28, 2024, 1:29pm UTC](https://forum.ghost.org/t/mailgun-alternative/29428/10 "2024-01-28T13:29:00Z")

</div>

Sendgrid. Moonmail. Moosend. SMTP2GO. Elastic Email. MailerLite.

---

<div class="post-metadata">

**Author:** ![barnabynagy](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/barnabynagy/32/28464_2.png) [@barnabynagy](https://forum.ghost.org/u/barnabynagy)\
**Post date:** [January 28, 2024, 1:55pm UTC](https://forum.ghost.org/t/mailgun-alternative/29428/11 "2024-01-28T13:55:31Z")

</div>

What other priorities are more important than this? I did talk to mailgun support without any success to whitelist my account. I even tried their sending limit “business as usual” and they said it doesn’t make them happy. It’s a horrible company. I had to do a zapier integration with brevo. And now my stats are off. Ghost has their priorities off big time

 ![CleanShot 2024-01-18 at 12.37.48](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/3X/d/e/de43c0f99629bb5da1f64e8ecc0a3bd0f542b2bf.png)

---

<div class="post-metadata">

**Author:** ![Cathy\_Sarisky](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cathy_sarisky/32/25750_2.png) [@Cathy\_Sarisky](https://forum.ghost.org/u/Cathy_Sarisky)\
**Post date:** [January 28, 2024, 3:12pm UTC](https://forum.ghost.org/t/mailgun-alternative/29428/12 "2024-01-28T15:12:53Z")

</div>

I’ve had zero problems with Mailgun, but I started with no list when I started my blog, so I never hit their new account sending restrictions. My stats look great and I’m happy not to manage a mail server.

---

<div class="post-metadata">

**Author:** ![block](https://avatars.discourse-cdn.com/v4/letter/b/839c29/32.png) [@block](https://forum.ghost.org/u/block)\
**Post date:** [January 28, 2024, 4:11pm UTC](https://forum.ghost.org/t/mailgun-alternative/29428/13 "2024-01-28T16:11:16Z")

</div>

I believe their priority isn’t necessarily hundreds of thousands of users using their product for free (self hosting); that’s just my perspective. Instead, if you seek a seamless experience without issues, exploring their Pro service might be a worthwhile option. In my only interaction with Mailgun, they did a “KYC” process, inquiring about my business and ensuring compliance with their terms. Now, I have multiple websites sending emails under a single account, and everything works smoothly. Mailgun is an excellent product; following their requirements is key. Sending a modest volume of 1-2 emails per day to avoid hitting limits and subsequently engaging in a conversation with their support can swiftly resolve any issues and get you unblocked.

---

<div class="post-metadata">

**Author:** ![andreascreten](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/andreascreten/32/28386_2.png) [@andreascreten](https://forum.ghost.org/u/andreascreten)\
**Post date:** [May 15, 2024, 1:02pm UTC](https://forum.ghost.org/t/mailgun-alternative/29428/14 "2024-05-15T13:02:04Z")

</div>

We had a similar issue. Out of frustration, I started working on a fork with [Postmark](https://postmarkapp.com/) support: [📮 Postmark integration by andreascreten · Pull Request #19398 · TryGhost/Ghost · GitHub](https://github.com/TryGhost/Ghost/pull/19398)

To make our life easy, we are running the upgrade from a Github Action:

```yml
name: Upgrade Ghost From Our Fork
on: workflow_dispatch
jobs:
  upgrade:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        name: 📥 Checkout Ghost
        with:
          repository: madewithlove/ghost
          submodules: true
      - name: 📦 Install dependencies
        run: yarn
      - name: 🗂️ Create archive
        run: yarn archive
      - name: Rename file
        run: mv ghost/core/ghost-*.tgz ghost-from-fork.tgz
      - name: ⬆️ Upload archive to Ghost server
        uses: appleboy/scp-action@v0.1.7
        with:
          host: "XXXXXX"
          username: "ghost-mgr"
          source: "ghost-from-fork.tgz"
          target: "/var/www/ghost"
          key: ${{ secrets.GHOST_SSH_KEY }}
          timeout: 90s
      - name: 🚀 Upgrade Ghost from our archive
        uses: appleboy/ssh-action@v1.0.3
        with:
          host: "XXXXXX"
          username: "ghost-mgr"
          key: ${{ secrets.GHOST_SSH_KEY }}
          script: |
            cd /var/www/ghost
            ghost update --archive=ghost-from-fork.tgz
            rm ghost-from-fork.tgz

```

---

<div class="post-metadata">

**Author:** ![bastien](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/bastien/32/40675_2.png) [@bastien](https://forum.ghost.org/u/bastien)\
**Post date:** [August 19, 2024, 7:41am UTC](https://forum.ghost.org/t/mailgun-alternative/29428/15 "2024-08-19T07:41:56Z")

</div>

Open source alternatives to Mailgun :

- [https://docs.postalserver.io/](https://docs.postalserver.io/)
- [https://www.useplunk.com/](https://www.useplunk.com/)

---

<div class="post-metadata">

**Author:** ![barnabynagy](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/barnabynagy/32/28464_2.png) [@barnabynagy](https://forum.ghost.org/u/barnabynagy)\
**Post date:** [September 14, 2024, 12:05am UTC](https://forum.ghost.org/t/mailgun-alternative/29428/16 "2024-09-14T00:05:45Z")

</div>

Could have worked for that use case but for those of us who have a list already ghost sucks. Big time.

---

<div class="post-metadata">

**Author:** ![markstos](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/markstos/32/18182_2.png) [@markstos](https://forum.ghost.org/u/markstos)\
**Post date:** [September 16, 2024, 2:50pm UTC](https://forum.ghost.org/t/mailgun-alternative/29428/17 "2024-09-16T14:50:43Z")

</div>

There’s a fork of Ghost that works with Postmark now.

> <https://github.com/TryGhost/Ghost/pull/20530>
>
> I have been working on an integration of Postmark with Ghost. Please provide you…r feedback before I continue.
> 
> \## To-Do
> 
> \- \[x\] Implement analytics
> \- \[\] Handle Postmark errors
> \- \[\] Add tests
> 
> \---
> 
> \_This a copy of \[a previous PR\](https://github.com/TryGhost/Ghost/pull/19398), submitting it again because our main branch got corrupted due to a merge conflict.\_

I’ve left some feedback on it a couple of different times that I think would make it more likely be merged, but the fork author hasn’t replied to the feedback, nor have any official Ghost team members commented on what it take to get the PR into a mergable state. If done well, it would accomplish two things:

1. Set up an “adapter” pattern that allowed for alternate providers to be configured. Mailgun, instead of being hard-coded, would become the first and default user of this adapter pattern.
2. Support Postmark as an alternate adapter. One the first step is done, the Postmark support wouldn’t need to be in the Ghost code base at all. It could be published as a separate NPM module and not reviewed or supported by the Ghost team at all.

See my full feedback on the PR here:

> <https://github.com/TryGhost/Ghost/pull/19398#issuecomment-2132520491>
>
> Hello @andreascreten, I'm not a Ghost core team member, but am someone who previ…ously submitted my own PR to allow non-mailgun senders ( https://github.com/TryGhost/Ghost/pull/14984 ), so I can give you some feedback from that perspective. (Ultimately, I ended up using Mailgun and abandoned that effort). 
> 
> I don't think there's a lot of appetite for maintaining non-Mailgun code in the core with their small team, but I think there /is/ interest in implementing an adapter pattern for bulk-email and email-analytics so other options can be plugged in and, crucially, completely maintained by third-parties outside of the core.
> 
> So I think the ideal PR implements the adapter pattern and has Mailgun as the included, default solution implementing that package. There would actually be no references to Postmark in the PR, but the PR would enable you make the swap using the config file system and third-party modules that implement bulk-sending and analytics. The rest of your solution would in modules you maintain and possibly publish to NPM yourself. 
> 
> I see you made some progress in that direction replacing explicit references to MailGun with more generic "Bulk Email" or "Email Analytics" language when that part of the code has multiple possible implementations.  
> 
> \## References
> 
> \* \[Adapter Manager README\](https://github.com/TryGhost/Ghost/blob/main/ghost/adapter-manager/README.md)
> \* \[Adapter Manager Code\](https://github.com/TryGhost/Ghost/blob/98d49f57d52299a7363c1adb040abc0e273b3e88/ghost/adapter-manager/lib/AdapterManager.js)
> \* \[Other Ghost adapters on NPM\](https://www.npmjs.com/search?q=ghost%20adapter)
> 
> What appears to be happening is that a path to where a custom solution is stored gets declared under the "adapters" section in the config file. If this is not present, the internal implementation in used.
> 
> \## Admin UX
> 
> I saw your PR also took care of getting some Postmark bits to appear in the admin UI. I'm not sure the current adapter pattern covers that. What's there so far may only cover purely backend tasks, like swapping out data storage. It's possible you need to extend the adapter system to allow modules that implement the adapter system to have bits appear in the admin UI when they are loaded.

Oh, I see that @andreascreten who authored the Postmark fork is also in this thread. 👋🏼 Maybe responding to the PR feedback will help forward support for all non-Mailgun options.

---

<div class="post-metadata">

**Author:** ![andreascreten](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/andreascreten/32/28386_2.png) [@andreascreten](https://forum.ghost.org/u/andreascreten)\
**Post date:** [September 17, 2024, 9:26am UTC](https://forum.ghost.org/t/mailgun-alternative/29428/18 "2024-09-17T09:26:32Z")

</div>

Yep 👋

The issue is that I don’t have the time to make the required changes. One of our team members is keeping the fork up to date and solving issues we find while using it.

As long as we don’t get feedback from the Ghost team that they would be open to this in the first place, I don’t think it makes sense to invest more time in it.

---

<div class="post-metadata">

**Author:** ![interactivity-studio](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/interactivity-studio/32/33441_2.png) [@interactivity-studio](https://forum.ghost.org/u/interactivity-studio)\
**Post date:** [November 27, 2024, 7:14am UTC](https://forum.ghost.org/t/mailgun-alternative/29428/19 "2024-11-27T07:14:47Z")

</div>

The Grow plugin by Mediavine has a fantastic option to collect emails and hook them to an automated email segment through the Kit API. Plus, everything is free for up to 500 subscribers I believe.

Still, this is a third party tool, so might not feel as native to Ghost.

---

<div class="post-metadata">

**Author:** ![bastien](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/bastien/32/40675_2.png) [@bastien](https://forum.ghost.org/u/bastien)\
**Post date:** [November 27, 2024, 9:11am UTC](https://forum.ghost.org/t/mailgun-alternative/29428/20 "2024-11-27T09:11:20Z")

</div>

for such a usecase [BestRegards](https://www.bestregards.me/) has a native Ghost integration, much better

[Next page](https://forum.ghost.org/t/mailgun-alternative/29428.md?page=2)
