mailgun stopped working
Design and Skin Customization
soaringeagle:
i thought the whole purpose was to avoid any possibility that your ip is flagged as spam and messages going to spam box
alsoo to handle outgoing mail that is bounced back as undeliverable
thats my main reason why i want to use it everytime i send a broadcast message i get about 1500 or more message not deliverable emails flooding my inbox
if its mostly for incoming i have a contact us thingy that i use wich works great
so i wouldnt need it
i thought the whole purpose was to avoid any possibility that your ip is flagged as spam and messages going to spam box
alsoo to handle outgoing mail that is bounced back as undeliverable
thats my main reason why i want to use it everytime i send a broadcast message i get about 1500 or more message not deliverable emails flooding my inbox
if its mostly for incoming i have a contact us thingy that i use wich works great
so i wouldnt need it
You misunderstand how Mailgun works. When you configure your local SMTP server to use a "smarthost" (that's what the guide I linked to above is basically doing) what happens is that your server SENDS outgoing email to Mailgun, and they THEY deliver it. Your server only ever talks to Mailgun. If a message bounces, it will come back to Mailgun's servers - NOT yours - since Mailgun does all the delivery. You need to think of your local SMTP server as simply being a local queue system that you can dump email into, and it will in turn forward it all over to Mailgun. This is MUCH faster than using a web API, since Postfix is designed to handle hundreds of emails being added to it's delivery queue in a matter of seconds. It will then properly forward those over to Mailgun for delivery.
https://en.wikipedia.org/wiki/Smart_host