https://bugzilla.novell.com/show_bug.cgi?id=460442 Summary: amavisd-new and Postfix need fqdn-hostname in "uname -n" Product: openSUSE 11.0 Version: Final Platform: i586 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: p.heinlein@jpberlin.de QAContact: qa@suse.de Found By: Consulting amavisd-new and Postfix try to set their hostname in $myhostname based on the output of "uname -n". On SuSE-systems this resolves just to the hostname: # uname -n host But not to a fqdn-version of that hostname (like it is on Debian-systems): # uname -n host.example.com amavisd-new isn't able to start out-of-the-box: atlas:/etc/init.d # rcamavis start Starting virus-scanner (amavisd-new): The value of variable $myhostname is "host", but should have been a fully qualified domain name; perhaps uname(3) did not provide such. You must explicitly assign a FQDN of this host to variable $myhostname in amavisd.conf, or fix what uname(3) provides as a host's network name! failed Postfix has problems with the same problems with a non-fqdn-hostname. Even if the hostname is setup with fqdn in YaST, Postfix can't read the domainpart with "uname -n". This leads to a stupid myhostname in Postfix: # postconf myhostname myhostname = atlas.localdomain It would be so easy if "uname -n" would give a fqdn -- and in this case Postfix would set up his hostname correctly: # postconf myhostname myhostname = atlas.example.com Setting $myhostname in /etc/amavisd.conf and /etc/postfix/main.cf is a kind of solution, but it's very ugly if you want to use the same syncronized amavisd.conf or main.cf in a cluster of multiple hosts. It would be much better if both programs could start without manual setup. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.