- dovecot - dovecot.org

[Dovecot] v1.2.13 released
by Timo Sirainen 25 Jul '10

25 Jul '10

http://dovecot.org/releases/1.2/dovecot-1.2.13.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.13.tar.gz.sig This release fixes a bug in ACL plugin, which could be considered a security bug: If Maildir is used with default settings (INBOX is same as Maildir root dir) and user set some ACLs to INBOX, those ACLs were copied to all newly created mailboxes. This should have been done only for "default ACLs", but with Maildir the INBOX directory is the same as the default ACL directory, so this mixup happened. This bug exists only in v1.2.x releases. Other fixes: - Fixed iconv() crash when it was processing several kilobytes of broken continuous input. This mainly could have caused a problem with IMAP SEARCH. Possibly also with some Sieve checks. - If MIME encoded-words contained line feeds, Dovecot logged cache corruption errors. - mbox: Renaming mailbox under newly created dir didn't move index directory. - mbox: When generating envelope to From_-line, don't append a second @owndomain if username already has one.

2 1

Re: [Dovecot] (Single instance) attachment storage
by Damon Atkins 25 Jul '10

25 Jul '10

Just keep in mine Signed Emails, the email contents needs to be present back to the client as it came, so the client says the email has not been altered.

2 1

[Dovecot] Unknown password scheme SSHA512
by Patrick Westenberg 24 Jul '10

24 Jul '10

Hello, I installed dovecot via Debians apt package manager. The passwords are stored as SHA256 hash in a PostgreSQL database. default_pass_scheme in dovecot-sql.conf is set to SHA256. However, smtp-auth fails. Jul 24 00:31:07 smtp01 dovecot: auth(default): sql(mail(a)jasbafliesen.de): Unknown password scheme SHA256 Can anybody help me? Regards Patrick

2 2

Re: [Dovecot] SSL / TLS Problem
by Leander S. 23 Jul '10

23 Jul '10

Am 23.07.10 02:59, schrieb Andrew Bruce: > eel free to post this to the running conversation on the list (strip my > email address from this email though please) The issue was a case sensitive typo. When Setting up your Thunderbird don't type in eMail Addresses & Usernames including uppercase letters! DON'T: User(a)Domain.tld BUT therefore: user(a)domain.tld I faced that Problem only when I was using dyndns as domain service provider.

3 5

[Dovecot] Shared folders issue
by Emmanuel Gonzalez Carmona 23 Jul '10

23 Jul '10

Hello guys, I have an issue with shared folders: 1) The USERA shares his INBOX with USERB 2) USERB subscribes the USERA share without problems. 3) USERA deletes all his / or some directories from his INBOX (Trash, Drafts and Sent) 4) USERA logouts and makes login, so dovecot recreates the folders. 5) USERB gains access to subscrive those folders (Trash, Drafts and Sent) this is my namespace configuration: ... namespace private { separator = / prefix = inbox = yes #list = yes #subscriptions = yes } namespace shared { separator = / prefix = "shared/%%u/" location = maildir:/maildirs/%%d/%%u/Maildir subscriptions = no list = children } ... any ideas? Thanx in advance. -- Emmanuel Gonzalez Babel S.r.l. - http://www.babel.it <http://www.babel.it/>

2 1

[Dovecot] Go Away Message after the first successful login on proxy server
by Tomislav Mihalicek 23 Jul '10

23 Jul '10

hello i have a dovecot 1.2.11 and i have implementation of 2 dovecot machines, one proxy one storage part. everything is working fine, i only have one question regarding the message that should go away after the first successful login on proxy server. how to remove it on proxy server? May 7 16:04:19 proxy-server dovecot: pop3-login: proxy(tmihal(a)example.com): started proxying to 192.168.1.100:110: user=<tmihal(a)example.com>, method=PLAIN, rip=192.168.22.222, lip=192.168.1.100:109 [root@dougie:/usr/local/src/dovecot-1.2-managesieve]/etc/init.d/dovecot restart Restarting DovecotIf you have trouble with authentication failures, enable auth_debug setting. See http://wiki.dovecot.org/WhyDoesItNotWork This message goes away after the first successful login. -- View this message in context: http://old.nabble.com/Go-Away-Message-after-the-first-successful-login-on-p… Sent from the Dovecot mailing list archive at Nabble.com.

2 3

[Dovecot] dovecot director service
by Xavier Pons 23 Jul '10

23 Jul '10

hi, we are using the dovecot-rc1 version, and we are testing the director service, as there is little documentation on this service, a pair of questions.. if i'm not wrong, the proxy_maybe it's not implemented, yet? will be soon? this limitation does not allow use the same two directors servers like mail backend servers? the fairlure of one director server it's automatically detected or require manual intervention? thanks and sorry for so many questions... Xavier

4 18

[Dovecot] Doveadm protocol for parallel user processing
by Timo Sirainen 23 Jul '10

23 Jul '10

A lot of doveadm commands process users' mails. They can optionally process either a single user or multiple users (e.g. -A = all, -u '*(a)domain.org'). For example to expunge old mails from everyone's Trash, you'd use: doveadm expunge -A mailbox Trash savedbefore 30d The problem is, this doesn't work with the new director way of doing proxying. Only a single server can access a user's mails safely, so this command can't be run safely if there are multiple mail servers. It's also a bit problematic for regular proxying, but it's especially problematic with director: Since users aren't permanently assigned anywhere, it's not even possible to build a user <-> host mapping and run the command only for those users in their assigned server. First I started thinking about adding another lib-storage backend that supports proxying to another server, maybe via IMAP or maybe via another protocol. Maybe I should do that some day anyway, but it seems a bit complex for this task. Then I also realized that even if all users are on local server, it would probably finish faster if doveadm could handle users in parallel in separate processes (due to disk I/O latencies and maybe other latencies). So, it seems like it would be a good idea to make doveadm internally a client/server architecture. When you start doveadm, it would be only the "brain" part, which connects to the worker doveadms either via local UNIX socket or to remote servers. Admin could configure how many doveadm worker processes the brain should connect per server (could be a per-server setting). So, what's needed to make this happen? 1. The actual client/server split and the protocol. Probably can be really simple and won't be anything interesting. Or maybe it becomes more interesting once I start thinking about it more, we'll see. :) 2. Authentication. 3. TLS-protection? After merging code from dovecot-2.0-sslstream branch this should be pretty easy. Although Dovecot should finally then add support for checking that CommonName/etc match the server name. Authentication -------------- For local UNIX sockets that are 0600 root, the authentication wouldn't be necessary. It could internally check that if the listener socket has these permissions, it would just announce that doveadm is already authenticated. Otherwise, and especially for TCP connections, there should be authentication. I was thinking about using already existing master users for this. Doveadm client says "I'm <masteruser>, my password is <pass>, and I want to access <user>'s mails". Auth process does the authentication and replies either success or failure, just like for similar IMAP/POP3/etc logins. It's possible to restrict what users a master user can log in as, like admin(a)domain.org could only log in as *(a)domain.org. This means that you could also enable doveadm protocol for external users, and let the domain administrators use doveadm directly to manage their own domain's users. PLAIN authentication mechanism would be easy to support. But this might be a good time to also introduce client side SASL library to Dovecot to support other auth mechanisms. But then again, maybe it doesn't really matter.. Privilege dropping ------------------ I hate it that with multiple UIDs doveadm processes currently have to be run as root and they only temporarily drop privileges. With client/server split it would be possible to get rid of this. Each doveadm worker process would then handle only a single user and then exit. This would be optional similar to how login processes are now, e.g.: service doveadm { # 1 = default = one user access per process, 0 = unlimited user accesses service_count = 1 } LMTP privilege dropping ----------------------- Completely unrelated to doveadm, but due to the above doveadm privilege dropping thinking I also started thinking about LMTP. It's also annoying that it runs as root, and only temporarily drops privileges. It could also avoid this by saving a mail only to a single user per process. The problem is that there can be multiple RCPT TO:s in a same session, but this can be handled by treating them similarly than when using LMTP proxying: Just connect to localhost again and proxy the mail there for each user separately. This could also be optionally done only when the process UID differs from the destionation user's UID. When? ----- These are too invasive changes to v2.0, so I guess they'll wait until v2.1. Luckily there won't be any hugely destabilizing changes going into v2.1, so maybe v2.1.0 release won't be too many months after v2.0.0. :)

1 2

[Dovecot] managesieve login fails
by Leander S. 23 Jul '10

23 Jul '10

Hi, when I try to make use of the managesieve capability maillog always shows: server dovecot: managesieve-login: Panic: file client.c: line 449 (client_set_auth_waiting): assertion failed: (client->to_auth_waiting == NULL) server dovecot: dovecot: child 5926 (login) killed with signal 6 (core not dumped) (ip=192.168.1.233) ... and Thunderbirds remote sieve optimizing plugin won't connect ... Otherwhise IMAP & POP authentication, etc. ... is working proper.

2 2

[Dovecot] dovecot 2.0rc2 [SERVERBUG] When trying to remove a folder which contains a subfolder
by Sven Kirmess 23 Jul '10

23 Jul '10

I'm going to risk to report something stupid again and waste resources... but [SERVERBUG] sounds like it should not happen. :) g create test g OK Create completed. h create test/test2 h OK Create completed. i list "test" "*" * LIST (\HasChildren) "/" "test" * LIST (\HasNoChildren) "/" "test/test2" i OK List completed. j delete "test" j NO [SERVERBUG] Internal error occurred. Refer to server log for more information. [2010-07-17 22:57:48] The log has the following entry: Jul 17 22:57:48 azati dovecot: [ID 583609 mail.error] imap(ski): Error: rmdir(/l/dovecot/ski/dbox/mailboxes/test) failed: File exists Which is correct $ ls /l/dovecot/ski/dbox/mailboxes/test/ test2 Deleting the mailboxes in sync does work. k delete "test/test2" k OK Delete completed. l delete "test" l OK Delete completed. m list "test" "*" m OK List completed. $ dovecot -n # 2.0.rc2: /etc/opt/dovecot/dovecot/dovecot.conf # OS: SunOS 5.10 i86pc zfs first_valid_uid = 100 mail_location = mdbox:/l/dovecot/%u/dbox passdb { driver = pam } protocols = imap service imap-login { inet_listener imap { port = 0 } } service imap { vsz_limit = 1073741824 } ssl = required ssl_cert = </etc/opt/dovecot/dovecot/certs/dovecot.pem ssl_key = </etc/opt/dovecot/dovecot/private/dovecot.pem userdb { driver = passwd } verbose_proctitle = yes protocol imap { imap_client_workarounds = tb-extra-mailbox-sep }

2 2