I'm dealing with the next order of magnitude of users, many checking every minute. We're logging 150-200 pop sessions/minute. However, this frequent checking (especially with LMOS) is more of an annoyance to ME than affecting anyone.
I've considered modifying the qpopper source to keep the connection open for x minutes after the customer closes the session. I'd also change the pop lock error message to explain it (instead of the POP lock busy). However, any changes to customers will just get them calling in, regardless of how well I explain things in the error message. My poor tech support reps will be tied up: 1) explaining why they can't check mail "like the always have" 2) justifying our policy to the people who understand it 3) spend x minutes waiting for pop sessions to time out after the customer attempts to check mail - SteveP At 03:24 PM 4/16/2002 -0400, you wrote: >Hello all, > >I was just wondering if anyone knew of a commonly used program used in >conjunction with Qpopper, or perhaps even a widely used patch, that would >enable me to limit the frequency with which users check their >mail. Currently there is no such limit, and believe it or not many have >their Eudora setup to autocheck every minute. This is unacceptable with >almost 2000 users per machine. Especially considering that they regularly >keep messages on server as well for a period of at least 5 days. I know >that I've seen other institutions implement such restrictions, and you are >sent an error message via standard POP protocol it appears, which Eudora >displays in the status telling you you are checking mail too often. THis >is more than sufficient. Any help or recommendations would be GREATLY >appreciated. Thanks in advance. > >PS - The client getting the descriptive error message is by FAR the most >important thing, as to avoid unnecessary calls to our helpdesk people. > >--- >Tim Meader >ACS Government Services, Inc. - (301) 286-8013 >[EMAIL PROTECTED]
