Good point and I wasn't sure why ipop3d wasn't giving me the same error. We probably will look into setting up some type of mail copy, but I believe we will attempt to an imap implementation first.
Thanks for the feedback. Jonathan Paul Cowherd Linux and Java Administrator Genscape, Inc. Email: [EMAIL PROTECTED] Office: (502) 583-3730 Mobile: (502) 314-0444 -----Original Message----- From: Clifton Royston [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 4:23 PM To: Jonathan Cowherd Cc: Subscribers of Qpopper Subject: Re: Multiple pop requests on the same account On Thu, Dec 12, 2002 at 03:24:06PM -0500, Jonathan Cowherd wrote: > We have serveral e-mail with things in them that we'd like to pop off > at the same time and process the different e-mails concurrently. When > two processes are popping at the same time, I get a busy/lock error > message. I assumed qpopper could do this since other pop servers > don't have trouble with it. Well, ipop3d at least won't give you a locking error, but manages this by simply killing the previously logged in POP session every time a new one connects. Since in principle the two POP sessions could be issuing incompatible updates to the spool, but neither is likely accept unexpected changes happening out from under it, it's hard to know what the "right thing" is. If this is all in support of some kind of script-driven automatic processing of certain specific accounts, it might be easier to .forward them or procmail them to clone all incoming mail to two different mailboxes and then process those mailboxes via independent POP sessions. -- Clifton -- Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED] "If you ride fast enough, the Specialist can't catch you." "What's the Specialist?" Samantha says. "The Specialist wears a hat," says the babysitter. "The hat makes noises." She doesn't say anything else. Kelly Link, _The Specialist's Hat_
