Puzzling pop lock files
Lisa Casey <lisa <at> jellico.net>
2006-03-01 14:59:39 GMT
I had a mail server crash on Monday of this week so I hurriedly set up
another FreeBSD box I have to accept email in place of the crashed machine.
The new box already had Sendmail installed but didn't have a POP3 server so
I installed Qpopper 4.0.5 from the ports.
I've been using Qpopper for several years now on various machines, I have
another mail server now with Qpopper 4.0.4 currently on it.
In the past, I've had occasional problems with pop lock files that, for one
reason or another, didn't want to go away. And of course, when a customer
attempts to pop mail while a pop lock is present for his mailbox the
customer gets a "password error" on his end and on our end I get logged the
message "Is another session active?". This is just the way it's always
worked and it's my understanding that this is how it's supposed to work
That's why I'm perplexed at what I see on this new box I set up on Monday.
Pop locks are staying around, but they are NOT preventing anyone from being
able to pop their mail. There are some pop locks on this machine now from
Monday, yet these customers are happily popping their mail today.
Why is this? I must of overlooked something perhaps in my haste to get this
setup, but it's been awhile since I've set up a new Qpopper and I don't know
what I've overlooked.