Re: Dragonfly Mail Agent (dma) in the base system

Ed Maste <emaste@FreeBSD.org> wrote:

> Since 2014 we have a copy of dma in the base system available as an
> optional component, enabled via the WITH_DMAGENT src.conf knob.

I thought it was enabled at default!

> I am interested in determining whether dma is a viable minimal base
> system MTA, and if not what gaps remain. If you have enabled DMA on
> your systems (or are willing to give it a try) and have any feedback
> or are aware of issues please follow up or submit a PR as appropriate.

I use it on my non-mailservers for delivering both local mail and remote
mail (from cron etc. to remote users) via my mailservers as smarthost.

It works perfectly. I've been using it for many years. It doesn't run as
a daemon - if a message can't be delivered (e.g. smarthost temporarily
unavailable), it will be requeued, and the process exits.

Don't forget to add the cron entry to retry requeued entries!

*/30    *       *       *       *       root    /usr/libexec/dma -q
 
Thus was my only minor "gotcha" - it wasn't obvious from the man pages
to add the cron entry (or maybe I just missed it)

As for the smarthost configuration, I've successfully used ipv4, ipv6,
both on port 25, and non-standard ports. I've also used combinations
of non-encrypted, TLS, and opportunistic TLS, - all work as expected.

I haven't ever used the smtp-login facility.

Cheers, Jamie