- dovecot - dovecot.org

[Dovecot] 1.0-stable update
by Timo Sirainen 26 Apr '05

26 Apr '05

Just a note, I backported some larger mbox changes from 1.0-test67. Hopefully works, but if you're going to try it test it well first :) Should fix some issues related to X-IMAP/X-IMAPbase header handling and maybe some other mbox related problems as well.

3 6

[Dovecot] configuration problem: maildir folders and messages not found
by Bram Mertens 26 Apr '05

26 Apr '05

Hi Perhaps I've been going too far OT in my previous thread or perhaps I just didn't explain my problem clear enough so forgive me for trying again. I have configured fetchmail to fetch my mail from my ISP's POP3-server. I have set up procmail to filter messages and deliver all non-filtered messages to the folder ".IN-catchall/" in "$HOME/Maildir" After sending some test messages the "Maildir" folder in my home-folder looks like: m8ram@medion:~$ tree -a Maildir Maildir |-- .IN-catchall | |-- cur | |-- new | | `-- 1114356268.8424_0.medion | `-- tmp |-- .IN-testing | |-- cur | |-- new | | |-- 1114354955.6900_0.medion | | `-- 1114356175.8292_0.medion | `-- tmp |-- .INBOX | |-- .IN-testing | | |-- cur | | |-- new | | | |-- 1114354955.6900_0.medion | | | `-- 1114356175.8292_0.medion | | `-- tmp | |-- .imap.index | |-- .imap.index.data | |-- .imap.index.log | `-- .imap.index.tree |-- .customflags |-- IN-catchall |-- cur |-- new `-- tmp 16 directories, 11 files Because I have been using the mbox format to test dovecot so far I had to modify my dovecot configuration but no matter what I try none of the messages above appear in evolution or thunderbird. Can anybody tell me what I need to add/remove/change in my config? I'm running: m8ram@medion:~$ /usr/sbin/dovecot --version 0.99.14 on debian testing /etc/dovecot/dovecot.conf contains the following: protocols = imap login = imap login = pop3 mail_extra_groups = mail default_mail_env = maildir:/%h/Maildir auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root When using mbox I used: default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u I also tried the following for maildir: default_mail_env = maildir:~/Maildir default_mail_env = maildir:/home/%u/Maildir But neither worked. TIA Bram -- # Mertens Bram "M8ram" <bram-mertens(a)linux.be> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 13:39:03 up 30 days, 19:52, 13 users, load average: 0.49, 0.50, 0.39 #

2 4

[Dovecot] ldap uid with static gid problem
by Farkas Levente 26 Apr '05

26 Apr '05

hi, i'd like to use dovecot to authenticate from ldap. in ldap each user has it's uniq uid and gid. unfortunately with postfix we can't use uniq uid/gid since in this case we have ot create all user's home in advance. so we decided to use uniq uid and a common gid in postfix since in this case postfix can create new users maildir and deliver new mails. so i'd like to use everyone's own uid in dovecot, but a common gid (same as in postfix). but how can i do so? i read the wiki, but the problem is if i use: auth_userdb = ldap /etc/dovecot-ldap.conf then i have to define ldap attrib name in dovecot-ldap.conf: user_attrs = mail,,,uid,uidNumber,gidNumber what should i use in the last field in user_attrs? or it's not possible with dovecot to define this? i'd be very said in this case:-( any advice? thanks in advance. yours. -- Levente "Si vis pacem para bellum!"

2 1

[Dovecot] libexecdir and localstatedir problem
by Marten Lehmann 26 Apr '05

26 Apr '05

Hello, I'd really like to define the finale libexecdir and localstatedir through the configure-script. But the Makefiles are rewriting them. Not $libexecdir is used, but $pkglibexecdir. And $pkglibexecdir is always defined as $libexecdir/dovecot. But I don't want this trailing "/dovecot". Same with localstatedir. I want dovecot to use a certain path. But to this path, a "run/dovecot" is appended. I surely could build some patchfiles to change the Makefiles. But it would be easier, if you could add a new directive --pgklibexecdir to the configure-script. I don't know where the "run/dovecot" is defined, but it would also be very fine to set it in the configure-script (specially when upgrading to new releases) instead of defining them all in the dovecot.conf (base_dir, login_dir). Regards Marten

2 5

[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