POP service crash

Discussion forum for Enterprise Edition.
Post Reply
Posts: 1
Joined: Thu Jan 14, 2010 10:49 am

POP service crash

Post by maextro » Thu Jan 14, 2010 11:04 am

Sorry for my bad english.
My version is 4.17, the pop service crashes, when I try to connect to the service, I received the following message: "ERR your Ip address has temporarily de3nied access " and in the file log is reported the following message:"[800] IP address denied access because it has voilated a secutity policy (too many invalid login attempts)". The IP is the IP number of the my firewall.
Help me!


Site Admin
Posts: 9227
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: POP service crash

Post by MailEnable-Ian » Mon Jan 18, 2010 3:53 am


The most likely reason why the IP address has been blocked by the POP service is because you have the option "Abuse detection and prevention" enabled within the "localhost" properties under the "policies" tab. This will temporarily add the IP address of the client if it detects an attempt to abuse the server. (EG: too many invalid password attempts). In order to remove the IP address from memory restart the POP service and try again.

I would suggest disabling the option "Abuse detection and prevention" and restarting the POP service to see if you are then able to connect to the service without it crashing.

Ian Margarone
MailEnable Support

Posts: 132
Joined: Tue Jan 31, 2006 8:42 pm

Re: POP service crash

Post by trusnock » Mon Apr 05, 2010 2:49 pm

Would you consider adding a button somewhere (maybe directly under the "Enable Abuse Detection and Prevention" checkbox?) to clear this without having to restart the POP service? We hate to restart services in the middle of the day to solve a single user's problem. The Abuse Detection and Prevention is a nice feature though, and I'm glad you added it!
-Tom R.

Posts: 92
Joined: Wed Jan 27, 2010 11:16 pm

Re: POP service crash

Post by RNEUSCHUL » Mon Apr 05, 2010 3:45 pm

I'd support Tom's request here: we're seeing lockdown issues for some of our external users who suffer from intermittent comms.

With lots of concurrent users online restarting the POP [or any other] service during the working day is simply not viable. A global facility to unlock all or specified named user accounts and/or IPs without a service restart would be a great boon.


Post Reply