- dovecot - dovecot.org

[Dovecot] Updating Database records from a Plugin
by John O'Brien 03 Aug '10

03 Aug '10

Guys, In the file /etc/dovecot-pgsql.conf I have driver = pgsql connect = host=localhost dbname=ivr.db user=ivr password=passwd default_pass_scheme = PLAIN password_query = SELECT password FROM embedded_device WHERE username='%u' user_query = SELECT home, uid, gid FROM embedded_device WHERE username='%u' In the table embedded_device there is a field called PIN. My plugin has the "user" and the "pin_value". What I want to do from the plugin is the following: UPDATE embedded_device SET PIN=pin_value WHERE username=user; Questions: Is there a way to locate the exiting database open connection? Is there a way to use the dovecot sql API to set the value of field? I have been looking for examples and have not been very successful. Regards, John

2 1

[Dovecot] Passing Arguments to Plugin
by John O'Brien 03 Aug '10

03 Aug '10

Guys, Making progress on my plugin to support the custom IMAP command required by a special embedded system. Have been looking through the documentation to see if it is possible to pass parameters down to a plugin through the dovecot.conf So is there a simple way? Regards, John

2 1

[Dovecot] [2.0] Experience in production environment
by Luigi Rosa 03 Aug '10

03 Aug '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I decided to put 2.0-pre3 in a couple of production environments with about 50 users each. The configuration is what I consider my own standard: Dovecot, Postfix with authentication via Dovecot, postfixadmin, maildir, userbase on MySQL. The new configuration schema is very flexible and much better than the "monolithic" file. The configuration conversion utility is very useful. No issue to report, the logfile is clean. The only difference between 2.0 and the previous version is the RIM server. Some users have configured their blackberry to synchronize the phone with their mailbox in IMAP. Previously RIM kept a connection open, after upgrading to 2.0, RIM opens a connection and then closes it. This is not an issue, because the synchronization is ok, and I think that is better this way than to keep an oper socket. Just for curiosity: it happens only to me and why this happens? Ciao, luigi - -- / +--[Luigi Rosa]-- \ We believe that no race can be truly intelligent without laughter. --Delenn, "A Race Through Dark Places", Babylon 5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxObh8ACgkQ3kWu7Tfl6ZQatQCfXmYcX7Ke1j76oV41UXr/naU1 gOcAoLw5aRqpynI3EBQW546ja35+Pxoa =tube -----END PGP SIGNATURE-----

3 3

[Dovecot] Patch: New event "mailbox_create" for the mail_log plugin
by Tobias Joch 02 Aug '10

02 Aug '10

Hello, the following patch for the mail_log plugin (source version = 1.2.13) adds a new logging event "mailbox_create". Perhaps this is also of interest to other people except me ;) Best regards, Tobias Index: src/plugins/mail-log/mail-log-plugin.c =================================================================== --- src/plugins/mail-log/mail-log-plugin.c (revision 571) +++ src/plugins/mail-log/mail-log-plugin.c (working copy) @@ -43,12 +43,14 @@ MAIL_LOG_EVENT_MAILBOX_DELETE = 0x10, MAIL_LOG_EVENT_MAILBOX_RENAME = 0x20, MAIL_LOG_EVENT_FLAG_CHANGE = 0x40, - MAIL_LOG_EVENT_APPEND = 0x80 + MAIL_LOG_EVENT_APPEND = 0x80, + MAIL_LOG_EVENT_MAILBOX_CREATE = 0x100 }; #define MAIL_LOG_DEFAULT_EVENTS \ (MAIL_LOG_EVENT_DELETE | MAIL_LOG_EVENT_UNDELETE | \ MAIL_LOG_EVENT_EXPUNGE | MAIL_LOG_EVENT_COPY | \ - MAIL_LOG_EVENT_MAILBOX_DELETE | MAIL_LOG_EVENT_MAILBOX_RENAME) + MAIL_LOG_EVENT_MAILBOX_DELETE | MAIL_LOG_EVENT_MAILBOX_RENAME | \ + MAIL_LOG_EVENT_MAILBOX_CREATE) static const char *field_names[] = { "uid", @@ -71,6 +73,7 @@ "mailbox_rename", "flag_change", "append", + "mailbox_create", NULL }; @@ -597,6 +600,22 @@ return 0; } +static int +mail_log_mailbox_create(struct mail_storage *storage, const char *name, + bool directory) +{ + union mail_storage_module_context *lstorage = MAIL_LOG_CONTEXT(storage); + + if (lstorage->super.mailbox_create(storage, name, directory) < 0) + return -1; + + if ((mail_log_set.events & MAIL_LOG_EVENT_MAILBOX_CREATE) == 0) + return 0; + + i_info("Mailbox created: %s", str_sanitize(name, MAILBOX_NAME_LOG_LEN)); + return 0; +} + static void mail_log_mail_storage_created(struct mail_storage *storage) { union mail_storage_module_context *lstorage; @@ -604,6 +623,7 @@ lstorage = p_new(storage->pool, union mail_storage_module_context, 1); lstorage->super = storage->v; storage->v.mailbox_open = mail_log_mailbox_open; + storage->v.mailbox_create = mail_log_mailbox_create; MODULE_CONTEXT_SET_SELF(storage, mail_log_storage_module, lstorage); -- Tobias Joch Dipl.-Informatiker (FH) Head of Solution Development inovex GmbH Karlsruher Straße 71 D-75179 Pforzheim Tel. +49 7231 - 31 91 71 Fax +49 7231 - 31 91 91 Mobil +49 173 - 31 81 004 tobias.joch(a)inovex.de www.inovex.de Sitz der Gesellschaft: Pforzheim AG Mannheim, HRB 502126 Geschäftsführer: Stephan Müller

2 2

[Dovecot] BUG: Unknown internal error
by myleetlist＠gmx.de 02 Aug '10

02 Aug '10

Hi, I saw this BUG message in the logfile (only one time). dovecot: IMAP(xxx): FETCH for mailbox INBOX UID 4572 failed to read message input: Input/output error dovecot: IMAP(xxx): Disconnected: BUG: Unknown internal error isp=xxx lip=xxx rip=xxx bytes=117/341182 No core file. v1.2.12 Maildir on NFS Debian 32Bit -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

2 1

[Dovecot] Plugin for XFS project quota
by Wessel Dankers 02 Aug '10

02 Aug '10

Hi, I just finished writing a small plugin that reports XFS project quota in de IMAP component of Dovecot (1.2, currently). It was written to fill the needs of our organization but someone else might find this useful as well. In its current form it's not suitable for inclusion in the generic quota backend (see “Drawbacks”). Features: - every mailbox/folder can have its own project ID; - every project ID is mapped to a quota “root”; - caching to ensure reasonable performance; - Debian APT repository available; - LGPL 3 (just like Dovecot itself). Drawbacks: - quota are readonly, you'll have to manage limits and project assignment yourself; - IMAP only: I tried to write a generic quota backend, but the current setup of the quota plugin does not really seem to permit this; - extremely Linux-specific: assumes devices to be available under /dev/block/<maj>:<min> (this is valid for at least Debian lenny); - received only very limited testing; - no documentation whatsoever. How to get it: Sources: https://www.non-gnu.uvt.nl/pub/dovecot-prjquota/ Subversion: https://svn.non-gnu.uvt.nl/uvt-dev/trunk/sources/dovecot-prjquota/ Debian (amd64): deb http://non-gnu.uvt.nl/debian lenny dovecot-prjquota deb-src http://non-gnu.uvt.nl/debian lenny dovecot-prjquota Configuration: protocol imap { ... mail_plugins = imap_prjquota ... } Setting up XFS project quota in general: http://blogs.cae.tntech.edu/mwr/2009/09/01/setting-up-project-quotas-under-… cheers, -- Wessel Dankers <wsl(a)fruit.je> “Sysadmins busy fighting SPAM.”

2 1

[Dovecot] LDAP + mail_location: Get "%d" from customfield
by Denny Schierz 02 Aug '10

02 Aug '10

hi, my mail_location looks like: mail_location = maildir:/imap/spool/%d/%1n/%n:INDEX=/imap/spool/% d/indexes/%1n/%n for example: /imap/spool/domain.foo/a/anton/new The problem is, that the user log in with only the username and no domainpart. So, Dovecot looks into: /imap/spool/a/anton/new what isn't correct. We created an LDAP entry in which domain the user is and searching for a way, to get it working. So, only what I want is to use our customfield as domainpart for the mail_location. Postfix works perfect and delivers the messages in the correct folder. any idea? cu denny

4 11

[Dovecot] Cant compile managesieve 0.11.11 on Solaris10
by Denny Schierz 02 Aug '10

02 Aug '10

hi, i can't compile managesieve-0.11.11 on Solaris 10 against Sieve 0.1.17 and Dovecot 1.2.13: [...] gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -I/usr/sfw/include -o managesieve-login client.o client-authenticate.o managesieve-capability.o managesieve-proxy.o cmd-noop.o /usr/local/dovecot/src/dovecot-1.2-sieve-0.1.17/src/lib-sieve/.libs/libsieve.a /usr/local/dovecot/src/dovecot-1.2.13/src/login-common/liblogin-common.a ../../src/lib-managesieve/libmanagesieve.a ../../src/lib-sievestorage/libsievestorage.a /usr/local/dovecot/src/dovecot-1.2.13/src/lib-storage/libstorage.a /usr/local/dovecot/src/dovecot-1.2.13/src/lib-index/libindex.a /usr/local/dovecot/src/dovecot-1.2.13/src/lib-imap/libimap.a /usr/local/dovecot/src/dovecot-1.2.13/src/lib-mail/libmail.a /usr/local/dovecot/src/dovecot-1.2.13/src/lib-charset/libcharset.a /usr/local/dovecot/src/dovecot-1.2.13/src/lib-auth/libauth.a /usr/local/dovecot/src/dovecot-1.2.13/src/lib/liblib.a -L/usr/sfw/lib -lssl -lcrypto -ldl -lldap -lnsl -lsocket -lrt -lsendfile -R/usr/sfw/lib Undefined first referenced symbol in file SSL_COMP_get_name /usr/local/dovecot/src/dovecot-1.2.13/src/login-common/liblogin-common.a(ssl-proxy-openssl.o) SSL_get_current_compression /usr/local/dovecot/src/dovecot-1.2.13/src/login-common/liblogin-common.a(ssl-proxy-openssl.o) ld: fatal: Symbol referencing errors. No output written to managesieve-login collect2: ld returned 1 exit status gmake[3]: *** [managesieve-login] Error 1 gmake[3]: Leaving directory `/usr/local/dovecot/src/dovecot-1.2-managesieve-0.11.11/src/managesieve-login' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/local/dovecot/src/dovecot-1.2-managesieve-0.11.11/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/local/dovecot/src/dovecot-1.2-managesieve-0.11.11' gmake: *** [all] Error 2 [...] I use OpenSSL from OpenSolaris. any suggestions? cu denny

3 4

Re: [Dovecot] salted passwords
by Leonardo Rodrigues 01 Aug '10

01 Aug '10

Em 31/07/2010 18:51, Patrick Westenberg escreveu: > Leonardo Rodrigues schrieb: >> >> that's all because i already have a account manager system, >> written on PHP, which i had to kept. So i was trying to understand >> how that's work to make it work on my system i couldnt stop using. >> >> but after some tryings i got everything running. All my passwords >> were already migrated from plaintext to Salted-SHA2-256. > > Hi Leonardo, > > can you tell me how you solved your problem with creating salted > passwords via PHP? > Hi .... yes i've acchieved some PHP routines for creating the salted SHA256 password with random salt and also comparing a stored hashed password with a plaintext supplied one. encoded passwords will be exited as: {SSHA256.HEX}acf5ce0f51cca2077e27884a7cec385c430bb402c2f961b02bfa779c18aaf9a373772d99 encoded password strings is 85-char length with the SSHA.256 prefix and 72 without it as i'm storing passwords with the SSHA256.HEX prefix, my dovecot conf has: default_pass_scheme = PLAIN so i can have any dovecot-supported encoded password on the database as well as plaintext ones code may not be very beautiful, i do admit that i'm not good on making beautiful codes .... but its working nice in several places :) http://pastebin.com/fzDGE561 the VerifyHashedPassword routine can receive passwords with the {SSHA256.HEX} string and without as well. That makes easier to just compare database stored passwords as well as the newly generated ones to compare with newly encoded ones based on the plaintext supplied. usage is pretty simple .... something like: $hashedpwd = HashedPassword($plainpwd); and store $hashedpwd whatever you want to store it checking the stored password against a supplied password would be something like: if ( VerifyHashedPassword($hashedpwd,$plainpwd) ) { // supplied plaintext password MATCH with supplied hashed password do whatever you want if passwords matches } else { // supplied plaintext password DO NOT MATCH with supplied hashed password do whatever you want if passwords DO NOT match } Hope this helps you :) -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, NÃO mandem email gertrudes(a)solutti.com.br My SPAMTRAP, do not email it

1 0

Re: [Dovecot] SSHA256 scheme
by Daniel Luttermann 31 Jul '10

31 Jul '10

Patrick Westenberg wrote on 31.07.2010: > Hallo, > Daniel Luttermann schrieb: >> Your PHP application generates the password with the given scheme and >> write it to the password field. > wie soll ich denn via PHP dass Passwort generieren, wenn ich nicht weis > in welcher Art und Weise Passwort und Salt miteinander kombiniert werden > müssen damit Dovecot es versteht. > Gruß > Patrick I'm not familiar with this but there were a thread in February this year about salted passwords: http://www.dovecot.org/list/dovecot/2010-February/046715.html As far as I know dovecotpw or doveadm creates a random salt on every run so when you use PHP it should be possible to use standard routines with a random salt. -- Daniel

1 0