similar to: simultaneous access to folder

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

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

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

I'm currently using mbox and mbx with UW-IMAP, mbox for space efficiency and mbx for folders with lots of messages for time efficiency without a large space cost. I've avoided maildir because it has a relatively high space cost; mbox has no inter-message cost while maildir wastes on average half a sector plus an inode for each message. What other formats are there, and has anyone come

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've been using UW-IMAPd for neigh on forever (at least since 2001). But, as it's basically stalled, and I'm about to update the hardware that is my mail server, I thought it was time to review existing open-source IMAP servers. Dovecot is the top three in my looking. The other of the top three candidates, because I know of people who've used it, is Cyrus IMAP. So, I should

(Using dovecot 1.0 RC7 on Fedora Core 5) <scene set> Hitherto we have used UW-IMAP on a "farm" of Linux machines mounting NFS from a NetApp. (The UW-IMAP author doesn't like use of NFS, but with careful use of NFS mount arguments ('noac,actimeo=0' etc.) and trying to ensure that all activity for a given user takes place within one machine in the farm, we seem to

I want to migrate my big mail folder hierarchy in preparation for converting from UW-IMAP to Dovecot. I've got a bunch of mbx format folders but some remain mbox. Has anyone done this? Any scripts out there for automating the conversion to all-mbox? I believe the only format conversion available is mailutil (part of UW-IMAP) and it works by opening an IMAP connection to the server and moving

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

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

Hello. I am currently testing dovecot (0.99.10.8, Debian woody from backports), with the maildir storage. I have noticed that when I use the mailutil tool from uw-imap distribution to transfer my IMAP mailboxes from our current server (uw-imap, mbx format) to the dovecot one, the mails arrival time are apparently lost. I can see this in Pine, using the Arrival sort: the mailboxes on the

Yesterday I gave a status report about 10.rc8 in production, which mentioned a problem about "Login process died too early..." Timo suggested a patch for logging error messages. I've applied this. Others suggested increasing "login_max_processes_count". That was already way above our likely maximum, but I've doubled it anyway. Today, I've just repeated the

to dovecot from UW imap. I think I will go all the way to maildir while I'm at it. I was having performance problems with mbox format files and converted to mbx but it's not really yielding a huge performance gain. Deletes and moves are still rather slow at times. my mailboxes are typically 2000 to 5000 messages. I've scanned the mailing lists a bit and picked up some hints on

On the whole we are pleased with our trials of dovecot to replace UW-IMAP. But (ah!) we have hit one particular problem, in which we think dovecot could probably benefit from a resilience improvement. We're running dovecot on Fedora Core 5 (FC5), with passwd map details supplied by NIS. We have found that "nscd" sometimes thinks that a username is invalid, even though it is valid.

Hi, we recently switched from Imap-Uw to Dovecot as a pop3 server. I was wondering why people who have the flag 'Leave messages on server' in their email client (Outlook, Outlook Expres) that they receive duplicates of their stored mail? Is it because Dovecot doesn't know that the messages has already been popped by Imap Uw or is the email client which thinks there are new messages

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)".

Thanks in advance for your patience and assistance. Since a system administrator's work is most successful when nobody knows you've done anything....(ugly that...you get neither raises nor equipment funding as a result), I prefer to learn from other's experiences rather than fail in the same pits. We are considering a switch from UW to Dovecot, since our users persist in using

Background: I'm new to dovecot (although with many years Washington IMAP behind me). We're considering migrating from Washington IMAP to dovecot on the main service here, and have just started trying dovecot, using RC7. Washington, IMAP has the usual(-ish) "/var/spool/mail" shared area for the INBOX (trad. UNIX "From " format); a user's folders default to being

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

(Complete newbie to dovecot. I hope what follows isn't something I've missed in some FAQ somewhere...) On a traditional UNIX filesystem with UW-IMAP several years ago, we encountered major performance problems when "/var/spool/mail/" got big (we would currently be ~20,000 entries). This was due to the inefficiency of the UNIX filesystem when creating and deleting the lockfiles