similar to: Confused about what MTA, MDA, IMAP/POP server to use

Hello, just to soothe my paranoia from many years of qpopper usage, which enforces solitary access to a POP mailbox. Only one login per user is possible at the same time and if a session terminates w/o qpopper being properly notified it will remain locked for some time, 30 minutes by default. With dovecot (0.99.10.4) one can login multiple times (using POP, with IMAP of course this comes as

I've been doing research on switching our current e-mail server (qpopper, sendmail) to imap. The decision on which server to use is essentially down to Cyrus and Dovecot -- I like Cyrus' approach to a lot of things, but the "blackbox" nature of it makes some niceties like using spamassassin and procmail difficult, or at least counterintuitive. Dovecot seems to play nicer with

Hello, Trying to set in dovecot.conf more than one auth section found that imap and pop3 auth process use bose of them. Loooks like thay do in round-robin way or maybe another way. Example of config: auth default { mechanisms = plain passdb sql { args =

Hello, I'm preparing to convert from qpopper + UW-IMAP to dovecot. So far testing has gone very well. One problem we haven't figured out is that long-running POP sessions keep the mailbox locked, so that the MDA times out while trying to deliver. We're using "maildrop" as our MDA if that matters. We don't see this issue for dovecot IMAP sessions. During long-running

OK, I am brand new to this so please bear with me. I have an FreeBSD 6.1 STABLE system. Postfix is installed with qpopper. The mailboxes are standard mbox format. I just installed Dovecot. At some point I want to update to a mdir format, etc., but quite frankly I do not know how to go about that. In any case, I shut down qpopper and started Dovecot. I modified the Dovecot.conf file SSL settings

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

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?

Hi, I found that dovecot have many nice features. Now I write because I'm tring to setup the dovecot server, I would substitute a qpopper daemon (patched for mysql authentication) The problem I find is to set up the pop-before-smtp using sql (mysq) as written in http://wiki.dovecot.org/moin.cgi/PopBSMTPAndDovecot (Waiting for post_login ;-) I would use the script popbsmtp.sh and not a perl

Hello, The users here have been migrated to the new mail system with dovecot 0.99.10.5 (Debian package) on the backends. Storage is maildir, only pop3 access for now. I see very seldom occurrences (compared to the session wide pop lock of qpopper on the old system) like this: --- Jun 16 14:35:52 mb01 pop3(user at gol.com): Timeout while waiting for release of exclusive fcntl() lock for index

Hello, we are currently using sendmail, procmail, uwimap and qpopper. We are planing to replace uwimap and qpopper with dovecot. Which seems to be a very good idea :-) But: Sendmail and Procmail will not be replaced. Now I've realized that deliver rewrites existing "From <....> ..." header lines to ">From <...> ..." and adds it's own "From

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 all, I'm at the stage of planning our new mail system and am evaluating dovecot for it. For large mailstore setups, it makes sense to split maildirs across many directories. I see that setting default_mail_env to something like maildir:/var/imap/domain/%1d/%d/%1u/user/%u/ would create almost identical on-disk layout as multidomain cyrus setup. Now, as dovecot does not have its own

Does anyone have a patch or information resource on implementing POP before SMTP with sendmail and DoveCot? I implemented it using a qpopper patch before we swiched to DoveCot for Maildirs. We have been using DoveCot for almost a year now and love it better than any other IMAP or POP3 server. Thanks for the info, Doug Eubanks SIMflex Internet Support support at simflex.com SIMflex Telephone

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

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

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

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

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