[BlueOnyx:20224] Re: POP authentication error on one network

[Lewis Gardner]

Michael,

Thanks so much for the complete info. Fortunately it was just a block 
that could be cleared in the GUI. Now I need to figure out why a machine 
on the private network IP was banging away at the email box...

I really appreciate Chris and your prompt replies. I should have figured 
it out but today has been a trial. As soon as I got the email cleared up 
it was on to restoring the results of a CryptoLocker infection on a 
different network. Thank goodness for good old on site backups. Over the 
Internet it would have taken at least a day...


Michael Stauber wrote:
> Hi Lewis,
> 
>> Any ideas on what to do. They are using Roundcube now but the complaints
>> are audible from quite a distance.
> 
> A couple of things come to mind here:
> 
> As Chris said: This could be a PAM_ABL problem. Either the IP is
> blocked, or the PAM_ABL database is corrupted.
> 
> The easiest way to clean that up from the command line is this command
> (as "root"):
> 
> rm /var/lib/pam_abl/*.db
> 
> That will delete the 1-2 PAM_ABL databases that might be there. They
> will get recreated eventually, so you can delete them w/o worries.
> 
> The other possible issue is that one of the Dovecot processes has gotten
> "stuck". This is best solved by restarting Dovecot:
> 
> /sbin/service dovecot restart
> 
> Or on 5209R:
> 
> systemctl restart dovecot
> 
> If it fails to restart cleanly, then this indicates that there are hung
> dovecot processes. This can be fixed by a reboot or - preferably -
> killing off an processes in the process list ("ps axf") related to
> dovecot. Once they're dead, the restart of the Dovecot service should
> work again.
>