Re: replacing dovecot POP3 with qpopper (1st post)

Ken A <[email protected]>
Newsgroups gmane.mail.qpopper
Message-ID <[email protected]>
Obantec Support wrote:
> Hi Ken
> 
> I cannot live with the file .lock problem beta8 is supposed to fix but so
> far Timo has not come up with a reason for beta8 not running on my mail
> server.
> 
> if he can resolve the issue then i will stay with dovecot as its easier to
> have the 1 system set-up. I currently only have around 200 mbox POP3 users.

We'd used qpopper for 9 years, and had very few problems with it. It 
logs some spurious errors now and then that generate questions on this 
list, but the answer is usually 'read the faq'. 200 mbox users should be 
a perfect fit for qpopper.

Ken
Pacific.Net

> Mark
> 
> ----- Original Message ----- 
> From: "Ken A" <[email protected]>
> To: "Subscribers of Qpopper" <[email protected]>
> Sent: Thursday, June 01, 2006 5:11 PM
> Subject: Re: replacing dovecot POP3 with qpopper (1st post)
> 
> 
>> Just went the other way, and won't be back to qpopper unless it gets
>> indexed mboxes. I still like qpopper, but it's just too slow for > 5000
>> users on a single box. Even with all the speed tweaks you can do with
>> qpopper, with lots of users leaving mail on the server, dovecot is much
>> faster and has been very reliable - so far!
>>
>> Ken A
>> Pacific.Net
>>
>> Obantec Support wrote:
>>> Hi
>>>
>>> i am having lots of problems with dovecot as a POP3 server with file
> locking
>>> and the latest beta8 that is supposed to cure this will not run on my
> live
>>> servers but is fine on a test box.
>>>
>>> just built qpopper 4.0.8 on the test box and it seems fine. has anyone
>>> turned off POP3 in dovecot and used qpopper as their POP3 server?
>>>
>>> Mark
>>>
>>
>> -- 
>> No virus found in this incoming message.
>> Checked by AVG Anti-Virus.
>> Version: 7.1.394 / Virus Database: 268.8.0/353 - Release Date: 31/05/2006
>>
>>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.