- dovecot - dovecot.org

[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

[Dovecot] need convert-tool advice
by Dave McGuire 31 Jul '10

31 Jul '10

Hi folks, I've got a few thousand accounts that I'd like to convert from mbox to maildir. I'm looking at using convert-tool from the command line to do this, but I'm uncertain about the command line syntax, so I hope someone can take a moment to go over this with me. I'm running dovecot 1.1.6 on this system. Mail accounts are not tied to UNIX system accounts, I'm using the dovecot LDA, users do not have home directories, everything is controlled from a database, and mail directories take the form of: /var/spool/mail/<domainname>/<username>/... The mail directories contain mbox-style spool files, including "inbox" and any user-created mbox-format folders. The entire hierarchy is owned by vmail.vmail. I'd like to batch-convert these offline in such a way that it's transparent to users. Here's what I have so far: ------------------------------------------------------------ mv ${user} ${user}-mbox convert_tool ${user} \ /var/spool/mail/${domain}/${user} \ mbox:/var/spool/mail/${domain}/${user}-mbox:\ INBOX=/var/spool/mail/${domain}/${user}-mbox/inbox \ maildir:/var/spool/mail/${domain}/${user} ------------------------------------------------------------ (sorry about that incomprehensibly long command line, I tried to break it intelligently) ...then I'll change the "mail" field returned by the database query to include maildir instead of mbox. I'll wrap the whole thing in a script and do it in one run. Is this correct usage of convert_tool's command line options? The thing that confuses me is the "home directory" command line option, not sure what that's for, as my mail users don't have home directories...at least not in the UNIX sense, does it mean something else? Will the users notice anything different here, with respect to UIDs, indices, or anything like that? If this is completely the wrong way to do it, I'm not opposed to using a different tool like mb2md.pl, but I looked at that and couldn't quite figure out how to make it work within my current directory structure. Thanks, -Dave -- Dave McGuire Port Charlotte, FL

2 1

[Dovecot] performance problems with {s,m}dbox
by Jake Johnson 31 Jul '10

31 Jul '10

using rc3 and with the latest pigeonhole, I had problems with dovecot (deliver) keeping up with high volumes of E-mail. I tried sdbox, mdbox, and cyrdir all with similar (failed) result. using the default Maildir I had no problems. I did not try mbox. The problems seemed to happen when there were multiple deliver's running to the same folder I had defined in my sieve rules, either it would timeout and fail, or timeout and get delivered to my inbox, crash, or eventually halt because the queue would reach 20,000 messages which is the maximum with my postfix configuration. Everything was fine when I was using Maildir, no errors and no sieve errors/timeouts. perhaps it is more of an issue with pigeonhole than sieve, but thought I would post my experience using dbox, since it sounded like it was a winner based on performance. Jul 29 06:59:12 db1 dovecot: lda(XXXX): Error: Timeout while waiting for lock for transaction log file /home/XXXX/Maildir.mdbox/storage/dovecot.map .index.log Jul 29 06:59:12 db1 dovecot: lda(XXXX): Error: sieve: msgid=< 20100729135337.D7BBA3A03B3(a)db1.XXXXXXX.COM>: failed to store into mailbox 'XXXX': Internal error occurred. Refer to server log for more information. [2010-07-29 06:56:12] Jul 29 06:59:27 db1 dovecot: lda(XXXX): Error: sieve: execution of script /home/XXXX/.dovecot.sieve failed, but implicit keep was successful Jul 29 07:13:53 db1 dovecot: lda(XXXX): Error: Timeout while waiting for lock for transaction log file /home/XXXX/Maildir.mdbox/storage/dovecot.map .index.log Jul 29 07:13:53 db1 dovecot: lda(XXXX): Error: sieve: msgid=< 20100729140329.9CBD73A0334(a)db1.XXXXXxxxxXXXX.com>: failed to store into mailbox 'XXXX': Internal error occurred. Refer to server log for more information. [2010-07-29 07:10:53] Jul 29 07:14:18 db1 dovecot: lda(XXXX): Error: sieve: execution of script /home/XXXX/.dovecot.sieve failed, but implicit keep was successful Jul 29 07:14:18 db1 dovecot: lda(XXXX): Panic: file dbox-file.c: line 76 (dbox_file_free): assertion failed: (file->refcount == 0) Jul 29 07:14:18 db1 dovecot: lda(XXXX): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x39bba) [0x7f40bf715bba] -> /usr/lib/dovecot/libdo vecot.so.0(i_syslog_fatal_handler+0x2b) [0x7f40bf715c4b] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f40bf6f31a6] -> /usr/lib/dovecot/libdov ecot-storage.so.0(+0x794ac) [0x7f40bfbd74ac] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_files_free+0x40) [0x7f40bfbd30b0] -> /usr/lib/doveco t/libdovecot-storage.so.0(+0x77f89) [0x7f40bfbd5f89] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_unref+0x7d) [0x7f40bfb87d4d] -> /usr/ lib/dovecot/libdovecot-storage.so.0(+0x23bf9) [0x7f40bfb81bf9] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_namespaces_deinit+0x23) [0x7f40bfb8 1cd3] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x2bd3d) [0x7f40bfb89d3d] -> /usr/libexec/dovecot/deliver(main+0x688) [0x402ea8] -> /lib/libc.so .6(__libc_start_main+0xfd) [0x7f40bef6bc4d] -> /usr/libexec/dovecot/deliver() [0x4025f9]

2 2

[Dovecot] Dovecot 2.0 - expire with flat file?
by Bernd Schmelter 30 Jul '10

30 Jul '10

I`m using Dovecot 2.0 with only one lokal user, so it`s imho overkill to use mysql. plugin quota with flat file running fine. It's possible expire also running with flat file? What's syntax in dovecot.conf (expire = file:??? and expire_dict?) Benn

3 2

[Dovecot] Dovecot and SSD
by Bryan Vyhmeister 30 Jul '10

30 Jul '10

I'm considering setting up my own mailserver with Dovecot 2.0 (as soon as it's out) and SSD. I'm debating whether it's worth it or not. I have been running a mailserver with the Dovecot 1.1 train for a couple of years and it's been flawless and amazing. I'm thinking about using either FreeBSD 8.1 w/ZFS or OpenBSD 4.8-beta on a 64 GB or 80 GB SSD (Corsair or Intel) using Dovecot 2.0 and mdbox. It seems like mdbox would benefit the most from an SSD because reads would be extremely fast while minimal writes (comparatively) take place due to the way mdbox is structured. I guess what I'm saying is that even if the SSD has average to slow write speeds the fast read speeds would make a big difference in many operations. Any thoughts? Alternately, run either option on a hard drive with indexes on fast flash memory. Anyone tried something like that? Thank you. Bryan

8 16