From: Curtis J Blank <curt@curtronics.com> Date: Wed, 26 Jun 2024 17:55:56 -0500 Ah ha! Thanks! Your explanation made me think of something that might be the difference between my two servers and why the new one needs the hostname set to a FQDN. /etc/resolv.conf The new server only had one entry, one nameserver. The existing server has two nameservers listed and a "search <myDomain>" entry. Oversight on my part. Put the second entry and search statement in resolv.conf on the new server. Yes, that would certainly explains it. Then on the new server set the hostname to just the servers name and cleared domainname so it then matched the old server's configuration and amavisd successfully starts. I'm betting having the search in resolv.conf is the key. -Curt It works, and I'm glad you're out of the woods now, but this all seems pretty hackish to me. Especially since (I just learned) that Amavis lets you set the server host name explicitly in amavisd.conf in the $myhostname variable [1], and so it's just using Net::Domain to compute a default. At the very least, it should catch errors like these and say "Please set $myhostname" instead of dying obscurely. You may want to submit an Amavis bug report. Interestingly, a little googling shows that failing in Net::Domain is something of a FAQ, going back to 2005 [2]. The nest-to-last post on that thread shows that it does produce a proper error message that explains the problem (as of release 2.2.3, 22-Aug-2005 [3]) when it doesn't die unexpectedly. -- Bob [1] https://github.com/aosm/amavisd/blob/master/amavisd/amavisd-new-2.6.6/amavis...; see line 73. [2] https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/251377 [3] https://gitlab.com/amavis/amavis/-/blob/master/RELEASE_NOTES?ref_type=heads; see line 11579.