Mailgun Alternatives
- Thread starter Daniel_D
- Start date
We support both Postmark and Mailgun. While Postmark's setup is similar, they increased their prices, prompting us to find an alternative. Sadly, few mail providers handle inbound emails via webhooks, as most focus only on outbound. Inbound email handling is essential to the FS PBX fax. Reading SMTP servers has proven unreliable and limited in features.
Do you do a lot of faxing? Have you thought about giving the users that need to fax, "fax" access to the FXPBX? You can set-up users to just have fax access, and then when they login, they Click "send New Fax", select their fax number, and put in the recipient's fax number and Drag & Drop the file to be faxed. It doesn't cost anything, and I've found my fax users like it, since it's so easy.
Take a look at this, I have been using it for years for other projects. Its open source: https://docs.postalserver.io/
I've never used this bit but it may do the job: https://docs.postalserver.io/developer/http-payloads
I've never used this bit but it may do the job: https://docs.postalserver.io/developer/http-payloads
There is a bit of faxing done over multiple end customers.
I have a mix of customers either doing just email to fax, faxing via portal and email to fax
Some of them do have portal access. Majority that do are happy with the email to fax functionality
Thanks for the suggestion, it looks good at a quick glance
ill have a look into it
Yes, but not as a drop-in replacement — because Gmail's model is fundamentally different from Mailgun/Postmark. Those two are email-parsing-to-webhook services; Gmail is a mailbox you read from. The crucial difference:
Mailgun / Postmark do PUSH. User sends an email to <phonenumber>@yourfaxdomain.com (the destination fax number is the local-part of the To: address). Mailgun/Postmark receives the email and POSTs a parsed email to FS PBX.
With Google, we have to do PUSH to fetch email from the mailbox. It would also require a much more complicated OAuth 2.0. In this case, it will be a shared service mailbox, a service account with domain-wide delegation.
This can be done, but it would require adding a large amount of new code to support all of the above.
Mailgun / Postmark do PUSH. User sends an email to <phonenumber>@yourfaxdomain.com (the destination fax number is the local-part of the To: address). Mailgun/Postmark receives the email and POSTs a parsed email to FS PBX.
With Google, we have to do PUSH to fetch email from the mailbox. It would also require a much more complicated OAuth 2.0. In this case, it will be a shared service mailbox, a service account with domain-wide delegation.
This can be done, but it would require adding a large amount of new code to support all of the above.
I just decomissioned postal server about half an hour ago. been using it for a while and while I loved it and kept my IP reputation fantastic I was blocked by Microsoft because some other IP in my server's IP range was abusing and Microsoft blocked the whole range. Just migrated anyy services to smto2go. Sadly smtp2go does not support webhook for inbound.
while I like pbx to read from inbox I love the functionality for user to send using number@domain.com format
Unfortunately, not many providers do. Mailgun includes a fair number of inbound emails in the free plan. There shouldn't be any issue for anyone to use it. You can continue using smtp2Go for everything else. Let Mailgun own only MX records for a subdomain, for example, fax.yourdomain.com. Then users will be sending emails to <phone_number>@fax.yourdomain.com