It would be nice when this is implemented to include an event point so a plugin can know when it has changed, updated, deleted, disabled or even failed to grab. Some sites might want to trigger an notification, send and email, send something using snpp, etc.

Thanks
Robert

Fixed for 5.6.1-dev

Hi,

I vehemently disagree with this issue, I think that this is an irresponsible implementation. I've before been critical of WGM implementing changes without thinking them through. This is one of those cases.

In the situation of a server outage, you now have a helpdesk that DOES NOT RECOVER from an outage of another system. If our mail server is down for even 5 minutes, the entire helpdesk will disable itself. Unless a tech is present immediately after the outage, the system is dead. Unless you're a tech company and everybody is a sysadmin, this can easily mean major downtime for a company.

I think that it's irresponsible, and I would suggest that this feature be ROLLED BACK IMMEDIATELY, or implemented in a different way.

I think that the only responsible way to implement this feature is to first start throttling, and then if throttling fails for e.g. 7 days, then you can disable the account. Thus, after 5 consecutive failures, you can roll back to only polling every 10 minutes, and then if that fails for e.g. 3 hours, then you roll back to polling every hour. If that fails for 7 days, then you can disable the account.

You can also not do anything, but simply EMAIL the sysadmin every 5 failures. That means that his inbox will be barraged with notifications of a failed POP3 account, and he will do something about. The social aspect of simply over-notifying is all it takes to get someone to do something about it.

I'm really stunned that you've implemented this feature without considering its ability to cripple a helpdesk during normal operation. A server outage of 5 minutes is to be fully expected in a normal operating environment. To install a feature that WILL, NOT CAN cripple the helpdesk, thus requiring tech intervention to bring the helpdesk back online, is absurd.

Per

Hi,

Per again here. I don't understand, the forum listing talked about disabling the POP3 account automatically, so I went here to comment on that. Yet clearly, this ticket doesn't mention disabling the POP3 account.

What is the status of this? As a business continuity person, it's very upsetting when changes are implemented that can automatically take a system offline. My life revolves around removing threats such as this implementation, so that systems can be assured to STAY ALIVE no matter what happens. I'm extremely keen on finding out of this change is actually being implemented.

Per

Hi,

I finally found it, the description above says "auto-disable pop3 account when over a certain threshold of failures". Unless this "threshold" can be set to 999,999,999,999, please undo this feature. This is a serious business continuity issue, and I think it's irresponsible that this has been implemented. It's an auto-destruct.

Per