- dovecot - dovecot.org

[Dovecot] dovecot and communitgate (stalker)
by tyco 05 Sep '05

05 Sep '05

hi there, i am totally new to dovecot and use communigate pro stalker.com as my mailserver. everything in communigate is fine. the only problem i do have is imap speed. i just got a login at a dovecot server and i must say WOW its so fast amazing. since communigate does not support indexing on mdir direcotries i need to find a solution. so i am wondering if it would be possible to use dovecot imap server on top of communigate as an imap server? i know that this would not work for special cgp features like shared mailboxes. etc.... thnax christof

1 0

[Dovecot] Dovecot 1.0 and ldap; does this combination works?
by Vedran Furac 05 Sep '05

05 Sep '05

Hi! After upgrading from dovecot 0.9.14 to 1.0 crashes immediately after starting when using ldap as userdb and passdb. You can find more information here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=320388 I'm confused with two users: login_user and auth_user. Witch of them has to be in ldap? If anyone here has a working dovecot+ldap configuration, could he show me his configuration? Regards Vedran

3 5

[Dovecot] Dovecot-LDA: Development questions
by Steffen Kaiser 05 Sep '05

05 Sep '05

Hello, I'm tinkering with Dovecot-LDA in order to achieve: + Better intergration into sendmail, and + tweaking its way to act on errors. Attached patch is a "brainstorming" like suggestion: a) when sendmail is dropping a message, it spawns the LDA, captures stderr/stdout and, if the LDA returns an exit code != 0, generates either a DSN or, when EX_TEMPFAIL, queues the mail. Hence, it is not necessary to have mail_send_rejection() to spawn another sendmail instance. The attached patch suggest to introduce an "operation_mode", in which Dovecot-LDA behaves differently for different environments. b) Some errors, like when spooling the message into the users folders fails, because the user is out of quota, one should prefer tempfailing the message, rather than a permanent error. Attached patch includes an option "-f", which has main() to return EX_TEMPFAIL. This is the way maildrop is acting, BTW. === Sendmail supports "account+detail" syntax out-of-the-box; that is for recipient matching only the portion left of the plus-sign is significant, the trailing portion may be used by the LDA as a hint to spool the message. Usually the information is passed via command line to the LDA. The libsieve seems to already support this notation, see tokens DETAIL, subaddress, :detail and the README file: Derrick Brashear (shadow+sieve@andrew...) Did somebody used or have some idea how to make use of the "+detail" stuff of libsieve? Basically the main problem in my opinion is what to query, because the information (final physical mailbox and/or owner) one can query is neither a header nor an envelope information (besides that the envelope information is not available to the LDA anyway). Consider a BCC to one recipient that expands to numerous maildrops, then the maildrop of actual delivery attempt can not be derived from neither the envelope nor the header information. The only way to integrate the +detail stuff into Dovecot-LDA seems to be when "keep" is performed (or no Sieve script is present). Then one could spool the message into folder "detail", if it already exists -- one should be allow other people to create mailboxes ;-) This is no action of the Sieve library, but of the LDA calling sieve. The Wiki mentions in the section about to setup exim: envelope_to_add What's this setting is doing? In src/sieve-cmu.c, static int getenvelope, there is: } else if (!strcasecmp(field, "to")) { *contents = m->temp; m->temp[0] = /*FIXME:msg_getrcptall(m, m->cur_rcpt)*/m->authuser; m->temp[1] = NULL; return SIEVE_OK; So it seems appropriate to tweak dovecot_sieve_run() into: mdata.authuser = username; mdata.recipient = detail_on_commandline ? concat(username, "+", detail_on_commandline) : username ; Or better: Have the complete recipient passed via command line option? and alter getenvelope(): m->temp[0] = m->recipient; I think this tweaks would be better than have the "-d" option support the plus-syntax. === Currently, the compiled Sieve script is placed into the same directory the script is located itself. How about to _always_ file the compiled script into [CONTROLDIR]/.dovecot.sievec? That would come over the problem with the system-wide default sieve script. Otherwise: The README mentions a test application and I found a sievec and sieved application (Sieve compile / decompiler) I presume. I can not just run "make sievec" to have it compile, does somebody played around with the Sieve stuff in LDA? Regards, -- Steffen Kaiser

1 0

Re: [Dovecot] qpopper UIDLs and migrating to dovecot/maildir
by Chris Wakelin 05 Sep '05

05 Sep '05

OK, here's the patch against dovecot-1.0-stable. (I just applied it to dovecot-stable-20050901. My version of stable has a few more patches applied, so I needed to apply the patch to a clean version!) Best Wishes, Chris grant beattie wrote: > On Sun, Sep 04, 2005 at 12:30:27AM +0100, Chris Wakelin wrote: > > >>Right! Here's a patch against dovecot-1.0.alpha1 which adds an extra option: >> >>pop3_reuse_xuidl = yes >> >>which if set will use the contents of the (first) X-UIDL header, if it >>exists, instead of the result of expanding pop3_uidl_format. It will use >>pop3_uidl_format if there is no X-UIDL header. >> >>This is typically for people migrating from Qpopper who don't want their >>users to get all the mail they've left on the server a second time, but >>should also work for any other POP server that happens to write X-UIDL >>headers, if any such exist ;) >> >>I've only done rudimentary testing, but it seems to work! I also have a >>version of the patch for dovecot-1.0-stable (which is what we'll be >>using next week!) if anybody's interested (only minor differences, use >>'mail->get_header(mail, "X-UIDL")' instead of >>'mail_get_first_header(ctx->mail, "X-UIDL")') > > > this is great stuff, thanks! > > I'm using the 1.0alpha1 diff and it seems to be working fine so far. > as we will probably be running 1.0 stable in production, would you > mind forwarding me the diff against 1.0 stable? > > this is an extremely useful feature, making it even easier to migrate > from alternate POP3 servers than Dovecot already is. :) > > grant. > -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094 diff -ruN dovecot-1.0-stable.orig/src/master/mail-process.c dovecot-1.0-stable/src/master/mail-process.c --- dovecot-1.0-stable.orig/src/master/mail-process.c Tue Feb 8 10:30:11 2005 +++ dovecot-1.0-stable/src/master/mail-process.c Mon Sep 5 10:29:22 2005 @@ -220,6 +220,8 @@ env_put("FULL_FILESYSTEM_ACCESS=1"); if (set->pop3_no_flag_updates) env_put("POP3_NO_FLAG_UPDATES=1"); + if (set->pop3_reuse_xuidl) + env_put("POP3_REUSE_XUIDL=1"); if (set->mbox_dirty_syncs) env_put("MBOX_DIRTY_SYNCS=1"); if (set->mbox_very_dirty_syncs) diff -ruN dovecot-1.0-stable.orig/src/master/master-settings.c dovecot-1.0-stable/src/master/master-settings.c --- dovecot-1.0-stable.orig/src/master/master-settings.c Sun Aug 7 14:00:41 2005 +++ dovecot-1.0-stable/src/master/master-settings.c Mon Sep 5 10:29:22 2005 @@ -125,6 +125,7 @@ /* pop3 */ DEF(SET_BOOL, pop3_no_flag_updates), DEF(SET_BOOL, pop3_enable_last), + DEF(SET_BOOL, pop3_reuse_xuidl), DEF(SET_STR, pop3_uidl_format), DEF(SET_STR, pop3_client_workarounds), @@ -297,6 +298,7 @@ /* pop3 */ MEMBER(pop3_no_flag_updates) FALSE, MEMBER(pop3_enable_last) FALSE, + MEMBER(pop3_reuse_xuidl) FALSE, MEMBER(pop3_uidl_format) "%v.%u", MEMBER(pop3_client_workarounds) NULL, diff -ruN dovecot-1.0-stable.orig/src/master/master-settings.h dovecot-1.0-stable/src/master/master-settings.h --- dovecot-1.0-stable.orig/src/master/master-settings.h Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/master/master-settings.h Mon Sep 5 10:29:22 2005 @@ -96,6 +96,7 @@ /* pop3 */ int pop3_no_flag_updates; int pop3_enable_last; + int pop3_reuse_xuidl; const char *pop3_uidl_format; const char *pop3_client_workarounds; diff -ruN dovecot-1.0-stable.orig/src/pop3/commands.c dovecot-1.0-stable/src/pop3/commands.c --- dovecot-1.0-stable.orig/src/pop3/commands.c Sun May 8 10:45:32 2005 +++ dovecot-1.0-stable/src/pop3/commands.c Mon Sep 5 10:29:22 2005 @@ -489,6 +489,7 @@ struct var_expand_table *tab; struct mail *mail; string_t *str; + const char *xuidl; int ret, found = FALSE; tab = t_malloc(sizeof(static_tab)); @@ -532,7 +533,15 @@ str_truncate(str, 0); str_printfa(str, ctx->message == 0 ? "%u " : "+OK %u ", mail->seq); - var_expand(str, uidl_format, tab); + if (reuse_xuidl) { + xuidl=mail->get_header(mail, "X-UIDL"); + if (xuidl != NULL) + str_append(str, xuidl); + else + var_expand(str, uidl_format, tab); + } + else + var_expand(str, uidl_format, tab); ret = client_send_line(client, "%s", str_c(str)); t_pop(); diff -ruN dovecot-1.0-stable.orig/src/pop3/common.h dovecot-1.0-stable/src/pop3/common.h --- dovecot-1.0-stable.orig/src/pop3/common.h Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/pop3/common.h Mon Sep 5 10:29:22 2005 @@ -18,7 +18,7 @@ extern struct ioloop *ioloop; extern enum client_workarounds client_workarounds; -extern int enable_last_command, no_flag_updates; +extern int enable_last_command, no_flag_updates, reuse_xuidl; extern const char *uidl_format; extern enum uidl_keys uidl_keymask; diff -ruN dovecot-1.0-stable.orig/src/pop3/main.c dovecot-1.0-stable/src/pop3/main.c --- dovecot-1.0-stable.orig/src/pop3/main.c Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/pop3/main.c Mon Sep 5 10:29:22 2005 @@ -41,6 +41,7 @@ enum client_workarounds client_workarounds = 0; int enable_last_command = FALSE; int no_flag_updates = FALSE; +int reuse_xuidl = FALSE; const char *uidl_format; enum uidl_keys uidl_keymask; @@ -166,6 +167,7 @@ parse_workarounds(); enable_last_command = getenv("POP3_ENABLE_LAST") != NULL; no_flag_updates = getenv("POP3_NO_FLAG_UPDATES") != NULL; + reuse_xuidl = getenv("POP3_REUSE_XUIDL") != NULL; uidl_format = getenv("POP3_UIDL_FORMAT"); if (uidl_format == NULL)

1 0

[Dovecot] 1.0a1 Coredumps / errors when moving multiple
by Gregory Bond 05 Sep '05

05 Sep '05

I've just tried upgrading 1.0t51 to 1.0a1 and it has been........ difficult. I've been getting logs of Sig11s and other errors, and have trouble tracking them down. Main problem seems to be with moving / copying messages. One at a time works (mostly), multiple will coredump the imap process (not yet managed to get a proper core out though...) I'm using imap & Maildir, maildir on NFS & Indexes on UFS, Solaris 8. Server is postfix / procmail (delivering pre-sorted into various Maildir folders) and Dovecot 1.0a1. Client is thunderbird on OS/X. If I turn off mbox_copy_with_hardlinks, then instead of a coredump I get a hang and an error message: > IMAP(gnb): Maildir /home/gnb/Maildir sync: UID inserted in the middle > of mailbox (3871 > 3870, file = 1125740849.23189_0.lenford:2,Saa) This is after I've removed all the cache/index files and even all the dovecot-uid files.... I'm back on 1.0t51 for now, but could have another crack at this if there are any hints.

1 0

[Dovecot] Dovecot logging
by Black Vette 05 Sep '05

05 Sep '05

Fedora Core 4 dovecot-0.99.14-4.fc4 I'm trying to diagnose some mail issues. I do not believe Dovecot is the problem. If I could see the Dovecot logs, it might be helpful in resolving my issue. In /etc/dovecot.conf I have tried to set the following: log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.log I have 'touch /var/log/dovecot.log'. When I try to restart dovecot 'service dovecot restart', it fails and I'm not able to see the reason why it is failing. Where am I going wrong getting this working? Also, are there various debug levels? I saw 'debug' mentioned on the list, but I was unable to see anything about it in the config file. Thanks, Mike __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Re: [Dovecot] qpopper UIDLs and migrating to dovecot/maildir
by Paul Vatta 05 Sep '05

05 Sep '05

Hi Chris, We migrated to Dovecot from Qpopper/UW-IMAP in July. We previously looked at altering the Dovecot code, client-side duplicate email cleanup utilities (for Eudora), and enforcing "download-then-delete from the server" prior to the migration. We got around the "downloading of previously downloaded emails" problem by moving all previously downloaded emails to a new folder called "ConvertedMail" during the conversion process from mbox (Qpopper) to maildir. This assumes you're going to maildir though. The benefit in this is that the POP client only retrieves email from th inbox folder, and after conversion, this will mean only new emails. If the POP client's previous download of older email dissappeared (for whatever reason), a Web Mail client accessing the mailstore via IMAP would allow access to the ConvertedMail folder. Regards, Paul

1 0

[Dovecot] login: Missing Protocol from server name 'imap'
by Phil Bettinson 04 Sep '05

04 Sep '05

Hello All (possibly again) I did send a messge earlier, but it may have been eaten by the mail system. I've now managed to get dovecot started, and I'm now getting "Missing protocol from server name 'imap'" This is somewhat confusing. Does it mean that I have somewhere called my server imap? or is it talking about it missing a protocol called imap? if it's meant to be "missing protocol imap definition" or somesuch, I have filled that out, but can't for the life of me figure out what the error message is actually trying to tell me! I'm running dovecot alpha1 on RedHat as3. I have the feeling I've been staring at the problem for too long, and somone will just say "have you tried this!", but it's worth a shot. Thanks in advance Phil

2 1

[Dovecot] qpopper UIDLs and migrating to dovecot/maildir
by grant beattie 04 Sep '05

04 Sep '05

hi all, I am hoping to convert a 350K user qpopper installation using mbox to dovecot and maildir (pop3 only). many of the users "leave mail on server", and qpopper's UIDL format isn't (yet) supported by dovecot. since the UIDLs have been written by qpoppper to the existing mbox files (and will be preserved when the mboxes are converted to maildir) it would be possible to do this seamlessly if dovecot could read the UIDLs from the messages and populate the index files as needed. is anything like this already possible? it doesn't matter what UIDLs new messages get, since they would never have been downloaded by the user via qpopper. any ideas would be appreciated. grant.

2 3

[Dovecot] "stable" v. "alpha"
by Ben Beuchler 03 Sep '05

03 Sep '05

Is "alpha" the new "-stable"? Should I switch? Gracias! -Ben

4 8