- dovecot - dovecot.org

Re: [Dovecot] Bug report: "doveadm rename" encodes special characters wrongly in mUTF-7 (in fs)
by megodin＠inboxalias.com 24 Sep '13

24 Sep '13

> If doveadm says it's invalid UTF-8, it's invalid UTF-8. I guess your > terminal isn't actually using UTF-8 then, but something else. ("locale" > output should say something about UTF-8.) I guess doveadm could also > automatically translate parameters to UTF-8, but that's a bit annoying > to implement. You were absolutely right. After thorough testing I could make up the problem to the SSH-Client PuTTY I was using on a Windows machine while testing. The default "remote character setting" is "ISO-8859-1:1998 (Latin-1, West Europe)", when re-setting to "UTF-8", opening a new shell and testing the "doveadm mailbox rename ..." with german umlauts just works fine then. (Just for the sake of completeness, the "locale" settings were set to (LANG=de_DE.utf-8) globally in /etc/sysconfig/i18n per default.) > The problem here is that * is expanded by your shell, not doveadm. > And it expands into Tr&-AOQ-sh as it's in the filesystem, but that's > only the mUTF-7 encoding of it. The UTF-8 version of the name is > Tr&AOQ-sh. So doveadm only sees that you attempted to resync a > nonexistent mailbox. Using '*' with quotes would work, since doveadm > would do the expansion then. Thanks for pointing that * / '*' issue out. I now unterstand that the "doevadm mailbox rename" converts the input to UTF _before_ applying it in the filesystem. Now it makes sense that doveadm mailbox rename -u user 'Trash' 'Tr&AOQ-sh' must be expanded to Tr&-AOQ-sh. The "-" character directly after the "&"in Tr&-AOQ-sh comes from a special mUTF-Specification (as stated in RFC 3501, section 5.1.3): "In modified UTF-7, printable US-ASCII characters, except for "&", represent themselves; that is, characters with octet values 0x20-0x25 and 0x27-0x7e. The character "&" (0x26) is represented by the two-octet sequence "&-"." So e.g. if I wanted a german umlaut to be encoded in the filesystem, I must enter it directly into dovedm instead of the UTF encoded value. One small point left... > The UTF-8 version of the name is Tr&AOQ-sh Just for understanding - "Tr&AOQ-sh" is IMHO UTF-7, not UTF-8. Accordingly to what stated before, "Tr&-AOQ-sh" and "Tr&AOQ-sh" are encoded both the same (UTF-7), the first seen in clients as "Tr&AOQ-sh" and the second as "TrÃ¤sh". Thanks for all your help! Megodin --- Alle PostfÃ¤cher an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen _________________________________________________________________ Send and receive anonymous emails to your inbox with InboxAlias. http://www.inboxalias.com

1 0

[Dovecot] Linux SO_REUSEPORT
by Timo Sirainen 24 Sep '13

24 Sep '13

I just read about Linux v3.9's SO_REUSEPORT feature and decided to implement it for Dovecot. Would be interesting to know how it works for people :) It's going to be in v2.2.6, which I'm planning on releasing tomorrow. Note especially the warning about the bug: http://hg.dovecot.org/dovecot-2.2/rev/a991a0547daa So the idea is that you'd do something like: service imap-login { inet_listener imap { reuse_port = yes } process_min_avail = 4 # number of CPU cores } And the load should be distributed more evenly to the processes.

4 4

[Dovecot] Fwd: lmtp
by Lampa 24 Sep '13

24 Sep '13

Hello, using dovecot with postfix with mysql. Some domains have alias. Local delivery is realized over lmtp. When lmtp delivery to aliased domains, it takes bad mail_location - it takes aliased instead real domain, so lmtp is creating domain and user directory. Lmtp doesn't make sql lookup. I need lmtp delivery to real domain and i don't want to create symlinks. mail_location = maildir:/home/mail/%d/%n/Maildir real domain: domain1.com aliased domain: domain2.com rcpt: user(a)domain2.com lmtp deliver message to /home/mail/domain2.com/user/Maildir instead /home/mail/domain1.com/user/Maildir -- Lampa

3 9

[Dovecot] Permission error
by Koenraad Lelong 24 Sep '13

24 Sep '13

Hi, I'm migrating an existing dovecot (1. series) to new hardware. The new dovecot is a 2. series. I copied the old config and did a doveconf -n -c /etc/dovecot/dovecot.conf > dovecot-2.conf Then I moved the dovecot-2.conf to dovecot.conf and restarted dovecot. When Postfix tries to deliver a message I get this error : 2013-09-16 11:00:10 auth: Fatal: net_connect_unix(auth-worker) in directory /run/dovecot failed: Permission denied (euid=65534(nobody) egid=65534(nogroup) missing +r perm: /run/dovecot/auth-worker, dir owned by 0:0 mode=0755) 2013-09-16 11:00:10 master: Error: service(auth): command startup failed, throttling I tried different things with /run/dovecot/auth-worker, but the error remains. I tried to chmod 777 the socket, I chown-ed to dovecot:dovecot, vmail:vmail. What am I missing ? AFAIK the sql-tables are OK. Thanks. doveconf -n is this : # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.5.0-39-generic x86_64 Ubuntu 12.04.3 LTS auth_debug = yes auth_mechanisms = plain login auth_verbose = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_uid = 499 info_log_path = /var/log/dovecot.debug last_valid_uid = 499 log_path = /var/log/dovecot log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_location = maildir:/var/vmail/%u 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 passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = vmail mode = 0660 user = vmail } user = nobody } service imap-login { executable = /usr/lib/dovecot/imap-login inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } } service imap { executable = /usr/lib/dovecot/imap } service pop3-login { executable = /usr/lib/dovecot/pop3-login inet_listener pop3 { address = * port = 110 } } service pop3 { executable = /usr/lib/dovecot/pop3 } ssl_ca = </etc/postfix/certificate/cacert.org.pem ssl_cert = </etc/postfix/certificate/mailbox.pem ssl_key = </etc/postfix/certificate/mailboxkey.pem userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_ssl = yes protocol imap { imap_max_line_length = 64 k } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol sieve { managesieve_logout_format = bytes ( in=%i : out=%o ) } protocol lda { auth_socket_path = /var/run/dovecot/auth-master info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-err.log mail_plugins = sieve postmaster_address = some-one(a)ace-electronics.be sendmail_path = /usr/lib/sendmail }

2 4

[Dovecot] doveadm mailbox create error codes
by Micah Anderson 24 Sep '13

24 Sep '13

Hello, I'm trying to find out what the different 'doveadm mailbox create' error codes are. I've been looking through the source, but I can't seem to find them. I did determine that '65' happens when "Error: Can't create mailbox x: Mailbox already exists", but I've also received error 67, and the more mysterious error code 16640. Thanks for any pointers! micah

2 1

Re: [Dovecot] Bug report: "doveadm rename" encodes special characters wrongly in mUTF-7 (in fs)
by megodin＠inboxalias.com 24 Sep '13

24 Sep '13

Hi there Timo, first of all thank you for taking your time for support! > Forget about mUTF-7 with Dovecot. It's an IMAP-protocol relic, and > Dovecot is trying to get rid of it in as many places as possible. > Although by default the filesystem users mUTF-7, but that can also > be changed with a setting. Thanks for clarifying this. > I suspect your shell is breaking the 8bit chars into invalid UTF-8. I > just tried and it works fine with me. Sorry, we got confusion here... apparently my (lousy) freemail provider which I use to post on this mailinglist doesn't send some special characters etc. unaltered exactly as I typed - so I made a console screenshot of the doveadm rename problem to make things clear. Please have a look here, it will reveal the doveadm rename problem (and that my shell is working fine): http://i.imgur.com/08wKji4.png > > To get things worse, when renaming the mailfolder in Thunderbird to > > "geschÃÂ¤ftliches" it gets correctly written in the filesystem as > > "gesch&AOQ-ftliches"- but afterwards it's NOT found anymore in the > > dovecot index, e.g. when trying doveadm force-resync -u user it is > > not listed anymore (untilback-renaming in fs to the name it was > > indexed before). > Folders aren't indexed by default (mailbox_list_index=no) and > force-resync doesn't affect them. Are you saying > "doveadm mailbox list -u user" doesn't show some folder? I'm not > aware of any bugs related to this. No, the "doveadm mailbox list -u user" works just fine. BUT - I'm still wondering about the resync issue - As I understand the "doveadm force-resync -u user *" command rebuilds the index for the MAILS within the mailfolders? If so, how can the resync be done if the mailfolder itself is not found by doveadm anymore? > I'd need to get some more specifics. Show show exists in filesystems > and what commands don't produce expected results (and what they > produce instead). For clearing up my point, I made another console screenshot with red markings to point out the problem (bug). Please have another look here: http://i.imgur.com/icPfys9.png Thanks for your support, Megodin --- Alle PostfÃ¤cher an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen _________________________________________________________________ Send and receive anonymous emails to your inbox with InboxAlias. http://www.inboxalias.com

2 1

[Dovecot] can't dovecot tls/ssl to openldap
by 牧原 24 Sep '13

24 Sep '13

Hi, I want to dovecot connect to openldap with ssl/tls, and got error. When without tls/ssl, it works ok. from /var/log/maillog got: Sep 24 05:38:03 mail dovecot: auth: Error: LDAP: ldap_start_tls_s() failed: Connect error Sep 24 05:38:03 mail dovecot: auth: Error: LDAP: ldap_start_tls_s() failed: Can't contact LDAP server Sep 24 05:38:03 mail dovecot: auth: Error: LDAP: ldap_start_tls_s() failed: Can't contact LDAP server Sep 24 05:38:05 mail dovecot: pop3-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<muyuan>, method=PLAIN, rip=192.168.100.99, lip=10.10.120.20, TLS: Disconnected, session=<wSvD1RPnWwDAqGRj> Sep 24 05:38:11 mail dovecot: auth: Error: LDAP: ldap_start_tls_s() failed: Can't contact LDAP server Sep 24 05:38:13 mail dovecot: pop3-login: Disconnected (auth failed, 1 attempts in 6 secs): user=<muyuan>, method=PLAIN, rip=192.168.100.99, lip=10.10.120.20, TLS: Disconnected, session=<2T761RPnXADAqGRj> But when I use ldapsearch, it seems also ok I use this from dovecot host ldapsearch -D "cn=dovecot,ou=bindusers,dc=smuy,dc=net" -W -H ldap://ldap.sv. hm -b "ou=accounts,dc=smuy,dc=net" �CZZ it works ok So I have no idea where to check? Or how can I got more detailed log from dovecot for that connection Sep 24 05:38:03 mail dovecot: auth: Error: LDAP: ldap_start_tls_s() failed: Connect error Because I use ldapsearch both tls/ssl works well, why dovecot connect error? What��s the detail happen in this connection? Here is my dovecot-ldap.conf.ext: # This file is commonly accessed via passdb {} or userdb {} section in # conf.d/auth-ldap.conf.ext # Space separated list of LDAP hosts to use. host:port is allowed too. #hosts = ldap.sv.hm #uris = ldaps://ldap.sv.hm:636/ uris = ldap://ldap.sv.hm:389/ dn = cn=dovecot,ou=bindusers,dc=smuy,dc=net dnpass = 1qaz2wsx #sasl_bind = no #sasl_mech = #sasl_realm = #sasl_authz_id = # Use TLS to connect to the LDAP server. tls = yes #tls = no tls_ca_cert_file = /etc/ssl/certs/ca/signing-ca.crt tls_ca_cert_dir = /etc/ssl/certs/ca #tls_cipher_suite = # TLS cert/key is used only if LDAP server requires a client certificate. #tls_cert_file = /etc/ssl/certs/mail.crt #tls_key_file = /etc/ssl/private/mail.key # Valid values: never, hard, demand, allow, try #tls_require_cert = never See some suggestions! Great thanks! muyuan

1 0

[Dovecot] dovecot 2.2.5 with plugin listescape and shared mailbox with dot in INBOX
by romain 23 Sep '13

23 Sep '13

Hi list, I have a problem with dovecot 2.2.5 and nightly (latest 20130923) with : * plugin listescape enabled * shared mailbox * and mail_shared_explicit_inbox = no Problem is I can't get list of mails in INBOX of my shared users. For example : ---------------------------------------------------------- 2013-09-23 22:20:06 imap-login: Info: Login: user=<roms>, method=PLAIN, rip=192.168.0.203, lip=192.168.20.200, mpid=6127, TLS, session=<R8D9vhLn3ADAqADL> 2013-09-23 22:20:06 imap: Debug: Loading modules from directory: /usr/local/lib/dovecot 2013-09-23 22:20:06 imap: Debug: Module loaded: /usr/local/lib/dovecot/lib01_acl_plugin.so 2013-09-23 22:20:06 imap: Debug: Module loaded: /usr/local/lib/dovecot/lib02_imap_acl_plugin.so 2013-09-23 22:20:06 imap: Debug: Module loaded: /usr/local/lib/dovecot/lib20_autocreate_plugin.so 2013-09-23 22:20:06 imap: Debug: Module loaded: /usr/local/lib/dovecot/lib20_listescape_plugin.so 2013-09-23 22:20:06 imap: Debug: Module loaded: /usr/local/lib/dovecot/lib20_zlib_plugin.so 2013-09-23 22:20:06 imap: Debug: Module loaded: /usr/local/lib/dovecot/lib30_imap_zlib_plugin.so 2013-09-23 22:20:06 imap: Debug: Added userdb setting: plugin/acl_groups=Exchange Services,Exchange Domain Servers,Propriétaires créateurs de la stratégie de groupe,Administrateurs du schéma,Admins du domaine,Administrateurs de l'entreprise,Administrators,Users,roms 2013-09-23 22:20:06 imap(roms): Warning: autocreate plugin is deprecated, use mailbox { auto } setting instead 2013-09-23 22:20:06 imap(roms): Debug: Effective uid=471, gid=471, home=/home/dovecot/dovecot//mail/roms 2013-09-23 22:20:06 imap(roms): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/home/dovecot/dovecot//mail/roms/Maildir 2013-09-23 22:20:06 imap(roms): Debug: maildir++: root=/home/dovecot/dovecot//mail/roms/Maildir, index=, indexpvt=, control=, inbox=/home/dovecot/dovecot//mail/roms/Maildir, alt= 2013-09-23 22:20:06 imap(roms): Debug: acl: initializing backend with data: vfile 2013-09-23 22:20:06 imap(roms): Debug: acl: acl username = roms 2013-09-23 22:20:06 imap(roms): Debug: acl: owner = 1 2013-09-23 22:20:06 imap(roms): Debug: acl vfile: Global ACL directory: (none) 2013-09-23 22:20:06 imap(roms): Debug: Namespace : type=shared, prefix=Other Users/%u/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=no location=maildir:%h/Maildir:INDEX=~/Other Users/%u 2013-09-23 22:20:06 imap(roms): Debug: shared: root=/usr/local/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= 2013-09-23 22:20:06 imap(roms): Debug: acl: initializing backend with data: vfile 2013-09-23 22:20:06 imap(roms): Debug: acl: acl username = roms 2013-09-23 22:20:06 imap(roms): Debug: acl: owner = 0 2013-09-23 22:20:06 imap(roms): Debug: acl vfile: Global ACL directory: (none) 2013-09-23 22:20:06 imap(roms): Debug: Namespace : type=public, prefix=Shared Folders/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=no location=maildir:/home/dovecot/dovecot//public:INDEX=~//public 2013-09-23 22:20:06 imap(roms): Debug: maildir++: root=/home/dovecot/dovecot//public, index=/home/dovecot/dovecot//mail/roms//public, indexpvt=, control=, inbox=, alt= 2013-09-23 22:20:06 imap(roms): Debug: acl: initializing backend with data: vfile 2013-09-23 22:20:06 imap(roms): Debug: acl: acl username = roms 2013-09-23 22:20:06 imap(roms): Debug: acl: owner = 0 2013-09-23 22:20:06 imap(roms): Debug: acl vfile: Global ACL directory: (none) 2013-09-23 22:20:07 imap(roms): Debug: auth input: l.dupont system_groups_user=l.dupont uid=471 gid=471 home=/home/dovecot/dovecot//mail/l.dupont 2013-09-23 22:20:07 imap(roms): Debug: maildir++: root=/home/dovecot/dovecot//mail/l.dupont/Maildir, index=/home/dovecot/dovecot//mail/l.dupont/Other Users/l.dupont, indexpvt=, control=, inbox=/home/dovecot/dovecot//mail/l.dupont/Maildir, alt= 2013-09-23 22:20:07 imap(roms): Debug: acl: initializing backend with data: vfile 2013-09-23 22:20:07 imap(roms): Debug: acl: acl username = l.dupont 2013-09-23 22:20:07 imap(roms): Debug: acl: owner = 1 2013-09-23 22:20:07 imap(roms): Debug: acl vfile: Global ACL directory: (none) 2013-09-23 22:20:07 imap(roms): Debug: maildir++: root=/home/dovecot/dovecot//mail/l.dupont/Maildir, index=/home/dovecot/dovecot//mail/roms/Other Users/l.dupont, indexpvt=, control=, inbox=/home/dovecot/dovecot//mail/l.dupont/Maildir, alt= 2013-09-23 22:20:07 imap(roms): Debug: acl: initializing backend with data: vfile 2013-09-23 22:20:07 imap(roms): Debug: acl: acl username = roms 2013-09-23 22:20:07 imap(roms): Debug: acl: owner = 0 2013-09-23 22:20:07 imap(roms): Debug: acl vfile: Global ACL directory: (none) 2013-09-23 22:20:07 imap(roms): Debug: acl vfile: file /home/dovecot/dovecot//mail/l.dupont/Maildir/.Other Users.l\2edupont/dovecot-acl not found ---------------------------------------------------------- Last line see that the Shared Mailbox "Other Users/l.dupont" is converted to "Other Users.l\2edupont" Note, that this does not append when I trie to access a subfolder like "Other Users/l.dupont/Sent" If I set "mail_shared_explicit_inbox = yes" with plugin listescape, I can access "Other Users/l.dupont/INBOX" If I remove "listescape" from my plugin directive, I can access the INBOX of "Other Users/l.dupont" Thanks for any help :) Regards, Romain

1 0

[Dovecot] Vacation message and DMARC validation
by Gerson Moraes 23 Sep '13

23 Sep '13

Greetings, I have found an issue in the interaction between sieve vacation messages and the SPF, DKIM and DMARC email validation systems. For example, let's say we have a message coming from a(a)a.com to b(a)b.com at a server imap.mydomain.com. The account b(a)b.com has a vacation rule in sieve, and that generates an autoresponse to a(a)a.com. Our problem begins with the definition of section-5.1 in RFC5230 <https://tools.ietf.org/html/rfc5230#section-5.1>. It says that the envelope-from in vacation messages should be set to <>. This is the behavior currently implemented in Dovecot. We have recently added DMARC's authentication to our e-mail servers. DMARC needs one of the two authentication to pass, either SPF or DKIM. SPF works, but not the way DMARC needs it to. DMARC needs a valid SPF record that also matches the "From:" header. In this message, there are no envelope-from, so there are no domain to validate. This is the reason we use SRS to rewrite envelope-from (to do that we use the server address). The last option is to use DKIM authentication. We have clustered SMTP servers. So, in order to make a DKIM signature, the vacation message needs to be sent to the right server. That is, the server where the key to account b(a)b.com is available. To do that, we are implementing a modification to Dovecot source allowing the use of the envelope-from. The modified envelope-from will be used with the Postfix option "sender_dependent_relayhost_maps" in order to choose the right cluster. This does not break RFC5230, because the use of null sender is only a recommendation. I would like to know if a patch to the main project would be appreciated. Could you also please confirm if there are any future plans involving this feature, like an optional configuration for custom envelope-from? Thanks in advance, Gerson Moraes Digirati

3 5

[Dovecot] default client_limit
by Micah Anderson 23 Sep '13

23 Sep '13

I recently upgraded my dovecot from 2.1 to 2.2, and when I started, I received this message: doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (1024) Searching through my configs, I do not have 1024 set anywhere. In order to stop this I set client_limit=1024 in my auth{} block... this seemed odd that the defaults disagreed with each other. However, it made me realize that my system could probably handle more, if it were properly tuned, and the different limit settings at their defaults are probably smaller than they could be for my server and the load it is under. So, I'm wondering how I can accurately set some of these values? The different possible things that can be set are: default_process_limit (for some reason I have this set to 256) default_client_limit (default) default_vsz_limit (I have this set to 512M) for the imap-login service, I have: service_count = 0 process_min_avail = 10 vsz_limit = 512M for service pop3-login, these are set: service_count = 0 process_min_avail = 10 vsz_limit = 512M for service imap, process_limit = 2048 service auth, I've just set the client_limit=1024 I've also got a ulimit -n set to 2048 and in my sysctl.conf, I have the following: fs.inotify.max_user_instances = 2048 because I was seeing this in the logs: Warning: Inotify instance limit for user 8 (UID mail) exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_instances What I am looking for is a few things: . is there a formula for setting a proper value for some of these? . will dovecot warn me when I've reached a limit, so I can adjust these? thanks for any suggestions or improvements, I'm pretty sure this system can handle a lot more than it is doing right now, I just am unclear on how to tune it up to do that. micah

1 0