- dovecot - dovecot.org

[Dovecot] Authentication mechanism and Password scheme
by Костырев Александр Алексеевич 10 Apr '12

10 Apr '12

Good day! I'm just trying to figure out that my understanding of subject is correct. So, if I want to store passwords in my database encrypted with SSHA512 scheme, my only choice for Authentication mechanism is plaintext? Thanks in advance! -- С уважением, Костырев Александр системный администратор ЗАО "Сервер-Центр" тел.: (423) 262-02-62 (доб. 2037) факс: (423) 262-02-10

3 3

[Dovecot] Per IP virtual domain
by Stéphane Locatelli 10 Apr '12

10 Apr '12

Hello, My dovecot server (2.0.18 on FreeBSD 9) has multiple interface. I would like to configure the authentication (pop and imap) to append different domain according to the local IP address. I've tested this: local 10.0.0.1 { auth_default_realm = domain1.com } local 10.0.0.2 { auth_default_realm = domain2.com } But it doesn't work. I get this error message: doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/dovecot.conf line 58: Auth settings not supported inside local/remote blocks: auth_default_realm -- Stephane Locatelli

2 2

[Dovecot] 2.0/2.1 - different behavior for LIST-EXTENDED
by Peter Mogensen 10 Apr '12

10 Apr '12

Hi Timo, We are sitting here wondering if this difference in behaviour between dovecot 2.0.17 and 2.1.3 is intended. When you create a folder, subscribe to it and rename it (without changing the subscription) these are the behaviours: For 2.0.17: . list (SUBSCRIBED) "" "*" RETURN (STATUS (MESSAGES)) * LIST (\Subscribed \NonExistent) "." "INBOX.test" For 2.1.3: . list (SUBSCRIBED) "" "*" RETURN (STATUS (MESSAGES)) * LIST (\Subscribed) "." "INBOX.test" * NO Mailbox doesn't exist: test If you don't use rfc5819 the folder will just get silently ignored by dovecot 2.1.x, but if you actually try to get the number of messages you'll get the error. It seems to me from reading rfc5258 that the 2.0.x behaviour is the correct ?? /Peter

2 1

[Dovecot] Problem with quota warning
by Patrick Westenberg 10 Apr '12

10 Apr '12

Hi again, my test environment is working now and finally I tried to implement my quota warning but it is not working. LDA says the mailbox is full even it is not (only 81% and that is why the quota warning is executed). Further I used :noenforcing in my script. Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: Namespace INBOX.: Using permissions from /var/mail/k-team.info/test/mdbox: mode=0700 gid=-1 Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: Quota root: name=User quota backend=dict args=:file://mdbox/dovecot-quota:noenforcing Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: Quota warning: bytes=0 (90%) messages=0 reverse=no command=quota-warning 90 raw mail user Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: Quota warning: bytes=0 (75%) messages=0 reverse=no command=quota-warning 75 raw mail user Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: dict quota: user=raw mail user, uri=file://mdbox/dovecot-quota:noenforcing, noenforcing=0 Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: none: root=, index=, control=, inbox=, alt= Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): Debug: Destination address: test(a)k-team.info (source: user@hostname) Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): msgid=unspecified: save failed to INBOX: Quota exceeded (mailbox for user is full) Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): msgid=unspecified: rejected: Quota exceeded (mailbox for user is full) Apr 9 15:08:21 backend01 dovecot: lda(test(a)k-team.info): msgid=: Return-Path missing, rejection reason: Quota exceeded (mailbox for user is full) # 2.1.3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.4 auth_debug = yes auth_debug_passwords = yes auth_verbose = yes listen = 172.17.99.96 mail_debug = yes mail_gid = vmail mail_home = /var/mail/%d/%n mail_location = mdbox:~/mdbox:INDEX=/var/indexes/%d/%n mail_plugins = quota 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 namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { autocreate = INBOX.Sent autocreate2 = INBOX.Trash autocreate3 = INBOX.Drafts autocreate4 = INBOX.Spamverdacht autosubscribe = INBOX.Sent autosubscribe2 = INBOX.Trash autosubscribe3 = INBOX.Drafts autosubscribe4 = INBOX.Spamverdacht quota = dict:User quota::file:%h/mdbox/dovecot-quota quota_rule2 = INBOX.Trash:storage=+100M quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=75%% quota-warning 75 %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve } protocols = imap pop3 lmtp sieve service auth { unix_listener auth-userdb { user = vmail } } service imap-login { service_count = 1 } service lmtp { inet_listener lmtp { address = 172.17.99.96 port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } service quota-warning { executable = script /usr/local/etc/dovecot/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl = required ssl_cert = </etc/ssl/certs/imap.wk-serv.de.crt ssl_key = </etc/ssl/certs/imap.wk-serv.de.key userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota sieve } protocol imap { mail_plugins = quota imap_quota autocreate } protocol pop3 { pop3_client_workarounds = oe-ns-eoh, outlook-no-nuls } #!/bin/sh PERCENT=$1 USER=$2 cat << EOF | /usr/local/libexec/dovecot/dovecot-lda -d $USER -o "plugin/quota=dict:User quota::file:%h/mdbox/dovecot-quota:noenforcing" From: support(a)example.com Reply-To: support(a)example.com Subject: Speicherplatz Ihrer Mailbox ...

2 5

[Dovecot] Multiply mailboxes vs one huge
by Alexander Chekalin 10 Apr '12

10 Apr '12

Hello, as I need to store a lot of messages on my IMAP server (order of 900K-1000K; this is an archive for some time, maybe a year or so), I see some "slowness" in dealing with such a huge amount. I mainly need to do searches like "get all messages from user1(a)domain1.com to user2(a)domain2.tld recieved between date1 and date2". So I really interested will it be wise to a) split all messages into several smaller mailboxes (per-month, or per-day, or create 2-level-structure like "month/day/") b) use dbox (vs currently used mbox) storage scheme (I'm afraid of mdbox as I still not sure I'll be able to parse it by scripts later "just in case") Dovecot is the latest one (2.1.3). No compression Dovecot-side, but it mails are in zfs volume with compression on. I ask this mainly due to my not fully understand how Dovecot indexes are working. I also test another approach: to use my own index somewhere outside Dovecot which will store reference between emails and UIDs, and dates and UIDs, so I'll simple query my index for things I need. But then, that's exactly what IMAP index can do, so I simple slow my search down, isn't it? The only reason I think about my own index is I won't use 'all header' as search scope, I need to deal only with From:, To:, Cc:, Bcc: (if any), Recieved (if nowehere else I see the from/to info), and date field(s) - I doubt IMAP will care for that for me. Yours, Alexander

2 3

[Dovecot] v2.1.4 released
by Timo Sirainen 10 Apr '12

10 Apr '12

http://dovecot.org/releases/2.1/dovecot-2.1.4.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.4.tar.gz.sig + Added mail_temp_scan_interval setting and changed its default value from 8 hours to 1 week. + Added pop3-migration plugin for easily doing a transparent IMAP+POP3 migration to Dovecot: http://wiki2.dovecot.org/Migration/Dsync + doveadm user: Added -m parameter to show some of the mail settings. - Proxying SSL connections crashed in v2.1.[23] - fts-solr: Indexing mail bodies was broken. - director: Several changes to significantly improve error handling - doveadm import didn't import messages' flags - mail_full_filesystem_access=yes was broken - Make sure IMAP clients can't create directories when accessing nonexistent users' mailboxes via shared namespace. - Dovecot auth clients authenticating via TCP socket could have failed with bogus "PID already in use" errors.

3 3

[Dovecot] mount
by Luigi Rosa 09 Apr '12

09 Apr '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a Dovecot installation on CentOS 5 where I sometimes mount external fs in /mnt Every Dovecot data is in local / file system, nothing is mounted elswhere After upgrading to 1.2.4 I rebooted the system for other reasons and at startup I got this on Dovecot log: master: Warning: /mnt is no longer mounted. If this is intentional, remove it with doveadm mount No /mnt entry in /etc/fstab and nothing pmounted under /mnt I THINK that the last time I used /mnt to mount something was few weeks ago to update VMware tools. Is there a way toi tell Dovecot to ignore /mnt ? Ciao, luigi - -- / +--[Luigi Rosa]-- \ $100 invested at 7% interest for 100 years will become $100,000, at which time it will be worth absolutely nothing. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+C58gACgkQ3kWu7Tfl6ZRc0wCgl0Z4OtblYbfYwzvOp1/vUifV PqYAoIvfltvmq3cijvDbOEKV2Tai2rpu =hyrI -----END PGP SIGNATURE-----

2 2

[Dovecot] Director pop-login and imap-login processes exiting on signal 11
by Andy Dills 09 Apr '12

09 Apr '12

We recently upgraded our cluster to 2.1.3, to enable director proxying. Everything appears to be working fine for the most part; the only odd thing is that I'm seeing a lot of entries in the logs like this: Apr 7 02:18:05 mail-out06 dovecot: pop3-login: Fatal: master: service(pop3-login): child 75029 killed with signal 11 (core not dumped - set service pop3-login { drop_priv_before_exec=yes }) This is on the proxy side, not that backend side. When I try to get a dump out of it, and add drop_prive_before_exec and chroot= to the pop3-login statement on the proxy, I keep running into permissions errors with the various service sockets. Any suggestions? Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 ---

2 2

[Dovecot] v2.0.20 released
by Timo Sirainen 09 Apr '12

09 Apr '12

http://dovecot.org/releases/2.0/dovecot-2.0.20.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.20.tar.gz.sig + doveadm user: Added -m parameter to show some of the mail settings. - doveadm import didn't import messages' flags - Make sure IMAP clients can't create directories when accessing nonexistent users' mailboxes via shared namespace. - Dovecot auth clients authenticating via TCP socket could have failed with bogus "PID already in use" errors.

1 0

[Dovecot] Director simplification?
by Timo Sirainen 09 Apr '12

09 Apr '12

An idea I just had: Director basically works by assigning the backend IP address by: ip = vhosts[ md5(username) mod vhosts_count ].ip The rest of director is about what happens when vhosts[] or vhosts_count changes. What about instead doing this on IP address level? ip = ip_pool[ md5(username) mod ip_pool_size ] When a backend dies, you'll reassign the backend's IPs to other backends. Each backend should have many IPs. The main restriction here is that the IP pool cannot change without stopping the entire Dovecot. But if you initially allocate enough IPs, that shouldn't be a problem. And the advantage of this over the current director? To guarantee that one director can't break others, because they don't need to communicate with each others. The disadvantage of course is that it's a little less flexible and requires more planning ahead. The IP address reassignment would also need some distro-specific scripts. This could be implemented as an alternative director-lite or something. The doveadm director status-related commands could still work with it.

1 0