- dovecot - dovecot.org

Re: [Dovecot] Mapping usernames [RESOLVED]
by Henry 13 Feb '09

13 Feb '09

Resolved. For others, this is the simple solution which works for me: /etc/dovecot.conf: auth default { userdb passwd-file { args = /etc/passwd } passdb passwd-file { args = scheme="MD5-CRYPT" /etc/dovecot.passwd } } /etc/dovecot.passwd: bob@vhost.com:$1$yAOjs09l$...::::::userdb_user=vabc_bob (the encrypted password "$1$yAOjs09l$..." comes from /etc/shadow) /etc/passwd: vabc_bob:x:20838:2362:bob:/home/mailusers/vabc_bob:/sbin/nologin "abc" could also be the domain ("vhost"), but this might be too large for really long domain names. So we rather use a short unique prefix for each domain. Cheers Henry -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.5 (GNU/Linux) mOIESXlwDRECAOycneJPOwSkETRkjJZdArag8V2rKOR2IUwlDOydIZXv/ITDlWDU dookzEdWh7Ektf1Jlh+YbPNEGoPpQunL8O8AoJbWmNkpoX7jP0Sw/5rDN2eKGHR7 Af9mxTqQ/j3C5LkrTRo9iCTt1TxoqPi6R/w0KkIAuTXBq6j+vIFJcOFgABlMQoXs V2crh1BUCmXVsV1puRJsLWKbAf4uL0V+N8WF4rvWHmJiYjgDn6exv3XHS0F6NhRz n1KVnV0XDWMDq/B/tmj4L2JYxEzWzeNulC5yQBOdx/dLU12XtCNIZW5yeSAoemVu LmNvLnphKSA8aGVucnlAemVuLmNvLnphPohgBBMRAgAgBQJJeXANAhsjBgsJCAcD AgQVAggDBBYCAwECHgECF4AACgkQCHhhdg2iQafVGACdEMtEuUGIW2XJyn9Fig7n sX4qzb4An0PGStBZvAP2qtzYP3SGlzsllzLjuI0ESXlwDRACAMsi4nl8/Yar2m9F ex4dFDgWylLgScQrEhhb2xN0Upcglm60nHQD7c1rP+63Iu+lU0eWvyr8o3JTCN4y PpoGMOMAAwUCAIUnLDMW/tz+qsYaOPyoh7HdAYqcrvVar7t+eKpihNBqfP4CT2Py aRVMN6cSJj9NKZDW6b0QQSCGgN7PpzrLqf6ISQQYEQIACQUCSXlwDQIbDAAKCRAI eGF2DaJBpxeiAJ9cNiuaftSoWke75RT1pn7qoibFfgCdHl6BgP9f450/oziDwaMM w49UeHQ= =qgmL -----END PGP PUBLIC KEY BLOCK-----

1 0

[Dovecot] file name missing component in error message
by Mike Abbott 13 Feb '09

13 Feb '09

Hi, we occasionally see this error message from maildir_mail_set_cache_corrupted(): "Maildir filename has wrong W value: %s/%s" but the path it prints is missing a component, specifically, the new/cur/tmp component. For example: /Volumes/Spool/user/maildir/12345.M123P123.example.com.... should be /Volumes/Spool/user/maildir/cur/12345.M123P123.example.com.... This is using dovecot-1.1.10. Now I just have to figure out why the file is corrupted in the first place.

2 3

[Dovecot] quota - implement via dovecot or postfix? which is easier ?
by Linux Advocate 13 Feb '09

13 Feb '09

Guys, i m new to dovecot. I m setting up a new mailserver and planning to run dovecot and postfix of a centos 5.2 box. I have been reading of quota management from various sources and understand that mail box quota can be implemented either thru postfix ( with vda patch ) or thru dovecot. i rather not patch postfix and m therefore leaning towards quota via dovecot. But after reading some posts ,etc, it seems that the information on the dovecot wiki is inaccurate. A.Any comments on this? B. Am i right in concluding that its easier and better in the long run to implement and enforce quotas thru dovecot instead of postfix? C. The right instructions for implementing quota thru dovecot? Regards, marco.

5 6

[Dovecot] CentOS 5 ... again
by Roderick A. Anderson 13 Feb '09

13 Feb '09

At this point I don't think I can do anymore damage to my mail server but I'd like to know if anyone else is using the pre-built RPM files from ATrpms before I install them? http://dl.atrpms.net/all/dovecot-1.1.11-0_90.el5.i386.rpm http://dl.atrpms.net/all/dovecot-sieve-1.1.6-9.el5.i386.rpm Or is there a dovecot-sieve for 1.0.7 from the rpmforge repo? I haven't found it yet but could have sworn I had it before. Thanks, Rod --

6 9

[Dovecot] Released Sieve v0.1.3 and ManageSieve v0.11.3 for Dovecot v1.2.beta1
by Stephan Bosch 13 Feb '09

13 Feb '09

Hello Dovecot users, It has been about two months since the last release of the new Sieve implementation and the ManageSieve service for Dovecot v1.2. Therefore, this release contains quite a few changes. It adds new sieve features like the enotify extension and multiscript support. Also, quite a few (user-reported) bugs were fixed since the last release. Changelog Sieve v0.1.3: * Adapted to changes in Dovecot, making this release dependent on Dovecot >= 1.2.beta1 * Made mail address comparison fully case-insensitive. This is particularly noticeable for the :addresses argument of the vacation command. + Finished enotify extension. Currently, only the mailto notification method is implemented. All still needs to be tested thoroughly. + Implemented multiscript support. It is now possible to execute multiple Sieve scripts sequentially. Administrator-controlled scripts can be executed before and after the user's script. Still needs to be tested thoroughly. + Implemented support for configuring the available Sieve extensions. + Made the subaddress extension (partially) configurable using the sieve_subaddress_sep setting, which allows specifying a (multi-charater) separator other than '+'. + Compiler now warns about invalid header field names used for the header and address tests. + Vacation extension now properly generates a References header for the response message. + Added testing of basic result execution to the test suite. Also added support for testing the outgoing messages produced by the Sieve interpreter. + Included execution of the actual result in the sieve-test command line tool. The undocumented sieve-exec tool that existed for this is now removed as planned. + Added support for the now obsolete 'imapflags' extension for backwards compatibility with CMUSieve. This also implements the mark/unmark commands. - Fixed bugs in the regex extension: 1) if an optional match value did not in fact match, subsequent match values would get unexpected indexes. 2) fixed segfault bug occuring when regex is freed. - Fixed bug in the use of the :from agrument for the vacation command. If this address included a phrase part, the response would not be a valid RFC822 message. - Plugged a theoretical security hole occuring when a directory is opened as a Sieve binary. - Cleaned up and fixed various log messages. - Fixed bug in the outgoing address verification. Addresses ending in ',' were erroneously accepted. Changelog ManageSieve v0.11.3: * Changed the SASL service name from "managesieve" into "sieve" as required in the protocol specification. Don't forget to adjust your configuration if your authentication mechanism depends on this service name. * Adapted to changes in Dovecot, making this release dependent on Dovecot >= v1.2.beta1. * Adapted to changes in the new Sieve implementation, making this release dependent on Dovecot Sieve >= v0.1.3 if used. The old cmusieve plugin is still supported. + Implemented making the SIEVE and NOTIFY capability fully dynamic, meaning that the sieve_extensions setting that was introduced for the new Sieve plugin properly affects the ManageSieve daemon as well. + Added support for the CHECKSCRIPT command. In terms of the supported commands, the ManageSieve daemon now complies with protocol VERSION 1.0 as listed in the CAPABILITY response. - Fixed maximum permissions for uploaded scripts; was 0777. This was shielded however by the default umask (not documented to be configurable), so the actual permissions would never have been 0777. - Fixed a segfault bug in the authentication time-out. Bug report and trace provided by Wolfgang Friebel. - Fixed handling of ~/ in use of mail-data for script location. - Fixed small problems in the login proxy support. The following files are released: Sieve: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.3.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.3.tar.gz.sig ManageSieve package: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.3.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.3.tar.gz.s… ManageSieve patch: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.beta1-managesieve-0.11.3.di… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.beta1-managesieve-0.11.3.di… Have fun testing the new releases and don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] delivering to folder based on recipient_delimiter?
by dovecot＠corwyn.net 13 Feb '09

13 Feb '09

I'm currently running postfix + dovecot, with virtual users In postfix I have set recipient_delimiter = + so that postfix accepts mail for user(a)example.com, user+foo(a)example.com, and user+spam(a)example.com all deliver to inbox. what I would like is to have email directed to user+foo(a)example.com delivered to the IMAP folder foo (and, in the context of amavisd, have amavis configured for recipient_delimited, and add addr_extension_spam_maps add +spam to each mail identified as spam, and thus the mail would go to the spam folder on delivery. The postfix guys say I should be able to do this. can someone point me to how to implement this with dovecot? (as I don't see how to even start). Thx Rick Rick Steeves http://www.sinister.net "The journey is the destination"

3 3

[Dovecot] Can't remove folder (no thunderbird issue)
by Jan Niggemann 12 Feb '09

12 Feb '09

Hi, first of all: yes, I already dug the internet but didn't find a solution - that's why I'm asking you. My provider uses dovecot, although I can't tell you more about the version - sorry. Mail is stored in mbox format. My trouble: I was unable to create subfolders and googled a bit. A proposed solution was to append a slash at the end of the folder name. I used Thunderbird to create a folder and called it "test/" (yes, with a slash). Now, in both, Thunderbird and Mulberry, I'm unable to delete that folder (that contains neither messages nor subfolders). Mulberry doesn't give an error message, and in Thunderbird I can't find an option to remove this folder (no matter if subscribed or not). My provider uses roundcube as a webmail interface. Trying to delete the folder there seems to work OK, but after refreshing the folder-view it re-appears. I have no (ssh|telnet|...) access to the server, so I can't remove the folder using the shell.. Do I have other options than calling support? Thank you already jan

4 5

Re: [Dovecot] Mapping usernames
by Henry 12 Feb '09

12 Feb '09

On Thu 12/02/09 18:36 , Timo Sirainen tss(a)iki.fi sent: > abc(a)123.com:. > ...:user=realnamea_abc Thanks Timo, Unfortunately this is still not working. Any further comments would be appreciated. I've tried it two ways:- ATTEMPT 1 ---------------- /etc/dovecot.conf: auth default { userdb passwd-file { args = /etc/dovecot.passwd } passdb passwd-file { args = scheme=plain-md5 username_format=%u /etc/dovecot.passwd } } /etc/dovecot.passwd: bob@vh1.com:$1$Vh6a...::::::userdb_user=vh1_bob Error: auth(default): passwd-file(bob@vh1.com,::ffff:127.0.0.1): no passwd file: scheme=plain-md5 username_format=bob(a)vh1.com /etc/dovecot.passwd ATTEMPT 2 ---------------- /etc/dovecot.conf: auth default { userdb passwd-file { args = /etc/dovecot.passwd } passdb passwd-file { args = /etc/dovecot.passwd } } /etc/dovecot.passwd: bob@vh1.com:{PLAIN-MD5}$1$Vh6a...::::::userdb_user=vh1_bob Error: auth(default): passwd-file(bob@vh1.com,::ffff:127.0.0.1): unknown user I'm missing something obvious, I'm sure of it. Any pointers appreciated. Thanks -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.5 (GNU/Linux) mOIESXlwDRECAOycneJPOwSkETRkjJZdArag8V2rKOR2IUwlDOydIZXv/ITDlWDU dookzEdWh7Ektf1Jlh+YbPNEGoPpQunL8O8AoJbWmNkpoX7jP0Sw/5rDN2eKGHR7 Af9mxTqQ/j3C5LkrTRo9iCTt1TxoqPi6R/w0KkIAuTXBq6j+vIFJcOFgABlMQoXs V2crh1BUCmXVsV1puRJsLWKbAf4uL0V+N8WF4rvWHmJiYjgDn6exv3XHS0F6NhRz n1KVnV0XDWMDq/B/tmj4L2JYxEzWzeNulC5yQBOdx/dLU12XtCNIZW5yeSAoemVu LmNvLnphKSA8aGVucnlAemVuLmNvLnphPohgBBMRAgAgBQJJeXANAhsjBgsJCAcD AgQVAggDBBYCAwECHgECF4AACgkQCHhhdg2iQafVGACdEMtEuUGIW2XJyn9Fig7n sX4qzb4An0PGStBZvAP2qtzYP3SGlzsllzLjuI0ESXlwDRACAMsi4nl8/Yar2m9F ex4dFDgWylLgScQrEhhb2xN0Upcglm60nHQD7c1rP+63Iu+lU0eWvyr8o3JTCN4y PpoGMOMAAwUCAIUnLDMW/tz+qsYaOPyoh7HdAYqcrvVar7t+eKpihNBqfP4CT2Py aRVMN6cSJj9NKZDW6b0QQSCGgN7PpzrLqf6ISQQYEQIACQUCSXlwDQIbDAAKCRAI eGF2DaJBpxeiAJ9cNiuaftSoWke75RT1pn7qoibFfgCdHl6BgP9f450/oziDwaMM w49UeHQ= =qgmL -----END PGP PUBLIC KEY BLOCK-----

1 0

[Dovecot] sendmail smtp auth using client socket
by EQX 12 Feb '09

12 Feb '09

Hi list I searched the net, but could not find something related. Is it possible to export the client socket to sendmail for smtp auth? What would be the sendmail.mc configuration for this? #client { # The client socket is generally safe to export to everyone. Typical use # is to export it to your SMTP server so it can do SMTP AUTH lookups # using it. #path = /var/spool/postfix/private/auth #mode = 0660 #user = postfix #group = postfix #} It can also be the other way round: can Dovecot use Cyrus SASL for user authentication? I need to use sendmail, ip based solutions like pop-before-smtp or poprelay are not an option. Thanks, Mike

4 4

[Dovecot] Mapping usernames
by Henry 12 Feb '09

12 Feb '09

Greets, We're using Dovecot 1.0.7 (which comes with CentOS 5.x). I have successfully configured dovecot to change a username from abc(a)123.com to realname1_abc for a machine which only has a single domain (using auth_username_format=realname1_%Ln). However, I'm pulling my hair out trying to get dovecot to handle multiple domains (the machine has existing /etc/passwd /etc/shadow and /etc/mail/virtusertable users). On an older machine, I simply hacked the source code to perform a berkeley DB lookup in /etc/mail/virtusertable.db for the realname[a-z0-9]_xx. This time round, though, I'm trying to do this cleanly. I've been reading the docs/wiki/etc but I now can't see the forest for the trees. This is what I've got so far: In /etc/dovecot.conf: ... auth default { userdb passwd-file { args = /etc/dovecot.passwd } passdb passwd-file { args = /etc/shadow #args = /etc/dovecot.passwd } } /etc/dovecot.passwd contains: realnamea_abc:{PLAIN-MD5}$1$Vjkfhaa....::::::userdb_user=abc@123.com I've been fiddling around blindly with all kinds of settings in userdb {} above, but I always get the error: "passwd-file(abc@123.com,::ffff:127.0.0.1): unknown user", amongst others. In a nutshell, I want to allow a user to login with abc(a)123.com, this name must be mapped to a real system user (eg, using /etc/dovecot.passwd), then authenticated against /etc/shadow or the MD5 password in /etc/dovecot.passwd I would appreciate any kind of pointers or advise here. It would have been nice if vpopmail allowed me to call an external perl script where I could perform the username mapping, but alas, this is not possible. Thanks Henry -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.5 (GNU/Linux) mOIESXlwDRECAOycneJPOwSkETRkjJZdArag8V2rKOR2IUwlDOydIZXv/ITDlWDU dookzEdWh7Ektf1Jlh+YbPNEGoPpQunL8O8AoJbWmNkpoX7jP0Sw/5rDN2eKGHR7 Af9mxTqQ/j3C5LkrTRo9iCTt1TxoqPi6R/w0KkIAuTXBq6j+vIFJcOFgABlMQoXs V2crh1BUCmXVsV1puRJsLWKbAf4uL0V+N8WF4rvWHmJiYjgDn6exv3XHS0F6NhRz n1KVnV0XDWMDq/B/tmj4L2JYxEzWzeNulC5yQBOdx/dLU12XtCNIZW5yeSAoemVu LmNvLnphKSA8aGVucnlAemVuLmNvLnphPohgBBMRAgAgBQJJeXANAhsjBgsJCAcD AgQVAggDBBYCAwECHgECF4AACgkQCHhhdg2iQafVGACdEMtEuUGIW2XJyn9Fig7n sX4qzb4An0PGStBZvAP2qtzYP3SGlzsllzLjuI0ESXlwDRACAMsi4nl8/Yar2m9F ex4dFDgWylLgScQrEhhb2xN0Upcglm60nHQD7c1rP+63Iu+lU0eWvyr8o3JTCN4y PpoGMOMAAwUCAIUnLDMW/tz+qsYaOPyoh7HdAYqcrvVar7t+eKpihNBqfP4CT2Py aRVMN6cSJj9NKZDW6b0QQSCGgN7PpzrLqf6ISQQYEQIACQUCSXlwDQIbDAAKCRAI eGF2DaJBpxeiAJ9cNiuaftSoWke75RT1pn7qoibFfgCdHl6BgP9f450/oziDwaMM w49UeHQ= =qgmL -----END PGP PUBLIC KEY BLOCK-----

2 1