Am Sat, Dec 18, 2021 at 07:19:19PM -0700 schrieb Grant Taylor:
> On 12/18/21 4:00 PM, Frank Steinmetzger wrote:
> > Just for the record and completeness’ sake: ... I found out that the
> > program was actually called dma -- the DragonFly BSD mail transport
> > agent, not mda.
> 
> Thank you for sharing your find Frank.
> 
> The DragonFly BSD MTA looks interesting.  I'll have to check it out.
> Especially if it's small and intended for local delivery and / or getting
> messages off of box all the while without exposing an SMTP port.

A little update report. After the setup of dma went so smoothly on my Arch
installations, I wanted to recreate it on my Gentoo-based NAS over the
weekend:

- cloned the dma repo¹ and installed everything
- removed everything from /var/spool/mail and any leftover queues for a
  clean start
- changed the sendmail path in fcron.conf from usr/bin to usr/local/bin
- had to amend /etc/mailutils.conf, because it sets up the root mailbox as
  a maildir called .maildir (according to the comment, that is Gentoo-
  specific). So I just commented out that block to (hopefully) get GNU
  maildir default behavior

Now I finally get mails from cron et al on my NAS and can read them with
mail or mutt. I can sleep better now, knowing that it will monitor its four
6 TB disks and notify me at the first sign of trouble, including “there is
new mail” on the console. \o/

There is one last niggle: after I read a message with the mail tool, it
saves those messages in /root/mbox. It does not do this on Arch, but keeps
them in /var/spool/mail/root instead. So far I haven’t found out why it does
that and where that might be configured. Perhaps some leftover config from
previous experiments with different mail packages.


¹ https://github.com/corecode/dma

-- 
Grüße | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

The circle is the parallel to the dot.

Attachment: signature.asc
Description: PGP signature

Reply via email to