- dovecot - dovecot.org

[Dovecot] imaptest update
by Timo Sirainen 07 Nov '07

07 Nov '07

http://dovecot.org/tools/imaptest.c now keeps track of messages' metadata and complains if they change. It relies on Message-ID: header being unique in the source mailbox, otherwise it'll give bogus errors. I might fix that some day. I changed the code from using simple line-based parsing to Dovecot's imap-parser code. Unfortunately it looks like it's pretty slow. At least I'm pretty sure imaptest didn't take more than a few % of CPU before, while now it's showing 35% CPU usage.. I guess I'll have to profile it a bit to see what's eating the CPU. And yes, looks like it found a couple of bugs from Dovecot 1.1's MIME parsing (BODY/BODYSTRUCTURE replies change). That was actually why I wrote this code in the first place, I was trying to figure out how to reproduce a bug. I'm getting closer to my stress testing dream tool. :) http://mailman1.u.washington.edu/pipermail/imap-protocol/2007-March/000413.…

1 0

[Dovecot] Unit testing
by Timo Sirainen 07 Nov '07

07 Nov '07

I finally added beginnings of unit tests to Dovecot v1.1 code tree: http://hg.dovecot.org/dovecot/rev/4e4a5d6bb2cb There are currently just a couple of tests implemented in test-lib (lib/ functions) and test-mail (lib-mail/ functions). I'm probably going to be pretty lazy at adding more of those tests, so if you've ever wanted to get your own code to Dovecot, now would be a great time to do it! :)

1 0

[Dovecot] index corruption
by rosenfield＠users.sourceforge.net 07 Nov '07

07 Nov '07

Hi people Just switched to Dovecot yesterday, and I've already got about five reports of users with duplicate mail in their inbox :-/. Not as bad as lost email, mind you, but pretty annoying still. Checking the server log, it says: postfix/smtpd: disconnect from unknown deliver: msync() failed with index file maildir/dovecot.index: Input/output error unionfs: new lower inode mtime (bindex=0, name=maildir) dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error IMAP: Disconnected: Internal error occurred. Refer to server log for more information. This is dovecot version 1.0.3, the log presented here relates to only one user; user name snipped for anonymity purposes. Afterwards things just get worse and worse with the affected user: dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error deliver: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: Corrupted transaction log file maildir/.SPAM/dovecot.index.log: invalid new transaction log sequence (1 >= 1) dovecot: IMAP: fscking index file maildir/.SPAM/dovecot.index dovecot: IMAP: Transaction log file maildir/.SPAM/dovecot.index.log: marked corrupted dovecot: IMAP: Corrupted transaction log file maildir/.SPAM/dovecot.index.log: invalid new transaction log sequence (2 >= 2) dovecot: IMAP: fscking index file maildir/.SPAM/dovecot.index dovecot: IMAP: Corrupted transaction log file maildir/.Junk/dovecot.index.log: invalid new transaction log sequence (1 >= 1) dovecot: IMAP: fscking index file maildir/.Junk/dovecot.index dovecot: IMAP: Transaction log file maildir/.Junk/dovecot.index.log: marked corrupted dovecot: IMAP: Corrupted transaction log file maildir/.Junk/dovecot.index.log: invalid new transaction log sequence (2 >= 2) dovecot: IMAP: fscking index file maildir/.Junk/dovecot.index deliver: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error deliver: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error dovecot: IMAP: msync() failed with index file maildir/dovecot.index: Input/output error What could be the problem? How do I go about debugging an issue such as this?

2 2

[Dovecot] IMAP - Empty attachments error
by Tomáš Klandra 06 Nov '07

06 Nov '07

Hallo, I have one problem with the following configuration: - server: debian, dovecot used as an IMAP server, version 0.99.14. - stations: windows 2k/XP, mailer seamonky 1.1.4 Sometimes (let's say once in 20 attemptes) when saving attachments, they are empty (zero size files). Simple re-saving them helps. I was looking on mozilla forums if it's not a bug in SeaMonkey, which looked more likely to me, but didn't find anything, so I got the idea it could be a bug in dovecot. If someone saw this as well or have any ideas, I would really appreciate any help about it, as the error is really annoying. Thank you, Tom

2 1

[Dovecot] assertion failed with hg current
by Jakob Hirsch 06 Nov '07

06 Nov '07

Hi, I get a lot of these after updating to the current 1.1 hg version: > Nov 6 16:05:35 seba deliver(jh): file mail-cache-transaction.c: line 736 (mail_cache_header_add_field): assertion failed: (cache->field_file_map[field_idx] != (uint32_t)-1) > Nov 6 16:05:35 seba deliver(jh): Raw backtrace: /usr/local/libexec/dovecot/deliver(i_syslog_fatal_handler+0x2b) [0x80bbeab] -> /usr/local/libexec/dovecot/deliver [0x80bbd4c] -> /usr/local/libexec/dovecot/deliver(mail_cache_add+0x2d2) [0x8091da2] -> /usr/local/libexec/dovecot/deliver(index_mail_cache_add_idx+0x69) [0x8085629] -> /usr/local/libexec/dovecot/deliver [0x806f776] -> /usr/local/libexec/dovecot/deliver(mail_storage_copy+0x53) [0x80ab3b3] -> /usr/local/libexec/dovecot/deliver(maildir_copy+0x52) [0x8067802] -> /usr/local/libexec/dovecot/deliver(deliver_save+0xcf) [0x80592df] -> /usr/local/libexec/dovecot/deliver(main+0x1317) [0x805a7e7] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x948f70] -> /usr/local/libexec/dovecot/deliver [0x8058541] Besides that, it seems to run fine.

2 1

[Dovecot] User keywords limit to 26
by Arthur Pétry 06 Nov '07

06 Nov '07

Hi, I'm planning to use dovecot 1.0.5 for a webmail using a lot of user- defined tags. Recently, I just saw the limit of 26 of them when messages are stored in maildir format. This is an important issue for me, since I didn't find how to remove a flag from the dovecot-keywords database. Is there any plan to get rid of the keywords limit ? Or perhaps the new dbox storage format can fix that ? By the way, the comportement of Dovecot when we try to add a new flag while the limit is exceeded is strange : (C: is client and S: Dovecot) The store of the flags is ok : C: RUBY0094 UID STORE 89 +FLAGS (test_0 test_1 test_2 test_3 test_4 test_5 test_6 test_7 test_8 test_9 test_10 test_11 test_12 test_13 test_14 test_15 test_16 test_17 test_18 test_19 test_20 test_21 test_22 test_23 test_24 test_25 test_26) S: * 81 FETCH (UID 89 FLAGS (\Seen test_1 test_2 test_3 test_4 test_5 test_6 test_7 test_8 test_9 test_10 test_11 test_12 test_13 test_14 test_15 test_16 test_17 test_18 test_19 test_20 test_21 test_22 test_23 test_24 test_25 test_26 test_0)) S: RUBY0094 OK Store completed. And then when we fetch them, dovecot reply 2 times. The first time with all the flags, and the second time with only the 26 flags stored in maildir. (I suppose Dovecot try to sync the flags when we fetch it) : C: RUBY0095 UID FETCH 89 FLAGS S: * 81 FETCH (FLAGS (\Seen test_1 test_2 test_3 test_4 test_5 test_6 test_7 test_8 test_9 test_10 test_11 test_12 test_13 test_14 test_15 test_16 test_17 test_18 test_19 test_20 test_21 test_22 test_23 test_24 test_25 test_26 test_0) UID 89) S: * 81 FETCH (FLAGS (\Seen test_1 test_2 test_3 test_4 test_5 test_6 test_7 test_8 test_9 test_10 test_11 test_12 test_13 test_14 test_15 test_16 test_17 test_18 test_19 test_20 test_21 test_22 test_23 test_24 test_25 test_0)) S: RUBY0095 OK Fetch completed.

2 1

[Dovecot] Sent vs Sent Items
by Ed W 06 Nov '07

06 Nov '07

Religious wars about which is "best" aside - some mail clients seem to default to using "Sent Items" folder for saving sent mail, and others (many) default to "Sent". Seems that in the interests of compatibility and "doing the right thing" (tm) that a symlink from one folder to the other name would ensure that either default would give the same result (in a mixed client setup)? However, I wonder if someone has already written a plugin to do something simple like this? More generally I guess it's folder aliasing, so that Sent == Sent Items and perhaps there are also synonyms for Drafts/Templates? Anyone got any thoughts on this simple idea? (The prob with sym links is a) creating them at mailbox setup time and b) what happens when someone tries to delete the folder...) Cheers Ed W

6 6

[Dovecot] MySQL-SSL
by xyon 06 Nov '07

06 Nov '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, I've been running dovecot authenticating against a local MySQL database, but it has come time to implement it with a remote database. Instead of using stunnel, I'd rather take advantage of MySQL's native SSL support. I didn't know if this was possible with dovecot, and if it was, what config changes I might need to get it going. I found the below page/patch from some time ago and tried to use the ssl_key and ssl_cert directives in /etc/dovecot-sql.conf, but it didn't seem to recognize them (perhaps I need to compile mysql-ssl support into dovecot manually?): http://www.dovecot.org/list/dovecot-cvs/2004-July/003003.html Also, I noticed a need for ssl_ca and ssl_ca_path but am unfamiliar with how to generate what's needed if these options are required. FYI, dovecot 1.0.7 is running on CentOS 4.5, using rpm from ATrpms: http://dl.atrpms.net/el4-i386/atrpms/stable/dovecot-1.0.7-0_63.el4.i386.rpm Thanks for any advice or documentation pointers you can provide. Have a great evening everyone! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHL85sJ6p9X8nw/2oRAr9JAJ9u5XTOXqqUvVFE5HqEAr4HzC2juwCgob5o 7usezyZdBjP44wEYQKUg/fQ= =tv5y -----END PGP SIGNATURE-----

1 0

[Dovecot] deliver to subfolder?
by Ralf Hildebrandt 06 Nov '07

06 Nov '07

Can dovecot's deliver deliver a mail to a certain subfolder within a user's mailbox? I was thinking of something along the lines of: deliver -m subfolder But what is the correct syntax to deliver to "spam", subfolder of INBOX? deliver -m spam < message.txt deliver -m INBOX.spam < message.txt -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de

2 1

[Dovecot] truncated messages / attachments
by Markus Stumpf 05 Nov '07

05 Nov '07

I am currently running dovecot-1.1.beta6 (at least beta5 also had the problem) Retrieving some messages via IMAP gets them truncated and it also happens with retrieving attachments (message is HTML part of multipart-alternative, attachments are at least some PDF files). A user reported she is rather sure one of the messages was ok, before moving it to some other folder. In the filesystem the messages are there in full length. It happens with Outlook as well as with Thunderbird. We're using Maildir. After upgrading from beta5 to beta6 I have removed all dovecot.index* files of a folder with a defect message. This didn't make a difference. (Thought it could be related to some indexing problem). Any one else seeing this? \Maex -- Markus Stumpf

2 2

[Dovecot] Couldn't init INBOX: Can't sync mailbox: Messages keep getting expunged
by Tom Sommer 05 Nov '07

05 Nov '07

After updating Dovecot, one of my servers keep spamming these errors in the log: dovecot: Nov 03 14:14:18 Error: POP3(foo(a)bar.com): Getting size of message UID=4402 failed dovecot: Nov 03 14:14:18 Error: POP3(foo(a)bar.com): Getting size of message UID=4402 failed dovecot: Nov 03 14:14:18 Error: POP3(foo(a)bar.com): Couldn't init INBOX: Can't sync mailbox: Messages keep getting expunged The funny thing is the mailbox is empty, there are no mails in the folder that should be needed to be parsed It was perfectly fine before I updated, and the permissions on the folder is correct. It only affects some mailboxes as well. Any ideas? // Tom

3 5

Re: [Dovecot] Dovecot write activity (mostly 1.1.x)
by mikkel＠euro123.dk 05 Nov '07

05 Nov '07

On Sun, November 4, 2007 4:32 pm, Timo Sirainen wrote: >> >> I didn't know that mail_nfs_index=yes resulted in a forced chown. >> How come that's necessary with NFS but not on local disks? >> > > It's used to flush NFS attribute cache. Enabling it allows you to use > multiple servers to access the same maildir at the same time while still > having attribute cache enabled (v1.0 required actime=0). If you don't need > this (and it's better if you don't), then just set the mail_nfs_* to "no" > and it works faster. > >> By the way I misinformed you about fsync_disable=yes. >> It was like that before i upgraded to v1.1, but v1.1 requires >> fsync_disable=no when mail_nfs_index=true so I had to disable it. > > So you use ZFS on the NFS server, but Dovecot is using NFS on client > side? The fsyncs then just mean that the data is sent to NFS server, not a > real fsync on ZFS. > Thanks a lot for the help - this changed a lot! Dist writes fell to about 1/3 of before. I guess the reason is that ZFS can now make use if it's caching capabilities. Delivers activity is completely random since it's impossible to load balance a connection based on the e-mail recipient, since only the ip is known at the load balancing point. Therefore I have fsync_disable=no for deliver. It's easy to force the clients using imap/pop3 to the same server since it can be based on the ip only. Therefore I have fsync_disable=yes for imap/pop3. This changed everything. Now there's a real performance gain upgrading from 1.0.x to 1.1.x. About two or three times less disk activity overall (reads were already improved) for both reads and writes. Thats pretty neat!

1 0

[Dovecot] Version 1.1beta 6 and OS X Leopard (10.5)
by Jerry Yeager 05 Nov '07

05 Nov '07

Just a quick note: The new 1.1-b6 is working fine on OS X 10.5.

1 0

Re: [Dovecot] Testing with some Unstable
by Jeff Grossman 05 Nov '07

05 Nov '07

Andrew Sackville-West wrote: > [SNIPPED] > > actually, assuming you now have unstable in your sources.list, those > are packages currently installed for which there are updates available > (probably unstable updates...). Be careful or you'll end up farther > than you want. > > I can't answer to the specifics of sendmail and libmilter, but so long > as you have unstable in your sources.list, those kept-back packages > will appear (unless you upgrade them, of course). Probably, on the > assumption that sendmail and libmilter is sufficient for your needs, > you should change you sources.list back once those two upgrades are > done. > > A > I have "APT::Default-Release "testing";" in my apt.conf file. Is it still advised to remove the unstable lines from my sources.list file even though I have the above in my apt.conf file? Thanks for you help. Jeff

1 1

[Dovecot] Dovecot write activity (mostly 1.1.x)
by mikkel＠euro123.dk 04 Nov '07

04 Nov '07

Im experiencing write activity thats somewhat different from my previous qmail/courier-imap/Maildir setup. This more outspoken in v.1.1.x than v1.0.x (Im using Maildir). Write activity is about half that of read activity when measuring throughput. But when measuring operations its about 5-7 times as high (measured with zpool iostat on ZFS). I think this might be due to the many small updates to index and cache files. Anyway since writing is much more demanding to the disk than reads dovecots ends up being slower (only a little though) than my old qmail/courier-imap/Maildir was. And the old setup didnt even benefit from indexes like Dovecot does. (What I mean saying slower is that it can service fewer users before it hits the wall). Of course theres also lots of benefits using Dovecot. Im just wondering whether this was a thing that should be focused on for later versions (maybe writes could be grouped together or something like that). Dovecot is very cheap on the CPU side so the only real limit in terms of scalability is the storage. Regards, Mikkel

2 6

[Dovecot] Sieve error messages (sieve 1.1.2, dovecot 1.1b6)
by mikkel＠euro123.dk 04 Nov '07

04 Nov '07

Sorry for spamming the list today:) Im getting a lot of these errors in the deliver log: deliver([recipient]): [date] Info: sieve runtime error: Fileinto: Generic Error deliver([recipient]): [date]:18 Error: sieve_execute_bytecode([path-to-sieve]) failed deliver([recipient]): [date] Info: msgid=<[msgid] >: save failed to [foldername]: Quota exceeded In this case the account is over the defined Dovecot quota limit. Dovecot knows what to do but sieve seems to throw its standard error message. Is there something wrong with Sieve or is it just that the error is misleading? This has been present in all v1.1.x I think (some changes was made to the error messages in b3 or b4 but believe this didnt change). Regards, Mikkel

1 0

[Dovecot] *notify config for 1.0.x doesn't enable inotify
by Paolo 04 Nov '07

04 Nov '07

hi, the current code has changed include linux/inotify.h to sys/inotify.h since 2006-01-17, but that won't work with inotify*.h as documented in the wiki. One has to either revert back to linux/inotify.h, or add #include <sys/inotify-syscalls.h> to both configure.in and src/lib/ioloop-notify-inotify.c Or, just symlink sys/inotify.h -> linux/inotify.h. That's on Debian 3.1 (Sarge). -- paolo GPG/PGP id:0x1D5A11A4 - 04FC 8EB9 51A1 5158 1425 BC12 EA57 3382 1D5A 11A4

3 6

[Dovecot] IMAP vs system username logging with checkpassword auth
by dale gallagher 03 Nov '07

03 Nov '07

Hi After upgrading to dovecot 1.0.7 I noticed that the actual username is no longer logged, but rather the system user (in my case 'vmail') under which my virtual set-up runs. Now I'm unable to see which virtual users log in. Any pointers on how to configure dovecot to log the actual username given during the IMAP dialogue would be appreciated. My dovecot.conf includes the following: auth default { mechanisms = plain passdb checkpassword { args = /var/qmail/bin/qmail-vauth } userdb prefetch { } user = auth } An example logfile entry: 2007-11-03 15:41:56.027191500 dovecot: Info: imap-login: Login: user=<vmail>, method=PLAIN, rip=192.168.0.141, lip=192.168.0.10, TLS

2 1

[Dovecot] MANAGESIEVE patch v8 for dovecot 1.0.7
by Stephan Bosch 03 Nov '07

03 Nov '07

Hello dovecot users, I have updated the MANAGESIEVE patch to the latest stable version of dovecot (1.0.7). This new version also adds extra configuration settings to explicitly specify the location of the sieve storage and the active sieve script. Additionally, the README now more clearly explains the configuration of the daemon. It currently won't compile with 1.1 due to significant changes in the master code. However, because 1.1 now approaches a stable release, the next version is going to be updated to version 1.1. Change Log V8 ------------- + Fixed a few incompatibilities with 1.0.7 version. For instance, the "Logged in" message is now sent by the -login process and not by the managesieve daemon anymore. This caused a segfault every once in a while. + Probably fixed the settings problem reported by Steffen Kaiser regarding login_dir. 'dovecot -n' now reports correct results, but testing will show whether the whole problem is solved. + The managesieve daemon now accepts the sieve_storage and sieve configuration settings, so it is now possible to explicitly configure the location of the sieve storage and the active script respectively. The daemon still falls back to using the mail_location (MAIL) settings if nothing else is specified. + The cyrus timsieved does not use the + character in string literals and many clients have adopted to this behaviour. The latest managesieve (08) advises to accept a missing + from clients. The server should not send any + characters as well. This behavior is now implemented on the server. + Cleaned up sieve-storage.c: split up the sieve_storage_create function in various sub-functions for obtaining the various paths and directories. + Forced manual intervention if rescueing a non-symlink file at the active script path fails somehow. Previously, this presented the admin with a log message that it had just eaten the script, which is not very nice. + Restructured the README.managesieve file and added some more explanation with regard to the configuration of the daemon. This patch still includes (yet another) instance of the CMU Sieve source, as explained in one of my previous e-mails (http://dovecot.org/list/dovecot/2006-July/015016.html) The patch can be downloaded at: http://sinas.rename-it.nl/~sirius/dovecot-1.0.7-MANAGESIEVE-v8.diff.gz The README.managesieve is located in the root of the dovecot source tree after applying the patch. Have fun testing the patch. Don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

4 6

[Dovecot] v1.1.beta6 released
by Timo Sirainen 02 Nov '07

02 Nov '07

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta6.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta6.tar.gz.sig Fixes since beta5: - dovecot.index.cache file wasn't actually being created/updated (or something like that) - SORT assert-crashed sometimes when sorting by string fields - etc.

1 0

[Dovecot] Listening only on localhost
by tobias-mail＠gmx.net 02 Nov '07

02 Nov '07

Hi! I've got dovecot 1.0.rc15. I want dovecot to listen only on localhost for imap, and on any interfaces for imaps. So I put the following into my config: protocol imap { listen = 127.0.0.1:143 ssl_listen = *:10993 .. } dovecot -n correctly reports: listen: 127.0.0.1:143 ssl_listen: *:10993 But I can still do a 'telnet MY_HOST 143' from the outside, and 'netstat -pltn | grep dovecot' reports: [ip changed ;)] tcp 0 0 77.my.ip.253:10993 0.0.0.0:* LISTEN 4847/dovecot tcp 0 0 77.my.ip.253:143 0.0.0.0:* LISTEN 4847/dovecot Am I doing something wrong? Or is there a bug? -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail

3 2

[Dovecot] Postfix and Dovecot Deliver LDA
by spammy 02 Nov '07

02 Nov '07

Hi all, Having problems moving from postfix/dovecot/mysq/maildrop existing intall to dovecot LDA dovecot -n # 1.0.5: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_location: maildir:/vmail/%d/%u mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth-client mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail master.cf (maildrop line commented. -f ${recipient} in maildrop was working ok) dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -d ${recipient} main.cf dovecot_destination_recipient_limit = 1 # I haven't found any docs about the following must work, but apparently working. virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql_virtual_domains_maps.cf virtual_transport = dovecot dovecot.log dovecot: 2007-11-02 12:32:40 Info: auth(default): master out: USER 1 vaina(a)neenux.com uid=5000 gid=5000 deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Info: auth input: vaina(a)neenux.com deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Info: auth input: uid=5000 deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Info: auth input: gid=5000 deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Fatal: setuid(5000) failed: Operation not permitted I'm using vmail:vmail (5000:5000) for all my virtual users and postfix chrooted. I have read the wiki but I'm not using diferrent uids and gids for every user so, I don't understand why deliver is trying to setuid. sorry for my newbie question but my english is not the best and I'm totally lost. any ideas? roger

2 2

[Dovecot] caching custom headers (via plugins)
by Paolo 02 Nov '07

02 Nov '07

hi, currently dovecot caches on disk some most common headers. Is it possible to tweak such headers list via plugins, eg to cache custom X-* headers, or do I need to hack the actual index/cache src? if so, which are the .c/.h files to touch? thanks -- paolo GPG/PGP id:0x1D5A11A4 - 04FC 8EB9 51A1 5158 1425 BC12 EA57 3382 1D5A 11A4

3 4

[Dovecot] Errors in Dovecot 1.0.5
by Jeff Tucker 02 Nov '07

02 Nov '07

Hello, I am running Dovecot 1.0.5 and seem to have lots of errors in my Dovecot logs. The worst errors are things like: Oct 30 16:11:42 delta2 dovecot: IMAP(x): Corrupted transaction log file /home/spamcop-net2/deputies/dovecot.index.log: end_offset (392) > current sync_offset (388) Oct 30 16:11:42 delta2 dovecot: IMAP(x): file mail-index-sync-update.c: line 841 (mail_index_sync_update_index): assertion failed: (view->hdr.messages_count == map->hdr.messages_count) Oct 30 16:11:42 delta2 dovecot: IMAP(x): Raw backtrace: imap [0x462a7e] -> imap [0x46234c] -> imap(mail_index_sync_update_index+0x7b2) [0x44a982] -> imap(mail_index_sync_commit+0xe7) [0x447f87] -> imap(maildir_sync_index_finish+0xd2) [0x420b32] -> imap [0x4225af] -> imap(maildir_storage_sync_init+0x63) [0x4227b3] -> imap(imap_sync_nonselected+0xf) [0x41be9f] -> imap(_cmd_select_full+0xc5) [0x413f95] -> imap(cmd_select+0xb) [0x41411b] -> imap [0x415a87] -> imap [0x415b2c] -> imap(_client_input+0x75) [0x415cd5] -> imap(io_loop_handler_run+0xee) [0x4684ce] -> imap(io_loop_run+0x2d) [0x46797d] -> imap(main+0x3e3) [0x41d7b3] -> /lib/libc.so.6(__libc_start_main+0xdb) [0x2aaaaace049b] -> imap [0x410cca] When this happens, my users just get timeouts trying to do stuff. I have my messages (maildirs) and indices all stored on NFS. For locking, I have mmap_disable = yes and lock_method = dotlock Do you have any idea what is going on here? In general, I get tons of errors about corrupted transaction log files for all users. Is this normal? Thanks Jeff

4 5

[Dovecot] Migration from courier pop3 to dovecot pop3
by Shailesh Singh 02 Nov '07

02 Nov '07

Hello, In mail client users have settings leave message on server. I dont want user download those messages again. i tried with courier-dovecot-migrate.plscript after running this if i am doing send recive all messages downloaded again please help me in this. Thanks Shailesh Singh

2 1

[Dovecot] v1.1.beta5 released
by Timo Sirainen 02 Nov '07

02 Nov '07

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta5.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta5.tar.gz.sig APPEND should be working now. Also lots of fixes to handling namespace prefixes and namespaces where virtual separator differs from real separator. zlib plugin now supports opening compressed maildir files. This is done for files that have Z flag. SORT still assert-crashes sometimes. Would be great if someone could show me how to reproduce it. SEARCH TEXT or Squat indexes apparently still have some problems, but I couldn't reproduce them (http://dovecot.org/list/dovecot/2007-October/026254.html)

2 3

[Dovecot] imaptest.c
by sergey ivanov 02 Nov '07

02 Nov '07

Timo, can you, please, update imaptest.c to be compatible with recent 1.1 beta5 dovecot sources? -- WBR, Sergey Ivanov.

2 1

[Dovecot] v1.0.6 released
by Timo Sirainen 02 Nov '07

02 Nov '07

http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz.sig * IDLE: Interval between mailbox change notifies is now 1 second, because some clients keep a long-running IDLE connection and use other connections to actually read the mails. * SORT: If Date: header is missing or broken, fallback to using INTERNALDATE (as the SORT draft nowadays specifies). + deliver: If message begins with a "From " line, ignore it. + zlib plugin: If maildir file has a "Z" flag, open it with zlib. - CREATE: Don't assert-crash if trying to create namespace prefix. - SEARCH: Fixes to handling NOT operator with sequence ranges. - LDAP reconnection fixes - Maildir: Don't break when renaming mailboxes with '*' or '%' characters and children. - mbox: Fixed "file size unexpectedly shrinked" error in some conditions. - quota+mbox: Don't fail if trying to delete a directory. - Fixes to running from inetd

5 12

[Dovecot] "Can't sync delivery mail"
by Rich Winkel 02 Nov '07

02 Nov '07

Dovecot 1.0.3 Deliver is saying this on two specific emails. Other emails to these 2 users are going through fine. Looking at the mail headers the only thing questionable I see is: From: "AMS Publication Division"@ams.org Is this the problem? # 1.0.3: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_disable: yes shutdown_clients: 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_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no first_valid_uid: 100 mail_extra_groups: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u:INDEX=/var/spool/dovecot_indexes/%u lock_method: flock mbox_read_locks: flock mbox_write_locks: flock 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_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 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: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 432 user: dovecot group: dovecot

2 4

[Dovecot] Bug within Authentication Caching
by Matthias Waffenschmidt 02 Nov '07

02 Nov '07

Hello, there seems to be a bug in the authentication caching code when using it in combination with username_translation (using the current version 1.0.7 on FreeBSD 6). I've set username_translation to +@:@ to allow usernames of the form test+dom.ain or test:dom.ain (historical reasons force us....). If someone has a successful login using the username test(a)dom.ain, the subsequent authentication information is read from the cache, no matter which of the 3 possible usernames the client uses the next time. But if someone has a successful login using the username test+dom.ain, the following data has or has not been found in the cache: test+dom.ain: miss test(a)dom.ain: miss test:dom.ain: hit If the first username is test:dom.ain the behaviour is the following: test:dom.ain: miss test(a)dom.ain: miss test+dom.ain: hit I've added the information if the username changes for better debugging possibilities. In practice the username is of course always the same. The complete authentication part of the tested config: auth default: cache_size: 10000 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@:+ username_translation: +@:@ verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /var/pop/%d/Accounts.passwd userdb: driver: static args: uid=70 gid=70 home=/var/emtpy It looks as if Dovecot does some wrong username translations before inserting/lookup up the data in the cache. BTW: a SIGUSR2 signal to the dovecot-auth process does not give any information as suggested in http://wiki.dovecot.org/Authentication/Caching. Please do not only answer to the list as I am not subscribed. Thanks. -- Gruss / Best regards | LF.net GmbH | fon +49 711 90074-411 Matthias Waffenschmidt | Ruppmannstr. 27 | fax +49 711 90074-33 mw(a)LF.net | D-70565 Stuttgart | http://www.lf.net

2 1

[Dovecot] Dovecot] Postfix and Dovecot Deliver LDA
by Jerry Yeager 02 Nov '07

02 Nov '07

On Nov 2, 2007, at 9:48 AM, dovecot-request(a)dovecot.org wrote: > ------------------------------ > > Message: 4 > Date: Fri, 02 Nov 2007 13:00:56 +0100 > From: spammy <spam(a)rogerp.org> > Subject: [Dovecot] Postfix and Dovecot Deliver LDA > To: dovecot(a)dovecot.org > Message-ID: <472B1178.2060200(a)rogerp.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi all, > > Having problems moving from postfix/dovecot/mysq/maildrop existing > intall to dovecot LDA > > dovecot -n > > stuff chomped out > deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Info: auth input: > gid=5000 > deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Fatal: setuid(5000) > failed: Operation not permitted > > I'm using vmail:vmail (5000:5000) for all my virtual users and postfix (snipped some more out) > > roger Hello Roger, Try this: cd to the path where the dovecot deliver app is. Then, sudo chmod u+s deliver You may or may not need to do sudo chmod g+s deliver -- probably not. This is in the Sendmail - LDA part of the docs. Recent changes to Dovecot seem to have brought this to Postfix - LDA as well. Jerry

1 0

[Dovecot] dovecot + LDAP + SASL?
by hadmut＠danisch.de 02 Nov '07

02 Nov '07

Hi, I would like to setup an IMAP server with SASL and LDAP support. As far as I can see dovecot supports SASL and LDAP, but not the way I need it. If I understand dovecot correctly, it has it's own set of SASL mechnisms and uses the LDAP server just to store the plaintext password. In case of authentication dovecot fetches the plaintext password from LDAP and then performs the SASL steps internally. I need to support proprietary SASL mechanisms built into an LDAP server, which are not based on just a single password. So is there a way to configure dovecot to just pass SASL through to LDAP, allowing the IMAP client to talk SASL with the LDAP server through dovecot? regards Hadmut

2 1

[Dovecot] Successful experience with auth_winbind module
by Dmitry Butskoy 02 Nov '07

02 Nov '07

Hi, Recently the support of Samba's ntlm_auth helper was added to dovecot-auth (mech-winbind.c etc.). It is alrready in 1.1, the patch for 1.0 is here: http://dovecot.org/patches/1.0/dovecot-1.0.3-winbind.patch . It allows auth against NT or AD domain. I would like to infrom all that we successfully use this new feature during 2 month and ~300 users 24x7 (an energy power company). No any failures at all! This feature allows to specify "SPA" (Secure Password Authentication) option in OE, and to avoid explicit user passwords in mail accounts. Some random notes: - In the mixed environment (both plain and ntlm methods in use), you have to specify: mechanisms = plain ntlm login i.e. "ntlm" before "login". When sending mails, OE just catch first seen and try to use it, even if you specify to use SPA in the mail account preferences. - It seems that MS Outlook requires the specifying of password even when SPA is in effect - When OE has several identities, and one of the identities has SPA for SMTP set (outgoing mail), it wins over all another identities. - "The Bat" mailer supports NTLM for reading, not sending, and requires password too. Regards, Dmitry Bustkoy http://www.fedoraproject.org/wiki/DmitryButskoy P.S. We use NTLM only, GSS-SPNEGO still not tested.

1 0

Re: [Dovecot] Dovecot push imap/imap notify support?
by Alan Ferrency 02 Nov '07

02 Nov '07

Mart Pirita <sysadmin(a)e-positive.ee> wrote: > Tried search, no luck, does the Dovecot include push imap/imap notify support? If you're looking for something iPhone-compatible, then "no." Theirs is a proprietary system which from what I've read, seems to use SMS in combination with IMAP. Wacky. (If you aren't talking about iPhone compatibility, I'm less knowledgeable, but dovecot does support IDLE-style "imap push" style notification.) Alan Ferrency

5 4

[Dovecot] mail-sql.tar.gz: missing mailbox-list-private.h
by Paolo 02 Nov '07

02 Nov '07

hi, I'm trying to compile with plugin in subject, but I get this error: In file included from mail-sql-plugin.c:4: sql-storage.h:5:34: mailbox-list-private.h: No such file or directory In file included from mail-sql-plugin.c:4: sql-storage.h:26: error: field `module_ctx' has incomplete type make[5]: *** [mail-sql-plugin.lo] Error 1 there's no such mailbox-list-private.h in the whole src tree, though seems it should be in the sql-plugin tarball. Is it in 1.1? thanks -- paolo GPG/PGP id:0x1D5A11A4 - 04FC 8EB9 51A1 5158 1425 BC12 EA57 3382 1D5A 11A4

2 2

[Dovecot] mail_location and master_user rel 1.0.x
by Robert Heller 02 Nov '07

02 Nov '07

login me(a)mymail.net*theboss thebossespwd this is a great piece of software, but it has some frustrating issues. i have included my two configurations below, just FYI. the one (older) system is 1.0rc7 on mandriva 2007.0 and postfix 2.3.3 and amavisd and spamassassin and using a maildir configuration the newer system is 1.0.5 (soon to be 7) on mandriva 2008.0 and postfix 2.4.5 amavisd and spamassassin and using a maildir configuration first, i followed the instructions in this document http://wiki.dovecot.org/Authentication/MasterUsers to the letter and it works for neither the old server nor the new. specifically i was using the first example configuration. all i ever got was: Connected to mail.mailserver.com Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS STARTTLS AUTH=LOGIN AUTH=PLAIN AUTH=DIGEST-MD5] Dovecot ready. login him(a)mailserver.com*theboss thebossespwd login BAD Error in IMAP command received by server. and the auth_debug information was completely useless. if someone goes to the trouble of writing great examples they really should test to make sure they actually work. secondly: this configuration on the old server (1.0rc7) works fine: ## Dovecot 1.0 configuration file base_dir = /var/lib/dovecot protocols = imap pop3 imaps log_path = /var/log/dovecot/error.log info_log_path = /var/log/dovecot/info.log first_valid_uid = 60000 last_valid_uid = 60000 first_valid_gid=15 last_valid_gid=15 default_mail_env = maildir:/var/spool/mail/%d/%u mailbox_check_interval = 60 maildir_copy_with_hardlinks = yes mbox_locks = fcntl umask = 0077 auth default { mechanisms = plain digest-md5 user = dovecot passdb pgsql { /etc/dovecot/dovecot-pgsql.conf } userdb pgsql { /etc/dovecot/dovecot-pgsql.conf } socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = postfix group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = mail } } } but the same configuration on the newer version 1.0.5 does not work, the problem being in mail location (note changed from default_mail_location to mail_location). so i had to make a number of changes... ## Dovecot configuration file base_dir = /var/lib/dovecot/ protocols = imap pop3 imaps disable_plaintext_auth = no log_path = /var/log/dovecot/error.log info_log_path = /var/log/dovecot/info.log ssl_cert_file = /etc/pki/tls/certs/dovecot.pem ssl_key_file = /etc/pki/tls/private/dovecot.pem login_dir = /var/lib/dovecot/login mail_location = maildir:/var/spool/mail/%d/%n: namespace private { prefix = location = maildir:/var/spool/mail/%d/%n inbox = yes } mail_extra_groups = mail first_valid_uid = 60000 last_valid_uid = 60000 first_valid_gid=15 last_valid_gid=15 maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = yes mbox_read_locks = fcntl mbox_write_locks = fcntl protocol imap { login_greeting_capability = yes } protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { postmaster_address = postmaster(a)example.com } auth default { mechanisms = login plain digest-md5 passdb sql { args = /etc/postfix/mysql/dovecot.conf } userdb sql { args = /etc/postfix/mysql/dovecot.conf } socket listen { master { path = /var/lib/dovecot/auth-master mode = 0660 user = nobody group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = mail } } } dict { } plugin { } or from the dovecot -n command: # 1.0.5: /etc/dovecot.conf base_dir: /var/lib/dovecot/ log_path: /var/log/dovecot/error.log info_log_path: /var/log/dovecot/info.log protocols: imap pop3 imaps ssl_cert_file: /etc/pki/tls/certs/dovecot.pem ssl_key_file: /etc/pki/tls/private/dovecot.pem disable_plaintext_auth: no login_dir: /var/lib/dovecot/login login_executable(default): /usr/lib64/dovecot/imap-login login_executable(imap): /usr/lib64/dovecot/imap-login login_executable(pop3): /usr/lib64/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no first_valid_uid: 60000 last_valid_uid: 60000 first_valid_gid: 15 last_valid_gid: 15 mail_extra_groups: mail mail_location: maildir:/var/spool/mail/%d/%n: maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mbox_write_locks: fcntl mail_executable(default): /usr/lib64/dovecot/imap mail_executable(imap): /usr/lib64/dovecot/imap mail_executable(pop3): /usr/lib64/dovecot/pop3 mail_plugin_dir(default): /usr/share/dovecot//imap mail_plugin_dir(imap): /usr/share/dovecot//imap mail_plugin_dir(pop3): /usr/share/dovecot//pop3 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 namespace: type: private location: maildir:/var/spool/mail/%d/%n inbox: yes auth default: mechanisms: login plain digest-md5 passdb: driver: sql args: /etc/postfix/mysql/dovecot.conf userdb: driver: sql args: /etc/postfix/mysql/dovecot.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/lib/dovecot/auth-master mode: 432 user: nobody group: mail what i found was that i HAD to add a namespace in order to be able to define my maildir location. that was ok, /*except */that the mail_location value is no longer being used for the pop3 server mail location. so i could pick up mail using IMAP no problem, but POP wasn't working. after a number of hours i modified my SQL script with 'CONCAT(path, maildir)' so that the 'mail' path is returned complete from the sql statement: in my initial SQL statement, works on the old server and the new version 1.0.5 IMAP as: user_query = SELECT maildir AS mail, 60000 AS uid, 15 AS gid FROM mailbox WHERE username = '%u' AND active='1' but in order to get the POP3 version working i had to change it thus: user_query = SELECT CONCAT('/var/spool/mail/', maildir) AS mail, 65534 AS uid, 12 AS gid FROM mailbox WHERE username = '%u' AND active='1' one would have expected changing the SQL statement to this new format would have resulted in a location for the IMAP server now being constructed as: /var/spool/mail/var/spool/mail/domain/user but that did not happen. they both (POP & IMAP) now can find the mail and folders. like i said, thanks very much for writing this s/ware. it is great...but needs some tweaking. thanks for listening

2 1

[Dovecot] sync with gmail?
by Neal Becker 02 Nov '07

02 Nov '07

Now that gmail added imap, I've been trying to see if I can sync gmail/imap with my local dovecot maildir. I've been trying offlineimap. So far, I've created a loop resulting in a directory with size > 1000000 entries. Anyone try this and have a working setup?

3 4

[Dovecot] receive date wrong in outlook
by Farkas Levente 01 Nov '07

01 Nov '07

hi, we migrate from exchange to dovecot. we do it with imapsync. first we try to do it with --syncinternaldates, but this fails on many messages with invalid date, so we drop this option. unfortunately after this those users who use outlook see the received date as the date we do the migration in stead of the real received date. other clients eg webmail, thunderbird etc sees the right date. so my question what can i do? it's a dovecot bug or outlook and if outlook's bug is there any workaround fro this? thanks in advance. -- Levente "Si vis pacem para bellum!"

2 4

[Dovecot] Authentication
by Isaac Scott 31 Oct '07

31 Oct '07

Hi I am looking to use dovecot with postfix/amavis/spamassasin and would like to be able to deliver spam/virus emails into specific virtual user folders. I wanted to know if it is possible to authenticate user for IMAP and POP3 access seperately using a database? All I have seen in the documentation/wiki is a single query for authentication. Regards, Isaac

2 1

[Dovecot] Dovecot, Mail.app @ Leopard
by DinnoM 31 Oct '07

31 Oct '07

Hi There, I'm using dovecot-imapd 1.0.rc15-2etch1 under Debain Etch AMD64 platform, recently, once of our user reported that there have "Unknown Namespace" problem with the new mail.app under leopard. So, is there a workaround at dovecot or I need to upgrade to a latest version of dovecot? Regards, Dino.

2 1

[Dovecot] dovecot-1.0.3 & apacheds ldap
by sergey ivanov 31 Oct '07

31 Oct '07

I have problem with dovecot-1.0.3 and apacheds ldap server. If I change just uris in dovecot-ldap.conf to point to fedora-ds server, everything works O.K. I've tried with apacheds ldap server versions 1.0.2 and 1.5.0 command line search with parameters taken from dovecot.debug log gives me all needed attributes. Comments and help welcome. Here is my data: --- # /opt/dovecot/sbin/dovecot -n # 1.0.3: /opt/dovecot/etc/dovecot.conf log_path: /tmp/dovecot.log info_log_path: /tmp/dovecot.debug protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/ssl/parkheights.cert ssl_key_file: /etc/ssl/parkheights.key login_dir: /opt/dovecot/var/run/dovecot/login login_executable(default): /opt/dovecot/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: maildir:/var/spool/imap/%n/.imap mail_debug: yes mail_executable(default): /opt/dovecot/libexec/dovecot/imap mail_executable(imap): /opt/dovecot/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args: /opt/dovecot/etc/dovecot-ldap.conf userdb: driver: ldap args: /opt/dovecot/etc/dovecot-ldap.conf userdb: driver: prefetch socket: type: listen master: path: /opt/dovecot/var/run/dovecot/auth-master mode: 384 user: vmail group: vmail --- # grep -v '#' /opt/dovecot/etc/dovecot-ldap.conf |grep -v '^\s*$' hosts = 192.168.10.43:389 dn = uid=admin,ou=system dnpass = Ahma3zoc sasl_bind = no auth_bind = no ldap_version = 3 base = ou=people,dc=parkheights,dc=dyndns,dc=org user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(uid=%Ln)) pass_attrs = uid=user,gidNumber=userdb_gid,userPassword=password,homeDirectory=userdb_home,uidNumber=userdb_uid default_pass_scheme = MD5 --- # tail -5 /tmp/dovecot.debug dovecot: Aug 03 08:07:10 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AHNlc(here_also_skipped_something)3N1Pg== dovecot: Aug 03 08:07:10 Info: auth(default): ldap(seriv,127.0.0.1): pass search: base=ou=people,dc=parkheights,dc=dyndns,dc=org scope=subtree filter=(&(objectClass=posixAccount)(uid=seriv)) fields=uid,gidNumber,userPassword,homeDirectory,uidNumber dovecot: Aug 03 08:07:10 Info: auth(default): ldap(seriv,127.0.0.1): result: uid(user)=seriv gidnumber(?unknown?)= userpassword(?unknown?)= homedirectory(?unknown?)= uidnumber(?unknown?)= dovecot: Aug 03 08:07:12 Info: auth(default): client out: FAIL 1 user=seriv temp dovecot: Aug 03 08:10:10 Info: imap-login: Disconnected: Inactivity: user=<seriv>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured --- # tail -3 /tmp/dovecot.log dovecot: Aug 03 08:06:53 Warning: auth(default): Killed with signal 15 dovecot: Aug 03 08:06:53 Warning: Killed with signal 15 dovecot: Aug 03 08:07:10 Error: auth(default): ldap(seriv,127.0.0.1): No password in reply --- here is the snippet from apacheds debug log: --- message Id : 2 Search Request Base Object : 'ou=people,dc=parkheights,dc=dyndns,dc=org' Scope : whole subtree Deref Aliases : never Deref Aliases Size Limit : no limit Time Limit : no limit Types Only : false Filter : '(&(objectClass=posixAccount)(uid=seriv))' Attributes : gidNumber, uid, userPassword, homeDirectory, uidNumber baseDn : 'ou=people,dc=parkheights,dc=dyndns,dc=org' filter : '(& (objectClass=posixAccount) (uid=seriv) ) ' scope : whole subtree typesOnly : false no limit Time Limit : no limit Deref Aliases : never Deref Aliases attributes : 'gidNumber', 'uid', 'userPassword', 'homeDirectory', 'uidNumber' message Id : 2 Search Result Entry Object Name : 'uid=seriv,ou=people,dc=parkheights,dc=dyndns,dc=org' Attributes Attributes Attribute id : 'uid', Values : ['seriv'] Attribute id : 'gidnumber', Values : ['1927'] Attribute id : 'userpassword', Values : [0x7B 0x4D ... (skipped some bytes here) ... 0x3D 0x3D ] Attribute id : 'homedirectory', Values : ['/var/spool/imap/seriv'] Attribute id : 'uidnumber', Values : ['1001']

4 11

[Dovecot] Sometimes Dovecot v1.0.3 does not accept new connections
by Steffen Kaiser 30 Oct '07

30 Oct '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, occasionally Dovecot stops to accept new connections. Already existing ones do function properly. Strace'ing dovecot-auth reveals that it is running and is authentificating users, the logfile logs new connections. However, lots of other connects just stall, before the IMAP server responds with the greeting. My user backend is a LDAP server. I've sniffed the interface, but I also don't see numerous connection attempts, so I suppose, that there is no DoS attack running. The logfile contains no warning or error except: dovecot: Oct 17 15:34:44 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:34:49 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:34:52 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:02 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:05 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:12 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:19 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:20 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:25 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:26 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:27 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:27 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:41 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:42 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:47 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:49 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:49 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:50 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:56 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:36:03 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 Does somebody has an idea, where to go to look into the issue? Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRxYYSi9SORjhbDpvAQL8JQf+KWGlq9ic5ufFKcc/hZu6ZUQCpvDTzQHy YGyCFWXNsMoumMEXieiUw6plGDqEWajrhuDNbWHLtc8NPykpopT29lBaxIL2up1R uY0FV02AIjtNbexoRnC9Fk+0z+keDBb9DtrgHDZeNeK+vizxFQeLIM2xtWgXky9t MjoUVYeuXPAb8kZPm3ryW10SadDIJOi7mmnPZFWscaBgN/3Pvf9/oakAaEJyezFj HJY3bYVj2SeblVnn8xFXxszFTV1I3IOM/vIQAtA6gJ4p5D5xXabGzyERgSck1jz6 OtdUIyLJmLdFq5jRdP2FtYyLyOdb27z7krxfFGXeAMbHxf3TCefaiA== =TVVY -----END PGP SIGNATURE-----

2 4

[Dovecot] .dovecot.sieve not being read
by ding dong 30 Oct '07

30 Oct '07

Mail seems to be delivered to INBOX without reading what is in .dovecot.sieve # cat /home/vmail/user(a)example.com/.dovecot.sieve if exists "From" { discard; stop; } # ls -alh /home/vmail/user(a)example.com/.dovecot.sieve -rw-r--r-- 1 vmail vmail 41B Oct 29 01:26 .dovecot.sieve # tail /var/log/dovecot-deliver.log deliver(user(a)example.com): Oct 29 01:33:14 Info: msgid=< 47253857.20500(a)example.com>: saved mail to INBOX # tail /var/log/maillog Oct 29 01:33:14 freebsdserver1 dovecot: auth-worker(default): sql( user(a)example.com) SELECT maildir AS home, uid AS uid, gid AS gid FROM virtual_mailboxes WHERE user = 'user(a)example.com' AND enabled = TRUE LIMIT 1 Oct 29 01:33:14 freebsdserver1 dovecot: auth(default): master out: USER 1 user(a)example.com home=user(a)example.com/uid=1002 gid=1002 Oct 29 01:33:14 freebsdserver1 postfix/pipe[25035]: 8CB9F1CC2A: to=< user(a)example.com>, relay=dovecot, delay=0.08, delays=0.04/0.02/0/0.03, dsn= 2.0.0, status=sent (delivered via dovecot service) # dovecot --version 1.0.5 # dovecot -n # 1.0.5: /usr/local/etc/dovecot.conf login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_gid: 0 mail_extra_groups: vmail mail_location: maildir:/home/vmail/%h imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep auth default: mechanisms: plain login verbose: yes debug: yes passdb: driver: pam passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /usr/local/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

2 3

[Dovecot] 1.1Beta5 Issue
by Jeff Grossman 30 Oct '07

30 Oct '07

I installed 1.1Beta 5 this weekend. I had no problems at all yesterday using Thunderbird. I started reading my mail with Squirrelmail this morning and everything was going pretty smooth. I tried to delete a daily e-mail I receive from careerbuilder.com and the IMAP process shot up to 99.9% and I was not able to do anything in Squirrelmail. I killed that process and tried it again just to be sure what it was. And it did it again. I can delete any other message with no problems, just that one causes me issues. I am not sure if Thunderbird is the same, I will have to wait until I get home tonight. If there is any troubleshooting you would like me to do, please let me know. Jeff

3 6

Re: [Dovecot] 1.1Beta5 Issue
by Jeff Grossman 30 Oct '07

30 Oct '07

> On Mon, 2007-10-29 at 08:08 -0700, Jeff Grossman wrote: >> I installed 1.1Beta 5 this weekend. I had no problems at all yesterday >> using Thunderbird. I started reading my mail with Squirrelmail this >> morning and everything was going pretty smooth. I tried to delete a >> daily >> e-mail I receive from careerbuilder.com and the IMAP process shot up to >> 99.9% and I was not able to do anything in Squirrelmail. > > Thanks, fixed: http://hg.dovecot.org/dovecot/rev/ac0e7f713d70 Yup, appears to be working correctly now. Thanks for the quick fix. Jeff

1 0

[Dovecot] time going back
by zbigniew szalbot 29 Oct '07

29 Oct '07

Hi all, Sorry if this is trivial. I am just concerned. In Poland we will be putting the clocks one hour behind (back) on Sunday. I once saw dovecot killing itself because I manually adjusted the clock in the past. Will it not happen in this case? Thanks for your ideas. Zbigniew Szalbot

4 4

[Dovecot] Static home while using LDAP
by David Bosque 29 Oct '07

29 Oct '07

Hello all, I've been googling for a workaround for this for nearly a week to no avail and I hope someone in the list can shed some light on it. I have downloaded and compiled dovecot 1.0.5 and applied the quota-warning to it. I have configured everything and it's working wonderfully, even the lda with the sieve plugin. This is my current relevant configuration: userdb static{ args = uid=501 gid=12 home=/var/mail/buzones/%d/%n allow_all_users=yes } passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } However, I need to obtain some more data from LDAP, so I need to switch to an ldap userdb, but want to keep the home as it is in the static configuration and not having to store it in LDAP. Is it possible to use a fixed home (as in the static userdb) while using an ldap userdb? I am looking for something similar to user_global_uid and user_global_gid but for the "home". If not, is it possible to fix or append something to the values in the user_attrs (like the following)? user_attrs = [whatever_i_want_to_append]uid=home uidNumber=uid,gidNumber=gid Regards, David Bosque

3 5

[Dovecot] v1.0.7 released
by Timo Sirainen 29 Oct '07

29 Oct '07

http://dovecot.org/releases/1.0/dovecot-1.0.7.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.7.tar.gz.sig Almost missed this one. I had already fixed it in v1.1 tree, but forgot to fix in v1.0 tree. - deliver: v1.0.6's "From " line ignoring could have written to a bad location in stack, possibly causing problems.

1 0

Re: [Dovecot] fallback for proxy?
by Bill Boebel 29 Oct '07

29 Oct '07

On Sunday, October 28, 2007 8:32am, Cor Bosman <cor(a)xs4all.nl> said: > Is it possible somehow to configure a fallback for a failed proxy? I am using > sql based proxying through dovecot, but it would be nice if you can fallback > to another host if the proxy destination server is down. High availability > and all.. We do this in our system by having a separate monitoring server update the IP in MySQL when a backend server fails. Bill

1 0

[Dovecot] Resource temporarily unavailable
by karpi.lists＠email.cz 29 Oct '07

29 Oct '07

Hello, Im using dovecot for ages and im happy.. but at now strange things happens: mutt returns: Error talking to localhost (Connection reset by peer) so i started telnet: alnagon ~ % telnet localhost 143 Trying 127.0.0.1... Connected to alnagon.localnet.cz. Escape character is '^]'. * OK Dovecot ready. 1 login karpi blablabla 1 OK Logged in. Connection closed by foreign host. Last line "Connection closed" appears immediatelly after logging.. log says: Oct 27 11:20:50 alnagon dovecot: imap-login: Login: user=<karpi>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 27 11:20:51 alnagon dovecot: IMAP(karpi): setuid(1000) failed: Resource temporarily unavailable Oct 27 11:20:51 alnagon dovecot: child 8537 (imap) returned error 89 my configuratilon runs on gentoo desktop and looks like: alnagon ~ # dovecot -n # 1.0.3: /etc/dovecot/dovecot.conf protocols: imap ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file: /etc/ssl/dovecot/server.key login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_processes_count: 1 mail_extra_groups: mail mail_debug: yes auth default: passdb: driver: pam args: * userdb: driver: passwd very thanks for any hint..

4 3