Question 1

How do I send attachments with Mailgun in Elixir?

Accepted Answer

Use the `attachments` parameter in `send_email` with a list of maps, each containing `filename` and either `path` for files or `content` for raw data. For example, `attachments: [%{path: file_path, filename: 'greetings.png'}]` as shown in the README.

Question 2

Mailgun Elixir client vs Swoosh: which one should I use?

Accepted Answer

Mailgun client is specific to Mailgun's API with a simple, declarative interface, ideal for direct Mailgun integration. Swoosh is a more feature-rich library supporting multiple adapters, templating, and async delivery, better for multi-provider or complex email workflows.

Question 3

How to test emails without sending them in Elixir Mailgun?

Accepted Answer

Configure test mode by setting `mode: :test` and `test_file_path` in your Mailer module. This writes email data to a JSON file at the specified path, allowing inspection without API calls, as demonstrated in the README.

Question 4

Can I use Mailgun client with Phoenix applications?

Accepted Answer

Yes, it integrates easily with Phoenix by adding the dependency to mix.exs and configuring it in config files. The README shows examples in `config/config.exs` and `lib/mailer.ex` for setting up domain and key.

Question 5

What HTTP client does the Mailgun library use?

Accepted Answer

It uses Erlang's `httpc` client, and you can customize it via `httpc_opts` in configuration. For instance, you can set timeouts like `connect_timeout: 2000` to control request behavior.

Question 6

Is the Mailgun Elixir library stable for production?

Accepted Answer

Given its version 0.1.2, it might be less stable or subject to changes. Check the GitHub repository for recent updates and issue tracking before deploying in critical production environments.

mailgun

What is mailgun?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions