User authentication when delivering mails to Exim

[jicho]

Hi,

I'm looking for an Exim implementation with a smarthost and the option to authenticatie the sending user.

When I'm reading the docs correct I can setup a smarthost with authentication using:

SMARTHOST_ADDRESS=mail.mysmtp.com
SMARTHOST_PORT=587
SMARTHOST_USER=myuser
SMARTHOST_PASSWORD=secret
SMARTHOST_ALIASES=*.mysmtp.com

But... Is it also possible to add a username/password for the internal applications? Looking at the docs I don't think it is possible, but... just to be 100% sure I'm asking the question :)

I'm looking for a user login for sending from my internal networking because:

• some (Docker) application only send mails when a user/password has been provided, like WUD (What's Up Docker)
• I want a central point of change when switching my hosting provider (the smarthost part)
• it is more secure (only internal applications with a login can send mail using port 25 using my smarthost)

I did found an article of how it should work, but implementing this is a different story: https://bobcares.com/blog/exim4-smtp-authentication/

Maybe you can add "Exim" to your project documentation/description. Initially I didn't foun this project due to the fact that that Exim isn't mentioned. I can imagine that more people are missing this, good looking, project.

[tlex]

Hello, This was never in the scope for this application. For exactly the use case you describe, I can only recommend a full MTA, where you can also manage the users you enable (for example jeboehm/docker-mailserver).

If you are using any type of SDN (either the docker swarm built-in, or anything from this list), then you can sort out what containers have access to your simple SMTP image on a network layer - no need for authentication on top.

[jicho]

Thanks for your quick reaction.

The example does not seem to support a smarthost/relay with authentication like your project does. That means trouble at the sending part of the proces :)

I will look further, or maybe I figure out a way to solve the problem at the application part that wants (for some reason) a required user/pass when sending messages.