From: Curtis J Blank <curt@curtronics.com> Date: Tue, 25 Jun 2024 12:48:33 -0500 Hope this is the correct place to post this. New to Tumblewed not new to openSuSE New install of Tumbleweed on new server. Can't get postfix to deliver mail it gets a 421 when trying to talk to port 10025 I don't think it's firewall related because amavisd fails to start with: Insecure directory in $ENV{PATH} while running with -T switch at /usr/lib/perl5/5.38.2/Net/Domain.pm line 173. BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.38.2/Amavis/Conf.pm line 1038. Compilation failed in require at /usr/lib/perl5/vendor_perl/5.38.2/Amavis.pm line 27. BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.38.2/Amavis.pm line 27. So is that indicating there are two distinct errors? PATH and Perl? Logged into the server checked all the directories I see in the PATH all are 755. According to "man perldiag" (albeit for perl 5.26.1 under openSUSE Leap 15.5, though I don't expect any different for later Perl versions), the entry for "Insecure directory ..." also says "... the PATH must not contain any relative directory." IME, "." is the usual offender. This same postfix conf (older version though) is running on another openSuSE server and for the life of me I cannot find what is different so I'm stumped at the moment as to why. This is not about Postfix, but about how amavisd is started. I looked at the current version of Net::Domain as distributed from CPAN [1] and in the repo [2] and that is certainly not what has changed. Line 173 uses backticks to invoke "domainname", so if you pruned PATH judiciously in the script that starts amavisd, that ought to be enough. -- Bob Rogers http://www.rgrjr.com/ [1] https://metacpan.org/pod/Net::Domain [2] https://github.com/steve-m-hay/perl-libnet/blame/master/lib/Net/Domain.pm