- dovecot - dovecot.org

[Dovecot] file rights for dictionary file
by Michael Köhler 06 Jun '11

06 Jun '11

Hi, I use Debian Squeeze and the sources from Stephan Bosch. A few weeks ago I´ve upgraded from 2.0.11 to 2.0.13 and got an error May 29 20:01:53 mailserver dovecot: dict: Error: Can't open configuration file /etc/dovecot/dovecot-dict-sql.conf.ext: Permission denied May 29 20:01:53 mailserver dovecot: dict: Error: Failed to initialize dictionary 'quota' and I could see that /etc/dovecot/dovecot-dict-sql.conf.ext is owning by root:root with 600. After changing to root:root 644 all works, but after each upgrade all files in /etc/dovecot will be set to 600. Is it a problem of the dovecot package or should I do some changes to config to allow dovecot reading the dict file? Here is my config: # 2.0.13 (9ae30e5d6935): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.1 ext3 auth_mechanisms = plain login cram-md5 dict { quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_uid = 106 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_location = maildir:/var/mail/%d/%u mail_plugins = quota 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 passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { autocreate = Sent Messages autocreate2 = Deleted Messages autocreate3 = Drafts autosubscribe = Sent Messages autosubscribe2 = Deleted Messages autosubscribe3 = Drafts quota = dict:User quota::proxy::quota quota_rule2 = Deleted Messages:storage=+1GB sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service dict { unix_listener dict { group = mail mode = 0660 } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl = required ssl_cert = </etc/ssl/certs/mailserver-cert.pem ssl_key = </etc/ssl/private/mailserver-key.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota } protocol imap { mail_plugins = quota imap_quota autocreate } local_name mailserver.makomi.de { ssl_cert = </etc/ssl/certs/mailserver1-cert.pem ssl_key = </etc/ssl/private/mailserver1-key.pem } local_name mailserver.kokoma.de { ssl_cert = </etc/ssl/certs/mailserver2-cert.pem ssl_key = </etc/ssl/private/mailserver2-key.pem } local_name mailserver.grooveb.de { ssl_cert = </etc/ssl/certs/mailserver3-cert.pem ssl_key = </etc/ssl/private/mailserver3-key.pem } local_name mailserver.koehler-gohlis.de { ssl_cert = </etc/ssl/certs/mailserver4-cert.pem ssl_key = </etc/ssl/private/mailserver4-key.pem } local_name mailserver.koehler-schroeder.de { ssl_cert = </etc/ssl/certs/mailserver5-cert.pem ssl_key = </etc/ssl/private/mailserver5-key.pem } Greetings, Michael

2 1

[Dovecot] doveadm problem with mail_plugins in database
by Ralf Zimmermann 06 Jun '11

06 Jun '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I use this user_query: - -------------------------------%<-------------------------------- user_query = SELECT LOWER(CONCAT(t2.login,'@',t1.name)) AS user,t2.home,t2.mail,5000 AS uid,5000 AS gid,CONCAT('*:storage=',quota_mb,'MB') AS quota_rule,t2.acl_groups,case when '%s'='lda' then 'acl quota sieve' when '%s'='lmtp' then 'acl quota sieve' when '%s'='doveadm' then mail_plugins when '%s'='sieve' then 'acl quota' else t2.mail_plugins end as mail_plugins FROM virtual_users as t2, virtual_domains as t1 WHERE ( t2.login='%n' OR t2.email='%u' ) AND t1.enabled IS true AND t2.enabled IS true AND t1.id=t2.domain_id - -------------------------------%<-------------------------------- When I use some doveadm commands I get this error for example: - -------------------------------%<-------------------------------- # doveadm fetch -u rzimmermann "hdr" savedbefore 3d doveadm(rzimmermann): Error: dlopen(/usr/local/lib/dovecot/lib02_imap_acl_plugin.so) failed: /usr/local/lib/dovecot/lib02_imap_acl_plugin.so: undefined symbol: client_fail_mailbox_name_status doveadm(rzimmermann): Error: Can't load plugin imap_acl_plugin: Plugin is intended to be used only by imap binary (we're doveadm) doveadm(rzimmermann): Fatal: Couldn't load required plugins - -------------------------------%<-------------------------------- Some doveadm commands runs fine. Here a example: - -------------------------------%<-------------------------------- # doveadm user rzimmermann userdb: rzimmermann home : /var/vmail/virtusers/boardfreunde.de/rzimmermann mail : maildir:~/Maildir uid : 5000 gid : 5000 quota_rule: *:storage=4000MB acl_groups: admins,boe-admins mail_plugins: quota imap_quota acl imap_acl autocreate fts fts_squat - -------------------------------%<-------------------------------- If I change the user_query part "'%s'='doveadm' then mail_plugins" to "'%s'='doveadm' then 'acl quota" all works fine, but I get a wrong mail_plugin output: - -------------------------------%<-------------------------------- userdb: rzimmermann home : /var/vmail/virtusers/boardfreunde.de/rzimmermann mail : maildir:~/Maildir uid : 5000 gid : 5000 quota_rule: *:storage=4000MB acl_groups: admins,boe-admins mail_plugins: acl quota - -------------------------------%<-------------------------------- What can I do to get doveadm working with "'%s'='doveadm' then mail_plugins"? Or must I use "'%s'='doveadm' then 'acl quota" in the user_query? I use dovecot 2.0.13. Greets Ralf -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJN7BDnAAoJENVjhbwuX+/H6F4H/ROB/J4/icebgAQdpqQxYgDt PEUR87dlgIufQWT7KVyYVYBxzfjRqk20+f/Djpxy6RGl2jVHajvtOpsovQQz92Dy C1ulagZ2mimhbP8qa6VSh3Ozjv9xASbXDJHEDhSR3i45V0bPFpN1resaP8pHHJkl bdvqrdXlvIdMvJ83fSTcElMdIrmg0wyUJMTB900NVkvndlGO1xs1vtfv2c+PhNDe 9nq9Vs2/uVt7NO6ct/d9tqd57X5fzqxzIvjWWCIyHB38W6KgNFM6TiHI1WtSFsKn 4UOcE9FKmePq17ugaj1yrn0gmOSgU1TqnSjRwEM0xoteUlio2NsuhzFSVojkq9s= =NzcM -----END PGP SIGNATURE-----

2 1

[Dovecot] Bug: Fixed a duplicate
by Tom Sommer 06 Jun '11

06 Jun '11

I restored a dovecot mailserver today, and when I started the server again, the logs filled up with "Fixed a duplicate" warnings. This in itself it not a problem, the problem is that it appears the fix is not done correct. Consider this: Warning: Fixed a duplicate: [X]/cur/1305907573.V807I37682f3M146183.mail8.xxx.com:2,S -> 1306601066.M382668P27710.mail8.xxx.com The problem appears to be the timestamp of this new file isn't updated correctly. Now I got hundreds of mailboxes filled with mails named 1305907573.* with random (in the past) timestamps, leading to mangled miss-sorted inboxes for customers. 3575 May 25 02:05 1306600913.M982997P26976.mail8.xxx.com:2,S 55313 May 6 01:50 1306600913.M982998P26976.mail8.xxx.com:2,S 9839 May 7 23:59 1306600913.M982999P26976.mail8.xxx.com:2,S 3453 May 10 01:32 1306600913.M983000P26976.mail8.xxx.com:2,S 16616 May 14 00:22 1306600913.M983001P26976.mail8.xxx.com:2,S 68850 May 25 00:46 1306600913.M983002P26976.mail8.xxx.com:2,S etc. Dovecot is v. 2.0.11 I guess I should have deleted all dovecot.* files after the restore, before I started dovecot? // Tom

2 3

[Dovecot] Help with Trash setup
by Ivan Rodrigues 05 Jun '11

05 Jun '11

Folks, I'm trying to setup a mail server just to store my mail, i use fetchmail to retrieve my messages and I want to configure the trash can, can you guys please help me with this mater? Dovecot Version: 1.2.9 No SQL nor LDAP installed dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-24-generic-pae i686 Ubuntu 10.04.2 LTS log_timestamp: %Y-%m-%d %H:%M:%S login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mail_location: maildir:~/Maildir mbox_write_locks: fcntl dotlock mail_plugins: delete_to_trash auth default: passdb: driver: pam userdb: driver: passwd plugin: deleted_to_trash_folder: Trash

2 1

[Dovecot] Custom sql query for keeping quota with dict-sql
by Marcin Mirosław 05 Jun '11

05 Jun '11

Hello! I'd like to setup quota for for virtualusers, i'm using both maildir++ and mdbox as storage, and i'm using postgresql to keep users. I'm keeping all users data in one table: [...] login text NOT NULL, domain text, password text, quota_mb integer NOT NULL DEFAULT 0 [... other columns ...] i'd like to keep present quota in such two columns: quota_dict_bytes integer NOT NULL DEFAULT 0, quota_dict_messages integer NOT NULL DEFAULT 0 I read wiki a little and it looks i can't define own sql queries, they appear to be hardcoded. Am i wrong? Is it possible to write own queries to get/set quota using such table schema? Or maybe there is diffrent way to track quota for diffrent storages? Regards! Marcin

4 10

[Dovecot] dsync: Invalid mailbox first_recent_uid
by David Jonas 04 Jun '11

04 Jun '11

For the life of me I can't get dsync to work. Please help! Remote server runs dovecot out of /usr/local/dovecot2. Everything makes sense until this line: dsync-local(djonas(a)vitalwerks.com): Error: Invalid mailbox input from worker server: Invalid mailbox first_recent_uid The local uid is 8989 and the remote uid is 89. I added "first_valid_uid = 89" to the local conf but to no avail. Local version is 2.0.12, remote is 2.0.1. # dsync -Dv -u djonas(a)vitalwerks.com mirror \ ssh vmail(a)192.168.15.54 \ /usr/local/dovecot2/bin/dsync -Dv -u djonas(a)vitalwerks.com dsync(vmail): Debug: Effective uid=8989, gid=8989, home=/home/vmail/domains/vitalwerks.com/djonas dsync(vmail): Debug: Quota root: name=user backend=dict args=vitalwerks.com-djonas:proxy::quota dsync(vmail): Debug: dict quota: user=vitalwerks.com-djonas, uri=proxy::quota, noenforcing=0 dsync(vmail): Debug: Namespace : type=private, prefix=, sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir:INBOX=~/Maildir dsync(vmail): Debug: maildir++: root=/home/vmail/domains/vitalwerks.com/djonas/Maildir, index=, control=, inbox=/home/vmail/domains/vitalwerks.com/djonas/Maildir dsync-local(djonas(a)vitalwerks.com): Debug: Namespace : Using permissions from /home/vmail/domains/vitalwerks.com/djonas/Maildir: mode=0770 gid=-1 dsync-local(djonas(a)vitalwerks.com): Error: Invalid mailbox input from worker server: Invalid mailbox first_recent_uid dsync-remote(djonas(a)vitalwerks.com): Error: read() from proxy client failed: EOF

2 2

[Dovecot] Segmentation fault again
by Jim Knuth 03 Jun '11

03 Jun '11

Hi, I have the following report after a cron job again? /root/tools/expunge: Zeile 3: 4869 Speicherzugriffsfehler doveadm expunge -A mailbox Spam savedbefore 5d /root/tools/expunge: Zeile 5: 4915 Speicherzugriffsfehler doveadm expunge -A mailbox Papierkorb savedbefore 4d See the attachment. Any ideas greatly appreciated. Thanks -- Mit freundlichen Grüßen, with kind regards, Jim Knuth --------- Das Leben ist bezaubernd, man muss es nur durch die richtige Brille sehen. (Alexandre Dumas)

3 8

[Dovecot] solr substring schema.xml
by Daniel Miller 03 Jun '11

03 Jun '11

I'm trying a modified schema.xml with solr - it appears I now have substring searches! I took the schema.xml file shipped with Dovecot, and modified the text field definition to be: <fieldType name="text" class="solr.TextField" positionIncrementGap="100"> <analyzer type="index"> <tokenizer class="solr.WhitespaceTokenizerFactory"/> <filter class="solr.StopFilterFactory" ignoreCase="true" words="stopwords.txt"/> <filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="1" catenateNumbers="1" catenateAll="0"/> <filter class="solr.LowerCaseFilterFactory"/> <filter class="solr.SnowballPorterFilterFactory" protected="protwords.txt"/> <filter class="solr.NGramFilterFactory" minGramSize="3" maxGramSize="15"/> <filter class="solr.RemoveDuplicatesTokenFilterFactory"/> </analyzer> <analyzer type="query"> <tokenizer class="solr.WhitespaceTokenizerFactory"/> <filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt" ignoreCase="true" expand="true"/> <filter class="solr.StopFilterFactory" ignoreCase="true" words="stopwords.txt"/> <filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="0" catenateNumbers="0" catenateAll="0"/> <filter class="solr.LowerCaseFilterFactory"/> <filter class="solr.SnowballPorterFilterFactory" protected="protwords.txt"/> <filter class="solr.RemoveDuplicatesTokenFilterFactory"/> </analyzer> </fieldType> Changing to the new "SnowballPorter" instead of the deprecated "EnglishPorter" filters is probably minor - the magic is the "NGramFilterFactory". 3 & 15 seemed reasonable defaults for the min/max size to search on. -- Daniel

2 2

[Dovecot] unexpected subfolder locaton in Maildir/.INBOX.subfolder
by wulf 03 Jun '11

03 Jun '11

Hallo, I try to migrate existing imap server to dovecot 1.2 in debian squeeze if I connect to imap://user@host/INBOX Inbox works as expected and I get the content of Maildir/{cur,new,tmp} Maildir/.subfolder already exists if I connect to imap://user@host/INBOX.subfolder I get "folder not found" if I do a imap directory listing (raw mutt config, no subscriptions) - I see "../" - If I navigate to "../" I se all my existing subfolders if I create a new folder via imap the folder is created in Maildir/.INBOX.new_subfolder I expect the creation of Maildir/.new_subfolder This doesn't fit to the client configs and if I move the existing folders it doesn't fit to existing delivery agent filters and settings. I enabled mail_debug and the expansion looks ok for me: dovecot: imap-login: Login: user=<wulf>, method=PLAIN, rip=85.178.xx.xxx, lip=80.81.xxx.xxx, TLS dovecot: IMAP(wulf): Effective uid=112, gid=114, home=/var/mail/home/wulf dovecot: IMAP(wulf): maildir: data=~/Maildir dovecot: IMAP(wulf): maildir++: root=/var/mail/home/wulf/Maildir, index=, control=, inbox=/var/mail/home/wulf/Maildir the existing subscription information from courier-imap looks like INBOX.subolder Yes I can sed them to subfolder (of course I have to copy them to Maildir/subscriptions anyhow) But is that the idea? I like to avoid trouble with all the users and their already configured mail-clients. Where is my mistake? Thanks for feedback Best Wulf CONF: protocols = imap imaps log_timestamp = "%Y-%m-%d %H:%M:%S " ssl = required ssl_cert_file = /etc/exim4/xxxxxxxxxxxxxxx.pem ssl_key_file = /etc/exim4/xxxxxx.key mail_location = maildir:~/Maildir mail_uid = 112 mail_gid = 114 mail_access_groups = vmail mail_debug = yes first_valid_uid = 112 protocol imap { } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol managesieve { } auth_verbose = yes auth_debug = yes auth default { mechanisms = plain passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb static { args = uid=112 gid=114 home=/var/mail/home/%u } user = root } dict { } plugin { } dovecot-ldap.conf: hosts = 127.0.0.1:389 auth_bind = yes auth_bind_userdn = uid=%u,ou=users,dc=xxxxxxxx,dc=de base = dc=xxxxxxxx,dc=de

3 4

[Dovecot] Running a dovecot cluster with mixed versions?
by Ian Foutch 03 Jun '11

03 Jun '11

I have been trying to find information and possible issues with running a cluster of dovecot server with different versions without any luck. We have an existing cluster with dovecot v1.1.10 and tried migrating to a new cluster with dovecot v2.0.12. We ran into some issues when we moved traffic to the new cluster and have been unable to reproduce it in our own testing. We may need to put real usage on the new servers but would like to be able to do this by adding newer servers into the existing cluster. What are the potential issues with doing this? Thanks, --Ian This message and any attachments to it are intended only for the addressee(s) identified above and may contain CONFIDENTIAL information. It is not intended for transmission to, or receipt by, any unauthorized persons. If you are not an intended recipient or an agent responsible for delivering it to an intended recipient, you have received this e-mail in error and any dissemination, distribution, or copying of this message or any attachment to it is strictly prohibited. If you have received this email in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the message from your system.

2 1