similar to: Replacing Qpopper with Dovecot

package logcheck-database tags 125794 pending tags 191637 pending thanks I've been running the latest version of qpopper from unstable for a few days and I've added the following rules to CVS: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ in.qpopper\[[0-9]+\]: connect from [._[:alnum:]-]+$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ in.qpopper\[[0-9]+\]: \(v[.[:digit:]]+\) POP login by user

Hi, I did some performance testing with dovecot and qpopper, if anyone is interested.. Hardware: Dual Xeon 2.8 with HT enabled (dmesg sees 4 cpu-s), 1 GB RAM, SCSI RAID 1 with 2x Maxtor Atlas 10K V disks. Software: CentOS 4.3, Qpopper 4.08 in standalone mode vs Dovecot 1.0-0_19.rc6, ext3 filesystem Mailbox format Mbox, tested Pop3 with PAM authentication My setup had 15 test users with 15

We have an older mail server using qpopper and the mbox format which we need to update to dovecot and maildir format. I have read through the docs on migrating from mbox to maildir, as well as a few nuggets on how to migrate from qpopper to dovecot, and I was wondering if I could get some suggestions on best practices for this specific migration. Would the built in dovecot conversion plugin be a

Heya, We are in the process of migrating from qpopper to dovecot as POP3 server (and IMAP as well) and we hit the UIDL issue with dovecot. Qpopper uses its own algorithm to create UIDL values and if you set it up to write them down in the mbox file as X-UIDL, then dovecot can use them (pop_uidl_reuse = yes). But if you don't use that feature from qpopper, than X-UIDLs are missing and there

hi all, I am hoping to convert a 350K user qpopper installation using mbox to dovecot and maildir (pop3 only). many of the users "leave mail on server", and qpopper's UIDL format isn't (yet) supported by dovecot. since the UIDLs have been written by qpoppper to the existing mbox files (and will be preserved when the mboxes are converted to maildir) it would be possible to do

Hi All, Our test users re-download the mail they've left on the server when they switch from Qpopper to Dovecot. Qpopper includes the X-UIDL header - X-UIDL: X8V"!E)<"!58?"!"9C"! - on read messages. Any suggestions are appreciated. I've included my dovecot configuration. Thank you, Tristan --- Tristan Tristan Goguen CEO, ILAP? T: 416-250-5600 ext. 205 F:

I''ve got qualcomm''s qpopper2.2, and am not sure if its vulnerable. The advisory mentions pop and imap servers, but only says: version of IMAP (Section B). If your POP server is based on the University of Washington IMAP server code, you should also upgrade to the latest version of IMAP. Until you can take one of these actions, I installed the new imapd about 3

I'm hoping to migrate to dovecot from qpopper, with the eventual goal of enabling IMAP. However, my qpopper installation is fairly specialized, so I thought I'd ask here to see if anyone could get me headed down the best path. Here's the situation. I'm running FreeBSD and have a virtual domains setup with an extremely hacked LDA to do delivery to mailboxes within hashed

Hello, As this is my first post to the list, first and foremost I'd like to thank Timo for writing great software; we've successfully moved to Dovecot for over 10,000 users from UW-IMAP and get great performance. On our overloaded staff POP3/IMAP server, we are looking at replacing qpopper+uw-imapd with dovecot, as an interim before moving them to the main Unix mailstore. The system is

Hi List, what do you think is the best way to migrate (to a new maschine) round about 30000 mboxes (Qpopper) with an amount of 43Gigs data, to maildir format (Dovecot). I think there are two ways: 1. - stop services (smtp and pop3) on the old maschine - copy the mboxes to the new maschine - run a conversion script (for excample: "Perfect_maildir" http://perfectmaildir.home-dn.net/)

Hello, does anybody know how to make XUIDLs compatible to qpopper? I'm migrating from qpopper and one of my test-migration-accounts leaves the mail on the server. As soon as I switch to dovecot it downloads the mails again and again.. bye! Dominik

I am testing migration from Qpopper 4.0.5 and have come across a problem. Dovecot dies while processing UIDL command when accessing malformed Qpopper's mbox which has duplicated "From " separator. Qpopper occasionally makes such header while rewriting mbox. In the attached file, unnecessary "From " at line 3. ---------------- * Dovecot 1.0.0 on Debian 4.0(x86) * ext3

Recieved this email on BugTraq today. Take the necessary precautions. ---------- Forwarded message ---------- Date: Tue, 30 Nov 1999 01:53:11 +0100 From: Mixter <mixter@NEWYORKOFFICE.COM> To: BUGTRAQ@SECURITYFOCUS.COM Subject: serious Qpopper 3.0 vulnerability Greetings, There is a remote buffer overflow in the qpop 3.0 server code that can lead to remote root compromise. Exploit

Hi, I am planning a migration from Qpopper 4.0.5 to Dovecot.. I need to use mbox format (because Openwebmail does not have native Maildir support yet) and pop3. The system will have about 1500 users, once migrating is complete. To avoid users downloading their mailboxes all over again, i need to set "pop3_reuse_xuidl = yes".. But that option works since Dovecot 1.0alpha1. RHEL

Dear list, I am planing to set up dovecot-imapd on my production-mail server which currently only runs pop3 via qpopper on debian-sarge. It would be best, if I could only use imapd and use the existing pop3- server (qpopper) as it is. Is this possible? Can the user both use pop3 (qpopper) and imapd (dovecot) in parallel then? Where does dovecot-imapd store its mails? Does it store its mail in

Hello, I'm attempting to move form qpopper 4.1 to Dovecot 2.2.5 on Linux. When a user checks POP mail qpopper seems to make a .username.pop temporary file in the same /var/mail directory as the mbox INBOX file. Watching what dovecot does I don't see this happening. Is this .pop file a lock file or just a temporary file? If its a temp file does dovecot do the same thing elsewhere?

Qpopper has a compile time option '--enable-auto-delete Automatically delete downloaded msgs' Is there anything similar in dovecot. I'm trying to migrate from qpopper to dovecot any help is appreciated.

Hi, We just migrated our IMAP service to Dovecot and it performs very well. We also want to migrate our POP3 service (qpopper) to Dovecot. The problem is that Dovecot and Qpopper differently act on expired passwords: Qpopper: -ERR "user": password expired. Dovecot: -ERR Authentication failed. Are there any way to tell Dovecot to report about expired passwords? We have about 30000

I'd like to revisit and old post if I may, will/does Dovecot support the old qpopper "Bulletin" ability? Basically I need a simple way of posting bulletins to all domain users. Qpopper maintained a bulletin db for each user and sent them the next bulletin in sequence. Thanks in advance Kevin

Hello, [Old problem; if it was fixed, I cannot see it (checked Changelog, wiki, source, as much as my grepping counts). Any help appreciated.] I have been begging since 2003 to be able to trash qpopper and use dovecot, but statistical logging of dovecot has been pretty much absent. Qpopper does this: Aug 19 11:18:02 mail in.qpopper[8099]: Stats: userid 0 0 12 51773 user.example.com