- dovecot - dovecot.org

[Dovecot] 1.0-test68 released
by Timo Sirainen 26 Apr '05

26 Apr '05

http://dovecot.org/test/ Recommended update, has had a lot of testing today. No new big features. Changes: - LDAP authentication should work finally? - Some header lookup fixes that should fix sort/threading issues - Don't crash with 0-byte size mboxes - Transaction log fixes. Also rotate .log file to .log.2 file, allowing more history and less "transaction log file lost" messages. - SEARCHing multiple headers might have crashed - mbox: When first message was expunged we might have gotten "uid-last unexpectedly lost" errors. - recent flag counter wasn't updated in index file header always even if the recent flags were removed - UIDVALIDITY changes are handled more transparently - Added --rundir configure option (not actually tested, does it work? :) - etc.

6 12

[Dovecot] INBOX can't be deleted
by Marten Lehmann 26 Apr '05

26 Apr '05

Hi, surely it can't and it shouldn't. I'm just wondering why a check for "INBOX" is done in src/imap/cmd-delete.c AND src/lib-storage/index/maildir/maildir-storage.c. The first is clear because it gives an imap-error to the client. But for which case is the check in maildir-sorage.c? Just to be absolutely sure? The reason for me to ask is, because I need to disable deletions for five folders: Drafts, Infected, Junk, Sent and Trash. A certain webmail-interface and spamfilter will rely on these folders, so nobody shall be able to delete or rename them. First I placed the checks in cmd-delete.c. Should I place them in maildir-storage.c additionally? In normal circumstance, the check in maildir-storage.c should never be reached, right? Regards Marten

2 1

[Dovecot] Dovecot Stable (or: When is 1.0 coming to a server near you?)
by Rich West 26 Apr '05

26 Apr '05

I'm mainly just curious, but what version of dovecot is considered to be stable enough to be running in a production environment? We're running the 0.99.13 version shipped with FC3 and, while experiencing great performance gains over UW-IMAP, we have hit a couple of snags here and there (random and infrequent characters at the beginning of a mailbox, periodic duplication of a message here and there, etc). I figure we should upgrade to something a bit more current, but I am not sure what the "recommended" verion would be.. Also, perhaps more important, what's the roadmap to getting 1.0 finalized? What's the timeframe? :-) -Rich

2 1

[Dovecot] -test68, -stable and ldap
by Thomas Hummel 25 Apr '05

25 Apr '05

Hello Timo, Thanks to your patches, LDAP authentication now works with -test68. However, I'm still experiencing a segmentation fault with today's snapshot of -stable, as shown in the following gdb backtrace. [I'm still running FreeBSD 5.3] Can you see where it comes from ? Is it because the ldap new code (as in -test68) hasn't been backported into -stable yet ? Thank you, -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau -- (gdb) n 186 userdb_preinit(); (gdb) n 187 passdb_preinit(); (gdb) n Program received signal SIGSEGV, Segmentation fault. auth_cache_parse_key (query=0x0) at auth-cache.c:39 39 for (; *query != '\0'; query++) { (gdb) bt full #0 auth_cache_parse_key (query=0x0) at auth-cache.c:39 str = (string_t *) 0x806a100 key_seen = '\0' <repeats 255 times> key = 0 '\0' #1 0x08055456 in passdb_ldap_preinit (args=0x8075100 "/usr/local/dovecot/etc/dovecot-ldap.conf") at passdb-ldap.c:237 conn = (struct ldap_connection *) 0x8078010 #2 0x08054b8d in passdb_preinit () at passdb.c:152 p = (struct passdb_module **) 0x8068914 name = 0x806b078 "ldap" args = 0x806891c "ÒP\006\b\bT\005\bdT\005\bxT\005\bøR\005\b\204S\005\bíQ\006\b" #3 0x0805108b in main (argc=1, argv=0x806a100) at main.c:187 No locals. (gdb) --

1 0

[Dovecot] HA heartbeat scripts
by Nigel Metheringham 25 Apr '05

25 Apr '05

Has anyone worked with getting dovecot to work in a HA cluster using heartbeat? If so do you have any magic startup scripting or other special sauce? [I'll be playing with this over the next couple of days, although concentrating on pop for our requirements. I can post any scripting I produce] Nigel. -- [ Nigel Metheringham Nigel.Metheringham(a)InTechnology.co.uk ] [ - Comments in this message are my own and not ITO opinion/policy - ]

1 0

[Dovecot] Limiting IP range access
by Luigi Rosa 25 Apr '05

25 Apr '05

First of all, MANY compliments for this fantastic software. Now the question: is it possibile to limit the access to dovecot (or a single service) to a specified range of IPs? Basically, I am thinking about an IP-based ACL. Thankyou in advance. Ciao, luigi -- A beer delayed is a beer denied.

4 3

[Dovecot] Quota
by Timo Sirainen 25 Apr '05

25 Apr '05

If anyone's interested about implementing quota code for Dovecot (there were a few of you before! :), now it's finally your chance to do it quite easily. With the API changes committed today to CVS, it's now much easier to write plugins that modify mail-storage behavior. So, I finally fixed my half-working quota plugin that had been lying there for a while. It implements the RFC2087 quota commands for IMAP, a generic quota API that should allow pretty much any kind of quota implementation, and the actual quota limit checking for saving and copying mails. As an example there's an implementation which just scans through all files in a directory and sums their sizes. Currently it can be made to work only when starting from command line, eg.: export QUOTA=~/mail:storage=1024 export MODULE_DIR=/usr/local/lib/dovecot/imap ./imap The QUOTA variable is passed to the quota implementation. In this case quota-dirsize reads it, figures out that ~/mail is the directory where to count the files, and 1024kB is the maximum for quota. I think I'll change the master process code so that any unrecognized varibles that come from userdb are fed to imap/pop3 processes. That way you could simply make the userdb return the quota value (and set other user-specific settings as well). Available from: http://dovecot.org/patches/1.0/quota.tar.gz Unpack under dovecot/src, compile command is at the beginning of quota-plugin.c I'm still wondering where this code should be placed. Maybe the core implementation should be built into Dovecot, while the different quota implementations would be plugins? ..And even better would be if Dovecot's build process was modified so that it's possible to specify with configure script what to compile in and what to compile as plugins.. Anyway, comments welcome, Maildir++ implementation welcome, other implementations welcome as well :)

3 8

[Dovecot] File isn't in mbox format - Couldn't open INBOX
by Rich West 24 Apr '05

24 Apr '05

While I saw another thread on the list similar to the issue I was experiencing (http://dovecot.org/pipermail/dovecot/2005-February/006168.html) I was wondering if there was a way around this problem (the thread simply suggested upgrading, but are the later version (specifically the 1.0-test releases) ready for prime time?)... We're periodically having this with some users (not sure what client they are using, but I am pretty sure it is MS Outlook) where the inbox is in near perfect shape except for some extra characters at the beginning of the file. POP or IMAP delivery fails with an error stating "File isn't in mbox format - Couldn't open INBOX". It looks like those characters are of a previous message that was not completely removed from the file, and those characters seem to throw everything out of wack.. It's easily correctable by removing the bogus characters from the beginning of the file, but that gets annoying quickly.. -Rich

4 7

[Dovecot] about filtering and dovecot
by Bram Mertens 24 Apr '05

24 Apr '05

Hi I would like to set up a local mailserver but I'm getting lost with all the available options. As I have already decided to use dovecot I hope someone here will be able to point me to the right docs/HOWTO's/... Here's my wish-list: 1) download mail from my ISP's POP3-server 2) scan with spamassassin 3) scan with ClamAV 4) filter messages (mailing lists/sender/...) 5) store messages in dovecot 6) be able to read messages on my desktop (where all of the above will be running) and on my laptop 7) be able to send messages (currently using evolution) from both my desktop and laptop so sent messages are stored in dovecot (the idea is to be able to see all sent messages on both PC's) I have already created a test-account om my ISP's POP3-server, installed and configured fetchmail and dovecot. Exim has been installed as well but I haven't touched it's configuration yet. Running fetchmail manually collects the mail and stores it in /var/mail/m8ram where dovecot finds it. So I would like to know (how to find out) how I can achieve 2), 3), 4) and 7). I have looked around and have discovered that there are many programs that can do some or all of this. But I haven't been able to figure out how to get them to work with dovecot. e.g. I don't understand what I would have to change to dovecot's config if exim or procmail or whatever moves certain messages to different folders (or even where these folders would be created). Perhaps I'm missing a HOWTO that explains all this, if so please let me know. TIA Bram -- # Mertens Bram "M8ram" <bram-mertens(a)linux.be> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 12:40:02 up 26 days, 18:53, 9 users, load average: 0.56, 0.46, 0.29 #

6 9

RE: [Dovecot] IMAP EXPUNGE disconnect/box hang - Fedora Core 2, Squirrelmail and Evolution
by Schettino, John Charles 24 Apr '05

24 Apr '05

Well, I just built and installed the 1.0 stable w/o tags version from source, and so far, it's not hanging/crashing the system - if this is the fix, I'm all over it :D Context: this is my problem: Correction: I'm running yum.log:03/07/05 05:48:28 Updated: dovecot 0.99.14-1.1.fc2.rf.i386 - Sorry about that. I'm a bit befuddled by this behavior. I've been using dovecot for close to a year, and recently the Fedora Core 2 Update: dovecot-0.99.13-4.FC2 build came in via yum. Since then I occasionally get this EXPUNGE disconnect error. When the error hits, the box does not crash but I can no longer log in*, nor start any new processes. I happen to have gkrellm running and I see a slow but steady climb in the # of processess. The only way to recover the box is to do a hard reset, as I cannot log in, nor su - to do a shutdown. In one case I happened to have a root shell open, and I still could not do a shutdown. Any ideas as to what I should do with this? As long as I don't expung everything is fine, but when I do expunge (move something or a filter runs in squirrelmail, or Action/Expunge in Evolution) sometimes it works fine, sometimes I get this error and a weird zombie state. It was all rock solid before this new version. Suggestions welcome - I don't seem to be getting any logging when it goes bad, perhaps I can up the log level? I'm more then happy to build the current dovecot from source, and if I should post this to some Fedora list, point me at it :D

3 3