Email not sending / receiving

Joel Vande Berg jdv at universal5.com
Fri Aug 12 16:33:44 CEST 2016


I didn't have a backup to restore, but since I had done a yum update.  I did a fresh deployment and re-installed kolab.  This time I did not run 'yum update'

The re-install did not set $myhostname in amavisd.conf.  I reset it and tried a restart.  Same result as last night.    After reading Greg's suggestion I ran 'yum update -exclude=clamav-*' and rebooted.  Same result.

[root at pontiac ~]# systemctl restart amavisd
Job for amavisd.service failed because the control process exited with error code. See "systemctl status amavisd.service" and "journalctl -xe" for details.
[root at pontiac ~]# journalctl -xe
Aug 12 14:31:47 pontiac amavis[4711]: logging initialized, log level 9, syslog: amavis.mail
Aug 12 14:31:47 pontiac amavisd[4711]: The value of variable $myhostname is "pontiac", but should have been
Aug 12 14:31:47 pontiac amavisd[4711]: a fully qualified domain name; perhaps uname(3) did not provide such.
Aug 12 14:31:47 pontiac amavisd[4711]: You must explicitly assign a FQDN of this host to variable $myhostname
Aug 12 14:31:47 pontiac amavisd[4711]: in amavisd.conf, or fix what uname(3) provides as a host's network name!
Aug 12 14:31:47 pontiac systemd[1]: amavisd.service: control process exited, code=exited status=255
Aug 12 14:31:47 pontiac systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
-- Subject: Unit amavisd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit amavisd.service has failed.
--
-- The result is failed.
Aug 12 14:31:47 pontiac systemd[1]: Unit amavisd.service entered failed state.
Aug 12 14:31:47 pontiac systemd[1]: amavisd.service failed.
Aug 12 14:31:48 pontiac systemd[1]: amavisd.service holdoff time over, scheduling restart.
Aug 12 14:31:48 pontiac systemd[1]: Starting Amavisd-new is an interface between MTA and content checkers....
-- Subject: Unit amavisd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit amavisd.service has begun starting up.
Aug 12 14:31:48 pontiac amavis[4715]: logging initialized, log level 9, syslog: amavis.mail
Aug 12 14:31:48 pontiac amavisd[4715]: The value of variable $myhostname is "pontiac", but should have been
Aug 12 14:31:48 pontiac amavisd[4715]: a fully qualified domain name; perhaps uname(3) did not provide such.
Aug 12 14:31:48 pontiac amavisd[4715]: You must explicitly assign a FQDN of this host to variable $myhostname
Aug 12 14:31:48 pontiac amavisd[4715]: in amavisd.conf, or fix what uname(3) provides as a host's network name!
Aug 12 14:31:48 pontiac systemd[1]: amavisd.service: control process exited, code=exited status=255
Aug 12 14:31:48 pontiac systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
-- Subject: Unit amavisd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit amavisd.service has failed.
--
-- The result is failed.
Aug 12 14:31:48 pontiac systemd[1]: Unit amavisd.service entered failed state.
Aug 12 14:31:48 pontiac systemd[1]: amavisd.service failed.
Aug 12 14:31:48 pontiac systemd[1]: amavisd.service holdoff time over, scheduling restart.
Aug 12 14:31:48 pontiac systemd[1]: start request repeated too quickly for amavisd.service
Aug 12 14:31:48 pontiac systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
-- Subject: Unit amavisd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit amavisd.service has failed.
--
-- The result is failed.
Aug 12 14:31:48 pontiac systemd[1]: Unit amavisd.service entered failed state.
Aug 12 14:31:48 pontiac systemd[1]: amavisd.service failed.

From: Gregor Adamczyk [mailto:g.adamczyk at netkult.eu]
Sent: Friday, August 12, 2016 12:01 AM
To: users at lists.kolab.org
Subject: RE: Email not sending / receiving

Am 12.08.2016 um 01:27 schrieb users-request at lists.kolab.org<mailto:users-request at lists.kolab.org>:

RE: Email not sending / receiving




Restored my backup and did only an:
yum update --exclude=clamav-*

Now it works correctly.

See also:
https://kolab.org/hub/topic/80/unchecked-tagging-on-all-messages/3
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20160812/1aef85ae/attachment.html>


More information about the users mailing list