Email not sending / receiving
Joel Vande Berg
jdv at universal5.com
Fri Aug 12 01:27:46 CEST 2016
The output is quite large. I'll try some excerpts, but let me know if you need the whole thing.
-- Unit session-19.scope has begun starting up.
Aug 11 20:46:17 pontiac sshd[5653]: pam_unix(sshd:session): session opened for user root by (uid=0)
Aug 11 20:46:54 pontiac polkitd[3266]: Registered Authentication Agent for unix-process:5675:895108 (system bus name :1.58 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, local
Aug 11 20:46:54 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 11 20:46:54 pontiac amavis[5680]: logging initialized, log level 9, syslog: amavis.mail
Aug 11 20:46:54 pontiac amavisd[5680]: The value of variable $myhostname is "pontiac", but should have been
Aug 11 20:46:54 pontiac amavisd[5680]: a fully qualified domain name; perhaps uname(3) did not provide such.
Aug 11 20:46:54 pontiac amavisd[5680]: You must explicitly assign a FQDN of this host to variable $myhostname
Aug 11 20:46:54 pontiac amavisd[5680]: in amavisd.conf, or fix what uname(3) provides as a host's network name!
Aug 11 20:46:54 pontiac systemd[1]: amavisd.service: control process exited, code=exited status=255
Aug 11 20:46:54 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 11 20:46:54 pontiac systemd[1]: Unit amavisd.service entered failed state.
Aug 11 20:46:54 pontiac systemd[1]: amavisd.service failed.
Aug 11 20:46:54 pontiac polkitd[3266]: Unregistered Authentication Agent for unix-process:5675:895108 (system bus name :1.58, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Aug 11 20:46:54 pontiac systemd[1]: amavisd.service holdoff time over, scheduling restart.
Aug 11 20:46:54 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 11 20:46:55 pontiac amavis[5685]: logging initialized, log level 9, syslog: amavis.mail
Aug 11 20:46:55 pontiac amavisd[5685]: The value of variable $myhostname is "pontiac", but should have been
Aug 11 20:46:55 pontiac amavisd[5685]: a fully qualified domain name; perhaps uname(3) did not provide such.
Aug 11 20:46:55 pontiac amavisd[5685]: You must explicitly assign a FQDN of this host to variable $myhostname
Aug 11 20:46:55 pontiac amavisd[5685]: in amavisd.conf, or fix what uname(3) provides as a host's network name!
Aug 11 20:46:55 pontiac systemd[1]: amavisd.service: control process exited, code=exited status=255
Aug 11 20:46:55 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 11 20:46:55 pontiac systemd[1]: Unit amavisd.service entered failed state.
Aug 11 20:46:55 pontiac systemd[1]: amavisd.service failed.
Aug 11 20:46:55 pontiac systemd[1]: amavisd.service holdoff time over, scheduling restart.
Aug 11 20:46:55 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 11 20:46:56 pontiac amavis[5689]: logging initialized, log level 9, syslog: amavis.mail
Aug 11 20:46:56 pontiac amavisd[5689]: The value of variable $myhostname is "pontiac", but should have been
Aug 11 20:46:56 pontiac amavisd[5689]: a fully qualified domain name; perhaps uname(3) did not provide such.
Aug 11 20:46:56 pontiac amavisd[5689]: You must explicitly assign a FQDN of this host to variable $myhostname
Aug 11 20:46:56 pontiac amavisd[5689]: in amavisd.conf, or fix what uname(3) provides as a host's network name!
Aug 11 20:46:56 pontiac systemd[1]: amavisd.service: control process exited, code=exited status=255
Aug 11 20:46:56 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 11 20:46:56 pontiac systemd[1]: Unit amavisd.service entered failed state.
Aug 11 20:46:56 pontiac systemd[1]: amavisd.service failed.
Aug 11 20:46:56 pontiac systemd[1]: amavisd.service holdoff time over, scheduling restart.
Aug 11 20:46:56 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 11 20:46:57 pontiac amavis[5693]: logging initialized, log level 9, syslog: amavis.mail
Aug 11 20:46:57 pontiac amavisd[5693]: The value of variable $myhostname is "pontiac", but should have been
Aug 11 20:46:57 pontiac amavisd[5693]: a fully qualified domain name; perhaps uname(3) did not provide such.
Aug 11 20:46:57 pontiac amavisd[5693]: You must explicitly assign a FQDN of this host to variable $myhostname
Aug 11 20:46:57 pontiac amavisd[5693]: in amavisd.conf, or fix what uname(3) provides as a host's network name!
Aug 11 20:46:57 pontiac systemd[1]: amavisd.service: control process exited, code=exited status=255
Aug 11 20:46:57 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 11 20:46:57 pontiac systemd[1]: Unit amavisd.service entered failed state.
Aug 11 20:46:57 pontiac systemd[1]: amavisd.service failed.
Aug 11 20:46:57 pontiac systemd[1]: amavisd.service holdoff time over, scheduling restart.
Aug 11 20:46:57 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 11 20:46:57 pontiac amavis[5697]: logging initialized, log level 9, syslog: amavis.mail
Aug 11 20:46:57 pontiac amavisd[5697]: The value of variable $myhostname is "pontiac", but should have been
Aug 11 20:46:57 pontiac amavisd[5697]: a fully qualified domain name; perhaps uname(3) did not provide such.
Aug 11 20:46:57 pontiac amavisd[5697]: You must explicitly assign a FQDN of this host to variable $myhostname
Aug 11 20:46:57 pontiac amavisd[5697]: in amavisd.conf, or fix what uname(3) provides as a host's network name!
Aug 11 20:46:57 pontiac systemd[1]: amavisd.service: control process exited, code=exited status=255
Aug 11 20:46:57 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 11 20:46:57 pontiac systemd[1]: Unit amavisd.service entered failed state.
Aug 11 20:46:57 pontiac systemd[1]: amavisd.service failed.
Aug 11 20:46:57 pontiac systemd[1]: amavisd.service holdoff time over, scheduling restart.
Aug 11 20:46:57 pontiac systemd[1]: start request repeated too quickly for amavisd.service
Aug 11 20:46:57 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.
-----Original Message-----
From: me at chrisfleming.org [mailto:me at chrisfleming.org]
Sent: Thursday, August 11, 2016 5:10 PM
To: Joel Vande Berg <jdv at universal5.com>
Cc: users at lists.kolab.org
Subject: Re: Email not sending / receiving
On 11/08/16 at 08:51pm, Joel Vande Berg wrote:
> Chris,
>
> Thanks for the continued help with this.
No problem - not quite enough information in the status command to tell us why it didn't start :(
Can you see if
journalctl -xe
Tells us why it's failing to start.
Cheers
Chris
>
> The restart failed -
>
> [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 ~]# systemctl status amavisd ● amavisd.service -
> Amavisd-new is an interface between MTA and content checkers.
> Loaded: loaded (/usr/lib/systemd/system/amavisd.service; enabled; vendor preset: disabled)
> Active: failed (Result: start-limit) since Thu 2016-08-11 20:46:57 UTC; 34s ago
> Docs: http://www.ijs.si/software/amavisd/#doc
> Process: 5697 ExecStart=/usr/sbin/amavisd -c
> /etc/amavisd/amavisd.conf (code=exited, status=255)
>
> Aug 11 20:46:57 pontiac systemd[1]: amavisd.service: control process
> exited, code=exited status=255 Aug 11 20:46:57 pontiac systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
> Aug 11 20:46:57 pontiac systemd[1]: Unit amavisd.service entered failed state.
> Aug 11 20:46:57 pontiac systemd[1]: amavisd.service failed.
> Aug 11 20:46:57 pontiac systemd[1]: amavisd.service holdoff time over, scheduling restart.
> Aug 11 20:46:57 pontiac systemd[1]: start request repeated too quickly
> for amavisd.service Aug 11 20:46:57 pontiac systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
> Aug 11 20:46:57 pontiac systemd[1]: Unit amavisd.service entered failed state.
> Aug 11 20:46:57 pontiac systemd[1]: amavisd.service failed.
>
> -----Original Message-----
> From: me at chrisfleming.org [mailto:me at chrisfleming.org]
> Sent: Thursday, August 11, 2016 4:42 PM
> To: Joel Vande Berg <jdv at universal5.com>
> Cc: users at lists.kolab.org
> Subject: Re: Email not sending / receiving
>
> On 11/08/16 at 06:27pm, Joel Vande Berg wrote:
> > It looks like amavisd is not accepting connections
> >
> > Aug 11 18:23:26 pontiac postfix/smtp[4781]: connect to
> > 127.0.0.1[127.0.0.1]:10024: Connection refused
>
> Have you tried restarting amavisd:
>
> systemctl restart amavisd
>
>
> You can then check the status using:
>
> systemctl status amavisd
>
>
> also check the maillog again.
>
> Cheers
> Chris
>
>
> > -----Original Message-----
> > From: me at chrisfleming.org [mailto:me at chrisfleming.org]
> > Sent: Monday, August 8, 2016 6:01 AM
> > To: Joel Vande Berg <jdv at universal5.com>
> > Cc: users at lists.kolab.org
> > Subject: Re: Email not sending / receiving
> >
> > On 06/08/16 at 04:51pm, Joel Vande Berg wrote:
> > > I’m looking for some help troubleshooting my new installation. I
> > > have Kolab installed on Centos7 on a Linode VM. I used the install guide at
> > > www.howtoforge.com. Everything worked correctly, the install went very
> > > smooth. I was able to access the webadmin page and set-up users
> > > without a problem. I am also able to access the roundcubemail
> > > login and can login and compose mail.
> > >
> > > My primary issue at this point is that messages are not sending/receiving.
> > > I’ve reviewed my DNS records with GoDaddy and they confirmed they
> > > look ok. I had previously installed citadel and was able to send
> > > and receive messages as well.
> >
> > The go to place, to start troubleshooting is to check
> > /var/log/maillog
> >
> > You should see the connections for incoming mails logged and if it's rejected there should be some kind of indication why.
> >
> > The same applies for outgoing messages.
> >
> > Cheers
> > Chris
> >
> >
> >
More information about the users
mailing list