June 2014 - dovecot - dovecot.org

[Dovecot] Installing Godaddy Certificate
by The Doctor, 3328-138 Ave Edmonton AB T5Y 1M4, 669-2000, 473-4587 02 Jun '14

02 Jun '14

I have 2 certs to install: One is intermediate the other the 'actual' cert. How do I do this?

2 1

[Dovecot] Dovecot 2 | Creating message rules
by Jos Chrispijn 02 Jun '14

02 Jun '14

Can someone explain how I can create message rules to use with this version of Dovecot? I specially switched to this version because it supports then Pigeonhole Sieve. I would like to volunteer to contribute as a volunteer when someone would like to create a html driven user interface that provides a user friendly configuration interface and would make such configuration a piece of cake. -- Best regards, Jos Chrispijn --- Artificial intelligence is no match for natural stupidity

5 5

[Dovecot] Dovecot 2.1.13: some questions about the mail-filter plugin
by Axel Luttgens 02 Jun '14

02 Jun '14

Looking at mail_filter_mailbox_allocated() of src/plugins/mail-filter/mail-filter-plugin.c: if ((class_flags & MAIL_STORAGE_CLASS_FLAG_OPEN_STREAMS) == 0 && (class_flags & MAIL_STORAGE_CLASS_FLAG_BINARY_DATA) != 0 && muser->out_socket_path != NULL) v->save_begin = mail_filter_mail_save_begin; it seems that a backend with MAIL_STORAGE_CLASS_FLAG_OPEN_STREAMS unset and MAIL_STORAGE_CLASS_FLAG_BINARY_DATA set is expected by the plugin. Technically, this would thus exclude the mbox backend, since its flag configuration seems to be exactly the opposite: struct mail_storage mbox_storage = { .name = MBOX_STORAGE_NAME, .class_flags = MAIL_STORAGE_CLASS_FLAG_MAILBOX_IS_FILE | MAIL_STORAGE_CLASS_FLAG_OPEN_STREAMS | MAIL_STORAGE_CLASS_FLAG_HAVE_MAIL_GUIDS, [...] Is this a correct interpretation? If yes, what is the rationale? I couldn't find any info related to such a limitation in the docs; the README file of http://dovecot.org/patches/2.2/mail-filter.tar.gz even says: "Mail filter plugin can read an email from any storage supported by Dovecot and modify the mail in some way"... All of this stems from my attempts to have working mail filters when I was trying to better understand the behaviors Stanislas was describing in a recent thread... Hence another question; in sdbox-storage.c, the definition of the "alias" for sdbox comes with: struct mail_storage dbox_storage = { .name = "dbox", /* alias */ .class_flags = MAIL_STORAGE_CLASS_FLAG_FILE_PER_MSG, [...] The initialization of member class_flags seems to be incomplete, when compared to the one for the name "sdbox". A typo? On the other hand, Stanislas showed a configuration with mail_location = dbox:/mailboxes/%Ld/%Ln and seemed to have a working mail filter. If above interpretation is correct, this would mean that the "alias" definition isn't used, but that the one for "sdbox" is used instead. Out of curiosity, how/where is that substitution achieved? Regards, Axel

1 0

[Dovecot] "doveadm fetch" fetches mails twice?
by Peer Heinlein 01 Jun '14

01 Jun '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As far as I understood fetch -u p.heinlein(a)jpberlin.de hdr mailbox-guid [...]93d5 uid 58175 should fetch exactly the header of the specified mail. But on my Dovecot 2.2.12 it fetches the header *twice* (same with body, same with text). ======================================== hdr: Return-Path: <hello(a)example.com> Delivered-To: <p.heinlein(a)jpberlin.de> [...] hdr: Return-Path: <hello(a)example.com> Delivered-To: <p.heinlein(a)jpberlin.de> [...] ======================================== Peer - -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTi4ttAAoJEAOLLpq5E82HL/MIAIx1WBDdzP/u5fI/VuyfSzYO gj8M5WL8MkamOpziOfADBdRR1qZwsuS8EjFmdNSrdqrLFM1tle/0Umaa3buJBeyF OuTIodbkv5prgoF/YDxsOKXMSCDx8JP3o5twNbTQfdMT+rYww80GGqDbAFv5VMzJ vNAOQZ3Le1S45da1wL526UcPSHNBXwMMbpCS3LY60iKRbHaURXJuotbXb4DemD0J En2ZjQzmstIBbyFL7X3JfiyiEe3Dmdq5u0XJC5j2Xo3U9mfHB2FBmbEE9KdKPXgu wL2cihep5lDExS2N89ne9Zp6n/Ff104Gki1gwQu0mSBPS8OGFSIJ5iGDBdWIEGk= =4smt -----END PGP SIGNATURE-----

1 0

[Dovecot] Combining userdbs
by Bubreg István 01 Jun '14

01 Jun '14

Hi, I think that using more than one userdb with setting the result actions doesn't work as expected from the documentation. The goal would be to set user-specific quotas for a few users with a specific passwd-file like this : cat /etc/dovecot/quotas foo:x::::::userdb_quota_rule=*:storage=2G The first userdb is passwd (with pam passwd): userdb { driver = passwd result_failure = return-fail result_internalfail = return-fail result_success = continue-ok skip = never } The second one is for the specific quota userdb { args = username_format=%n /etc/dovecot/quotas driver = passwd-file result_failure = continue result_internalfail = continue result_success = return-ok skip = notfound } User 'foo' exists in (pam) passd, but there's no place to store his own quota rule, that's why came handy to use a second userdb for storing just one extra field. That's working quiet well, he default quota is overriding form passwd-file. BUT: I've played a lot with changing the result_* and the 'skip' parameters, but none of them worked in the situation where a user ('bar') _only_ exists in passwd (and has to use the default quota config). doveadm quota get -u bar says doveadm(bar): Fatal: User doesn't exist With changing the parameters this error has gone, but the second userdb doesn't used for user 'foo' - even if the parameters are : userdb { driver = passwd result_failure = return-fail result_internalfail = return-fail result_success = continue <-- in theory, the next userdb is coming skip = never } userdb { args = username_format=%n /etc/dovecot/quotas driver = passwd-file result_failure = continue result_internalfail = continue result_success = return-ok skip = notfound } My question is that how should i set the result_* and 'skip' parameters to solve this : - there's a default quota rule in the config - some (a few) users has a larger quota - there's no way to store the user-specific quotas in the 'real' userdb (because it's pam/passwd) Thank you for your effort. # dovecot -n # 2.2.13 (de9b10f2e168): /etc/dovecot/dovecot.conf # OS: Linux 3.11.0-15-generic i686 Ubuntu 12.04.4 LTS auth_debug = yes auth_debug_passwords = yes auth_verbose = yes auth_verbose_passwords = yes disable_plaintext_auth = no listen = * log_path = /var/log/dovecot.log mail_debug = yes mail_location = maildir:~/Maildir 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 ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { quota = maildir:User quota quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap sieve" service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { process_limit = 1024 } ssl = no ssl_cert = </etc/dovecot/private/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd result_failure = return-fail result_internalfail = return-fail result_success = continue-ok } userdb { args = username_format=%n /etc/dovecot/quotas driver = passwd-file result_failure = continue-ok result_internalfail = continue-ok skip = notfound } protocol imap { mail_plugins = quota }

1 0

[Dovecot] Disabling plus sign extension delimiter in lmtp listener (or userdb)
by Benoit Panizzon 01 Jun '14

01 Jun '14

Hello We have migrated our email services from a server, which did not support IMAP and folders, therefore threated the plus sign + as a normal character in a part of an email address. Our new server delivers the emails via lmtp to dovecot. the few users which got a + character in the username first could not log-in (fixed by adding + to auth_username_chars). Now the next problem turn out to be, that the lmtp listener stripps everything after the + sign. The MTA correctly sends the whole email address, so it's not the MTA's fault. It can easily be tested by connecting to the dovecot LMTP listener IP address by telnet: 220 grautvornix.imp.ch Dovecot ready. mail from:<nobody> 250 2.1.0 OK rcpt to:<b+enoit(a)iscan.ch> 550 5.1.1 <b+enoit(a)iscan.ch> User doesn't exist: b(a)iscan.ch I could not find any configuration parameters for the lmtp listener or userdb service to tell it what to do with the + sign. Did I miss something, or is it impossible to have the + sign accepted as a normal character in an email address? Kind regards -Benoit-

3 6