Lorenzo

It should.

In my case, I first made sure I purged all / everything exim4 related from my system, rebooted to make sure and then and installed DMA.
Had no issues, my system mail works perfectly well and a little old thingue called coolmail* sits in a corner on my desktop and lets me know when any system mail gets delivered to my box.

It got/gets installed by default in all (?) Devuan editions.

System mail was, till my exim4 incident, something absolutely transparent to me.
No idea it was called exim4, much less how complex it was.

Think a Norton 500 instead of a single speed rear-coaster brake cycle to go for your order of onion bhajis four blocks from your house.

I have put forth here at Dev1 that it would be a good idea to replace exim4 with DMA as the default MTA in all Devuan releases, with the exception of (maybe) server. ie: desktop-live, netinstall, desktop and minimal-live.

The logic behind that idea is that if a user knows about and needs whatever advantage exim4 has with respect to DMA, they will install it.
Otherwise, their system's MTA will be absolutely transparent to them. ie: it will just work as intended.

The plus will be that they will have avoided the possibility of hassle and wasted resources.

* See here: https://dev1galaxy.org/viewtopic.php?pid=30487#p30487

Best,

A.

That said and unless you really need something as complex as exim4 running in your box, you may want to consider using a simpler, much lighter and less complicated MTA such as Dragonfly.

If DMA works out of the box, I'll use it instead. I have no idea why I need exim4 at all. I do not carry out any administrative work that requires mail. I don't use /var/mail at all, I just don't need it. No use cases.

It was my mistake.

I linked to the DragonflyBSD page because it is where all data / info / How-to is, very complete.

But forgetting that when I went looking for it, I also found it hard to get the package location, I neglected to explain that for Debian / Devuan it is called DMA. ie: DragonFly Mail Agent 

DragonflyBSD and DMA are the same application, different ports / packaging (?).

Best,

A.

Look again:

Yes, you are right. Somehow I missed it. Thank you.

Look again:

~$ apt list | grep dma
--- snip ---
dma/stable,now 0.13-1+b1 amd64 [installed]
dma/stable 0.13-1+b1 i386
--- snip ---
~$

See:
https://pkginfo.devuan.org/cgi-bin/poli … a&x=submit
https://pkginfo.devuan.org/cgi-bin/pack … =0.13-1+b1

Best,

A.

That said and unless you really need something as complex as exim4 running in your box, you may want to consider using a simpler, much lighter and less complicated MTA such as Dragonfly.

Hello.

This package is not available in the official Devuan package repository...and compiling it is not a good idea.

Exim4 had a huge lot of issues at one point and it could be that (depending on your installed version / upgrade cycle) you are suffering them now.

You may want to have a read at this thread (specifically the last two posts) to get an idea of what may be going on in your box.

https://dev1galaxy.org/viewtopic.php?pid=30412#p30412
https://dev1galaxy.org/viewtopic.php?pid=30469#p30469

That said and unless you really need something as complex as exim4 running in your box, you may want to consider using a simpler, much lighter and less complicated MTA such as Dragonfly.

See this thread and the DragonflyBSD web page.

Best,

A.

#!/usr/bin/env /lib/runit/invoke-run
#Copyright: 2022 Lorenzo Puliti <plorenzo@disroot.org>
#License: CC0-1.0

exec 2>&1

# only works for "combined" configuration mode
QUEUERUNNER='combined'
[ -d /run/exim4 ] || \
  install -d -oDebian-exim -gDebian-exim -m750 /run/exim4
LANG=C
export LANG

if [ -e /etc/runit/verbose ]; then
        echo "invoke-run: starting ${PWD##*/}"
fi
#-bdf is also ok but no log to stdout for svlogd
exec /usr/sbin/exim4 -bd -d -q${QFLAGS}${QUEUEINTERVAL} $COMMONOPTIONS $QUEUERUNNEROPTIONS $SMTPLISTENEROPTIONS

It is broken. exim4 complains about incompatible command line parameters. runit ends up racking my PID table by constant attempts to restart. My current (half clueless) workaround is

mkdir env
echo 30m > env/QUEUEINTERVAL