Thanks for the suggestion! The following works great on my server:
tcpserver -c 70 0 pop3 /var/qmail/bin/qmail-popup mailsrv.fwi.com \
/bin/checkpassword /usr/contrib/bin/setlock -nx Maildir/.poplock \
/var/qmail/bin/qmail-pop3d Maildir
The second and subsequent concurrent POP3
I'm looking to put a locking scheme in the current default pop3
process for qmail (checkpassword, qmail-pop3d) so that when a user
checks their mail, if they attempt to check it again while the previous
instance is still running, they will be immediately dropped. This is
to avoid a potential
On Tue, Oct 05, 1999 at 01:40:07PM -0600, [EMAIL PROTECTED] wrote:
Has anyone implemented such a thing already? If not, any ideas
on how it might be done? As I understand it, locking the maildir
in qmail-pop3d is probably the best solution to this, as it gets
called immediately after
