Why use the Mailgun API

You can send emails using SMTP via any mail server, so why use this PL/SQL API for Mailgun? There are a number of advantages:

• Reputation

  If you're sending lots of emails to people around the internet, you'll probably have had to contend with mail servers randomly marking your emails as "spam" - especially if you haven't set up SPF and DKIM signatures for your emails. Mailgun handles this automatically for you.

  Mailgun also handles volume limitations with ramp up and back off strategies, so if a target server is not accepting too many emails it will wait and retry later.

• Automated unsubscribes

  You can add an "Unsubscribe" link to each email very easily, and you don't need to code anything more; Mailgun will automatically screen those recipients who have unsubscribed from any future emails you send. You can make these unsubscribe links specific to a "tag" so that they can unsubscribe from general announcements (for example) while still getting transactional emails.

• Reliability

  Mailgun handles retries and backoff strategies to both manage your server's reputation and minimise non-delivery of emails.

• Performance

  The API calls are faster (than SMTP) and the emails generally arrive sooner. BLOB data isn't expanded to base64 when sent to Mailgun; the Mailgun server will take care of the correct encoding when it sends it on.

• Easily integrated

  For existing interfaces (e.g. Oracle APEX) that use SMTP, it's easy to set it up so that they work seamlessly with Mailgun too.