- dovecot - dovecot.org

[Dovecot] Crash on malformed ldap user_filter
by Anders 26 Feb '08

26 Feb '08

I did a little too much copy/paste, and ended up with an ldap config file containing a line of the form user_filter = user_filter = (&objectClass=... (with "user_filter =" repeated). This caused the auth process to segfault (v1.1.rc1). I suppose that I can reproduce this problem if more information is needed. Anders. 11:56:33 localhost dovecot: auth(default): ldap(a(a)invalid,127.0.0.1): user search: base=o=hosting,dc=invalid, dc=dk scope=subtree filter=user_filter = (&(objectClass=JammMailAccount)(mail=a@invalid)(accountActive=TRUE)(delete=FALSE)) fields=mail 11:56:33 localhost dovecot: child 21296 (auth) killed with signal 11 11:56:33 localhost dovecot: pop3-login: Internal login failure: user=<a@invalid>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured (addresses are edited)

2 1

[Dovecot] Update from 1.0.10 -> 1.1rc1: Odd "quota exceeded" output
by Ralf Hildebrandt 26 Feb '08

26 Feb '08

>From my log: Feb 25 14:53:26 postamt postfix/local[22546]: 0EAA8220697: to=<username(a)postamt.charite.de>, relay=local, delay=0.61, delays=0.16/0.04/0/0.42, dsn=5.7.0, status=bounced (permission denied. Command output: Warning: Growing pool 'Environment' with: 4096 Quota exceeded ) I'm not sure if "Warning: Growing pool 'Environment' with: 4096" should be in that message :) What does it mean, anyway? -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) snickebo(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Unix IS user friendly - it's just selective about who its friends are.

2 2

[Dovecot] Redundant timers
by Anders 25 Feb '08

25 Feb '08

Hello. I am on an irrational crusade against unneeded timers (it started as a well-meaining power saving exercise), and I have now started removing polling in Dovecot. Attached is a patch with the work I did on this the other night. Would something like that be acceptable, or should I make it in a different way? There seems to be no one-shot timer support, right? Is there a Dovecot coding style document? (I did notice that there appears to be an 80 char width that I exceeded) Cheers, Anders

2 4

[Dovecot] 1.1rc1 signal 6 crash (with backtrace)
by Ralf Hildebrandt 25 Feb '08

25 Feb '08

Core was generated by /usr/local/libexec/dovecot/imap'. Program terminated with signal 6, Aborted. (gdb) bt #0 0xb7f6f410 in __kernel_vsyscall () #1 0xb7e3ef15 in raise () from /lib/i686/cmov/libc.so.6 #2 0xb7e40891 in abort () from /lib/i686/cmov/libc.so.6 #3 0x080ce979 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80e9534 "Trying to close mailbox %s with open transactions", args=0xbf8d46b4 "\030�\020\b�F\215��\005\b\020;\020\bg\033\016\b\n") at failures.c:415 #4 0x080ce5cc in i_panic (format=0x80e9534 "Trying to close mailbox %s with open transactions") at failures.c:187 #5 0x0809fbb6 in mailbox_close (_box=0x6) at mail-storage.c:471 #6 0x0805f9db in cmd_logout (cmd=0x81040c0) at cmd-logout.c:18 #7 0x08061c59 in client_command_input (cmd=0x81040c0) at client.c:546 #8 0x08061cee in client_command_input (cmd=0x81040c0) at client.c:595 #9 0x08062483 in client_handle_input (client=0x8103af0) at client.c:636 #10 0x0806269e in client_input (client=0x8103af0) at client.c:691 #11 0x080d6267 in io_loop_handler_run (ioloop=0x81009b0) at ioloop-epoll.c:201 #12 0x080d5518 in io_loop_run (ioloop=0x81009b0) at ioloop.c:301 #13 0x08069f5d in main (argc=Cannot access memory at address 0x34da) at main.c:293 (gdb) -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) snickebo(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de FreeBSD for x86 feature completeness, NetBSD for portability/quality, OpenBSD for "proactive security" and making the system administrator jump through hoops and spit over the left shoulder to make anything work as expected.

3 6

[Dovecot] on dovecot quota.
by Mauro Sanna 25 Feb '08

25 Feb '08

Is it true that if a user reaches quota limit he isn't be able to delete his messages to free his mailbox space?

5 6

[Dovecot] Authentication using multiple password schemes
by hever＠web.de 25 Feb '08

25 Feb '08

Hi there, I tried to patch the actual Dovecot 1.1 rc1 with the http://dovecot.org/patches/1.1/auth-multi-password.diff. The patch doesn't work for this version and I don't want to get an old version. Is this patch perhaps in the 1.1 rc1version included? I'm not sure because I don't really know how it's to use. I thought about returning some password fields from a database. If not could someone provide a working patch ? I need this patch because I'm going to provide NTLM and CRAM-MD5 POP/IMAP authentication because Outlook doesn't support CRAM-MD5 as non-plaintext authentication and I don't want store plaintext passwords. _______________________________________________________________________ Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220

2 1

[Dovecot] mbox with two storage locations
by Bill Pitz 25 Feb '08

25 Feb '08

Hello, I'm trying to migrate a legacy system to Dovecot in which I need to support mbox format storage with the following parameters: Inbox is in: /var/spool/mail/%u Additional mail folders are stored in: /var/spool/mail2/%u (i.e. Spam, Sent, Trash, Drafts, etc.) /var/spool/mail and /var/spool/mail2 are configured with the same permissions. (Read/write/execute user root, Read/write/execute group mail). I've added mail as an additional group in the Dovecot configuration. # dovecot --version 1.0.10 # 1.0.10: /etc/dovecot.conf ssl_cert_file: /etc/pki/dovecot/certs/dovecot.pem ssl_key_file: /etc/pki/dovecot/private/dovecot.pem login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login first_valid_uid: 100 mail_extra_groups: mail mail_location: mbox:/var/spool/mail2/%u:INBOX=/var/spool/mail/%u:INDEX=MEMORY auth default: passdb: driver: pam userdb: driver: passwd The problem is what when I run this configuration, I am not able to see any of the contents of /var/spool/mail2. I ran around with this problem for a while and ultimately found that the following fixes it: cp -Rpfd /var/spool/mail2 /home Change Dovecot to use /home/mail2/%u instead: # 1.0.10: /etc/dovecot.conf ssl_cert_file: /etc/pki/dovecot/certs/dovecot.pem ssl_key_file: /etc/pki/dovecot/private/dovecot.pem login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login first_valid_uid: 100 mail_extra_groups: mail mail_location: mbox:/home/mail2/%u:INBOX=/var/spool/mail/%u:INDEX=MEMORY auth default: passdb: driver: pam userdb: driver: passwd Further investigation revealed that no path outside of /home would work for the storage of the mbox directory. Any ideas? Everything seems to work great except for this one (pretty major) issue. Also, /home, /var, and / are separate filesystems. I'm not sure if that's playing into this or not (doesn't seem like it, since it seems to have no issue storing INBOX in /var/spool/mail). Thanks, -Bill

2 1

[Dovecot] 1.1rc1: Maximum number of mail processes exceeded
by Ralf Hildebrandt 25 Feb '08

25 Feb '08

I'm getting "Maximum number of mail processes exceeded" messages when 512 imap Processes are active. Dovecot reports: Warning: fd limit 1024 is lower than what Dovecot can use under full load (more than 1712). Either grow the limit or change login_max_processes_count and max_mail_processes settings But in my /var/service/dovecot/run script I use: #!/bin/sh mkdir /var/core chmod 1777 /var/core echo /var/core/%p > /proc/sys/kernel/core_pattern ulimit -n unlimited ulimit -c unlimited /usr/local/sbin/dovecot -F So how can I raise the filedescriptor limit above 1024 (linux-2.6.24.2, Debian)? -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) snickebo(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de StGB SS328 Absatz 2.3: Mit Freiheitsstrafe bis zu f�nf Jahren oder mit Geldstrafe wird bestraft, wer eine nukleare Explosion verursacht

4 5

Re: [Dovecot] Dovecot Sieve scalability
by Jan van den Berg 25 Feb '08

25 Feb '08

Hi, What exactly do you mean with "deliver preps the index"? Dovecot itself preps/creates/alters the index, when retrieving mail; right? Or are you (probably) saying this is one more benefit of using 'deliver'. Anyone know of any 'deliver'/(dovecot) stresstests with regards to forking and threading of the deliver binary? Cheers, Jan -----Oorspronkelijk bericht----- Van: Gabriel Millerd [mailto:gmillerd@gmail.com] Verzonden: zaterdag 23 februari 2008 4:01 Aan: Jan van den Berg Onderwerp: Re: [Dovecot] Dovecot Sieve scalability On Fri, Feb 22, 2008 at 2:55 AM, Jan van den Berg <jan.vandenberg(a)isp.solcon.nl> wrote: > > The Dovecot/Sieve implementation is functional but not very elegant or > robust. But this can be explained because Dovecot is build for > _retrieving_ mail (imap/pop) and _not_ delivering mail. > Deliver preps the index, makes retrieving email faster. More so for the average disorganized INBOX in my only folder customers. Sieve makes a lot of things smoother for users, the customer. Especially if they expect server side rules. Obviously the rules that drop each message into a Backups or forward messages to other hosts take up what they take up. My sievec files have ancient mtimes. They are definitely not recompiled upon receiving each email. > Any thoughts on this? Are there people out there with large > Dovecot+Sieve implementations (100k+ users). Are there benchmarks > available; how well does it perform under heavy load (mails/sec)? > Depends entirely on the sieve rules in place. -- Gabriel Millerd

1 0

[Dovecot] Dovecot Sieve scalability
by Jan van den Berg 25 Feb '08

25 Feb '08

Hi, I just finished setting up a functional design with Dovecot+Sieve and it works like a charm. However I'm having serious doubts about the scalability of this. Here is part of a discussion we're having here: About Dovecot+Sieve. What happens here is that your MTA is configured to pass _all_ email to Dovecot which is configured as a LDA. In practice this means this in the Exim config: command = /usr/local/dovecot/libexec/dovecot/deliver So you call on a single binary "deliver". This binary then looks for a .dovecot.sieve file in the user maildir, _compiles_ it to .dovecot.sievec file, and than drops the mail according to the rules. Calling a single binary: that's isn't threaded, doesn't fork, and that has to compile a file (everytime?) it's called isn't scalable. Multiply this with 100 mails(calls) per second and this is bound for problems. The Dovecot/Sieve implementation is functional but not very elegant or robust. But this can be explained because Dovecot is build for _retrieving_ mail (imap/pop) and _not_ delivering mail. Any thoughts on this? Are there people out there with large Dovecot+Sieve implementations (100k+ users). Are there benchmarks available; how well does it perform under heavy load (mails/sec)? Cheers, Jan

2 2