similar to: Qpopper 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:

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

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, I have read in lots of places about how I should use pop3_reuse_xuidl = yes to prevent pop3 users having to re-download mail (and duplicate their e-mail) after a migration. This fails with the message: pop3_uidl_format setting is missing from config file Which setting for pop3_uidl_format should I set to prevent the e-mail being downloaded again?

Hello, I'm try to use the convert plugin, but I cannot seem to get it working properly. Is there any setting that I'm missing. -------- dovecot -n # 1.0.10: dovecot.conf log_path: /var/log/dovecot protocols: imap imaps pop3 pop3s listen(default): 127.0.0.1:143 listen(imap): 127.0.0.1:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995

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.

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

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

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

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

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

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

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

In the process of migrating to Dovecot 1.0beta3, any tips or step-by-step instructions that might relate to Solaris 9. Thanks Bertrand Leboeuf leboeuf at emt.inrs.ca

On 08/04/2020 19.14, Ben Mulvihill wrote: > Thanks for the suggestion. I think my next step will be to investigate > imapsync, or maybe isync, which also looks promising. I've recently migrated a server with imapsync with 150Gb of email and 200+ accounts. I found the trick with this was the run imapsync in several runs: Messages older than 1 year; messages older than 6 months; messages

Hello, I am mounting via NFS a number of volumes and re-sharing these as CIFS. We have been using this arrangement successfully for a number of years. We are replacing the "CIFS>NFS" proxy servers (which are also PDC/BDCs to OpenLDAP) and a weird problem seems to occur. The problem is the quota/disk size appears to be wrong. For example, if I use the unix quota command on the SMB