Email not sending / receiving

Discussion:

Joel Vande Berg

2016-08-06 16:51:21 UTC

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<http://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.

Thanks,

Joel

m***@chrisfleming.org

2016-08-08 10:00:49 UTC

Permalink

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

Joel Vande Berg

2016-08-11 18:27:01 UTC

Permalink

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

-----Original Message-----
From: ***@chrisfleming.org [mailto:***@chrisfleming.org]
Sent: Monday, August 8, 2016 6:01 AM
To: Joel Vande Berg <***@universal5.com>
Cc: ***@lists.kolab.org
Subject: Re: Email not sending / receiving

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

m***@chrisfleming.org

2016-08-11 20:42:12 UTC

Permalink

Post by Joel Vande Berg
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

Post by Joel Vande Berg
-----Original Message-----
Sent: Monday, August 8, 2016 6:01 AM
Subject: Re: Email not sending / receiving

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

Joel Vande Berg

2016-08-11 20:51:43 UTC

Permalink

Chris,

Thanks for the continued help with this.

Joel

The restart failed -

[***@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.
[***@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: ***@chrisfleming.org [mailto:***@chrisfleming.org]
Sent: Thursday, August 11, 2016 4:42 PM
To: Joel Vande Berg <***@universal5.com>
Cc: ***@lists.kolab.org
Subject: Re: Email not sending / receiving

Post by Joel Vande Berg
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

Post by Joel Vande Berg
-----Original Message-----
Sent: Monday, August 8, 2016 6:01 AM
Subject: Re: Email not sending / receiving

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

m***@chrisfleming.org

2016-08-11 21:10:13 UTC

Permalink

Post by Joel Vande Berg
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

Post by Joel Vande Berg
The restart failed -
Job for amavisd.service failed because the control process exited with error code. See "systemctl status amavisd.service" and "journalctl -xe" for details.
● 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-----
Sent: Thursday, August 11, 2016 4:42 PM
Subject: Re: Email not sending / receiving

Post by Joel Vande Berg
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

systemctl restart amavisd
systemctl status amavisd
also check the maillog again.
Cheers
Chris

Post by Joel Vande Berg
-----Original Message-----
Sent: Monday, August 8, 2016 6:01 AM
Subject: Re: Email not sending / receiving

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

Joel Vande Berg

2016-08-11 23:27:46 UTC

Permalink

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: ***@chrisfleming.org [mailto:***@chrisfleming.org]
Sent: Thursday, August 11, 2016 5:10 PM
To: Joel Vande Berg <***@universal5.com>
Cc: ***@lists.kolab.org
Subject: Re: Email not sending / receiving

Post by Joel Vande Berg
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

Post by Joel Vande Berg
The restart failed -
failed because the control process exited with error code. See "systemctl status amavisd.service" and "journalctl -xe" for details.
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-----
Sent: Thursday, August 11, 2016 4:42 PM
Subject: Re: Email not sending / receiving

Post by Joel Vande Berg
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

systemctl restart amavisd
systemctl status amavisd
also check the maillog again.
Cheers
Chris

Post by Joel Vande Berg
-----Original Message-----
Sent: Monday, August 8, 2016 6:01 AM
Subject: Re: Email not sending / receiving

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

m***@chrisfleming.org

2016-08-11 23:32:50 UTC

Permalink

Post by Joel Vande Berg
The output is quite large. I'll try some excerpts, but let me know if you need the whole thing.

Sorry - I should have been more specific - you only need to check the
amavisd part.

Post by Joel Vande Berg
-- 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!

So I think that setting $myhostname in amavisd.conf to a fully qualified
domain name should resolve this.

Cheers
Chris

Post by Joel Vande Berg
-----Original Message-----
Sent: Thursday, August 11, 2016 5:10 PM
Subject: Re: Email not sending / receiving

Post by Joel Vande Berg
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

Post by Joel Vande Berg
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

systemctl restart amavisd
systemctl status amavisd
also check the maillog again.
Cheers
Chris

Post by Joel Vande Berg
-----Original Message-----
Sent: Monday, August 8, 2016 6:01 AM
Subject: Re: Email not sending / receiving

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

Joel Vande Berg

2016-08-12 01:34:05 UTC

Permalink

Made some progress, but still not starting. Changed $myhostname

# $myhostname = 'pontiac.centralsw.com'; # must be a fully-qualified domain name!

systemctl restart amavisd fails. Updated journalctl -xe returns

Aug 12 01:31:39 pontiac amavis[4894]: logging initialized, log level 9, syslog: amavis.mail
Aug 12 01:31:39 pontiac amavisd[4894]: The value of variable $myhostname is "pontiac", but should have been
Aug 12 01:31:39 pontiac amavisd[4894]: a fully qualified domain name; perhaps uname(3) did not provide such.
Aug 12 01:31:39 pontiac amavisd[4894]: You must explicitly assign a FQDN of this host to variable $myhostname
Aug 12 01:31:39 pontiac amavisd[4894]: in amavisd.conf, or fix what uname(3) provides as a host's network name!
Aug 12 01:31:39 pontiac systemd[1]: amavisd.service: control process exited, code=exited status=255
Aug 12 01:31:39 pontiac systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
-- Subject: Unit amavisd.service has failed

-----Original Message-----
From: ***@chrisfleming.org [mailto:***@chrisfleming.org]
Sent: Thursday, August 11, 2016 7:33 PM
To: Joel Vande Berg <***@universal5.com>
Cc: ***@lists.kolab.org
Subject: Re: Email not sending / receiving

Post by Joel Vande Berg
The output is quite large. I'll try some excerpts, but let me know if you need the whole thing.

Sorry - I should have been more specific - you only need to check the amavisd part.

Post by Joel Vande Berg
-- 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!

So I think that setting $myhostname in amavisd.conf to a fully qualified domain name should resolve this.

Cheers
Chris

Post by Joel Vande Berg
-----Original Message-----
Sent: Thursday, August 11, 2016 5:10 PM
Subject: Re: Email not sending / receiving

Post by Joel Vande Berg
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

Post by Joel Vande Berg
The restart failed -
failed because the control process exited with error code. See "systemctl status amavisd.service" and "journalctl -xe" for details.
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-----
Sent: Thursday, August 11, 2016 4:42 PM
Subject: Re: Email not sending / receiving

Post by Joel Vande Berg
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

systemctl restart amavisd
systemctl status amavisd
also check the maillog again.
Cheers
Chris

Post by Joel Vande Berg
-----Original Message-----
Sent: Monday, August 8, 2016 6:01 AM
Subject: Re: Email not sending / receiving

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

Andy Kopciuch

2016-08-12 15:25:16 UTC

Permalink

Post by Joel Vande Berg
# $myhostname = 'pontiac.centralsw.com'; # must be a fully-qualified domain name!

Your config line here will be ignored because it is a comment. You have a #
at the beginning.

$myhostname = 'pontiac.centralsw.com';

or

$myhostname = `hostname --fqdn`;

Should do the trick.

Andy

Joel Vande Berg

2016-08-12 16:00:18 UTC

Permalink

Apparently. I'm an idiot. :)

Looks like that did the trick. Emails are now going in and out.

Thanks to everyone that helped with this!

-----Original Message-----
From: Andy Kopciuch [mailto:***@bddf.ca]
Sent: Friday, August 12, 2016 11:25 AM
To: ***@lists.kolab.org; Joel Vande Berg <***@universal5.com>
Cc: ***@chrisfleming.org
Subject: Re: Email not sending / receiving

Post by Joel Vande Berg
# $myhostname = 'pontiac.centralsw.com'; # must be a fully-qualified domain name!

Your config line here will be ignored because it is a comment. You have a #
at the beginning.

$myhostname = 'pontiac.centralsw.com';

or

$myhostname = `hostname --fqdn`;

Should do the trick.

Andy

Gregor Adamczyk

2016-08-12 04:01:03 UTC

Permalink

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

Joel Vande Berg

2016-08-12 14:33:44 UTC

Permalink

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.

[***@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.
[***@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:***@netkult.eu]
Sent: Friday, August 12, 2016 12:01 AM
To: ***@lists.kolab.org
Subject: RE: Email not sending / receiving

Am 12.08.2016 um 01:27 schrieb users-***@lists.kolab.org<mailto:users-***@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