similar to: qpopper to dovecot migration

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

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

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 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

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

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

Hello All, I am new to Dovecot and the Dovecot mailing list. I am trying to migrate an existing Exim + qpopper - mbox (pop3 only) installation over to Exim + Dovecot using mdir (pop3 and imap) And am running into problems with preserving the XUIDL headers. I am running Dovecot 2.0.14 I have used the mb2md.pl script : http://dovecot.org/tools/mb2md.pl from this page

hi all, this is needed to make the pop3_reuse_xuidl option work in 1.0alpha4. I am using maildir and I noticed that for each message which doesn't have an indexed X-UIDL header, the entire message is read from disk. as this is reading only headers, it is probably reasonable to stop reading at the end of the headers. it would also be neat if dovecot could be configured to only try reading

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

I currently have a Centos server with Sendmail and Qpopper supporting about 50 mail users. I am planning to replace Qpopper with Dovecot to allow some users to have IMAP access to their mail (others will still use POP3.) Is there anything special to be aware of in setting up this migration? Thanks for your comments. Gerald

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

Heya, We are expiriencing issues with dovecot 2.1.1 on Linux with weird filenames in home directory of username. We are using mbox IMAP folders, with no special changes (mail_location = mbox:~/:INBOX=%h/.mailbox). Mar 6 13:37:17 machine dovecot: imap(username): Panic: file mail-storage.c: line 628 (mailbox_alloc): assertion failed: (uni_utf8_str_is_valid(vname)) Mar 6 13:37:17 machine dovecot:

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/)

Hi, Considering the scenario, where you have some old account with a different POP3 UIDL format and you migrate them to dovecot. So these old UIDLs would be saved to dovecot-uidlist. At some later time you want to introduce a virtual POP3 INBOX like described on: http://wiki.dovecot.org/Plugins/Virtual So you decide to make the new UIDL format "%f" - to make them unique across

Heya, I am expiriencing compiling issues on Solaris 8 and Solaris 10 boxes with dovecot 1.2.6. On Solaris 8 the compiler is gcc 64bit 3.2.2, on Solaris 10 gcc 3.4.3. On both systems the compiling fails with: /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2

Hi, We're upgrading a cluster of servers from v1.0.15 to v1.1.x or v1.2.x. It appears that the UIDL generation mechanism has changed, and thus we'll be getting POP3 dups with users that leave mail on server (which is a nasty practice, I know). From checking the sources, and performing a number of controlled tests in various scenarios, here is the outcome: upgrade from 1.0.15 to

Hi there, I've just been experimenting with the latest courier-dovecot-migrate.pl script and I notice that it favours keeping pop3 UIDL ordering rather than IMAP UID preservation. There is this comment (line 312): # POP3 clients may want to get POP3 UIDLs in the same order always. # Preserve the order even if it causes IMAP UIDs to change. Does anyone have details as to which

Heya, we are seeing some strange issues with IMAP ID command using latest Roundcube builds on dovecot 2.2.10 responding "Input buffer full, aborting". Roundcube webmail connects to IMAP server and issues ID command first with some long arguments to ID command, however shorter than 1024 octets, which are specified in RFC2971 for ID IMAP extension. The situation is easily