similar to: Storage plugin documentation

I was thinking about documentation for alternate storage. We have a few mentions at: http://wiki2.dovecot.org/MailboxFormat/dbox http://wiki2.dovecot.org/Tools/Doveadm http://wiki2.dovecot.org/Tools/Doveadm/Altmove But I was thinking it would be helpful if there could be a page about alternate storage. I could write the page, but I currently have so many unknowns that I think it would be

I have an existing openldap schema which is handling mail, web and ftp services right now. I am trying to get a windows machine talking to the same filesystem as apache on linux via samba and read/write using the correct uid/gid. I was trying to shy away from using pam_ldap as there is no need to tie the user in ldap directly to the filesystem. The problem is it looks like the samba ldap module

Anyone know how to setup dovecot with mdbox so that it can be used through shared storage from multiple hosts? I've setup a gluster volume and am sharing it between 2 test clients. I'm using postfix/dovecot LDA for delivery and I'm using postal to send mail between 40 users. In doing this, I'm seeing these errors in the logs Mar 21 09:36:29 test-gluster-client2 dovecot:

Is it possible to query LDAP differently for different protocols? I am using dovecot for both pop3/imap and lmtp deliveries and there are different enable flags in ldap for them. I tried wrapping user_filter inside the protocols in the file dovecot-ldap.conf.ext as shown below but this didn't seem to work. protocol lmtp { user_filter =

I am messing around with gluster management and I've added a couple bricks and did a rebalance, first fix-layout and then migrate data. When I do this I seem to get a lot of failures: gluster> volume rebalance MAIL status Node Rebalanced-files size scanned failures status --------- -----------

Hello, >From what I have read on the dovecot site, it's possible to create a plugin for a custom data store format. We have emails in a custom format in a database and would like to create a plugin for accessing these emails through dovecot. Is there any supporting documentation from creating a plugin like this? Are there any samples? TIA, Gary

I'm exploring adding a new storage backend to dovecot, storing mail in some sort of database, and had a few questions. Hoping someone here might be able to help :) -Is all of the 'storage' specific code in housed in lib-storage/index? Would adding a new storage backend be as simple as recreating all of the public functions of the current /mbox or /maildir code such as they pertain to

I am looking through the logging options and wondering if there are a couple of things that we can do 1. Logouts don't seem to show the IP address of the logout, we typically see multiple sessions at a time and wondering if there is a way to tie the logouts to an IP 2. POP logouts show the number of messages retrieved/deleted but I don't see a way to do this with IMAP, is there a logout

I'm playing with running dovecot over NFS and I am running into some issues. I have followed the guide at http://wiki2.dovecot.org/NFS and my setup includes 1 nfs server and 1 client running postfix/dovecot. In testing I am running postal via the command: postal -t 10 -c 10 localhost users399 The test file has a list of 399 users to deliver to. I've provided a sample of the errors

v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to have a stable v1.1 in a month or two. The rest of the features that didn't make it into v1.1 will go to v1.2. I'll write more about this when v1.1 alpha is released. I also did a bit of benchmarking. v1.1's performance improvements are looking pretty great, it seems to be twice as fast as v1.0. v1.0:

On 25.09.2017 20:28, Sami Ketola wrote: >> On 25 Sep 2017, at 21.19, Garry Glendown <garry at glendown.de> wrote: >> >> doveadm(root): Error: chdir(/root/) failed: Permission denied >> (euid=479(dovecot) egid=478(dovecot) missing +x perm: /root, dir owned >> by 0:0 mode=0700) >> doveadm(root): Error: chdir(/root) failed: Permission denied >> >>

I have setup director and a backend dovecot service on the same machine using different ports. The backend service is listening on the default 24, 110 and 143 for lmtp, pop3 and imap respectively. Director is listening on 10024, 10110 and 10143 for the same respective services. I can get this setup to work if I have one backend server on a different IP listening on 10024, it seems director

I have setup samba to share a local filesystem with the following config: [global] smb ports = 139 workgroup = WORKGROUP server string = %h server (Samba, Ubuntu) dns proxy = no log level = 255 debug timestamp = yes log file = /var/log/samba/log.%m max log size = 1000 syslog = 1 panic action = /usr/share/samba/panic-action %d encrypt passwords = no security = user obey pam restrictions = yes

I've just enabled zlib for our users, and am looking at how to compress the existing files. The routine for doing this at http://wiki2.dovecot.org/Plugins/Zlib seems a bit complicated. What do you think about simply doing: find /var/vmail -type f -name "*,S=*" -mtime +1 -exec gzip -S Z -6 '{}' + I.e. find all maildir-files: - with size in the name ("*,S=*") -

In https://wiki2.dovecot.org/Tools/Doveadm/Sync#section_arguments the destination list 5 possible options for the destination but in the page on migration https://wiki2.dovecot.org/Migration/Dsync it seems to use a sixth undocumented "imapc:" option for destination e.g. doveadm -o mail_fsync=never backup -R -u user at domain imapc: "imapc:" is also referenced on

Hi, after setting up a new Dovecot server with shared and public namespaces, both with hidden=no and list=children, I see some inconsistency in the folder listing. . NAMESPACE * NAMESPACE (("" "/")) (("Shared/" "/")) (("Public/" "/")) . OK Namespace completed. . LIST "" * * LIST (\HasNoChildren) "/"

I'm trying to get the snarf plugin working with dovecot 2.0.7. Specifically, I want to use the UW-IMAP style optional snarfing. I'm looking at the wiki2 documentation. The first question is whether the UW-IMAP optional snarfing will require any changes to the mail_location. The first section suggests (but doesn't specifically state, which I'd propose be clarified) that

http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz.sig * Pre-login CAPABILITY includes IDLE again. Mainly to make Blackberry servers happy. * auth: auth_cache_negative_ttl default was 0 in earlier v2.0.x, but it was supposed to be 1 hour as in v1.x. Changed it back to 1h. If you want it disabled, make sure doveconf shows it as 0.

http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz.sig * Pre-login CAPABILITY includes IDLE again. Mainly to make Blackberry servers happy. * auth: auth_cache_negative_ttl default was 0 in earlier v2.0.x, but it was supposed to be 1 hour as in v1.x. Changed it back to 1h. If you want it disabled, make sure doveconf shows it as 0.

Hi guys, this page needs to be updated: https://wiki2.dovecot.org/MailLocation/Maildir#Control_files (link was from here: https://wiki2.dovecot.org/MailLocation) Section 'Control files' is mentioning only 2 files but, in fact, Dovecot will store some additional files in CONTROL location: dovecot-uidvalidity dovecot-uidvalidity.* subscriptions (anything more?) Even more, page