- dovecot - dovecot.org

[Dovecot] Fishing attempt locking up dovecot
by Patrick Milvich 29 Dec '07

29 Dec '07

I've mentioned this before but only heard from one other person who has experienced this, but it's becoming a pretty serious issue. The situation: A spammer sets a bot on a fishing attempt to gain email addresses, causing numerous login processes to spawn and suck up all available resources. The problem: Obviously this can act like a dos attack, but the real issue is after the spammer stops (by virtue of being added to our firewall blacklist, being caught and shut down by their isp, or otherwise), dovecot doesn't seem to relinquish the resources, causing "too many files open" errors for normal usage. The master process usually hangs around 40-50 files open at any given time, with about 10,000 logins a day (I use: lsof -p `cat /var/run/ dovecot/master.pid ` | wc -l), after the attempt is over I always see the files open shoot up to near 3,000 without it able to go down until a dovecot restart. This usually happens about once a month, though we can get unlucky and have it happen a few days apart. I have some log excerpts below. Wondering if this is happening through my own fault or at least within my ability to alleviate the issue. Is there a way to limit the number of connections from an ip address? Has anyone used login_executable to first hit their own solution to keep track of, and implement connection restrictions similar to what I'm aiming for? Thanks for any insight Patrick dovecot -n # 1.0.8: /usr/local/mail/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/local/mail/ssl/certs/dovecot.pem ssl_key_file: /usr/local/mail/ssl/private/dovecot.pem ssl_cipher_list: ALL:!LOW disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/mail/dovecot/libexec/dovecot/ imap-login login_executable(imap): /usr/local/mail/dovecot/libexec/dovecot/imap- login login_executable(pop3): /usr/local/mail/dovecot/libexec/dovecot/pop3- login first_valid_uid: 500 mail_location: maildir:/Volumes/data/mail/%Ld/%Ln mail_executable(default): /usr/local/mail/dovecot/libexec/dovecot/imap- before mail_executable(imap): /usr/local/mail/dovecot/libexec/dovecot/imap- before mail_executable(pop3): /usr/local/mail/dovecot/libexec/dovecot/pop3- before mail_plugin_dir(default): /usr/local/mail/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/mail/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/mail/dovecot/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: plain digest-md5 login passdb: driver: sql args: /usr/local/mail/dovecot/etc/dovecot-sql.conf userdb: driver: static args: uid=exim gid=exim plugin: quota: maildir From the logs, first entries showing the problem: dovecot: Dec 10 16:17:02 Info: pop3-login: Disconnected: rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:02 Info: pop3-login: Disconnected: rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:03 Info: pop3-login: Disconnected: rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:03 Info: pop3-login: Disconnected: rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:03 Info: pop3-login: Disconnected: rip=207.245.39.90, lip=<lip> A little later on: dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<pwitest>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<tsinternetuser>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<bill>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<web>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<barbara>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<www>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<user>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<nathan>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<webmaster>, method=PLAIN, rip=207.245.39.90, lip=<lip> etc. etc.

3 2

[Dovecot] v1.1.beta11 released
by Timo Sirainen 29 Dec '07

29 Dec '07

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta11.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta11.tar.gz.sig This one should be the last beta release before the first v1.1 release candidate. I'll try to stay away from this list and Dovecot in general for the next 1,5 weeks. I've several exams coming up and I should have started studying for them days ago already.. :) The main things left in my TODO are: - Squat indexes should handle expunges - Lucene indexes are broken - See if \recent flag handling could be fixed for maildir/mbox (it works for dbox though) - Some other minor things which I'll do if I have time, but won't block v1.1.0 release. Changes since beta10: - One major performance issue found and fixed. This was the main reason why we weren't yet in release candidate stage. - configure --with-package now gives an error if it can't find the necessary libs/headers for the package. Use --with-package=auto for the old behavior. - Memory leak fixes - Convert plugin fixes. Conversion is now done to namespace with INBOX. - Changes to handling group adding/removing to processes. Hopefully didn't break anything. - Message flag/keyword searches are now faster - Fixes/optimizations to handling SORT. After building initial indexes, my 260k mail mailbox sorts in about 0.01 seconds. :) - Fixes to searching mails with unknown charsets/invalid data - deliver_log_format setting

3 8

[Dovecot] 1.1.beta10 pop3 process hangs with 100% CPU
by arvids 29 Dec '07

29 Dec '07

Hello, we have observed pop3 process which got stuck consuming all available CPU. It seems that it happened because of some kind of abnormal POP3 connection termination. Here is strace info for this process: 13:36:05.866190 writev(1, [{"508qWWH96If+uVXeH2Zxl/hkn+plVwmI"..., 3975}, {"HP1oxt+np0o4Xtz27VQBtxx0zWfGuA3r"..., 193}], 2) = -1 EPIPE (Broken pipe) 13:36:05.866250 --- SIGPIPE (Broken pipe) @ 0 (0) --- 13:36:05.866288 epoll_ctl(6, EPOLL_CTL_DEL, 1, {0, {u32=135259776, u64=135259776}}) = 0 13:36:05.866335 setsockopt(1, SOL_TCP, TCP_CORK, [1], 4) = 0 13:36:05.866372 writev(1, [{"508qWWH96If+uVXeH2Zxl/hkn+plVwmI"..., 3975}, {"HP1oxt+np0o4Xtz27VQBtxx0zWfGuA3r"..., 193}], 2) = -1 EPIPE (Broken pipe) 13:36:05.866441 --- SIGPIPE (Broken pipe) @ 0 (0) --- 13:36:05.866478 writev(1, [{"508qWWH96If+uVXeH2Zxl/hkn+plVwmI"..., 3975}, {"HP1oxt+np0o4Xtz27VQBtxx0zWfGuA3r"..., 193}], 2) = -1 EPIPE (Broken pipe) 13:36:05.866539 --- SIGPIPE (Broken pipe) @ 0 (0) --- 13:36:05.866575 epoll_ctl(6, EPOLL_CTL_ADD, 1, {EPOLLOUT|EPOLLERR|EPOLLHUP, {u32=135259776, u64=135259776}}) = 0 13:36:05.866623 setsockopt(1, SOL_TCP, TCP_CORK, [0], 4) = 0 13:36:05.866660 gettimeofday({1197372965, 866675}, NULL) = 0 13:36:05.866698 epoll_wait(6, {{EPOLLHUP, {u32=135259776, u64=135259776}}}, 4, 6986) = 1 13:36:05.866737 gettimeofday({1197372965, 866752}, {4294967176, 0}) = 0 Regards, Arvids

2 1

Re: [Dovecot] namespace problem / 1.1beta11
by ja nein 29 Dec '07

29 Dec '07

Hi Timo, well, I don't know how I managed it, either :) Here's the output of the log file with mail_debug=yes. Interestingly it prints out the correct namespace in the log file (I did a synchronization of some folders in this period): Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): Loading modules from directory: /opt/dovecot-1.1-beta12/lib/dovecot/imap Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): Module loaded: /opt/dovecot-1.1-beta12/lib/dovecot/imap/lib20_fts_plugin.so Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): Module loaded: /opt/dovecot-1.1-beta12/lib/dovecot/imap/lib21_fts_squat_plugin.so Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): Effective uid=40000, gid=40000, home=/home/dovecot/mail/smcc.net/merk@smcc.net Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): Namespace: type=private, prefix=INBOX/, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): maildir: data=/home/dovecot/mail/smcc.net/merk@smcc.net:INDEX=/home/dovecot/index/sm… Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): maildir++: root=/home/dovecot/mail/smcc.net/merk@smcc.net, index=/home/dovecot/index/smcc.net/merk@smcc.net, control=, inbox=/home/dovecot/mail/smcc.net/merk@smcc.net Dec 28 23:24:33 51 dovecot: imap-login: Login: user=<merk(a)smcc.net>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Dec 28 23:24:52 51 dovecot: IMAP(merk(a)smcc.net): Disconnected: Logged out bytes=17572/71038 It seems that the output to the client doesn't correspond to the settings dovecot uses internally?! Regards, Sebastian ----- Ursprüngliche Mail ---- Von: Timo Sirainen <tss(a)iki.fi> An: ja nein <reg9009(a)yahoo.de> CC: Dovecot Mailing List <dovecot(a)dovecot.org> Gesendet: Freitag, den 28. Dezember 2007, 18:45:56 Uhr Betreff: Re: [Dovecot] namespace problem / 1.1beta11 On Sat, 2007-12-22 at 13:48 +0000, ja nein wrote: > I think I've hit a separator bug: > > This is namespace query of dovecot and source server: > > * NAMESPACE (("INBOX/" ".")) NIL NIL Yes, that does look like a bug, but I've no idea how you managed to cause it. I just tested your namespace configuration and it works fine with me. Also there shouldn't even be any way to cause this configuration for a list=yes namespace: imap(tss)(pid=31754): namespace configuration error: list=yes requires prefix=INBOX/ to end with separator What do logs show with mail_debug=yes? __________________________________ Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern. www.yahoo.de/clever

2 1

[Dovecot] auth-ldap not resetting connection state after failed bind
by Brendan Braybrook 29 Dec '07

29 Dec '07

timo, i think i found a small problem with the ldap implementation: when using auth_bind (this might be in all conditions, not just that one - i haven't tested further), if the server lost connection to the ldap server (ie, the ldap server died) dovecot-auth would never reconnect to the ldap server and all subsequent auth attempts would fail. after a little more digging, i discovered that if the ldap server went down and came back up before the next dovecot request then everything would be fine. however, if a request came in while the ldap server was down then dovecot-auth would "cache" that the server was unavailable and never recheck it. i believe i tracked it down to a couple lines in db_ldap_bind and fixed it - dovecot-auth is reconnecting to ldap in the condition where it was not previously: --- dovecot-1.0.3/src/auth/db-ldap.c 2007-10-15 18:26:55.983349000 +0000 +++ dovecot-1.0.3/src/auth/db-ldap.c.new 2007-10-15 18:28:03.124136000 +0000 @@ -446,7 +446,10 @@ msgid = ldap_bind(conn->ld, conn->set.dn, conn->set.dnpass, LDAP_AUTH_SIMPLE); if (msgid == -1) { - db_ldap_connect_finish(conn, ldap_get_errno(conn)); + if (db_ldap_connect_finish(conn, ldap_get_errno(conn)) < 0) { + /* lost connection, close it */ + ldap_conn_close(conn, TRUE); + } i_free(ldap_request); return -1; }

3 3

[Dovecot] sieve variables
by Pavel Volkovitskiy 29 Dec '07

29 Dec '07

Hello! I wonder if that possible to add support for sieve variables extension in upcoming dovecot 1.1? ( ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-sieve-variable… ) -- Pavel

3 2

[Dovecot] dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server
by Rolf E. Sonneveld 28 Dec '07

28 Dec '07

Hi, I'm new to the list; excuse me if this has been asked recently/before. running: # dovecot --version 1.0.8 Output of dovecot -n: base_dir: /var/run/dovecot protocols: none ssl_disable: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf socket: type: listen client: path: /usr/local/postfix/spool/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot-auth-master mode: 438 Using dovecot only for the purpose of providing SMTP AUTH service for Postfix, using Active Directory (AD) as authentication source. As you can see from the config, connectivity between Dovecot and AD is implemented using LDAP. Contents of /usr/local/dovecot/etc/dovecot-ldap.conf (some site-specific info masqueraded): auth_bind = yes pass_filter = (sAMAccountName=%u) hosts = AD1.domain.com:3268 AD2.domain.com:3268 dn = CN=Service Account Postfix,OU=Services,DC=domain,DC=com dnpass = secret ldap_version = 3 base = DC=domain,DC=com scope = subtree Now, this works fine and authentication via SMTP AUTH + Dovecot works perfect. Yet, every 15 minutes I get the following warning in the syslog logfile: Dec 24 07:20:00 hostname dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Dec 24 07:35:01 hostname dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Dec 24 07:50:01 hostname dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Dec 24 08:05:02 hostname dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Dec 24 08:20:02 hostname dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Dec 24 08:35:03 hostname dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server I've looked through the archives and it seems that this problem is caused by the fact that Dovecot (using the OpenLDAP client libraries?) keeps the LDAP connection open; after (in our case) 15 minutes Active Directory closes the connection and Dovecot signals this in the syslog (and presumably automatically will create a new connection to AD). I'm pretty sure that the OpenLDAP client libraries provide options to use a client-side timeout for LDAP connections. My questions are: * is there a reason that Dovecot wants to keep the LDAP connection open? * Will the new V1.1 version have a config parameter to set the LDAP client timeout or a default timeout value to close the connection? * If there's no 'fix' foreseen for V1.1, I'd like to file a request to add such a parameter. How can I file such a request? The warning is annoying; the sysadmin will create a filter, to filter the warning out from the syslog, but I'm afraid that if there's a real problem with authentication, that will be filtered too and the real problem is not noticed, before users start to complain. /rolf

2 3

Re: [Dovecot] namespace problem / 1.1beta11
by ja nein 28 Dec '07

28 Dec '07

Hi Timo, I think I've hit a separator bug: This is namespace query of dovecot and source server: ---snip--- * OK Dovecot ready. 1 login ... 1 OK Logged in. 2 NAMESPACE * NAMESPACE (("INBOX/" ".")) NIL NIL 2 OK Namespace completed. 3 logout * BYE Logging out 3 OK Logout completed. Connection closed by foreign host. Escape character is '^]'. * OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID STARTTLS AUTH=CRAM-MD5 AUTH=DIGEST-MD5 AUTH=NTLM AUTH=SRP AUTH=OTP AUTH=PASSDSS-3DES-1 SASL-IR] Cyrus IMAP4 v2.3.8 server ready 1 login ... 1 OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID LOGINDISABLED ACL RIGHTS=kxte QUOTA MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT SORT=MODSEQ THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE CATENATE CONDSTORE IDLE LISTEXT LIST-SUBSCRIBED X-NETSCAPE URLAUTH] User logged in 2 NAMESPACE * NAMESPACE (("INBOX/" "/")) (("user/" "/")) (("" "/")) 2 OK Completed 3 logout * BYE LOGOUT received ---snip--- So Dovecot is stating Namespace separator is ".". But my dovecot -n namespace section shows: namespace: type: private separator: / prefix: INBOX/ inbox: yes list: yes subscriptions: yes According to this I've set separator to "/". And this is the problem. I think problem arised somewhere between beta9 and beta11, as it worked before... The separator in imapsync was for both "/" (--sep1 /, --sep2 /), I just played with all possibilities... Well, never mind if v1.2 or v2.0, as long as LMTP makes it in ;) Anyway, we can provide some good stress testing in such an environment... Regards and for all Merry Christmas and a happy new year! Sebastian ----- Ursprüngliche Mail ---- Von: Timo Sirainen <tss(a)iki.fi> An: ja nein <reg9009(a)yahoo.de> CC: dovecot(a)dovecot.org Gesendet: Freitag, den 21. Dezember 2007, 18:19:31 Uhr Betreff: Re: [Dovecot] namespace problem / 1.1beta11 On Wed, 2007-12-12 at 07:16 +0000, ja nein wrote: > From Folder [INBOX/Trash] .. > /home/imapsync/imapsync --host1 ip.of.host.1 --user1 user1 --password1 password --host2 127.0.0.1 --user2 user2 --password2 password --authmech2 LOGIN --regextrans2 s/\./_/g --delete2 --sep1 . --sep2 . --justfolders Shouldn't those be -sep1 / -sep2 /. Or at least the one that's on Dovecot's side. > Btw., as we work in a load balanced environment, LMTP delivery would be a great feature for upcoming releases, as it would enable people to use multiple frontends of SMTP servers without the need of connecting them to a somewhat shared file system. Forwarding all mail to a SMTP server on the machine running dovecot and doing delivery there isn't the favoured option (at least for us). Yes, LMTP would be nice, but it pretty much requires v2.0 framework. I'm still not sure if the next version will be v1.2 or v2.0.. Jetzt Mails schnell in einem Vorschaufenster überfliegen. Dies und viel mehr bietet das neue Yahoo! Mail - www.yahoo.de/mail

3 2

[Dovecot] assertion on deliver (1.1.beta10)
by Nuno Lopes 28 Dec '07

28 Dec '07

Hi, I'm testing version 1.1.beta10 and getting these assertions on deliver: file index-transaction.c: line 54 (index_transaction_finish_rollback): assertion failed: (t->mail_ref_count == 0) This was after an upgrade from a 1.0 release candidate. If you need I can try and reproduce this in a more controled environment to pinpoint the problem. Thanks, -- Nuno Lopes

2 4

[Dovecot] Dovecot + Cygwin the 2nd
by Ronny 28 Dec '07

28 Dec '07

Hi, i still try to get dovecot to run under cygwin. After a post on the cygwin list i am able tu run dovecot. Under Cygwin you have to run dovecot by inetd. Starting the binary "dovecot.exe" does not work. Well the server is running but answers with a fatal error. Account: 'localhost', Server: 'localhost', Protokoll: POP3, Serveranswer: 'Fatal: EOF while reading environment from master', Port: 110, Secure (SSL): No, error on server: 0x800CCC90, Fehlernummer: 0x800CCC90 This error is from Outlook, Thunderbird just says there is an error without any error message. So maybe you can help me to bring my story to a hapy end ;-) Cheers Ronny

3 11

[Dovecot] cache files corruption
by Dmitry Pryadko 28 Dec '07

28 Dec '07

Here what one of my users sometimes gets in logs when using IMAP: dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Disconnected in IDLE dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Maildir /usr/local/mail/pawlin.mass.hc.ru/skribtsov/Maildir sync: UID inserted in the middle of mailbox (59 > 16, file = 1198267793.H747026P68033.mail5.hc.ru:2,RS) dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Disconnected: Mailbox is in inconsistent state, please relogin. dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Maildir /usr/local/mail/pawlin.mass.hc.ru/skribtsov/Maildir sync: UID inserted in the middle of mailbox (59 > 16, file = 1198267793.H747026P68033.mail5.hc.ru:2,RS) dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Disconnected: Mailbox is in inconsistent state, please relogin. dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Corrupted transaction log file /usr/local/mail/pawlin.mass.hc.ru/skribtsov/Maildir/dovecot.index.log.2: invalid indexid (1198254020 != 1198498301) dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Corrupted index cache file /usr/local/mail/pawlin.mass.hc.ru/skribtsov/Maildir/dovecot.index.cache: indexid changed After that, some messages could "disappear" from messages list. And then maybe "appear" again. When I delete dovecot.* files, all goes ok. I use NFS storage. BTW, it seems like this problem exists only when working with M$ Outlook :) # 1.0.5: /usr/local/etc/dovecot.conf syslog_facility: local7 protocols: imap pop3 imaps pop3s ssl_cert_file: /etc/ssl/mail5.hc.ru.pem ssl_key_file: /etc/ssl/mail5.hc.ru.pem disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: Mail server ready. login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_max_processes_count: 256 max_mail_processes: 2048 verbose_proctitle: yes first_valid_uid: 90 last_valid_uid: 65000 first_valid_gid: 90 last_valid_gid: 90 mail_extra_groups: mail mail_location: maildir:~/Maildir mmap_disable: yes lock_method: dotlock mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login cram-md5 verbose: yes debug: yes debug_passwords: yes worker_max_count: 150 passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vexim plugin: quota: maildir -- Dmitry Pryadko http://www.hc.ru

2 5

[Dovecot] per user quota
by Massimo Maioli 28 Dec '07

28 Dec '07

Hi, i've tryed to setup per user quota with postfix/dovecot, but without luck. My configuration is: postfix 2.3.8 with virtualdomain on mysql (http://workaround.org tutorial) dovecot 1.0.9 IMAP/PO3 OK on dovecot config, i've made the changes for the quota plugin, i've setup the gereral quota at 20MB, with this configuration: quota = maildir:storage=20480:messages=1000 it works very well, from telnet connection and squirrelmail, i see the right % of quota used. My problem is the per user quota, if i want give some user, more or minus space, i'm not able to do this. I've added a quota field to the mysql that read dovecot, but i don't know ho to read this in dovecot-mysql.conf. Someone can help me? Thanks

2 1

[Dovecot] Audit log?
by Bjørn T Johansen 26 Dec '07

26 Dec '07

Where can I found the log that dovecot writes if a user fails to log in? I am authenticating agains an sql db, but I can't find where dovecot logs this, if it does? Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bjørn T Johansen btj(a)havleik.no ----------------------------------------------------------------------------------------------- Someone wrote: "I understand that if you play a Windows CD backwards you hear strange Satanic messages" To which someone replied: "It's even worse than that; play it forwards and it installs Windows" -----------------------------------------------------------------------------------------------

5 9

[Dovecot] v1.1.beta12 released
by Timo Sirainen 25 Dec '07

25 Dec '07

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta12.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta12.tar.gz.sig Still not a release candidate, maybe the next one.. This release fixes a lot of bugs and adds some new sanity checks. Fixes quite a lot of mbox problems. v1.1.beta11 (no other versions) had a potential security hole where memory was free()d multiple times. \Recent flags should work perfectly now with mbox. Still somewhat broken with maildir.

2 1

[Dovecot] Dovecot Log control=
by Evaggelos Balaskas 24 Dec '07

24 Dec '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i use dovecot-1.0.9 + sieve plugin 1.0.2 pop3 - imap, virtual users from file with MD5-CRYPT some with maildir some with mbox, spamassasin + sieve filter per user, etc - etc and everything are simple perfect. The only real question i have is this: in the logs when the dovect LDA deliver a mail to a maildir account is something control= What exactly is this ? deliver(ebalaskas): Dec 14 23:32:35 Info: maildir: root=/var/mail/folders/ebalaskas, index=/var/mail/index/ebalaskas, control=, inbox= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYvb0WIK+Pe9twhoRAnyVAKCKHsvi7DJ01uYnAQvbeLNh85HBoQCgxtSp Sm9WetpSQMJsiyp0wAkReOQ= =k0f0 -----END PGP SIGNATURE-----

2 2

[Dovecot] Brute Force Blocking?
by Ben Cadieux 24 Dec '07

24 Dec '07

Hi Everyone, Before I begin, I'd just like to mention: I love dovecot. Thank you :) Anyway, today I had 8000 login attempts to my dovecot server in an hour before blocking the IP with my firewall. After googling, I didn't see very much discussion on the topic. There was some mention of blocksshd which was supposed to support dovecot in the next release (but doesn't appear to) and also fail2ban. While a script that parses logfiles will work, I'm not sure that this is the best way to go about handling repeated authentication failure. Would it not be best built into dovecot? Are there any plans for this? Best Regards, Ben Cadieux

8 8

[Dovecot] Compact all maildirs with dovecot-1.0.9?
by Jeff Kowalczyk 23 Dec '07

23 Dec '07

I'm running dovecot-1.0.9 on Gentoo Linux. I recently observed a large increase in disk usage on this dedicated mailserver. I attribute it to high spam traffic and/or large attachments for legit email retained on the server. How can I run a command equivalent to an IMAP client's 'Compact Folder' on the entire tree of maildirs under each /home/(user)? Thanks.

2 1

Re: [Dovecot] namespace problem / 1.1beta11
by ja nein 22 Dec '07

22 Dec '07

yep, originally I want Dovecot to behave exactly the same like our Cyrus environment regarding namespaces, in preparation of a migration :) The first login shows Dovecot output, second show Cyrus, for comparison... Regards, Sebastian ----- Ursprüngliche Mail ---- Von: Charles Marcus <CMarcus(a)Media-Brokers.com> An: Dovecot Mailing List <dovecot(a)dovecot.org> Gesendet: Samstag, den 22. Dezember 2007, 16:24:00 Uhr Betreff: Re: [Dovecot] namespace problem / 1.1beta11 On 12/22/2007, ja nein (reg9009(a)yahoo.de) wrote: > AUTH=DIGEST-MD5 AUTH=NTLM AUTH=SRP AUTH=OTP AUTH=PASSDSS-3DES-1 > SASL-IR] Cyrus IMAP4 v2.3.8 server ready Cyrus?? -- Best regards, Charles __________________________________ Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern. www.yahoo.de/clever

2 1

Re: [Dovecot] v1.1.beta12 deliver crashes (arvids) Ditto!
by Jerry Yeager 22 Dec '07

22 Dec '07

On Dec 22, 2007, at 5:00 AM, dovecot-request(a)dovecot.org wrote: (stuff cut out) > Message: 10 > Date: Sat, 22 Dec 2007 11:12:30 +0200 > From: arvids <arvids(a)mpe.lv> > Subject: [Dovecot] v1.1.beta12 deliver crashes > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <200712221112.30760.arvids(a)mpe.lv> > Content-Type: text/plain; charset="us-ascii" > > Hello, > > v1.1.beta12 deliver crashes: > > Dec 22 11:05:29 iserver deliver(tests2): file index-mail.c: line > 1042 (index_mail_close): assertion failed: (!mail- > >data.destroying_stream) > Dec 22 11:05:29 iserver deliver(tests2): Raw backtrace: /usr/local/ > dovecot/libexec/dovecot/deliver(i_syslog_fatal_handler+0x2c) > [0x80baa8c] -> /usr/local/do > vecot/libexec/dovecot/deliver [0x80ba88b] -> /usr/local/dovecot/ > libexec/dovecot/deliver [0x80852e1] -> /usr/local/dovecot/libexec/ > dovecot/deliver(index_mail > _free+0xe) [0x8085f5e] -> /usr/local/dovecot/libexec/dovecot/ > deliver(mail_free+0x10) [0x80a9b70] -> /usr/local/dovecot/libexec/ > dovecot/deliver(main+0xfce) [ > 0x805a9be] -> /lib/libc.so.6(__libc_start_main+0xd8) [0xb7e69df8] - > > /usr/local/dovecot/libexec/dovecot/deliver [0x8058a51] > more stuff cut out > > Regards, Arvids > > > ------------------------------ > I am getting essentially the same type of error, except that the message actually is delivered along with a receipt to the sender that it was not able to be delivered. Dec 22 11:33:57 mac-g5 deliver(jerry(a)scene-naturally.dyndns.org) [28416]: msgid=<B865E78F-83BB-4B46-864C-44EEC1BC01AF(a)scene-naturally.dyndns.org >: saved mail to INBOX Dec 22 11:33:57 mac-g5 deliver(jerry(a)scene-naturally.dyndns.org) [28416]: file index-mail.c: line 1042 (index_mail_close): assertion failed: (!mail->data.destroying_stream) Dec 22 11:33:57 mac-g5 deliver(testuser(a)scene-naturally.dyndns.org) [28417]: auth input: testuser(a)scene-naturally.dyndns.org Dec 22 11:33:57 mac-g5 deliver(jerry(a)scene-naturally.dyndns.org) [28416]: Raw backtrace: 2 deliver 0x00000000000c8ae4 i_syslog_fatal_handler + 124 -> 3 deliver 0x00000000000c8598 i_fatal + 0 -> 4 deliver 0x0000000000057f5c index_mail_close + 264 -> 5 deliver 0x0000000000058958 index_mail_free + 68 -> 6 deliver 0x00000000000a406c mail_free + 68 - > 7 deliver 0x00000000000055d8 main + 4344 -> 8 deliver 0x00000000000010d0 start + 68 Dec 22 11:33:58 mac-g5 postfix/pipe[28415]: 251EE4D094C: to=<jerry(a)scene-naturally.dyndns.org >, relay=dovecot, delay=0.38, delays=0.02/0.04/0/0.32, dsn=5.3.0, status=bounced (Command died with signal 6: "/usr/local/libexec/ dovecot/deliver") Dec 22 11:33:58 jerry-yeagers-power-mac-g5 postfix/qmgr[67]: 251EE4D094C: removed Switching to using the Postfix deliver works and it seems everything else in the new beta 12, so far, is fine. Running on OS X 10.5.1 Jerry

1 0

[Dovecot] v1.1.beta12 deliver crashes
by arvids 22 Dec '07

22 Dec '07

Hello, v1.1.beta12 deliver crashes: Dec 22 11:05:29 iserver deliver(tests2): file index-mail.c: line 1042 (index_mail_close): assertion failed: (!mail->data.destroying_stream) Dec 22 11:05:29 iserver deliver(tests2): Raw backtrace: /usr/local/dovecot/libexec/dovecot/deliver(i_syslog_fatal_handler+0x2c) [0x80baa8c] -> /usr/local/do vecot/libexec/dovecot/deliver [0x80ba88b] -> /usr/local/dovecot/libexec/dovecot/deliver [0x80852e1] -> /usr/local/dovecot/libexec/dovecot/deliver(index_mail _free+0xe) [0x8085f5e] -> /usr/local/dovecot/libexec/dovecot/deliver(mail_free+0x10) [0x80a9b70] -> /usr/local/dovecot/libexec/dovecot/deliver(main+0xfce) [ 0x805a9be] -> /lib/libc.so.6(__libc_start_main+0xd8) [0xb7e69df8] -> /usr/local/dovecot/libexec/dovecot/deliver [0x8058a51] My dovecot -n: # 1.1.beta12: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ syslog_facility: local0 protocols: pop3 imap ssl_cert_file: /etc/postfix/mail-cert.pem ssl_key_file: /etc/postfix/mail-key.pem disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_greeting: Server. login_process_per_connection: no login_processes_count: 5 login_max_processes_count: 32 verbose_proctitle: yes first_valid_uid: 95 first_valid_gid: 95 mail_uid: 95 mail_gid: 95 mail_location: maildir:~/Maildir mail_debug: yes fsync_disable: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/rawlog /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/rawlog /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail imap_client_workarounds(imap): delay-newmail imap_client_workarounds(pop3): pop3_enable_last(default): no pop3_enable_last(imap): no pop3_enable_last(pop3): yes pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: . inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login digest-md5 cram-md5 apop cache_size: 1024 cache_ttl: 600 cache_negative_ttl: 60 user: doveauth verbose: yes passdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: dict:::proxy:/var/run/dovecot/dict-server:quotadict dict: quotadict: mysql:/usr/local/dovecot/etc/dovecot-sql-dict-quota.conf Regards, Arvids

2 1

[Dovecot] How to restore old mailbox
by Simon Gao 22 Dec '07

22 Dec '07

Hi, I have issue with one user mailbox in /var/spool/mail. I have to restore older version of the same mailbox file over the newer one. What's the best way to do this? Simon

2 1

[Dovecot] Squirrelmail + Dovecot + Maildir
by Vicki Stanfield 21 Dec '07

21 Dec '07

I have been struggling with getting my Fedora 7 box set up to use dovecot with Squirrelmail and Maildir. It works correctly with the exception of writing outgoing mail to the right folder (.Sent) or drafts (.Drafts). If I send a mail with Mutt, it writes the mail to the right place, so it has to be squirrelmail config or dovecot config. I want to use .Sent for sent-mail (~user/Maildir/.Sent) and .Drafts for drafts (~user/Maildir/.Drafts). Here is what I see in /etc/squirrelmail/config.php $optional_delimiter = '.'; [snip] $default_folder_prefix = ''; $trash_folder = 'Trash'; $sent_folder = 'Sent'; $draft_folder = 'Drafts'; $default_move_to_trash = true; $default_move_to_sent = true; $default_save_as_draft = true; The error in the browser is: * ERROR : Bad or malformed request.* Server responded: {830} BAD Error in IMAP command : Unknown command. and in the logs I see this: Dec 18 09:41:56 opus postfix/smtpd[12747]: connect from localhost[127.0.0.1] Dec 18 09:41:56 opus postfix/smtpd[12747]: 4CB7329B00B2: client=localhost[127.0.0.1] Dec 18 09:41:56 opus postfix/cleanup[12750]: 4CB7329B00B2: message-id=<51150.127.0.1.1.1197988916.squirrel(a)127.0.1.1> Dec 18 09:41:56 opus postfix/qmgr[2650]: 4CB7329B00B2: from=<vic(a)thepenguin.net>, size=1015, nrcpt=1 (queue active) Dec 18 09:41:56 opus postfix/smtpd[12747]: disconnect from localhost[127.0.0.1] Dec 18 09:41:56 opus dovecot: imap-login: Login: user=<vic>, method=PLAIN, rip=::ffff:127.0.1.1, lip=::ffff:127.0.1.1, secured Dec 18 09:41:56 opus dovecot: IMAP(vic): Disconnected: Too many invalid IMAP commands. Dec 18 09:41:59 opus postfix/smtp[12751]: 4CB7329B00B2: to=<vstanfield(a)other.com>, relay=platinum.fusionalliance.com[168.215.73.114]:25, delay=3.6, delays=0.08/0.01/2.6/0.89, dsn=2.0.0, status=sent (250 Requested mail action okay, completed) Dec 18 09:41:59 opus postfix/qmgr[2650]: 4CB7329B00B2: removed As you can surmise from the logs, the mail does get sent. Anybody see my mistake? CaptainVic

5 5

[Dovecot] 1.1.beta11 crashes
by Brian Taber 21 Dec '07

21 Dec '07

I am running 1.1.beta11 because I was having locking and coruption issues with indexes and mailbox on the latest release version. Some of my previous corrupted indexes caused an issue with 1.1.beta11: Dec 20 21:25:40 ra dovecot: IMAP(bodil(a)mydomain.com): Raw backtrace: imap [0x47ef81] -> imap [0x47eca6] -> imap [0x42c3bc] -> imap [0x42f201] -> imap [0x42f324] -> imap [0x41d585] -> imap(imap_fetch+0x147) [0x41cb17] -> imap(cmd_fetch+0x1bc) [0x41686c] -> imap(cmd_uid+0x52) [0x419c42] -> imap [0x41a508] -> imap [0x41a5aa] -> imap(client_input+0x72) [0x41ab72] -> imap(io_loop_handler_run+0x106) [0x485746] -> imap(io_loop_run+0x1d) [0x484dbd] -> imap(main+0x401) [0x421f51] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x30af61d8a4] -> imap [0x414fa9] Dec 20 21:25:40 ra dovecot: child 4353 (imap) killed with signal 6 Dec 20 21:28:24 ra dovecot: IMAP(bodil(a)mydomain.com): file maildir-uidlist.c: line 840 (maildir_uidlist_set_ext_real): assertion failed: (rec != NULL) Dec 20 21:28:24 ra dovecot: IMAP(bodil(a)mydomain.com): Raw backtrace: imap [0x47ef81] -> imap [0x47eca6] -> imap [0x42c3bc] -> imap [0x42f201] -> imap [0x42f324] -> imap [0x41d585] -> imap(imap_fetch+0x147) [0x41cb17] -> imap(cmd_fetch+0x1bc) [0x41686c] -> imap(cmd_uid+0x52) [0x419c42] -> imap [0x41a508] -> imap [0x41a5aa] -> imap(client_input+0x72) [0x41ab72] -> imap(io_loop_handler_run+0x106) [0x485746] -> imap(io_loop_run+0x1d) [0x484dbd] -> imap(main+0x401) [0x421f51] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x30af61d8a4] -> imap [0x414fa9] Dec 20 21:28:24 ra dovecot: child 4385 (imap) killed with signal 6 Dec 20 21:30:08 ra dovecot: IMAP(bodil(a)mydomain.com): file maildir-uidlist.c: line 840 (maildir_uidlist_set_ext_real): assertion failed: (rec != NULL) Dec 20 21:30:08 ra dovecot: IMAP(bodil(a)mydomain.com): Raw backtrace: imap [0x47ef81] -> imap [0x47eca6] -> imap [0x42c3bc] -> imap [0x42f201] -> imap [0x42f324] -> imap [0x41d585] -> imap(imap_fetch+0x147) [0x41cb17] -> imap(cmd_fetch+0x1bc) [0x41686c] -> imap(cmd_uid+0x52) [0x419c42] -> imap [0x41a508] -> imap [0x41a5aa] -> imap(client_input+0x72) [0x41ab72] -> imap(io_loop_handler_run+0x106) [0x485746] -> imap(io_loop_run+0x1d) [0x484dbd] -> imap(main+0x401) [0x421f51] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x30af61d8a4] -> imap [0x414fa9] Dec 20 21:30:08 ra dovecot: child 4397 (imap) killed with signal 6 I removed the index files for that mainbox and that error went away, but it caused another error: Dec 20 21:45:29 ra dovecot: IMAP(bodil(a)mydomain.com): file_dotlock_open() failed with file /mailindex/mydomain.com/bodil/.INBOX/dovecot.index.log: No such file or directory I had to recreate the .INBOX folder manually and all was great. The funny thing is it had already created all the other folders in the mailbox....

2 1

[Dovecot] Recent message flag unavailable ?
by Nicolas KOWALSKI 21 Dec '07

21 Dec '07

Hello, When a message is copied or newly-delivered to a folder, it does not have the "recent" flag set. Is there something in the configuration to activate it ? Thanks. # dovecot -n # 1.0.9: /usr/local/etc/dovecot.conf protocols: imap login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: mbox:~/mail:INBOX=~/mail/INBOX:INDEX=/var/cache/dovecot mbox_write_locks: fcntl auth default: passdb: driver: pam userdb: driver: passwd The MUA which shows it is Alpine 0.999999. -- Nicolas

2 2

[Dovecot] namespace problem / 1.1beta11
by ja nein 21 Dec '07

21 Dec '07

Hi all, actually I got a problem with the namespaces in dovecot 1.1 beta11. It occured after purging index files and resynch via imapsync. Dovecot complains about "Unknown namespace", though it worked with versions before. I cannot comfirm for 1.1beta10, but I surely know 1.1beta9 worked with these settings. Example: From Folder [INBOX/Trash] To Folder [___________] To Folder ___________ does not exist Creating folder [___________] Couldn't create [___________]266 NO Unknown namespace. Used imapsync command: /home/imapsync/imapsync --host1 ip.of.host.1 --user1 user1 --password1 password --host2 127.0.0.1 --user2 user2 --password2 password --authmech2 LOGIN --regextrans2 s/\./_/g --delete2 --sep1 . --sep2 . --justfolders Another run with different namespace settings shows up the folders in Thunderbird as INBOX^2002, INBOX^Trash ans so on... My goal is to keep all client settings when migrating a bigger installation of cyrus to dovecot. For know all folders in Cyrus appear as subfolders of INBOX, which I had achieved with dovecot < 1.1beta11. Any ideas? Btw., as we work in a load balanced environment, LMTP delivery would be a great feature for upcoming releases, as it would enable people to use multiple frontends of SMTP servers without the need of connecting them to a somewhat shared file system. Forwarding all mail to a SMTP server on the machine running dovecot and doing delivery there isn't the favoured option (at least for us). And a huge thx to Timo on working that hard on such a great working product! Regrads, Sebastian Dovecot conf putput: # 1.1.beta11: /etc/dovecot/dovecot.conf base_dir: /home/dovecot/ syslog_facility: local3 protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /home/dovecot/var/run/login login_executable(default): /opt/dovecot-1.1-beta11/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot-1.1-beta11/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot-1.1-beta11/libexec/dovecot/pop3-login verbose_proctitle: yes mail_location: maildir:/home/dovecot/mail/%d/%u:INDEX=/home/dovecot/index/%d/%u mail_executable(default): /opt/dovecot-1.1-beta11/libexec/dovecot/imap mail_executable(imap): /opt/dovecot-1.1-beta11/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot-1.1-beta11/libexec/dovecot/pop3 mail_plugins(default): fts fts_squat mail_plugins(imap): fts fts_squat mail_plugins(pop3): mail_plugin_dir(default): /opt/dovecot-1.1-beta11/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot-1.1-beta11/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot-1.1-beta11/lib/dovecot/pop3 namespace: type: private separator: / prefix: INBOX/ inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login digest-md5 cram-md5 verbose: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /home/dovecot/var/run/dovecot/auth-client master: path: /home/dovecot/var/run/dovecot/auth-master user: vuser plugin: fts: squat __________________________________ Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern. www.yahoo.de/clever

2 1