- dovecot - dovecot.org

A solution : dsync(someuser) Error: Mailbox GUIDs are not permanent without index files
by James Rogers 12 Jun '14

12 Jun '14

While migrating from mbox to maildir using dsync, I kept running into a brick wall. Some folders would not sync. The message in stderr was: Error message GUID: Mailbox GUIDs are not permanent without index files. This is what solved things for me. I hope this might help someone. Let me know if I'm completely off sides. When working with dsync to migrate from mbox to maildir format mailboxes, I kept running into the error: dsync(someuser): Error: Couldn't get mailbox Drafts GUID: Mailbox GUIDs are not permanent without index files dsync(someuser): Error: Couldn't get mailbox Junk E-mail1 GUID: Mailbox GUIDs are not permanent without index files dsync(soemuser): Error: Couldn't get mailbox TO DO LATER - US GUID: Mailbox GUIDs are not permanent without index files dsync(someuser): Error: Couldn't get mailbox Notes GUID: Mailbox GUIDs are not permanent without index files dsync(someuser): Error: Couldn't get mailbox Orders Pending GUID: Mailbox GUIDs are not permanent without index files dsync(someuser): Error: Couldn't get mailbox Junk E-mail GUID: Mailbox GUIDs are not permanent without index files dsync(someuser): Error: Couldn't get mailbox Server Mgmt+Config GUID: Mailbox GUIDs are not permanent without index files The error messages were helpful, but it would be nice to know what prevented the creation of the indexes in the errors (permissions, settings, disk space, etc.). I finally figured it out semi-randomly when I dumped my doveconf file using doveconf -n, and saw: mbox_min_index_size = 100 k I felt very um... happy? And not too bright. The following made my problems go away, and the sync worked flawlessly. mbox_min_index_size = 0 I guess it's best to set this using dsync -o'mbox_min_index_size=0' Mail now converts quickly and completely even for 0 length mailboxes (i.e. empty folders are created). Also, I would like to note that mb2md.pl should not be used to convert mbox to maildir. The regex used to split mboxes will fragment messages. mb2md.pl uses: if ( /^From / And in the very least, the following would be less harmful: if ( /^From\s+(\S+.*(a)\S+.*|MAILER.DAEMON)\s+.*$/ I love dovecot. I knew it must be something bone-headed I just wasn't seeing. And now I can go get some rest. --James W. Rogers

1 0

lazy_expunge mangles dovecot-acl-list
by Christoph Bußenius 12 Jun '14

12 Jun '14

Hi, I think I found a bug in Dovecot 2.1.17 and 2.2.13. In our setup, sometimes ACLs stop working because "dovecot-acl-list" is replaced by an empty file. We found that lazy_expunge is connected to this. To reproduce, create ACLs for "user1" in a folder. Put a mail in that folder and expunge it, so that the folder will be created in the "expunged" namespace. For instance, # cat user1/mail/mailboxes/folder/dbox-Mails/dovecot-acl user=user2 keilrwts # cat user1/mail/dovecot-acl-list 1350914868 folder # doveadm -f flow fetch -u "user1" 'guid' mailbox _EXPUNGED.\* # ls -l user1/mail/dovecot-acl-list -rw------- 1 vmail vmail 0 2014-06-12 11:40 user1/mail/dovecot-acl-list You see that we have used doveadm to list the expunged namespace, which has emptied the "dovecot-acl-list" file. Cheers, Christoph # 2.2.13: /usr/local/dovecot/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-57-server x86_64 Ubuntu 10.04.4 LTS disable_plaintext_auth = no mail_gid = vmail mail_location = mdbox:~/mail mail_plugins = acl mail_uid = vmail namespace { inbox = no list = children location = mdbox:%%h/mail prefix = INBOX.shared.%%u. separator = . subscriptions = no type = shared } namespace default { inbox = yes location = prefix = INBOX. separator = . type = private } namespace expunged { hidden = yes list = no location = mdbox:~/mail:MAILBOXDIR=expunged:SUBSCRIPTIONS=expunged-subscriptions prefix = _EXPUNGED. separator = . subscriptions = yes } passdb { args = scheme=CRYPT username_format=%u /usr/local/dovecot/etc/dovecot/users driver = passwd-file } plugin { acl = vfile acl_shared_dict = file:/mail/shared-mailboxes lazy_expunge = _EXPUNGED. } protocols = imap pop3 service auth { unix_listener auth-userdb { group = vmail mode = 0660 } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /usr/local/dovecot/etc/dovecot/users driver = passwd-file } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 20 mail_plugins = acl imap_acl acl } -- Christoph Bußenius Rechnerbetriebsgruppe Informatik und Mathematik Technische Universität München

2 2

Parse dovecot 2.2 logs with logstash
by Bruno Galindro da Costa 12 Jun '14

12 Jun '14

Guys, I need to parse my dovecot log files with logstash grok patterns. Is there any document specifying the patterns used by dovecot to write it's logs? I need to find all the log possibilities that could be writed to log files by dovecot. So, if a document like that exists or if anyone could answer my question, I'll could make the parser with less difficult. -- Att. Bruno Galindro da Costa

3 3

Problems with dsync and global acls
by Michał Węgrzynek 12 Jun '14

12 Jun '14

Hi all! I have 2 servers running dsync tcp replication between them. After setting global ACLs to * user=admin lrwstipekxa on both hosts, I get the following errors during replication for every folder: dsync-local(mwegrzynek): Error: Mailbox Trash: Failed to set attribute vendor/vendor.dovecot/pvt/acl/user=admin: Invalid right '' This error first manifested in version 2.2.13, there were no such errors in 2.2.9 (stock Ubuntu 14.04) version. Am I doing something wrong? My configuration: # 2.2.13.3 (6dab0352ccb3+): /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-29-generic x86_64 Ubuntu 14.04 LTS ext4 auth_cache_size = 10 M auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/krb5.keytab auth_master_user_separator = * auth_mechanisms = plain login gssapi auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@() auth_username_format = %Ln auth_verbose = yes default_client_limit = 10000 default_process_limit = 1000 default_vsz_limit = 2 G doveadm_port = 12345 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_rcpt_check_quota = yes lmtp_save_to_detail_mailbox = yes mail_gid = vmail mail_home = /var/mail/users/%u mail_location = mdbox:/var/mail/users/%u/mdbox mail_plugins = acl quota virtual zlib listescape fts fts_squat notify replication mail_prefetch_count = 20 mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate mdbox_preallocate_space = yes namespace dzielone { list = children location = mdbox:%%h/mdbox:INDEXPVT=~/shared/%%u prefix = Dzielone/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } namespace publiczne { list = children location = mdbox:/var/mail/public:INDEXPVT=~/public prefix = Publiczne/ separator = / subscriptions = no type = public } passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.passdb.ext driver = ldap } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = file:/var/mail/config/shared-mailboxes fts = squat fts_squat = partial=4 full=10 mail_replica = tcps:xxx.yyy.zzz quota = dict:User quota::file:%h/dovecot-quota sieve = ~/.dovecot.sieve sieve_dir = ~/sieve zlib_save = gz zlib_save_level = 6 } pop3_uidl_format = %v.%u protocols = imap pop3 lmtp sieve quota_full_tempfail = yes replication_dsync_parameters = -d -l 60 -n inbox -U service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail user = vmail } } service doveadm { inet_listener { port = 12345 ssl = yes } process_limit = 10 } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl_ca = </etc/ssl/certs/xxx.pem ssl_cert = </etc/ssl/certs/default.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_client_ca_file = /etc/ssl/certs/xxx.pem ssl_key = </etc/ssl/private/default.key userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap.userdb.ext driver = ldap } protocol lmtp { mail_plugins = acl quota virtual zlib listescape fts fts_squat notify replication sieve } protocol lda { mail_plugins = acl quota virtual zlib listescape fts fts_squat notify replication sieve } protocol imap { mail_plugins = acl quota virtual zlib listescape fts fts_squat notify replication imap_acl imap_zlib imap_quota } Thanks in advance for your help, -- *Michał Węgrzynek*

1 0

Converting mailboxes from one Maildir format to another
by Patrick C 12 Jun '14

12 Jun '14

I am currently running dovecot 2.0.9 on a CentOS 6 server with the following layout for mailboxes: mail_location = maildir:~/Maildir I would like to change the layout to this format to match the output of other software packages such as offlineimap, mbsync, etc: mail_location = maildir:~/Maildir:LAYOUT=fs:INBOX=~/Maildir/INBOX Is there a way to convert the mailbox layout for all mail accounts currently on the server? I was looking at dsync, but there aren't any Maildir <--> Maildir examples. I was also looking at potentially writing a script to manually rename directories/move files around to match the new format, but wasn't sure whether that would mess with UIDs or other dovecot internals. pat patrickc81(a)gmail.com

2 1

Maildir index
by Eduardo Ramos 11 Jun '14

11 Jun '14

Hi all! I store my maildir mailboxes in a ocfs2 volume. By default, my indexes are stored with the inbox. If I change now to a local disk, could I have trouble? That's my production server. Thanks!

1 0

Safe to downgrade 2.2 to 2.1?
by Florian Tischler 11 Jun '14

11 Jun '14

Hi, is it safe to downgrade Dovecot 2.2 to 2.1 (in my case 2.2.13 to 2.1.17 with mdbox format) or will there be troubles with index files and backup/restore is recommended? Unfortunately with 2.2+ it is not to be possible to use acl + lazy_expunge together anymore, so downgrading is the only option for me... @Timo, please fix acl + lazy_expunge in 2.2 if you find some time. Florian -- Florian Tischler System Administrator *Johann Radon Institute for Computational and Applied Mathematics (RICAM) http://www.ricam.oeaw.ac.at/

1 0

Change index location problem
by igord 11 Jun '14

11 Jun '14

Hi All, I was unable to change location of Dovecot indexes. Currently they are under /var/vmail/%d/%u, but I want to change them to /media/ephemeral0/%u I've changed conf line in /etc/dovecot/dovecot.conf: mail_location = maildir:/var/vmail/%d/%u:INDEX=/media/ephemeral0/%u and setup permissions of /media/ephemeral0 to dovecot:dovecot, tried also vmail:mail (which is default user for e-mails) and also tried with 777 on all dirs, but Dovecot is keeping creating indexes on the old location. I tried moving them from old to new location, but Dovecot recreates them on the old location. Details: # dovecot --version 2.0.9 # doveconf -a | grep location mail_location = maildir:/var/vmail/%d/%u:INDEX=/media/ephemeral0/%u Has anyone experienced something similar, any solution for this? Thanks in advance! -- View this message in context: http://dovecot.2317879.n4.nabble.com/Change-index-location-problem-tp48468.… Sent from the Dovecot mailing list archive at Nabble.com.

2 4

Re: Subject tag [Dovecot] is gone
by Professa Dementia 11 Jun '14

11 Jun '14

On 6/9/2014 7:26 PM, Timo Sirainen wrote: > The main reason is DKIM, which is starting to be a real problem. I have not used DKIM much. My mail server and client mostly deal with SPF. I have a filter that colorizes messages that have no SPF or a missing DKIM or bad DKIM signature. I *have* noticed that a lot of messages from the list get marked in such manner, but it never really bothered me and I never thought about it much. Now I understand why that happens (the [Dovecot] identifier in the subject). When trying to solve a problem, the first thing is to correctly identify the problem. You cannot solve a problem if you do not even know what it is. The underlying problem is to identify and classify emails as ones you want and ones you do not want. This is not easy and involves reading a person's mind. A person may, depending on their mood, classify the same email differently at different times, which complicates things. DKIM assumes that you can, in many cases, classify emails this way based on authenticating the *domain* of the sender. This has some serious flaws in that it does not address this issue, even though it purports to. One way to classify an email as "wanted" is if it comes from someone you know and want to communicate with. Signing based on a domain does nothing to address this. If my girlfriend is judy(a)yahoo.com, I want to receive her emails. That does not means I want to receive all emails from the yahoo.com domain. I do not want someone else to impersonate her. If later, we break up and I no longer want to receive her emails, DKIM does nothing to help with that, either. That could be OK if such functionality is beyond its scope. DKIM erroneously bundles sender authentication with message validation. I want to know that it really was judy(a)yahoo.com that sent me the message and not someone trying to impersonate her. However, as a separate function, I would like to know that the message I received is not the one she sent. These functions should not be integrated. As it is now, if the signature does not verify, I do not know why. Was the sender spoofed? Was some part of the message modified in some way? And just for the record, I believe that the subject line should conceptually be treated as part of the message, along with the date. DKIM is too strict. If I want to present a legal document (email) in court, I may want to prove that the document I present to the court is exactly as it was when it was sent to me. However, this is not a common occurrence. The real world is messy and imperfect and often, changes to emails are innocuous and legitimate. Mailing lists are an example of this. A mailing list or anti-virus scanner *should* be able to add a footer or add a mailing list identifier to the subject line, as long as those changes can be marked as later additions that the original sender is not accountable for. An email program should make it clear to the recipient which parts are not accountable to the original sender. I am not proposing a new standard, simply pointing out that breaking an established protocol (by removing the [Dovecot] subject identifier) because of a flawed anti-spam system is not in people's best interest. Can a spammer spoof messages from the list? Sure. Has it happened? Not that I am aware of. Is it a problem? Not so far. So why, then, make people go through all this trouble of setting up new filters and rules, mail routing, software upgrades, etc, just to appease a standard that is clearly broken? Dem

5 4

replication with plugin won´t work
by Florian Schaal 11 Jun '14

11 Jun '14

Hi all, i try to setup a master-master replication with dovecot / dsync. I´m using virtual-users. When I call doveadm sync -A remote:vmail@server2 new mails are copied to the second server, but new messages from server 2 not on Server 1. To fix this i run doveadm sync -A remote:vmail@server on the 2nd server But I want that it works with dovecot / dsync (see my config at the end - identical on bot servers, only mail_replica is different). I added some services regarding http://wiki2.dovecot.org/Replication If i send a local mail on one server it will not be replicated to the other server until i run doveadm sync. Maybe i just missed some steps in my setup? doveadm user '*' displays the right users on both servers. === docecot.conf === # 2.2.13 (7b25994a8cb7): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab076.8 x86_64 Debian 7.5 auth_mechanisms = plain login ntlm disable_plaintext_auth = no dsync_remote_cmd = ssh -p 4711 -l%{login} %{host} doveadm dsync -u%u listen = *,[::] log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_plugins = " notify replication" mail_privileged_group = vmail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { mail_replica = remote:vmail@server2 quota = dict:user::file:/var/vmail/%d/%n/.quotausage replication_full_sync_interval = 1 hours sieve = /var/vmail/%d/%n/.sieve } protocols = imap pop3 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } user = root } service config { unix_listener config { user = vmail } } service doveadm { user = vmail } service imap-login { client_limit = 1000 process_limit = 500 } service replicator { process_min_avail = 1 } ssl_cert = </etc/postfix/smtpd.cert ssl_key = </etc/postfix/smtpd.key userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve quota } === docecot.conf === regards Florian

1 0

[Dovecot] Can't get authentication for masterusers on Mac OS X Server 10.6.8
by Gilles Celli 11 Jun '14

11 Jun '14

Hi dovecot masters, This is my first post here, since I desperately need some advices from the dovecot community. I've tried to get an answer on the Apple Forums but til now no luck....here we go: I've tried to sync our users emails (Mac OS X Server 10.6.8 Snow Leopard with dovecot 1.1.20-apple0.5) via imapsync to our new server by using the masterusers authentication method on the old 10.6.8 server... The main problem on OS X Server 10.6.8 is that dovecot 1.1.20 uses the OD (OpenDirectory) driver (well I think), so that when following the directions of Master users/password from this page I can't login with the http://wiki1.dovecot.org/Authentication/MasterUsers I couldn't find anything on the OD driver directive....the dovecot 1.1.20-apple build doesn't even have the shadow driver built in (see below the dovecot --build-options), so that passdb shadow {} won't work anyway I always get NO Authentication failed, when trying the following: >telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. 1 login user1*mailadmin PASSWORD 1 NO Authentication failed. I've tried also to add a Post-login scripting like described here, but no luck either: http://www.stefanux.de/wiki/doku.php/server/dovecot Does someone know how to fix my migration issue ? Any help is greatly appreciated. Gilles Here's my dovecot : >dovecotd --build-options Build options: ioloop=kqueue notify=kqueue ipv6 openssl Mail storages: maildir mbox dbox cydir raw SQL drivers: Passdb: checkpassword od pam passwd passwd-file Userdb: od passwd passwd-file prefetch static Here's my dovecot -n output: >dovecotd -n # 1.1.20apple0.5: /private/etc/dovecot/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 306). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: Darwin 10.8.0 i386 hfs base_dir: /var/run/dovecot syslog_facility: local6 protocols: pop3 imap pop3s imaps ssl_ca_file: /etc/certificates/Default.DB14D82BF89A0DDCE123137BC94AEA0C94DDD838.chain.pem ssl_cert_file: /etc/certificates/Default.DB14D82BF89A0DDCE123137BC94AEA0C94DDD838.cert.pem ssl_key_file: /etc/certificates/Default.DB14D82BF89A0DDCE123137BC94AEA0C94DDD838.key.pem ssl_cipher_list: ALL:!LOW:!SSLv2:!aNULL:!ADH:!eNULL disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_user: _dovecot login_process_per_connection: no max_mail_processes: 50 mail_max_userip_connections(default): 20 mail_max_userip_connections(imap): 20 mail_max_userip_connections(pop3): 10 verbose_proctitle: yes first_valid_uid: 6 first_valid_gid: 6 mail_access_groups: mail mail_location: maildir:/var/spool/imap/dovecot/mail/%u mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_process_sharing: full mail_max_connections(default): 10 mail_max_connections(imap): 10 mail_max_connections(pop3): 5 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 lda: postmaster_address: postmaster(a)example.com hostname: mymailserver.example.com mail_plugins: quota quota_full_tempfail: yes sendmail_path: /usr/sbin/sendmail auth_socket_path: /var/run/dovecot/auth-master log_path: /var/log/mailaccess.log info_log_path: /var/log/mailaccess.log auth default: mechanisms: plain login gssapi apop cram-md5 master_user_separator: * verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd.masterusers pass: yes master: yes passdb: driver: od userdb: driver: od args: partition=/etc/dovecot/partition_map.conf enforce_quotas=no socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: _dovecot group: mail plugin: quota_warning: storage=100%% /usr/libexec/dovecot/quota-exceeded.sh quota_warning2: storage=90%% /usr/libexec/dovecot/quota-warning.sh quota: maildir:User quota sieve: /var/spool/imap/dovecot/sieve-scripts/%u/dovecot.sieve

3 5

[Dovecot] imap-login killed with signal 11 in Dovecot 2.2.13 (feea8645c4d7)
by Thomas Leuxner 10 Jun '14

10 Jun '14

Latest 2.2.13 HG feea8645c4d7 seems to unexpectedly kill imap-login sessions: Jun 7 11:56:10 nihlus dovecot: imap(tlx(a)leuxner.net): Disconnected: Logged out in=2203 out=851225 Jun 7 11:56:10 nihlus dovecot: imap(tlx(a)leuxner.net): Disconnected: Logged out in=316 out=2417 Jun 7 11:56:10 nihlus dovecot: imap-login: Fatal: master: service(imap-login): child 60505 killed with signal 11 (core not dumped - add -D parameter to service imap-login { executable } Jun 7 11:56:10 nihlus dovecot: imap-login: Fatal: master: service(imap-login): child 60595 killed with signal 11 (core not dumped - add -D parameter to service imap-login { executable } Adding the -D parameter does not generate a core dump however...

5 7

Dovecot auth NTLM
by dovecot.lista＠palacio.cu 10 Jun '14

10 Jun '14

Hello, this is my first email to the list... i´m configuring Dovecot with NTLM authentication, at least this is what i wanted, but i´m having a few problems. 1-I made my configuration following the steps from this howto http://wiki2.dovecot.org/HowTo/ActiveDirectoryNtlm from the dovecot official site, but my dovecot´s version is 2.1.7 and the tutorial dovecot´s version is 1.1.16. But, the fact is that when i enter to the wiki1, for the version 1.x i found that all the howtos are obsoletes and the tutorial for the version 1.x is the same for the 2.x version, so this howto is not trustful.... but, there is not another one. 2-When i implement it all seems to work OK, but the communication between dovecot and the helper in "/usr/bin/ntlm_auth". I made the tests with the binary(/usr/bin/ntlm_auth) and i got the right answers from it, and i also made the test with the tool wbinfo and were successful. During the tests i was monitoring the logs of my Domain Controller (The server from where i want to authenticate) and it logged all the requests i made however when i try to authenticate with dovecot in my Domain Controller nothing is written in the logs... then i get to the conclusion that Dovecot is not communicating with the helper, and of course in dovecot´s logs appears: auth: Info: winbind(?,10.10.10.10): user not authenticated: NT_STATUS_UNSUCCESSFUL As i said, my friends, there is no any other tutorial or howto in internet, at least i did not see it. I´m asking for your help... if any of you have configured Dovecot to auth against NTLM, please tell me how. Im working on Debian Wheezy and Dovecot 2.1.7. PS:Please forgive my English i speak Spanish

1 0

Dovecot Configuration for access with GSSAPI / Kerberos
by Sandra 10 Jun '14

10 Jun '14

Hi Dovecot-Mailinglist! I try to install a new Dovecot-Server with Kerberos-Authentification (Kerberos-Server is already authenticating user-account ). The following error-notice occurs when I use mail-programm Gnome Evolution to access IMAP-Account: "Ordner konnte nicht geöffnet werden (Folder can not be opened) The reported error was "GSSAPI-Legitimation ist fehlgeschlagen". (GSSAPI-Legitimation failed) Is anybody able to help me??? Thanks in advance, Sandra Dovecot Version: 2.1.17 Configuration: auth_mechanisms = gssapi auth_debug = yes auth_gssapi_hostname = kerberosServer.domain auth_realms = REALM auth_default_realm = REALM auth_krb5_keytab = /etc/krb5.keytab auth_verbose = yes disable_plaintext_auth = yes userdb { driver = static args = uid=vmail gid=vmail home=/service/mailServer_Kommunikations-Server/mails/%u } mail_location = maildir:/service/mailServer_Kommunikations-Server/mails/imap/% u/:INBOX=/service/mailServer_Kommunikations-Server/mails/maildir/%u log_timestamp = "%Y-%m-%d %H:%M:%S " managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave protocols = imap pop3 ssl = no service auth { unix_listener /var/spool/postfix/private/auth_dovecot { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0600 user = mail } user = root } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master postmaster_address = root(a)mailServer.domain } mail_privileged_group = mail Logfile: 2014-06-09T09:59:22.596608+02:00 highlands dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/modules/auth 2014-06-09T09:59:22.598243+02:00 highlands dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/modules/auth/libdriver_mysql.so 2014-06-09T09:59:22.598559+02:00 highlands dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/modules/auth 2014-06-09T09:59:22.600354+02:00 highlands dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/modules/auth/libmech_gssapi.so 2014-06-09T09:59:22.600982+02:00 highlands dovecot: auth: Debug: auth client connected (pid=5770) 2014-06-09T09:59:22.602211+02:00 highlands dovecot: auth: Debug: client in: AUTH#0111#011GSSAPI#011service=imap#011session=E7rSlmL70wDAqEWd#011lip=mailServerIP#011rip=clientIP#011lport=143#011rport=46035 2014-06-09T09:59:22.602498+02:00 highlands dovecot: auth: Debug: gssapi(?,clientIP,<E7rSlmL70wDAqEWd>): Obtaining credentials for imap(a)dartmoor.outback 2014-06-09T09:59:22.610815+02:00 highlands dovecot: auth: gssapi(?,clientIP,<E7rSlmL70wDAqEWd>): While acquiring service credentials: Unspecified GSS failure. Minor code may provide more information 2014-06-09T09:59:22.611097+02:00 highlands dovecot: auth: gssapi(?,clientIP,<E7rSlmL70wDAqEWd>): While acquiring service credentials: No key table entry found matching imap/dartmoor.outback@ 2014-06-09T09:59:24.113071+02:00 highlands dovecot: auth: Debug: client passdb out: FAIL#0111#011temp 2014-06-09T09:59:24.113818+02:00 highlands dovecot: imap-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<>, method=GSSAPI, rip=clientIP, lip=mailServerIP, session=<E7rSlmL70wDAqEWd>

1 0

Bug when virtual mailbox is set to auto=subscribe
by Daniel Neugart 10 Jun '14

10 Jun '14

Hi everybody, I'd like to submit a bug: My setup: dovecot version: 2.2.13-1 Kernel: 3.14.5-1-ARCH on arch linux x64 Filesystem: ext4 Bug description: If a virtual mailbox is defined with auto = subscribe dovecot crashes upon access via imap. Configuration is as followed: namespace inbox { [...] mailbox virtual/Flagged { auto = subscribe special_use = \Flagged } [...] dovecot-virtual file: # ~/Maildir/virtual/Flagged/dovecot-virtual * -Trash -Trash/* flagged 'auto' must be set to 'no' for virtual mailboxes, otherwise dovecot crashes when the virtual folder is tried to be accessed via a imap (thunderbird in my case). Crash log: Jun 09 21:55:07 pluto dovecot[24881]: imap($MAILADRESS): Panic: file mail-index-sync.c: line 413 (mail_index_sync_begin_to2): assertion failed: (!index->syncing) Jun 09 21:55:07 pluto dovecot[24881]: imap($MAILADRESS): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x68680) [0x7fa67a692680] -> /usr/lib/dovecot/libdovecot.so.0(+0x6876c) [0x7fa67a69276c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa67a64c83d] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc3dfe) [0x7fa67a9c3dfe] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin_to+0x3f) [0x7fa67a9c3eaf] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin+0x1c) [0x7fa67a9c3f3c] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0xc3) [0x7fa679e71d23] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x29) [0x7fa67a97cf29] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fa67a97d037] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7fa67a9a59e1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x8c9d) [0x7fa679e70c9d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7fa67a97e321] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0xf94) [0x7fa679e72bf4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x29) [0x7fa67a97cf29] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fa67a97d037] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7fa67a9a59e1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x8c9d) [0x7fa679e70c9d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7fa67a97e321] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0xf94) [0x7fa679e72bf4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x29) [0x7fa67a97cf29] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fa67a97d037] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7fa67a9a59e1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x8c9d) [0x7fa679e70c9d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7fa67a97e321] -> dovecot/imap(imap_status_get+0x67) [0x41d6f7] -> dovecot/imap(cmd_status+0x188) [0x4131c8] -> dovecot/imap(command_exec+0x3c) [0x4171ac] -> dovecot/imap() [0x416202] Jun 09 21:55:07 pluto dovecot[24881]: imap($MAILADRESS): Fatal: master: service(imap): child 24926 killed with signal 6 (core dumped) Below a complete dump of doveconf -n (with corrected 'auto' value for virtual mailboxes): # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.14.5-1-ARCH x86_64 mail_home = /home/vmail/%d/%n mail_location = maildir:~/Maildir:LAYOUT=fs mail_plugins = " virtual" namespace { location = virtual:~/Maildir/virtual prefix = virtual/ separator = / } namespace inbox { inbox = yes location = mailbox Archive { auto = create special_use = \Archive } mailbox Drafts { auto = create special_use = \Drafts } mailbox Junk { auto = create special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = create special_use = \Trash } mailbox virtual/All { auto = no special_use = \All } mailbox virtual/Flagged { auto = no special_use = \Flagged } prefix = } passdb { args = username_format=%n scheme=SHA512-CRYPT /etc/dovecot/%d/passwd driver = passwd-file } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = vmail } ssl_cert = </$PATH to my ssl cert ssl_key = </$PATH to my ssl key userdb { args = username_format=%n /etc/dovecot/%d/passwd default_fields = uid=vmail gid=vmail driver = passwd-file } protocol lmtp { postmaster_address = postmaster(a)mydomain.com } Best regards Daniel

1 0

[Dovecot] NoSQL support
by List 09 Jun '14

09 Jun '14

Is there any support for NoSQL databases such as Cassandra (CQL) or MongoDB now or planned in the future for userdb and passdb lookups?

2 1

[Dovecot] Issues with VANISHED CHANGEDSINCE
by Michael J Rubinsky 09 Jun '14

09 Jun '14

I've been seeing the following wonky behavior with Dovecot. Currently this is with Dovecot 2.0.19, but I was also seeing it in earlier versions as well, including versions from the 1.x series. Some background, this is from Horde's ActiveSync library, when it is trying to determine what UIDs have recently been expunged. I can guarantee that when this command was sent, there was only one or two emails that were removed since the provided MODSEQ value. C: 8 UID FETCH 1:* UID (VANISHED CHANGEDSINCE 587742) S: * VANISHED (EARLIER) 1:119944,119947:123482,123484:128043,128045:130388,130390:130456,130458:132127,132129:135832,135834:136201,136203:136301,136303:136316,136318:138502,138504:140099,140101:141908,141910:142607,142609:142744,142746:142865,142867:143160,143164:143173,143176:143179,143181:143187,143189:143190,143192:143195,143197:143270,143272:143273,143275:143280,143282:143302,143305:143307,143309:143318,143320:143333,143335:143337,143339:143341,143343:143375,143377:143400,143402:143551,143553:143637,143640:143706,143708:144069,144071:144178,144180:144307,144309:144316,144318:144329,144331:144931,144933:144983,144985:145000,145002:145069,145071:145072,145074:145132,145136:145178,145180:145191,145193 Also, to verify it wasn't something screwy with my server, Michael Slusarz provided me with this from his server: <quote> There's definitely something wonky going on in the code. There's a certain tipping point of modseqs where the values become incorrect. For a mailbox with HIGHESTMODSEQ of 54004, I see this: a uid fetch 1:* UID (VANISHED CHANGEDSINCE 53881) * VANISHED (EARLIER) 1:37308,37310:40788,40791:41032,41034:41083 a OK Fetch completed. b uid fetch 1:* UID (VANISHED CHANGEDSINCE 53882) * VANISHED (EARLIER) 41029:41030,41047:41083 b OK Fetch completed. </quote> Thanks for any guidance. -- mike The Horde Project (www.horde.org) mrubinsk(a)horde.org

4 21

[Dovecot] checkpassword memory limit
by a 08 Jun '14

08 Jun '14

Hi. I am trying to authenticate dovecot from a wordpress database. I was thinking of using the checkpassword script to start a cli php script. That php script would then include the necessary wordpress functions, do the auth (find the wp username from user database using the email address, and authenticate with the user/pass), and return the result to the checkpassword script. I made the above scripts (the php script will be used to authenticate some other services too), and when I run them "by hand" (even with "sudo -u dovecot ..."), it works. But, when the dovecot runs them, the php runs out of memory. After a lot of debuging, I find out that when the dovecot starts the checkpassword script, it makes a 250kB memory limit. But it is not enough for the php script, it needs 14MB. I tried to put a "ulimit -v 16777216" into the checkpassword.sh, but it doesn't work.Is there some hardcoded limit in the dovecot itself? And if there is, could it be somehow changed?I am using a simple D ebian Wheezy LAMP, and installed everything from repo. Thanks for every idea.

2 2

[Dovecot] Authentication Failure (newbie)
by Danny Gorton 08 Jun '14

08 Jun '14

Greetings, I'm am learning about running a mail server and I set up a brand new Ubuntu 14.04 server with postfix and dovecot. I had some initial problems with dovecot not starting, and then with not having proper permissions/access to the various directories and files and pipes, etc, and in the process starting to learn how this thing works. After searching in web-land I seem to have overcome those issues and dovecot and postfix both start and accept connections now (http://wiki2.dovecot.org/TestPop3Installation) However when I check to see if I can authenticate I get Authentication Failed. At the time of these login attempts there are no messages added to syslog or mail.log, dovecot log entries are below. Note I redacted my test user and password values to 'xxxxx', and my domain value to 'domain.com'. Also I'm testing with my plain text password, but I've tried using AUTH PLAIN <base64 encoded uid/pwd>. I have also tried the setup with a default auth domain, and I've tried authenticating with and without the domain name as part of the user name, with the same results. I added the debug settings and disable_plaintext_auth = no to try to solve this issue. Here is my test command set: xxxxx@apacweb:~$ sudo doveadm user xxxxx field valueuserdb lookup: user xxxxx doesn't exist and : xxxxx@apacweb:~$ telnet localhost 110 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK Dovecot (Ubuntu) ready. user xxxxx +OK pass xxxxx -ERR [AUTH] Authentication failed. Here is a cut from the dovecot log: 2014-06-08 01:22:10 auth: Error: passwd-file(xxxxx): stat(uid=vmail gid=vmail home=/home/vmail//xxxxx /etc/dovecot/users) failed: Address family not supported by protocol I figure this is the root cause of this issue and the solution to it is supposedly to tell dovecot to not listen on IPv6 (listen = *), but I did that and it didn't help (see config). Here is a cut from the dovecot.info log: 2014-06-08 00:16:25 auth: Debug: auth client connected (pid=3131) 2014-06-08 01:22:10 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth 2014-06-08 01:22:10 auth: Debug: Read auth token secret from /var/run/dovecot//auth-token-secret.dat 2014-06-08 01:22:10 auth: Debug: passwd-file /etc/dovecot/passwd: Read 1 users in 0 secs 2014-06-08 01:22:10 auth: Debug: master in: USER 1 xxxxx service=doveadm 2014-06-08 01:22:10 auth: Debug: userdb out: NOTFOUND 1 Here is my dovecot config: # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-24-generic x86_64 Ubuntu 14.04 LTS ext4 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain cram-md5 auth_verbose = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no info_log_path = /var/log/dovecot.info listen = * log_path = /var/log/dovecot log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n/Maildir passdb { args = /etc/dovecot/passwd driver = passwd-file } protocols = imap pop3 service auth { executable = /usr/lib/dovecot/auth unix_listener /var/spool/postfix/private/auth-client { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix mode = 0777 user = postfix } user = vmail } service imap-login { chroot = login executable = /usr/lib/dovecot/imap-login user = dovecot } service imap { executable = /usr/lib/dovecot/imap } service pop3-login { chroot = login executable = /usr/lib/dovecot/pop3-login inet_listener pop3 { address = * port = 110 } inet_listener pop3s { address = * port = 995 } user = dovecot } service pop3 { executable = /usr/lib/dovecot/pop3 } ssl = required ssl_cert = </etc/ssl/certs/smtpd.crt ssl_key = </etc/ssl/private/smtpd.key userdb { args = uid=vmail gid=vmail home=/home/vmail/%d/%n /etc/dovecot/users driver = passwd-file } valid_chroot_dirs = /var/spool/vmail protocol pop3 { pop3_uidl_format = %08Xu%08Xv } I'm sure I've done something stupid, but after thrashing about for some days I haven't been able to figure out what it is. Regards, Danny

2 4

Re: [Dovecot] imap-login killed with signal 11 in Dovecot 2.2.13
by Patrick De Zordo 07 Jun '14

07 Jun '14

Same problem here! Updated dovecot some minutes ago from xi.rename-it.nl.. Please resolve it very quick! Having big problems! Thanks, Patrick. > -----Ursprüngliche Nachricht----- > Von: dovecot [mailto:dovecot-bounces@dovecot.org] Im Auftrag von > Thomas Leuxner > Gesendet: Samstag, 7. Juni 2014 17:29 > An: dovecot(a)dovecot.org > Betreff: Re: [Dovecot] imap-login killed with signal 11 in Dovecot 2.2.13 > (feea8645c4d7) > > * Thomas Leuxner <tlx(a)leuxner.net> 2014.06.07 12:15: > > > Latest 2.2.13 HG feea8645c4d7 seems to unexpectedly kill imap-login > sessions: > > I can crash the process at will over a TLS connection with mutt, which I can't > when disabling TLS. So the culprit most-likely is this change: > > http://hg.dovecot.org/dovecot-2.2/rev/09d3c9c6f0ad > > It seems difficult to predict the imap-login process that will crash, hence I > struggle which one to connect GDB to...

1 0

Re: [Dovecot] doveadm index - Bug or expected behaviour?
by Bruno Galindro da Costa 06 Jun '14

06 Jun '14

ok tks! 2014-06-06 3:16 GMT-03:00 Steffen Kaiser <skdovecot(a)smail.inf.fh-brs.de>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Thu, 5 Jun 2014, Bruno Galindro da Costa wrote: > > My ldap config is using the variable %d in base search for domain >> replacement when dovecot will search for users in LDAP. Its works fine for >> dovecot operation. >> > > When an user logs into Dovecot, the login process can extract the domain > part from the login username. > > > But, for doveadm index, not. It ignores that variable and tries to pass a >> base search without domain. So, the search will not working. >> >> This is the command: >> # doveadm -v index -A INBOX >> > > If you iterate all users (-A), doveadm would need to guess all domains and > iterate through them. So, in your case you cannot use -A. However, -u > should work. That is, you call the command for each single user that you've > iterated from LDAP via script. > > base = ou=%d,ou=mail,ou=services,dc=domain >> > [...] > > iterate_filter = >> (&(objectclass=nisMailAlias)(ContaAtiva=TRUE)(!(EmailQuota=0))) >> iterate_attrs = rfc822mailmember=user >> > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU5Fcynz1H7kL/d9rAQI7IggAitRJlAU4olmkTzUqXxrxxPAtF0FMcm0c > PqWdByrNM0aLr1WTIShN7y83OnTwFhznuuTg6oVO6s72KZ6Izo9COOK70kLvoGzZ > G4TyNu9S671hDVWsasuI+FvChGZURM+6E4G+ctsqTSjY8N8MV6hEdwrNhxBWbbfE > nQ0BEMDDaM0Qeycyiy59nhlOkLiSkv40P2NnOekkSvogxb3rpxt9FQ6vIrBkCxJd > K1xlwAWzg7Hr4LIUw3PJm0YjT7T4H+1AmiIm7iaAnT8My/9SSB9WCtmFQpzFNWOD > tpKc3RcQJykJMpC4oKjgTi0Vh6PTl6g3xMdA9yJ2jmgpLVqpU2fNKw== > =l3yY > -----END PGP SIGNATURE----- > -- Att. Bruno Galindro da Costa

1 0

[Dovecot] Running dovecot under Cygwin
by Manolis Spanakis 06 Jun '14

06 Jun '14

Hi, In http://wiki2.dovecot.org/DovecotFeatures I found the following statement regarding devcot support of cygwin: Cygwin works after a few code changes, but doesn't support SCM_RIGHTS I downloaded "dovecot-2.2.13.tar.gr" and tried to compile it under cygwin version 1.7.30 (0.272/5/3) CYGWIN_NT-6.3-WOW642.580 (32-bit). As I executed the: $./configure I got the following error: error: fd passing is required for Dovecot to work If I bypass this error by changing "configure" I get no other errors either in "configure" or "make". It seems that "src/lib/fdpass.c" is the only library incompatible with cygwin. Is there any file version available that provides a solution? Thank you in advance, Manolis Spanakis

1 0

[Dovecot] CRAM-MD5 authentication memory leak problem.
by Kenji Tonami 06 Jun '14

06 Jun '14

I used dovecot Auth daemon for postfix SMTP Auth. I saved clear password to OpenLDAP, then I set up that as the password will be used. There ware no trouble when authentication had sucessed. But when authentication failed by using "CRAM-MD5", it caused increasing memory allocation of dovecot auth daemon. In case of using "PLAIN" or "LOGIN", there were no problem even if authentication had failed. I got same result on dovecot-2.0.9(RHEL6) and dovecot-2.2.13. Does anyone know similar case? I tried restarting dovecot Auth daemon by using service_count parameter in service auth settings. When authentication failed, message on postfix was as follows: ** 535 5.7.8 Error: authentication failed: "CRAM-MD5 string" When authentication failed and restarting dovecot auth daemon at the same time, message on postfix was changed as follows: ** 535 5.7.8 Error: authentication failed: Connection lost to authentication server It looks like that the failed authentication request is suspended by restarting auth daemon. -- config (10-auth.conf) auth_mechanisms = plain login cram-md5 -- -- config (10-master.conf) service auth { executable = auth unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } } -- -- auth-ldap.conf.ext passdb { driver = ldap args = /etc/dovecot/ldap-passdb.conf.ext } -- -- ldap-passdb.conf.ext host = xxx.xxx.xxx.xxx dn = LDAP Manager DN dnpass = Manager DN password base = ou=mail,dc=xxxxxx,dc=xx scope = subtree pass_attrs = mailID=user,mailClearPassword=password pass_filter = (mailID=%u) auth_bind = no default_pass_scheme = plain -- Thanks. -- Kenji Tonami

1 0

Re: [Dovecot] Outlook 2007 & 2010 hangs in v2.2?
by Joseph Tam 06 Jun '14

06 Jun '14

Timo Sirainen <tss(a)iki.fi> writes: > Has anybody noticed Outlook 2007 & 2010 (but apparently not 2013) > hanging IMAP connections with Dovecot v2.2 (but not v2.1) when they're > FETCHing large mails? I can't think of any reasonable explanation for > this. It's a shot in the dark, but I had a problem with a different client, where semi-large attachments was problematic. It turned out to be a TCP scaling problem. If a router/firewall drops packets with a TCP scaling option set, the endpoints disagree on how many outstanding non-ACK packets are allowed, resulting in timeouts. http://support.microsoft.com/kb/935400 http://en.wikipedia.org/wiki/TCP_window_scale_option The Microsoft KB does hint those versions of Outlook may be affected, but I can't figure out why there would be a difference between Dovecot 2.1 and 2.2. Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] Sharing folder with others
by Claudinei Santos 05 Jun '14

05 Jun '14

Hello, The sharing folders with dovecot works, but when the user that i shared the folder reads any e-mails in the folder, all my subcribed folder (the folders that i do not shared with this user) is unsubcribed from my account. The only folders that remains is the default ones ( inbox, trash, spam and sent) and the folder that i shared with that user. my configurations: # separator for master-users, example: "login_user*master_user -> user(a)domain.tld*masteruser auth_master_user_separator = * passdb passwd-file { driver = passwd-file args = /etc/dovecot-masterusers master = yes } namespace private { type = private separator = / prefix = #location defaults to mail_location. inbox = yes } namespace shared { type = shared separator = / prefix = Share Folders/%%u/ location = maildir:/var/spool/mail/vmail/%d/%%n:INDEX=/var/spool/mail/vmail/%d/%n/shared/%%u subscriptions = yes list = children } # cat /etc/dovecot-postlogin #!/bin/bash export MASTER_USER="$USER" exec /usr/lib64/dovecot/imap "$@" Can someone help me out with this? Thanks in advance.

1 0