- dovecot - dovecot.org

[Dovecot] IDLE with Leopard Mail
by Scott Murman 07 Nov '07

07 Nov '07

imap IDLE is now built into the apple mail client in Leopard (finally!!). anyone looked at compatibility issues with dovecot? -SM-

2 1

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

07 Nov '07

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta7.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta7.tar.gz.sig Changes since beta6: - Beginnings of unit tests, as I mentioned in a previous mail - Message parsing fixes - Cache file handling fixes Known bugs: - Cache file doesn't keep track of how much it contains deleted data, which means it could grow infinitely. This worked at some point, so I'm not sure what I did to break it. I'll figure it out later. - Apparently for some use cases v1.1 is still slower (about 2x) than v1.0. Probably more or less specific to NFS + mmap_disable=yes.

1 0

Re: [Dovecot] Unit testing
by Alan Ferrency 07 Nov '07

07 Nov '07

Timo Sirainen <tss(a)iki.fi> wrote: > I finally added beginnings of unit tests to Dovecot v1.1 code tree: > http://hg.dovecot.org/dovecot/rev/4e4a5d6bb2cb Great! Unit testing is good, even though it's boring and not very glamorous. I wonder if you have seen or considered libtap, possibly as an optional dependency for those who care about running the tests? http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap It looks like it could almost drop in, in place of some of your existing test helpers. It is also compatible with a variety of end user test tools. However, I could see hesitation in adding external dependencies where they aren't really necessary. If you had TAP compatibility through libtap or other means, I could easily drop dovecot into our existing suite of nightly smoke tests on FreeBSD. > 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! :) With a 5 month old and a 4 year old on hand, "copious free time" isn't my strong point, but I'll at least attempt to provide tests with any future bug reports. Thanks! Alan Ferrency

1 0

[Dovecot] How to set multi backends (with same type)
by maximatt 07 Nov '07

07 Nov '07

hi..... i don't know if its posible. i have two ldap directories, and i want use them to use as my dovecot users backend... so i have two configurations files... "dovecot-ldap1.conf" and " dovecot-ldap2.conf" and i try setting like: Test 1: (simil postfix ) :D This dont work auth default { : : passdb ldap { args= /etc/dovecot/etc/ldap/dovecot-ldap1.conf, /etc/dovecot/etc/ldap/dovecot-ldap2.conf } userdb ldap { args= /etc/dovecot/etc/ldap/dovecot-ldap1.conf, /etc/dovecot/etc/ldap/dovecot-ldap2.conf } } Test 2: This dont work auth default { : : passdb ldap { args= /etc/dovecot/etc/ldap/dovecot-ldap1.conf/etc/dovecot/etc/ldap/dovecot- ldap2.conf } userdb ldap { args= /etc/dovecot/etc/ldap/dovecot-ldap1.conf/etc/dovecot/etc/ldap/dovecot- ldap2.conf } } Test 3: (looking "passbd ldap" as a set) :) this work, but dovecot-ldap2.conf override dovecot-ldap1.conf (the set vision, none) auth default { : : passdb ldap { args= /etc/dovecot/etc/ldap/dovecot-ldap1.conf args= /etc/dovecot/etc/ldap/dovecot-ldap2.conf } userdb ldap { args= /etc/dovecot/etc/ldap/dovecot-ldap1.conf args= /etc/dovecot/etc/ldap/dovecot-ldap2.conf } } ¿How could i do this? :( Thanks in advance :) -- Salu2 ;)

1 1

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

06 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 06 Nov '07

06 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 06 Nov '07

06 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 05 Nov '07

05 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 05 Nov '07

05 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 04 Nov '07

04 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 03 Nov '07

03 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 02 Nov '07

02 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