Email not sending / receiving

[me at chrisfleming.org]

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
> > 
> > 
> >