How can we use Mailgun service and what is the entire process?
Welcome to the Ghost community, @BarcodeMaker.
Please read the help guides.
1 Like
I didn’t set up any JSON logic at all, just followed the bouncing ball [instructions] after creating a mailgun account:
- Set up DNS records
- In Ghost Admin v5.x: Email newsletter : Mailgun settings
… entered my email subdomain and Mailgun API and I was done.
It sends emails upon publishing a fresh newsletter.
- I received my own email notification about a new publication
- Ghost admin statistics on emails sends, opens, …
- Mailgun Statistics on emails having gone out, opened, bounced, spam, …
It took more than 57sec to set up, contrary to Mailgun propaganda, but it works, for now …
… just need to find the correct flow to downgrade to Mailgun’s flex subscription when the time comes.
Just discovered that a user was trying to subscribe and he got an error in regards to getting his magick cookie for login.
BEFORE I’d set up mailgun, my DIRECT email (on my FreeBSD server that means DragonFly MTA) function was working as I tested it. It seemed to work after, too … so I don’t know where the disconnect it.
In the end, I did have to set up JSON: config.production.json and use mailgun for sending magick cookies … now login works again.
Did anyone else have this experience? Any insights in what I might have missed? Is ghost specifically set up so that once Mailgun is configured for bulk email/newsletters, local MTA is disregarded and must also use Mailgun?
… just curious …