similar to: Direct groups of users to pairs of backend servers

HI All, We have a couple of dovecot director proxies and six backed mailstores each accessing mailboxes stored on five NFSv4 filsystems with about 1TB of mail on each in maildir format.? We have about 800 max users on each mailstore at peak times and performance appears to starting to degrade at these times.? The mailstores are pretty recent hardware with 64GB of RAM and 24 cores.?? The NFS

HI All, I have setup my Dovecot director proxies and Dovecot backend mail stores.? I intend setting up several incoming and outgoing Exim MTA's.? I am a bit confused about what I need to run on the backend Dovecot MTA's to get the incoming mail delivered to them.? Do I need to install Exim on them or use LMTP to receive mail from the MTA's?? Also, can I directly deliver mail to the

Hi All, We are using Dovecot in a Director setup with two director proxies, six backend mailstores, mailbox storage in NFS, and user accounts stored in LDAP.?? Currently we have five NFS filesystems on EMC VNX storage which are all mounted on each of the six backend mailstores.?? At the moment all users could be directed to any of the six mailstores.? We have a group of users with very large

Hi All, I am synchronizing a few hundred dovecot mailboxes with a perl script via a crontab. ? It works for a while (ie exit status=0)? but the rest then start failing with exit code 19200.?? I tried redirecting STDERR but showed nothing.? I suspect the cron job is hitting some sort of resource limit?? If I run the perl script from the command line it appears to dsync all the accounts OK.?? The

Hi All, I need to import mailboxes into my Director NFS setup via one of my director proxy's as doing a direct dsync to the backend mailstores appears to giving me NFS locking issues. It looks like it may be possible to do this using doveadm listeners. I have setup doveadm listeners on a test proxy and backend mailstore. I am not sure how to make the dsync proxy through to the backend

Having > 10 TByte mailstore filesystem-checks takes too much time. At the moment we have four different partitions, but I don't like to set symlinks or LDAP-flags to sort customers and their domains to there individual mount-point. I'd like to work with mdbox:/mail/%d/%n to calculate the path automatically. How do you handle >> 10 TB mailstore? I'm very interested in the

Hi all. We've just migrated our back-end NFS mailstore from FC1 systems to CentOS4 and are experiencing problems/delays with vpopmail and user Maildirs. IMAP is fine, it's just POP access that causes us problems. Now, NFS mounts successfully, the clients can see /home/vpopmail and serve content as we would expect. IMAP works perfectly and sees new messages as soon as they're

I'm using roundcube webmail managesieve plugin. Webmail can login managesieve to a specific mailstore successfully without proxying. Because I have mutiple mailstores, I have to use proxying to redirect the correct mailstores just as imap/pop3. ???? Stephan Bosch ????? 2016-04-03 22:50 ???? Hawk Chen; dovecot ??? Re: ??: Re: managesieve proxying not working Op 3-4-2016 om 16:32 schreef

Hi All, I am having trouble removing all messages in a mailbox.?? The command below doesn't remove all the messages: doveadm expunge -u user at domain mailbox? '*' all Do I need to add .* or other? THanks Murray

Hello, With the same basic configs as in my previous messages, I tried with the maildir format instead of the mbox format. That is, in both cases ("virtual" uids/gids vs a single "real" uid/gid), doveconf -n shows: mail_location = maildir:~/maildir instead of: mail_location = mbox:~/mboxes:INBOX=~/mboxes/inbox Here too, with "virtual" uids/gids, connections thru

Hi list, I am trying to build an email system that is using multiple frontends, to a clustered backend using nfs. The backend mounts his filesystems from a central storage, and will be running active-active. While reading through the dovecot documentation, I read that I could do without indexes (well: use memory indexes), and could then be able to run dovecot over NFS. Well: that was until

I am sure resolving works fine. I tested this in a running mesos container, but also in docker run[1]. I need to have the search local option in resolve.conf. It was actually working, until I started adding the proxy for managesieve, but when I reverted, it still does not work. I think the building from cache mislead me. I suspect this is a different problem, that at some point is giving

Folks, We are in the process of purchasing new san/s that our mail server runs on (JES3). We have moved our mailstores to zfs and continue to have checksum errors -- they are corrected but this improves on the ufs inode errors that require system shutdown and fsck. So, I am recommending that we buy small jbods, do raidz2 and let zfs handle the raiding of these boxes. As we need more

Hi, we've found a weird bug (?) in Dovecot 1.1.11. Since day and age we've been running dovecot for our student mailserver, getting the location of the mailbox from a LDAP directory. We allow login and LDA with both full mail address and an internal username, so the mailbox directory is based on a LDAP attribute user_attrs =

I am trying to use dovecot. I've got a GFS2 shared volume on two servers with dovecot running on both. On one server at a time, it works. The test I am trying is to attach two mail programs (MUA) via IMAPS (Thunderbird and Evolution as it happens). I've attached one mail program to each IMAPS server. I am trying to move emails around in one program (from folder to folder), and then

I'm running beta7 on two machines, with maildir on NFS. I have lockd running on all machines. I've found that Dovecot is highly unstable with NFS when accessing a mailbox on more than one machine at the same time. Both dovecot machines have: mmap_disable = yes lock_method = fcntl NFS is version 3, exported from a third linux machine. All machines are running 2.6.9 kernel. Any ideas

Hello list, I am currently testing a setup for a PoC wit this configuration. - 1 x Frontend dovecot for proxying IMAP/POP3/LMTP/ManageSieve/Submission - 2 x Backend dovecot with local mail storage The frontend does the user authentification and communicate with the backends using a master password The fronted accepts PLAIN and LOGIN auth mechanisms and talk with backends using PLAIN auth

I am using qmail-ldap to provide virtual users to my system, but I also have some shell users on the system as well. Virtual users go into /home/vmail/mailstore/$username/ System users go into /home/$username/Maildir How can I have both of these available as inboxes in dovecot using ldap logins? Do I need to use namespaces or am i missing something with default_mail_env? Thanks, -- Brian T

Hi, yesterday I updated my second server from Debian Squeeze to Debian Wheezy. Since todaay I get the followinig errors in my logs: Error-Log: ... Jun 26 09:08:28 mailstore dovecot: imap(user at domain.net pid:28898 session:<iuMX3Lf8fACXLrFC>): Fatal: master: service(imap): child 28898 killed with signal 11 (core dumped) ... Mail-log ... Jun 26 09:08:28 mailstore dovecot: imap-login: ID

Hi, We're using dovecot to provide pop3 for a number of mailboxes. The setup is pretty simple: Each user / domain has a mailstore in /data/mailstore/<domain>/<user>/Maildir (backed by NFS). Passwords are in simple passwd-file format in the top level domain directory eg: # cat /data/mailstore/foo.com/.passwd user:{plain}password The passdb setup looks like this. passdb {