I like the proposal because we use the temp file to know when the user last
accessed their mail.
Butch
At 09:10 PM 6/8/01, you wrote:
> As far as I'm aware, the only purpose for the keep-temp-drop config
>variable (or --enable-keep-temp-drop) which keeps the 0-length POP
>session temp file around, is to have a "cheap" way to check when a user
>last checked their mail via POP. That's what's cited as the motive for
>the option in the Administator's guide (PDF): "Some sites like to
>retain it to determine the last time a user has accessed his or her
>mail."
>
> However, with server mode under qpopper 4.x, while the option is
>still supported, it's no longer directly useful for that: the POP temp
>file doesn't seem to get created or touched unless the spool file has
>been modified since the last POP check. This means that unless the
>user has received new mail, any POP check they do will not be reflected
>in the time, so it's much less useful.
>
> In particular, our support department uses this to help determine if
>customers are able to check their mail and where their problem may lie.
>Scanning through the POP log is fairly resource-intensive and slow,
>especially if you have to go back to rotated log files from preceding
>weeks.
>
> So, I'm considering a fix that if "keep-temp-drop" was set, would
>simply "touch" the (empty) temp file each time a POP connection was
>made, to set the date. That shouldn't be too expensive and should
>solve the problem.
>
> Does anyone else use this option? If so, feedback?
>
> -- Clifton
>
>--
> Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED]
> WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
TSTAR Internet, Inc | Making the Net Work
Marble Falls, TX | Serving Blanco, Burnet,
830-693-6967 | Llano, and Mason Counties
