similar to: quetion about duplicate messages

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

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, 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, i never used dovecot so far, but i heard a couple good things about it .. for one the debian maintainer of the exim package recommended it :-) so i want to change our mailserver (currently using ipop3 and uw-imap) to dovecot ... now my boss seems to favour cyrus. i could use some good arguments for dovecot, also your experiences with it and with other mailservers so i can make a

At what level does Dovecot log to syslog? UW-IMAP uses local6.debug to log to syslog, but it doesn't seem that dovecot does the same.. (the file I defined for UW-IMAP's output hasn't received anything since I moved over to Dovecot? Also, has anyone managed to get LogWatch and Dovecot to play nicely together? I noticed that LogWatch no longer gives any statistics on the imap

Hmm, this is peculiar! This mailbox has been unchanged on my test server since September. I've been using it to test each new version of Dovecot just after I've compiled it. When beta1 was released, I opened this mbox with no problems. However, when I upgraded to beta2, I got "file size unexpectedly shrinked in mbox file /export/mail/a/24/vis99003/INBOX (16895967 vs 16899267)".

We have for many years been a UW-IMAP site, with users having their own traditional, private, mbox-format INBOX and folders: almost (but not quite) no complications of shared or simultaneous access. We have just completed a transparent transition to dovecot (official 1.0.0 release). But we have one residual issue affecting one important user account. UW-IMAP specifically only allows single

We recently switch from up-imapd to dovecot But many users are reporting that they cannot access certain mail folders. The log file has: imap(dws): Sep 14 00:06:19 Error: File isn't in mbox format: /home/research/dws/mail/TaskDL The files in the logs are "MBX mail folders", not "ASCII English text" as are the folders that can be read under Outlook. Can anyone tell me

I've got a problem with subscriptions in 1.0-stable when migrating from UW-IMAP. I've modified the SUBSCRIPTION_FILE_NAME entries as suggested in the Wiki http://wiki.dovecot.org/Migration and included the "~/mail/" etc. hidden namespaces. The .mailboxlist files contain entries like "~/mail/somefolder" and the clients have "~/mail/" set as a prefix. In

I've got several users testing Dovecot IMAP at the moment, but some of them are also accessing their mail via UW-IMAP at other times. (I've warned them about accessing the same folder simultaneously via UW-IMAP and Dovecot!) In addition, we have special folders "AutoSpam" and "Trash" that pruned using Washington's "mailutil" automatically every so

I've been struggling with an odd bug in the latest 1.0-stable (20050427) release. Sometimes Dovecot seems to forget that a message has been read or deleted and marks it unread (or not deleted). As far as I've been able to determine, it seems to happen when 1) There have been several recent deliveries 2) Possibly some of those deliveries are of multiple messages 3) Possibly they are read

I've been having problems with Pine 4.62 talking to Dovecot 1.0 stable. It's fine when the folder collection path is empty, but if I have "~/mail/" or "mail/" it gives access errors (I'm using the "~/mail/", "mail/" etc. hidden namespaces for backwards compatability). It seems to me that Dovecot is not replying correctly to a "LIST"

It never hurts to ask...... I am bringing up DC on my production mailserver (which runs UWIMAP for production IMAP service) to learn and test it, much as I did when I introduced SSL protected IMAP, using an unpublicized non-standard port. The folder and mailbox location and format will remain the same. Questions: 1) Will DC be building indices for everything or just for the userid that I use

Hello, I have a setup where each user has different mailbox formats (some use only /var/spool/mail/user) mailbox format, some is stored in mbx format ~/INBOX or ~/mbox and some is stored in maildir format in ~/Mail/ I currently use UW-IMAP to read /var/spool/mail/... and the mbx format mailboxes in ~/INBOX and mutt to read ~/Mail/... (the maildirs in ~/Mail/ are created by procmail rules) Does

Hi All, I just installed Dovecot-Imap because uw-imap is awful... and Dovecot seems like a good Imap Server. Anyway I am using a Debian Server and apt-get install dovecot Seems to be working... I can telnet to port 143 and run /var/run/dovecot/login However SquirrelMail Config test cannot detect if, If anyone knows a guide to make Dovecot work with SquirrelMail please let me know... THis is

We converted from uw-imapd to dovecot but are still having problems with MBX mail folders. The user can't access this "MBX mail folder": [root at volt Resume's]# file "Sys Admin" Sys Admin: MBX mail folder [root at volt Resume's]# mailutil copy ./"Sys Admin" '#driver.unix/new' Can't open mailbox ./Sys Admin: no such mailbox [root at volt

Hi, I just switched (or tried to) from UW-IMAP to dovecot. When I try to login through the telnet client I get: 1 NO Authentication failed and in the log I get: imap-login: Authenticate PLAIN failed: Unsupported authentication mechanism If I try to login through the IMAP client (Thunderbird), in the log I get the slightly different: imap-login: Authenticate login failed: Unsupported

Hi, I've been lurking on the list since Spring, planning to replace UW-IMAP with dovecot 1.0 sometime this summer. The recent thread on "1.0" has not given me a good feeling about seeing it before summer's end. So I wonder if I should use dovecot-1.0-test-xx code or dovecot-stable-[date] code (which seems to change every day, how stable is that???). This is confusing,

Does "dovecot" have anything similar to the UW IMAP "mailadm" group operation? From near the end of: http://www.washington.edu/imap/documentation/RELNOTES.html 'Support for SASL authentication identity vs. authorization identity in the IMAP and POP3 servers. If the user indicated by the authentication identity is in the "mailadm" group, he may

I am getting this failure when trying to compile dovecot on Sparc Solaris 8: make[4]: Entering directory `/home/systems/looneytr/dovecot-1.1.rc12/src/lib' source='str-find.c' object='str-find.o' libtool=no \ DEPDIR=.deps depmode=gcc /bin/bash ../../depcomp \ gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/openssl/include -g -O2 -Wall -W -Wmissing-prototypes