- dovecot - dovecot.org

[Dovecot] Roff typo in sievec.1.in
by Mike Abbott 27 Aug '10

27 Aug '10

There is a roff typo in pigeonhole's sievec.1.in. Roff treats the leading apostrophe on line 54 as an invalid command and produces bad output: dump to be written to stdout. The out-file argument may also be omitted, which has the same effect as for a com- piled Sieve binary file. Note that this option is not The output should be: dump to be written to stdout. The out-file argument may also be omitted, which has the same effect as '-'. The output is identical to what the sieve-dump(1) command pro- duces for a compiled Sieve binary file. Note that this Here is a patch: --- a/doc/man/sievec.1.in +++ b/doc/man/sievec.1.in @@ -50,8 +50,9 @@ Don\(aqt write the binary to \fIout\-file\fP, but write a textual dump of the binary instead. In this context, the \fIout\-file\fP value '\-' has special meaning: it causes the the textual dump to be written to \fBstdout\fP. -The \fIout\-file\fP argument may also be omitted, which has the same effect as -'\-'. The output is identical to what the \fBsieve\-dump\fP(1) command produces +The \fIout\-file\fP argument may also be omitted, which has the same effect +as '\-'. +The output is identical to what the \fBsieve\-dump\fP(1) command produces for a compiled Sieve binary file. Note that this option is not allowed when the \fIout\-file\fP argument is a directory. .TP

2 1

[Dovecot] pigeonhole needs to ship doc/man/{reporting-bugs.inc, sed.sh}
by Paul Howarth 27 Aug '10

27 Aug '10

A tarball created from current pigeonhole hg using "make dist" doesn't include the files doc/man/{reporting-bugs.inc,sed.sh} and fails to build as a result. Attached patch works for me. Paul

2 1

[Dovecot] dovecot - mac firewall problem
by Patrick Fay 27 Aug '10

27 Aug '10

Hi, I am running dovecot 1.2.11 on mac osx 1.5.8. Everything works perfectly with the application-level firewall off, but enabling the application firewall prevents dovecot connections. I have tried explicitly authorizing dovecot in the firewall, but it does not work. I have searched everywhere I can think of to look, and haven't found a solution, but have seen a couple other reports of what seems to be the same problem. The firewall logs the activity with what looks like a corrupt process name: a typical appfirewall.log entry looks like: Aug 26 20:43:45 hostname Firewall[55]: Deny ^L connecting from XX.XX.XX.XX:37310 uid = 0 proto=6 Aug 26 20:43:53 hostname Firewall[55]: Deny ^H�^U��^Z connecting from XX.XX.XX.XX:37310 uid = 0 proto=6 Aug 26 20:44:09 hostname Firewall[55]: Deny ^L connecting from XX.XX.XX.XX:37310 uid = 0 proto=6 Aug 26 20:44:34 hostname Firewall[55]: Deny ^L connecting from XX.XX.XX.XX:37312 uid = 0 proto=6 Aug 26 20:44:45: --- last message repeated 6 times --- where "hostname" is my server name and the XX's are my client's IP address. For all of the other services I've used, the process name (e.g. dovecot) should appear after "Deny" when blocking traffic, instead of the funny characters. Any advice on how I could resolve this issue would be greatly appreciated. Thanks!

2 1

[Dovecot] LDAP & static userdb
by spamvoll＠googlemail.com 27 Aug '10

27 Aug '10

hi.. im just testing 2.0 before upgrading to v1.2 :) in auth-ldap.conf.ext i found # If you don't have any user-specific settings, you can avoid the userdb LDAP # lookup by using userdb static instead of userdb ldap, for example: # <doc/wiki/UserDatabase.Static.txt> #userdb { #driver = static #args = uid=vmail gid=vmail home=/var/vmail/%u #} On 1.2 im using LDAP lookup and everthing works like a charm. user_attrs = homeDirectory=home,uid=mail=maildir:/home/MAILBOXES/%$/mail On 2.0 is now tried to use this option cause all my mail are stored in /home/MAILBOXES/%uid/mail userdb { driver = static args = uid=vmail gid=vmail home=/home/MAILBOXES/%u/mail } and that doesnt work log say: dovecot: imap(hpeter): Error: user hpeter: Initialization failed: mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/MAILBOXES/hpeter/mail Hans

1 1

Re: [Dovecot] (Single instance) attachment storage
by Damon Atkins 27 Aug '10

27 Aug '10

Some interesting reading on SHA256 checksum http://blogs.sun.com/bonwick/entry/zfs_dedup http://blogs.sun.com/darren/entry/improving_zfs_dedup_performance_via

1 0

[Dovecot] Single instance storage - testing please
by Timo Sirainen 27 Aug '10

27 Aug '10

http://hg.dovecot.org/dovecot-2.0-sis contains the code for it. Otherwise it's the latest (as of writing this) dovecot-2.0 hg tree. Please test if you're interested in SIS. :) Once there's at least some testing, I'll probably add this to v2.0.x since very little of this new code is used when SIS is disabled (which is the default of course). SIS works pretty much like explained in http://dovecot.org/list/dovecot/2010-July/050832.html and http://dovecot.org/list/dovecot/2010-July/050992.html Two things I'm not yet entirely sure about: 1. What hash algorithm to use? Currently it's hard coded to SHA1. Besides more CPU usage, the other potential problem with larger hashes is that they also generate larger filenames. The filenames are currently hex-encoded, but to save space they could be changed to some kind of modified-base64 (base64 uses '/' chars, so it can't be regular base64). Example filename lengths: hex modified-base64 SHA1 73 50 SHA256 97 66 SHA512 161 109 Yet another possibility would be to use SHA256/SHA512 and just truncate the hash length to less number of bits. 2. Should I add support for trusting hash uniqueness and to avoid disk I/O generated by the byte-by-byte comparison? It could still first check that the file sizes match. Usage ----- You can enable SIS for sdbox and mdbox: mail_attachment_dir = /var/attachments Just setting the above enables "instant SIS", where byte-by-byte comparison is done immediately during saving mails. Alternative is to leave the comparing later by setting: mail_attachment_fs = sis-queue /var/attachments/queue:posix This does no deduplication itself yet. To do that you'll need a nighty (or whatever) run, which calls: doveadm sis deduplicate /var/attachments /var/attachments/queue There's also a feature to easily find all attachments based on a hash. For example: % sha1sum foo 351641b73feb7cf7e87e5a8c3ca9a37d7b21e525 foo % doveadm sis find /var/attachments 351641b73feb7cf7e87e5a8c3ca9a37d7b21e525 /var/attachments/35/16/351641b73feb7cf7e87e5a8c3ca9a37d7b21e525-e13a841f28ba764c123b00008c4a11c1 /var/attachments/35/16/351641b73feb7cf7e87e5a8c3ca9a37d7b21e525-1d3b940628ba764c0b3b00008c4a11c1 If you want to save attachments to a separate files without SIS (e.g. you want to use your filesystems deduplication), set: mail_attachment_fs = posix By default only attachments larger than 128 kB are written to attachment storage. You can change it from: mail_attachment_min_size = 128k It's also possible to create a plugin that adds further restrictions to when the attachment is saved separately. This might be useful to reduce disk seeks for attachments that are typically shown inline by clients/webmail. You can do this by overriding mailbox.save_is_attachment() method. If you want to distribute attachments to multiple filesystems, just create /var/attachments/[0-9a-f][0-9a-f] as symlinks pointing to whatever mount paths you want.

3 8

[Dovecot] Panic, rawtrace, log, etc
by Brandon Lamb 27 Aug '10

27 Aug '10

While running some doveadm expunge -A mailbox Spam savedbefore 30d and doveadm purge -A after 2010-08-26 16:20:51 auth: Error: net_accept() failed: Too many open files 2010-08-26 16:20:51 master: Warning: service(auth): process_limit reached, client connections are being dropped 2010-08-26 16:21:21 auth: Panic: file auth-request-handler.c: line 85 (auth_request_handler_unref): assertion failed: (hash_table_count(handler->requests) == 0) 2010-08-26 16:21:21 auth: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x39c1a) [0x7fe41f5f5c1a] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x39c6a) [0x7fe41f5f5c6a] -> /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0x7fe41f5d3026] -> dovecot/auth [8 wait, 0 passdb, 0 userdb]() [0x412153] -> dovecot/auth [8 wait, 0 passdb, 0 userdb]() [0x40c3ad] -> dovecot/auth [8 wait, 0 passdb, 0 userdb](auth_client_connections_deinit+0x41) [0x40c461] -> dovecot/auth [8 wait, 0 passdb, 0 userdb](main+0x2ea) [0x4168ca] -> /lib/libc.so.6(__libc_start_main+0xfd) [0x7fe41e60ac4d] -> dovecot/auth [8 wait, 0 passdb, 0 userdb]() [0x40b1f9] 2010-08-26 16:21:21 master: Error: service(auth): child 14880 killed with signal 6 (core dumps disabled) 2010-08-26 16:21:21 auth: Error: Master requested auth for nonexistent client 14875 2010-08-26 16:21:21 auth: Error: Master requested auth for nonexistent client 14873 2010-08-26 16:21:21 auth: Error: Master requested auth for nonexistent client 14873 2010-08-26 16:21:21 auth: Error: Master requested auth for client 14874 with invalid cookie 2010-08-26 16:21:21 auth: Error: Master requested auth for client 14874 with invalid cookie 2010-08-26 16:21:21 auth: Error: Master requested auth for client 14875 with invalid cookie 2010-08-26 16:21:21 auth: Error: Master requested auth for client 14876 with invalid cookie 2010-08-26 16:21:21 auth: Error: Master requested auth for client 14875 with invalid cookie

2 3

[Dovecot] Configuration Update From v1.x To v2.0.1-2
by Carlos Mennens 26 Aug '10

26 Aug '10

I just upgraded my Dovecot IMAP package on my mail server and when I restarted the service, I got the following warnings... doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:12: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:14: passdb pam {} has been replaced by passdb { driver=pam } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:16: userdb passwd {} has been replaced by userdb { driver=passwd } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:18: auth_user has been replaced by service auth { user } The list was much longer but I was able to self resolve them. I was wondering if someone here can assist me in converting my 'dovecot.conf' file? Below is how my dovecot.conf file appears: protocols = imap disable_plaintext_auth = yes log_timestamp = "%b %d %H:%M:%S " mail_location = maildir:~/mail auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep } auth default { mechanisms = plain login passdb pam { } userdb passwd { } user = root socket listen { client { path = /var/run/dovecot/auth-client user = postfix group = postfix mode = 0660 } } } ***doveconf -n*** [root@mail /]# doveconf -n # 2.0.1: /etc/dovecot/dovecot.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:12: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:14: passdb pam {} has been replaced by passdb { driver=pam } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:16: userdb passwd {} has been replaced by userdb { driver=passwd } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:18: auth_user has been replaced by service auth { user } # OS: Linux 2.6.35 x86_64 auth_mechanisms = plain login mail_location = maildir:~/mail passdb { driver = pam } protocols = imap service auth { unix_listener auth-client { group = postfix mode = 0660 user = postfix } user = root } userdb { driver = passwd } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep }

4 7

[Dovecot] How to pipe to external program
by Egbert 26 Aug '10

26 Aug '10

Hi, Second try... I have mailsystem with virtual users only (/home/vmail/domain/user). I need to integrate RT3.x (a ticketing system). I have installed the RT-client but I need to send the mail to an extrnal program. Rt wants me to insert: |/usr/bin/rt-mailgate --queue bla --action bla --url http://bla.bal/ In /etc/postfix/aliases. That does not work for me becase my local delivery agent is dovecot. The Sieve plugin seems not capable to forward to a external program. What is the right way to achieve that mail to rt@mydomain is sent to the pipe? TIA Egbert Jan

2 1

Re: [Dovecot] Investigating suspected cache corruption
by Maria Elinger 26 Aug '10

26 Aug '10

Hi David and all, I´ve read the mail you posted in the Dovecot list. We´re are having this same problem in a site which is very similar to yours. We also migrated from Courier to Dovecot nearly 9 months ago, and every now and then users complain about slowness in the imap connection. We fix it by removing the index files in the user's maildir. We use Horde as webmail, but the problem appears with any imap or pop connection, so we feel that the problem is in Dovecot. Did you find any solution or workaround at your site?, it would be very useful if you gave us a hint on this. Thanks in advance, María Elinger [Dovecot] Investigating suspected cache corruption David Warden Wed, 14 Oct 2009 13:18:17 Hi All, I'm running Dovecot 1.1.11 for a site of about 7000 active users with a Squirrelmail frontend. We migrated from Courier (big shout to everyone who worked on the wonderful part of the Dovecot wiki that deals with Courier migration) and I have been extremely happy with the performance gains Dovecot has given us. Not only is the IMAP part of Squirrelmail faster, but our same hardware is under far less stress than it was before the migration. To date, the only problem we have experienced is a seemingly random but significant slowdown in Squirrelmail's loading of the messages in a user's Inbox. Each time, I have been able to fix the problem by deleting the user's dovecot.index, dovecot.index.cache and dovecot.index.log files in the user's INDEX directory for their dovecot Inbox. I tried having users experiencing this problem log in to a test Squirrelmail box with mail_debug on, but I didn't see anything out of the ordinary and they report the same slowness on the test server. I don't see anything but normal login/logout IMAP lines in the production dovecot logs. I have hesitated a bit in posting to the list since this seems to be happening to a small percentage of users and it technically may be a problem with Squirrelmail, but the fact that I'm able to fix the problem by nuking Dovecot's index files has me concerned - does anyone have any suggestions for troubleshooting? My first idea when I get another one of these is to do a telnet IMAP session to Dovecot on one of the Squirrelmail boxes and see if I can get it to slow down when retrieving messages from the Inbox. We are using Maildir over NFS with the control/index files stored on NFS as well. We're doing FS quota over NFS using rquotad to query the NFS server for each user's quota. Here's the output of dovecot -n: # 1.1.11: /etc/dovecot.conf Warning: fd limit 1024 is lower than what Dovecot can use under full load (more than 1536). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: Linux 2.6.18-128.1.1.0.1.el5 x86_64 Red Hat Enterprise Linux Server release 5.3 (Tikanga) login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_process_per_connection: no login_processes_count: 10 login_max_processes_count: 512 verbose_proctitle: yes first_valid_uid: 0 mail_location: maildir:~/Maildir:CONTROL=/Mail/mailhome/ %u/.dovecot:INDEX=/Mail/mailhome/%u/.dovecot mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): imap_logout_format(default): bytes(in/out)=%i/%o imap_logout_format(imap): bytes(in/out)=%i/%o imap_logout_format(pop3): bytes=%i/%o pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): UID%u-%v pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_logout_format(default): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_logout_format(imap): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_logout_format(pop3): top(count/bytes)=%t/%p, retr(count/bytes)=%r/ %b, del(deleted/pre-deleted)=%d/%m, mailbox-size(bytes)=%s namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd plugin: quota: fs:Mail Quota:user Many thanks, David Warden

2 2

[Dovecot] 1.2.13 QRESYNC crash.
by David Woodhouse 26 Aug '10

26 Aug '10

Aug 18 22:07:31 twosheds IMAP(dwmw2): : Panic: file mail-index-transaction.c: line 637 (mail_index_transaction_lookup): assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq) * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS] Logged in as dwmw2 0 enable condstore qresync * ENABLED CONDSTORE QRESYNC 0 OK Enabled. A00131 SELECT lists.bluez (QRESYNC (1154090296 1861 1:* (1,120,1578,2064,2226,2280,2298 1,120,12037,12523,12685,12739,12757))) Program received signal SIGABRT, Aborted. 0x00000034ace326c5 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.23-9.fc12.x86_64 glibc-2.11.2-1.x86_64 keyutils-libs-1.2-6.fc12.x86_64 krb5-libs-1.7.1-9.fc12.x86_64 libcom_err-1.41.9-8.fc12.x86_64 libgcc-4.4.4-10.fc12.x86_64 libselinux-2.0.90-5.fc12.x86_64 nss-softokn-freebl-3.12.6-2.fc12.1.x86_64 openldap-2.4.19-4.fc12.x86_64 openssl-1.0.0a-1.fc12.x86_64 zlib-1.2.3-23.fc12.x86_64 (gdb) bt #0 0x00000034ace326c5 in raise () from /lib64/libc.so.6 #1 0x00000034ace33ea5 in abort () from /lib64/libc.so.6 #2 0x00000000004a2698 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:160 #3 0x00000000004a273b in i_syslog_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=<value optimized out>, args=<value optimized out>) at failures.c:315 #4 0x00000000004a1d86 in i_panic (format=0x6 <Address 0x6 out of bounds>) at failures.c:207 #5 0x00000000004787f0 in mail_index_transaction_lookup ( t=<value optimized out>, seq=<value optimized out>) at mail-index-transaction.c:637 #6 0x000000000047be45 in tview_lookup_uid (view=<value optimized out>, seq=<value optimized out>, uid_r=<value optimized out>) at mail-index-transaction-view.c:162 #7 0x00000000004580fb in index_mail_set_seq (_mail=0x7282b8, seq=1578) at index-mail.c:1229 #8 0x0000000000423eb4 in expunges_drop_known (ctx=0x70a628) at imap-fetch.c:178 #9 get_expunges_fallback (ctx=0x70a628) at imap-fetch.c:269 #10 imap_fetch_send_vanished (ctx=0x70a628) at imap-fetch.c:291 #11 imap_fetch_begin (ctx=0x70a628) at imap-fetch.c:314 #12 0x000000000041e8e2 in select_qresync (cmd=<value optimized out>, ---Type <return> to continue, or q <return> to quit--- readonly=<value optimized out>) at cmd-select.c:243 #13 select_open (cmd=<value optimized out>, readonly=<value optimized out>) at cmd-select.c:320 #14 cmd_select_full (cmd=<value optimized out>, readonly=<value optimized out>) at cmd-select.c:382 #15 0x0000000000420ead in client_command_input (cmd=0x70a458) at client.c:612 #16 0x0000000000420f8d in client_command_input (cmd=0x70a458) at client.c:661 #17 0x00000000004211b5 in client_handle_next_command (client=0x709ff0) at client.c:702 #18 client_handle_input (client=0x709ff0) at client.c:714 #19 0x0000000000421a5c in client_input (client=0x709ff0) at client.c:753 #20 0x00000000004aa7cd in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:208 #21 0x00000000004a9c38 in io_loop_run (ioloop=0x707cc0) at ioloop.c:335 #22 0x0000000000429726 in main (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>) at main.c:327 It's a public mailing list folder, so I've uploaded it to http://david.woodhou.se/bluez-maildir.tar.gz Filed as Red Hat bug #625907: https://bugzilla.redhat.com/show_bug.cgi?id=625207 -- dwmw2

3 10

[Dovecot] New problem with migration to 2.0
by Carsten Laun-De Lellis 26 Aug '10

26 Aug '10

Hi guys After fixing my master_auth problem i have one error message left and i don't know what to do. The message from dovecot -n is: service auth { unix_listener /var/spool/postfix/private/auth { group = vmail mode = 0666 user = vmail } unix_listener auth-master { mode = 0666 } } My conf file looks like userdb { driver=static args = uid=10000 gid=10000 home=/mail/%d/%n allow_all_users=yes } As you can see pretty simple, but for me it looks like that the driver=static won't be accepted. Does anyone know which driver to use here ? Mit freundlichem Gruß Carsten Laun-De Lellis Dipl.-Ing. Elektrotechnik Certified Information Systems Auditor (CISA) Hauptstrasse 13 D-67705 Trippstadt Phone: +49 (6306) 992140 Mobile: +49 (151) 27530865 email: carsten.laun-delellis(a)delellis.net

2 4

[Dovecot] migration to dovecot 2.0
by Carsten Laun-De Lellis 26 Aug '10

26 Aug '10

Hi everyone I am not the dovecot guru and i would appreciate if anyone could help me on my problems. I am running a mail server on dovecot 1.2 and want to migrate to dovecot 2. I have edited the conf file and now using the new keywords and got everything fixed but the following error message still exists, when i try to start dovecot. doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/dovecot.conf line 1036: Unknown setting: auth_socket doveconf: Error: managesieve-login: dump-capability process returned 89 doveconf: Fatal: Error in configuration file ./dovecot.conf line 1036: Unknown setting: auth_socket My conf file looks like auth_socket listen { master { # Master socket provides access to userdb information. It's typically # used to give Dovecot's local delivery agent access to userdb so it # can find mailbox locations. path = /var/run/dovecot/auth-master mode = 0600 # Default user/group is the one who started dovecot-auth (root) user = vmail #group = } 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 # path = /var/run/dovecot/auth-client mode = 0660 user = postfix group = postfix } } I would appreciate any hints and help. Mit freundlichem Gruß Carsten Laun-De Lellis Dipl.-Ing. Elektrotechnik Certified Information Systems Auditor (CISA) Hauptstrasse 13 D-67705 Trippstadt Phone: +49 (6306) 992140 Mobile: +49 (151) 27530865 email: carsten.laun-delellis(a)delellis.net

2 2

[Dovecot] Does Dovecot support the use of the INDEX directive for mdbox?
by William Blunn 26 Aug '10

26 Aug '10

Does Dovecot support the use of the INDEX directive for mdbox? e.g. mail_location = mdbox:~/mdbox:INDEX=/var/indexes/%u Bill

2 1

[Dovecot] Table mail.users doesn't exist (using built-in default iterate_query: SELECT username, domain FROM users)
by Jerrale G 26 Aug '10

26 Aug '10

connect = host=127.0.0.1 user=mail password=thecorrectpass dbname=mail map { pattern = shared/expire/$user/$mailbox table = mail.expires value_field = expire_stamp fields { username = $user mailbox = $mailbox } } dovecot: auth: Error: mysql: Query failed, retrying: Table 'mail.users' doesn't exist Aug 26 05:16:24 server1 dovecot: auth: Error: sql: Iterate query failed: Table 'mail.users' doesn't exist (using built-in default iterate_query: SELECT username, domain FROM users) Why isn't the expire dict trying to use the defined working mysql auth instead of using the built-in default? The howto doesn't say how to override this, at wiki2.dovecot.org, and I didn't know the expire dict wanted to lookup the mailbox table; I thought it only wanted to lookup the expire table and use that soley for deleting messages as all info needed was stored, in the expire table, by the expire plugin on message delivery or copy. Jerrale G rrale G. SC Senior Admin

1 0

[Dovecot] best way something thinks to upgrade dovecot to 1.2.* 2.0.*
by fakessh 26 Aug '10

26 Aug '10

hello all hello dovecot network hello timo What are your tips for successful migration for dovecot (atrpms , atrpms-testing depot for centos ) the page of wiki http://wiki2.dovecot.org/Upgrading/2.0 explains the method to upgrade I tried on my personal machine and the command cites wiki returns errors on the terminal what to do with errors: correct the error in the configuration file ? the question may seem simple but it is not pointless many returns are welcome something thinks are welcome thanks

2 10

[Dovecot] dovecot 1 to 2 migration FreeBSD
by Frank Bonnet 26 Aug '10

26 Aug '10

Hello is there some specials recommentations to migrate from dovecot 1.1.x to 2.0.1 with FreeBSD boxes ? Thanks

5 11

[Dovecot] Home directories
by Timo Sirainen 26 Aug '10

26 Aug '10

I've noticed that a lot of people are using e.g.: mail_location = maildir:/var/vmail/%d/%n Then either they don't have home directory set, or their home directory is the same as the maildir. http://wiki.dovecot.org/VirtualUsers/Home explains all the problems of not separate home and mail directories. Also whenever I try to suggest using a separate home and mail directory, the answer is way too often: "But I'm using virtual users. (They don't have home directories.)" So I started wondering. Maybe simply renaming the "home" to something else would help here at least some. Make all of the documentation use only the new word, and add alias for userdb so that the new name and the "home" both work (I guess docs would need to keep using the "home" as field name for some more years). So far I've only come up with "vhome" as the replacement name. Other ideas?

12 19

[Dovecot] DSYNC needs a lot more documentation
by Marc Perkel 26 Aug '10

26 Aug '10

Started looking into the dsync utility and the doc are seriously incomplete. I can of course scour the internet looking for the missing information but that doesn't fix the problem with the docs. I might try to rewrite the docs myself once I figure it out.

9 15

[Dovecot] Pure virtual user and RT3.x
by Egbert 25 Aug '10

25 Aug '10

Hi, I have mailsystem with virtual users only (/home/vmail/domain/user). I need to integrate RT3.x (a ticketing system). I have installed the client but I need to send mail to a pipe. Rt wants me to insert: |/usr/bin/rt-mailgate --queue bla --action bla --url http://bla.bal/ In /etc/postfix/aliases. That does not work for me. What is the right way to achieve that mail to rt@mydomain is sent to the pipe? Should I install, configure and use a Sieve filter? I have none installed at the moment. Or are there other (simpler?) ways? TIA Egbert Jan

2 2

Re: [Dovecot] Live Mirror dovecot / OS X 10.6.4 (Timo Sirainen)
by Eric Boltz (MMI / UPC) 25 Aug '10

25 Aug '10

Timo Sirainen <tss(a)iki.fi> wrote: > Two potential problems I see with this: > 1. If users can do any changes on the secondary server (flag changes, > saving new mails, etc), you're going to have problems syncing the > changes back (without losing any changes or causing other problems). > > 2. If users can access the secondary server via IMAP clients, the > clients could become confused if the secondary server isn't completely > up-to-date. > > With v2.0 dsync would help with the first problem. Change in strategy. Primary rsyncs regularly to the secondary which keeps all mail services off. When primary fails email services are started manually until primary back online. Then I (or another ITer) manually stop the backup, rsycn and restart services on the primary. A bit labor intensive, but it should work.

4 5

[Dovecot] Problems compiling Dovecot 2.0.0 on Solaris 10 x86
by Drew Schatt 25 Aug '10

25 Aug '10

I'm having issues getting Dovecot 2.0.0 to compile - I get the following error: cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-settings -I../../src/lib-master -DPKG_RUNDIR=\""/usr/local/var/run/dovecot"\" -DPKG_LIBEXECDIR=\""/usr/local/libexec/dovecot"\" -DEXAMPLE_CONFIG_DIR=\""/usr/local/share/doc/dovecot/example-config"\" -DMODULEDIR=\""/usr/local/lib/dovecot"\" -DSSLDIR=\""/etc/ssl\"" -I/usr/local/include -I/usr/local/ssl/include -D_XPG6 -L/usr/local/lib -L/usr/local/ssl/lib -KPIC -lm -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -xc99 -I/usr/local/include -I/usr/local/ssl/include -L/usr/local/lib -L/usr/local/ssl/lib -D_XPG6 -xstrconst -KPIC -lm -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -c doveconf.c "config-request.h", line 6: warning: useless declaration "doveconf.c", line 554: undefined symbol: optarg "doveconf.c", line 554: warning: improper pointer/integer combination: arg #2 "doveconf.c", line 560: warning: improper pointer/integer combination: op "=" "doveconf.c", line 581: undefined symbol: optind "doveconf.c", line 583: undefined symbol: optind "doveconf.c", line 584: undefined symbol: optind cc: acomp failed for doveconf.c gmake[3]: *** [doveconf.o] Error 2 gmake[3]: Leaving directory `/home/schatt/code/evaluation_src/dovecot-2.0.0/src/config' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/home/schatt/code/evaluation_src/dovecot-2.0.0/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/home/schatt/code/evaluation_src/dovecot-2.0.0' gmake: *** [all] Error 2 Anyone have any idea on how to resolve this one? -Drew

2 1

[Dovecot] Signal 11 - can't get core dump?
by Marty Anstey 25 Aug '10

25 Aug '10

Hi all, We have been running Dovecot for over a year now in our moderate volume mail environment (>4000 mailboxes) and it's been running great. However, over the past month or so we've begun to experience issues where IMAP clients will appear to "hang" for a period of time, we then see a sig 11, and afterwards mailflow returns to normal. This usually happens a few times a day. Naturally, our first instinct was to try and get a core dump, but after following the instructions at http://www.dovecot.org/bugreport.html we now recieve this warning: 2010-08-24T13:33:56-07:00 mail dovecot: child 9728 (login) killed with signal 11 (core not dumped - add -D to login_executable) (ip=208.98.210.13) Adding -D to the login_executable lines didn't seem to have any effect, we are still receiving the same message. Did we perhaps misinterpret the hint? As we've been trying for over a week now to find a way to get a dump without any success, we figured posing this to the list might help us shed some light on the issue. Any suggestions would be appreciated! dovecot -n -- # 1.1.20: /etc/dovecot.conf # OS: Linux 2.6.18-164.15.1.el5xen i686 CentOS release 5.5 (Final) nfs base_dir: /var/run/dovecot/ listen: 208.98.210.10 ssl_ca_file: /etc/ssl/gd_bundle.crt ssl_cert_file: /etc/ssl/sunwave.net.crt ssl_key_file: /etc/ssl/sunwave.net.key ssl_parameters_regenerate: 1 ssl_cipher_list: ALL:!LOW verbose_ssl: yes login_dir: /var/run/dovecot//login login_executable(default): /usr/libexec/dovecot/imap-login -D login_executable(imap): /usr/libexec/dovecot/imap-login -D login_executable(pop3): /usr/libexec/dovecot/pop3-login -D mail_max_userip_connections(default): 50 mail_max_userip_connections(imap): 50 mail_max_userip_connections(pop3): 10 first_valid_uid: 200 last_valid_uid: 200 first_valid_gid: 200 last_valid_gid: 200 mail_location: maildir:/var/spool/mail/%Ld/%1Lu/%Ln/Maildir mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_executable(default): /usr/local/bin/mailtools/mail_imap.sh mail_executable(imap): /usr/local/bin/mailtools/mail_imap.sh mail_executable(pop3): /usr/local/bin/mailtools/mail_pop3.sh mail_plugins(default): quota imap_quota trash mail_plugins(imap): quota imap_quota trash mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes lda: postmaster_address: do_not_reply(a)sunwave.net mail_plugins: quota cmusieve auth default: mechanisms: plain login default_realm: sunwave.net verbose: yes passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot-mysql.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: 511 user: vmail plugin: sieve: /var/spool/mail/%Ld/%1Lu/%Ln/Maildir/.sieve quota: maildir:Quota quota_rule2: Trash:storage=10%% quota_warning: storage=70%% /usr/local/bin/mailtools/quota-warning.sh 70 quota_warning2: storage=80%% /usr/local/bin/mailtools/quota-warning.sh 80 quota_warning3: storage=90%% /usr/local/bin/mailtools/quota-warning.sh 90 trash: /etc/dovecot-trash.conf Thanks, Marty

3 3

[Dovecot] Help needed with plugin - Read Only access to IMAP mailbox
by Chris Moules 25 Aug '10

25 Aug '10

System info: # 1.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686-bigmem i686 Debian squeeze/sid .. mail_plugins: readonly .. I have a requirement to have read-only to a mailbox. I have been researching through the wiki, the mailing list archives and good old Google. There was a number of similar questions with no real definitive answer. Option 1: ACL This can work, but not if the mailbox(s) can change without you knowing how. I.E. a online read-only archive of someone else's mailbox. There is no wild-card or recursive ACL options. Rsync style backups don't allow for easy creation of custom ACL files per mailbox. Option 2: Read-only filesystem (Linux) This seems easy, but it's not. 1) how do you update your archive? I tried with a bind mount, this does not let you set the 'ro' option *directly*. You must then use "-o remount,ro" to get your read-only bind mount. This is a little messy (needs custom init scripts for mounting on boot), but do-able. 2) Dovecot needs write access to CONTROL and INDEX files. This lead me to using the "CONTROL" and "INDEX" options on the mail_locaiton. Setting these to the original 'rw' mount and the rest to my 'ro' bind mount. Again, messy but do-able. 3) Clients try to move messages from 'new' to 'cur' for Maildir. Every time I opened a maildir I got an error per mail (dovecot log) about read-only filesysem as the client was trying to set the Seen flag and dovecot was trying to move the 'new' mail to the 'cur' folder. My test client, mutt, has a 'read_only' option when connecting. This eliminates this issue, but I cannot get everyone to use this archive with a correctly configured mutt. This sent me looking for 'read only' options in other clients. I could hardly find any. I noted that mutt send an EXAMINE and not a SELECT to open the mailbox when in read_only mode and this set me thinking about doing this in another way. Option 3: Dovecot Plugin I started looking into the dovecot plugins. Being more a systems administrator than developer I have cobbled together a working plugin. It nearly does what I want, but not quite, and I don't know why. NOTE: I no longer use the setup that I had to test Options 1 and 2. I thought that this plugin can either be used server-wide or with the 'mail_plugins' userdb option. The plugin forces the MAILBOX_OPEN_READONLY flag in a mailbox_open() call. The plugin returns an error for all mailbox_create() calls. Testing in mutt: - I am unable to delete a mail - I am unable to create a new folder So far so good. However: - I am able to move/copy a mail to an *existing* mailbox (note, the move operation makes the copy but fails to set the 'delete' flag) I do not understand why this works. I have been grep-ing through the source of dovecot and the plugins to find some answer, but without luck. Attached is the full source to my plugin and the Makefile (adapted from Johannes Berg's antispam plugin Makefile) When finished, I will be happy to release this to the dovecot community under the GPL/LGPL or whatever. Regards Chris

3 10

[Dovecot] v2.0.1 released
by Timo Sirainen 24 Aug '10

24 Aug '10

http://dovecot.org/releases/2.0/dovecot-2.0.1.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.1.tar.gz.sig Some small fixes mainly, but since people aren't reporting much bugs for v2.0.0 anymore maybe v2.0.1 release will change that. :) Some of the more important changes since v2.0.0 are: * When dsync is started as root, remote dsync command is now also executed as root instead of with dropped privileges. - IMAP: QRESYNC parameters for SELECT weren't handled correctly. - UTF-8 string validity checking wasn't done correctly (e.g. mailbox names in Sieve fileinto) - dsync: Fixed a random assert-crash with remote dsyncing

1 0