similar to: Architectural questions

Is dovecot still considered unreliable when combined with NFS? Is this true for mbox only, or Maildir as well? If dovecot Is still considered unreliable with NFS, how about having a dovecot mode that would chain into procmail for delivery, so that dovecot doesn't (necessarily) have to reinvent that wheel? Thanks!

Hi, I am running dovecot 0.99-14 on a Fedora Core 2 machine. I had a few questions: 1) I wanted to upgrade to the dovecot-1.0 release. However, I am not sure if that's really required. dovecot-0.99-14 has been running very well for me for quite some time. Is there a real advantage to switching to the latest release. The reason I'm asking this is because: i) I don't have too

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

Hello! I run the following environment: UW imapd pine sendmail procmail mbox format I migrated from UW imapd to dovecot. It is pretty faster than UW imapd. To ensure a compatible environment I did the following configuration changes in /etc/dovecot.conf: protocols = imaps default_mail_env = mbox:~:INBOX=/var/mail/%u mail_full_filesystem_access = yes mbox_read_locks = fcntl mbox_write_locks

Folks, I'm running into some issues with pine and dovecot. (dovecot is running mbox for now... plan to switch to maildir soon.) At first I thought it was a funky issue with the way I was using pine to access mailboxes. (I use rsh to invoke imap as pre-authenticated so when I switch to maildirs, I don't have to worry about pine being patched to support it.) But after switching over to

Hello! In this email you can find a configuration primer for a Migration from UW IMAP with pine, Thunderbird and squirrelmail as client. For compatibility the mbox format is used. A description for pine with imap acces without entering any password is also discussed. Please use dovecot 1.0beta1 or later for correct handling with pine. Short overview of Mail folders:

Hi all, I've done a bit of searching and haven't seen anybody else coming across this problem yet: I noticed that Dovecot uses the opposite flags for marking messages as deleted and draft to most other MUAs I've seen or used: With PINE, mutt and uw-imapd at least, messages are marked with X-Status 'D' for Deleted, and 'T' for drafT. Dovecot reverses this behaviour,

I have Dovecot 1.0 in trial use by the IT staff, and have some locking questions Background, the mail server runs procmail, sendmail and NFS exports the user homedir and mailbox to a) a login shell host and b) a mailing list services host. It runs UWIMAP on the usual ports and dovecot on a arbitrary port number. Because of concern with NFS and file access contention. I have the following

There are three applications that have their mitts on files on my mail server, which is running AIXV5.3 and UWIMAP and mbox format. The mail folders and INBOXES are native to that machine, but also are NFS exported to a login server and a mailing list server. All three machines are running the lockd daemon. Everybody wants to lock differently 1) procmail (delivering for sendmail), which

I am at wits end...So far it seems dovecot is light years ahead of UW-IMAP. Glad to have UW-IMAP behind me...well almost. My setup = Sendmail 8.13.4 with Procmail delivery to /var/spool/mail/<userfile> openssl 0.9.8 dovecot 0.99.11 I want to continue to use the standard mbox with all the user's mail stored in /var/spool/mail/<userfile>.

Hi, We are thinking of converting to Dovecot to lighten our I/O load. I have done some performace tests comparing UW-IMAP to Dovecot when using mbox format if anyone is interested. They primarily examine the I/O improvements that can be gained from using Dovecot over UW when staying with mbox format: http://whizzo.uoregon.edu/public/src/mailperf/results.html I had too much cached for this set

hi list, i'm in the process of testing dovecot before a hopeful switchover from uw-imap/qpopper to dovecot, primarily to get off of the uw-imap/mbox combo and moved to Maildir. i think we've worked out the logistics to avoid any service downtime, with only a short window of a few minutes per user for when we convert from mbox to maildir format. however, during testing a few issues have

Hi, Could you say a few words about Dovecot and POP/IMAP to an NFS mounted filesystem? I thought I saw on the dovecot webpage that NFS is "no way" with 0.99 and "maybe" with 1.x. I was looking for the FAQ and couldn't find it. My setup is like so: My mail server is a Solaris 9 system, running sendmail/procmail, and qpopper POP. Mail is stored in mbox format. The

I'm using Dovecot 1.0.0 (mbox) with Postfix 2.4 on my FreeBSD box, as a pop3-only server (imap is disabled). All account mailboxes are accessed using Outlook clients. I've noticed that, whenever I'm retrieving mail with pop3, a "DON'T DELETE THIS MESSAGE" is created in mbox. Although these messages are never sent to client MUAs, I found them very annoying. BTW I

Hello, I just installed dovecot (1.0.10) to replace UW-IMAP. So far almost everything works. But I need shared folders (mbox format). I hope I've set up everything but when a user subscribes to one of the shared folders a file .subscriptions with perm 600 is created in the parent directory of the shared mailboxes ("namespace public" below). As I understand the docs that file should

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

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, a few days ago I switched out UW-server installation to dovecot 0.99.14 (Solaris 9). There were a few client issues, but mostly the migration was ok. But I have still some questions/problems: +) dovecot-auth: ... PAM: pipe() failed: Too many open files I increased the max. number of open files. Is this normal behaviour, that more than 512 open files are needed ? +) we're using mbox

Hi folks. I just converted my site from UW+mbox to dovecot+maildir (stable-test59, 2005/02/25). For the most part, everything is great. The server seems faster and less memory intense than the UW server (this part has made me very happy). And it's definitely more user friendly to me than Courier. There is one thing however... A few of my users are using the web based mail reader

I just migrated from a FreeBSD/Sendmail/UW-IMAP setup to RHEL 3/Postfix/Dovecot (1.0a5 currently). Both systems used Procmail as the final delivery agent (into inboxes or . Since the changeover, things have *mostly* been going ok, but I've been having some problems that I think are locking-related. I'm getting reports from users about IMAP hangs (mostly from Thunderbird). Sometimes I see