In /var/spool/dma are some 200+ messages a few are cron daily reports the rest are ' fail to deliver'.
I don't see anything in /etc/dma/dma.conf that looks like it should be other than default except SMARTHOST smtp.frontier.com
/etc/aliases points everything to root, then root to mike.
I didn't expect it to make a diference but created /root/Mail just in case. It didn't help.
I use fetchmail and mutt to read mail from off site and that works fine.
Thinking it might be a permissions problem I looked at these:
mike@DevuanPI4b:~> ls -l /var/mail
lrwxrwxrwx 1 root root 26 Feb 10 11:06 /var/mail -> /mc/docs/letters/incoming/
Mikemike@DevuanPI4b:~> ls -l /var/mail/
total 312
-rw--w---- 1 mike mail 317051 May  4 16:17 mike
-rw--w---- 1 root mail      0 Feb 20 02:05 root
mike@DevuanPI4b:~> ls -l /mc/docs/letters/incoming/
total 312
-rw--w---- 1 mike mail 317051 May  4 16:17 mike
-rw--w---- 1 root mail      0 Feb 20 02:05 root

At the moment I'm baffled, what am I missing?
Suggestions welcome.
Thanks,
Mike

I made the mistake of purging network-manager and it's associated packages then discovered I couldn't figure out how to get the network configured again.
    Consequently I switched to a Debian bookworm install to replace the packages I had purged. I was unable to figure out how to tell the 'Devuan Package Information' system that I wanted arm64 rather than amd64 packages.
   The only way I found was to search for the package, select the appropriate version that matched up with daedalus, on the new page I then scrolled down to the download link for the amd64 version copied the link, pasted it into the browser address bar, changed 'amd64' to 'arm64' in the address and then downloaded the correct package.
    Needless to say that was rather a hassle and quite time consuming for 21 packages.
    I suspect there is an easier way and hope someone here will point it out to me.

Thanks,
Mike

mike@DevuanPI4b:~> uname -a
Linux MikesDevuanPI 6.1.70 #1 SMP PREEMPT Sun Jan  7 04:13:59 CET 2024 aarch64 GNU/Linux

After my initial install with LXDE I broke the system trying to remove it so reinstalled from scratch then installed twm.
I've got it working but LibreOffice tools don't play well and I use calc daily. Changing calc's window size throws it for  loop and I must close it then reload it to make it usable again.
Looking through the output of `apt-cache dumpavail' I see several window managers who install under 100,000 bytes. Among them 9wm, cwm, dwm, evilwm, flwm, lwm and windowlab and many wouldn't require adding more libs than twm has already installed.
I was wondering if anyone here had tried any of those and liked them.

Thanks for your thoughts,
Mike

This is not really a Devuan problem but I'm not having the problem on my Raspberry Pi Debian system.
I'm just getting a Devuan system set up and had to start over after installing LXDE via tasksel.

mike@DevuanPI4b:~> uname -a
Linux MikesDevuanPI 6.1.70 #1 SMP PREEMPT Sun Jan  7 04:13:59 CET 2024 aarch64 GNU/Linux

When I installed firefox-esr this time it came without the top menu that has 'File, Bookmarks. etc.' and I can't find how to put it back.

If anyone here has solution I'll be grateful.

Thanks,
Mike

mike@RPI4b3:~> uname -a
Linux MikesPI 6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux

Yes I'm on Raspberry Debian now but my Devuan system still isn't working well enough to post here and I ran into this first on my daedalus system.
visudo complains that my hostname can't be found via DNS, which i don't find surprising since I'm a single user system serving no ports. It's been like that for years and never caused a problem until I installed Devuan. 'visudo /etc/sudo.conf'  shows a line '# Set probe_interfaces false' which should tell sudo not to worry whether hostname returns an FQDN. Unfortunalely, visudo sees that as a syntax error and sudo ignores that line. If I leave the line uncommented sudo still complains if mike takes eth0 up or down. I just checked and the same thing happens on this system. Both are Debian based systems and I'm wondering if anyone here can say Iif the problem comes from Debian or upstream.
Thanks for listening.
Be well,
Mike