On Wed, Mar 23, 2005 at 05:27:13PM -0500, Sylvain Robitaille wrote:
> Earlier, I wrote:
>
> > What I'm wondering is, is this an appropriate place to submit that
> > patch? Are the Qpopper developpers known to use this mailing list?
> > Are other people interested in my patch?
>
>
> Joe Maimon replied:
>
> > Yes
>
...
> For the first patch, pop_dropcopy.c and pop_updt.c are changed as
> follows:
>
> In pop_dropcopy.c, link the mail spool to the temp spool, acquire a
> lock on the mail spool, unlink and recreate the mail spool, and release
> the lock. If the link fails, (either because the temp spool is on a
> different file system than the mail spool, or because the temp spool
> already exists), fall back to the original code that copies the mail
> spool into the temp spool.
>
> In pop_updt.c, if no updates are pending (no messages were read,
> requiring Status: or X-UIDL: header updates, and no no messages were
> marked to be deleted), after the lock has been acquired on the mail
> spool, and any new messages have been appended to the temp spool,
> rename the temp spool to mail spool (overwriting the existing mail
> spool whose contents have already been copied), rather than copying
> the contents back.
Isn't this almost precisely what the "-F" flag or "fast-update"
config file option does?? See the Qpopper 4.0 Manual PDF, p.33
> The second patch permits us to use the system lastlog file to monitor
> which accounts are used regularly, or more to the point, which ones
> haven't been used in any way (interactively, POP, IMAP, FTP, etc.; I've
> made the same mod to IMAP and FTP servers) in some extended period of
> time. I added a function to pop_pass.c to update the lastlog file, then
> added a call to that after the user authentication succeeds.
This sounds like a nice idea.
-- Clifton
--
Clifton Royston -- [EMAIL PROTECTED]
Tiki Technologies Lead Programmer/Software Architect
"I'm gonna tell my son to grow up pretty as the grass is green
And whip-smart as the English Channel's wide..."
-- 'Whip-Smart', Liz Phair