- dovecot - dovecot.org

Re: [Dovecot] An alternate "dovecot-auth" daemon using cyrus-sasl
by Andrey Panin 06 Sep '05

06 Sep '05

On 249, 09 06, 2005 at 01:35:58PM +0400, Dmitry Butskoy wrote: > Andrey Panin wrote: > > >On 248, 09 05, 2005 at 03:48:19PM +0400, buc wrote: > > > > > >>We use dovecot in a heterogeneous environment (Windows/Linux desktops > >>and Linux servers). For unified authentication we use a sheaf > >>"Samba/Openldap" (i.e., Samba NT domain with openldap backend and > >>pam/nss_ldap for Linux). > >> > >> > >So why you can't use dovecot with openldap as passdb ? > > > Yes, now we use dovecot with pam, which uses openldap by pam_ldap etc... > But PAM can handle plain passwords only, therefore it is not suitable > for NTLM. > I have not found it in examples, but may be dovecot`s ntlm can take > appropriate password hashes from openldap directly? > (sambaLMPassword/sambaNTPassword) Yes, dovecot can handle LM/NTLM password hashes and it can fetch them from OpenLDAP directly (look at doc/dovecot-ldap.conf) In general you can store passwords in any supported form, just add proper password scheme prefix. For example: {NTLM}69943C5E63B4D2C104DBBCC15138B72B For more information read here: http://wiki.dovecot.org/Authentication > >>Windows users are authenticated well everywhere, but there is one old > >>issue. As "SPA" (NTLM) against NT domain is not supported by dovecot, it > >>is necessary to use default "plain" method. In addition to security > >>problems, it does also a problem of password unification. Each time a > >>user changes the password, he should do it one more time for the mail > >>program. > >> > >>I know that dovecot supports NTLM, however against local database only > >>(not for NT domain controller). In early versions support of cyrus-sasl > >>(which supports NTLM now) had been incorporated, however it like not > >>work and now is removed. > >>Fortunately, there is a possibility to substitute dovecot-auth > >>executable. Therefore I have tried to make an alternate variant of > >>dovecot-auth, which supports all that we need. > >> > >>For us, it seems to be more useful to create an auth daemon using > >>cyrus-sasl, rather than to add domain support to existing ntlm code. > >>First of all, it is easier for implementation. Besides it enables use of > >>all mechanisms supported by cyrus-sasl (present and future), including > >>GSSAPI. Anyway, it will be the useful additive to dovecot. > >> > >> > > > >Dovecot doesn't support cyrus-sasl for a good reason - it's a mess. > > > > > Certainly, I do not suggest to switch to use cyrus-sasl in upstream dovecot. > > But can give this patch the right to a life? Somewhere in "unofficial > patches"... > > >>I have made appropriate patches for both dovecot-1.0-stable and > >>dovecot-1.0.alpha1. > >>The idea is to copy "src/auth" to "src/auth-cyrus", strip all unneeded > >>from newly created directory and add cyrus-sasl support. The resulting > >>code probably looks not so elegantly as if it has been written > >>separately, however this way allows to not make a lot of things from the > >>scratch. > >> > >> > >>The patch against 1.0.alpha1 is > >>here: http://dmitry.butskoy.name/dovecot/dovecot-1.0.alpha1-cyrus.tar.gz . > >>To be more readable, it is not a flat patch (due to a lot of whole > >>files add/remove). It is a tarball with 3 files: a list of files to > >>initial copy from auth/ to auth-cyrus/, a patch for resulting tree, and > >>a script which automates this steps (:-)). (The script should be run in > >>the root of the main source, i.e. a dir with src/ and doc/ subdirs). > >> > >>I already have successfully tested this patch with PLAIN method. > >>However before testing of other methods, it would be desirable that > >>somebody have looked at it. > >> > >>Whether someone could check up my patch (just fluently having read), > >>at least for obvious bugs and typos? > >> > >> > > Dmitry Butskoy <Dmitry(a)Butskoy.name> > Saint-Petersburg, Russia > Red Hat Certified Engineer 809003662809495 > > -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 1

[Dovecot] upgrading: should I and what will change?
by Joshua Paine 06 Sep '05

06 Sep '05

I've been running dovecot 0.99.11 with postfix and postgresql in a production environment with about 25 real users and a couple hundred aliases split over a few domains for nearly a year now. No problems of any kind that I have noticed. Should I upgrade to the latest dovecot? What changes, if any, will I have to make? I've looked through the archives for a couple months without seeing much, and I don't see anything specific in the docs about upgrading. -Joshua <><

2 1

[Dovecot] Dovecot-LDA & OpenBSD
by Björn Ketelaars 06 Sep '05

06 Sep '05

Im having a bit of a problem with compiling dovecot-lda on OpenBSD. I used information from wiki.dovecot.org but this, unfortunately, resulted in some errors. Am I missing something? make all-recursive Making all in src Making all in libsieve if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/mnt/files/dovecot-1.0-test80/src/lib -I/mnt/files/dovecot-1.0-test80/src/lib-mail -I/mnt/files/dovecot-1.0-test80/src/lib-storage -I/mnt/files/dovecot-1.0-test80/src/lib-storage/index/mbox -DSYSCONFDIR=\""/usr/local/etc"\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -MT deliver.o -MD -MP -MF ".deps/deliver.Tpo" -c -o deliver.o deliver.c; then mv -f ".deps/deliver.Tpo" ".deps/deliver.Po"; else rm -f ".deps/deliver.Tpo"; exit 1; fi In file included from common.h:4, from deliver.c:5: /mnt/files/dovecot-1.0-test80/src/lib/lib.h:6:22: config.h: No such file or directory In file included from /mnt/files/dovecot-1.0-test80/src/lib/lib.h:23, from common.h:4, from deliver.c:5: /mnt/files/dovecot-1.0-test80/src/lib/compat.h:17:4: #error uoff_t size not set In file included from /mnt/files/dovecot-1.0-test80/src/lib/lib.h:23, from common.h:4, from deliver.c:5: /mnt/files/dovecot-1.0-test80/src/lib/compat.h:37: error: conflicting types for `socklen_t' /usr/include/sys/types.h:95: error: previous declaration of `socklen_t' In file included from common.h:5, from deliver.c:5: /mnt/files/dovecot-1.0-test80/src/lib-storage/mail-storage.h:428: error: syntax error before "mail_get_virtual_size" /mnt/files/dovecot-1.0-test80/src/lib-storage/mail-storage.h:428: warning: type defaults to `int' in declaration of `mail_get_virtual_size' /mnt/files/dovecot-1.0-test80/src/lib-storage/mail-storage.h:428: warning: data definition has no type or storage class /mnt/files/dovecot-1.0-test80/src/lib-storage/mail-storage.h:431: error: syntax error before "mail_get_physical_size" /mnt/files/dovecot-1.0-test80/src/lib-storage/mail-storage.h:431: warning: type defaults to `int' in declaration of `mail_get_physical_size' /mnt/files/dovecot-1.0-test80/src/lib-storage/mail-storage.h:431: warning: data definition has no type or storage class In file included from deliver.c:13: /mnt/files/dovecot-1.0-test80/src/lib/istream.h:5: error: syntax error before "uoff_t" /mnt/files/dovecot-1.0-test80/src/lib/istream.h:20: error: syntax error before "uoff_t" /mnt/files/dovecot-1.0-test80/src/lib/istream.h:25: error: syntax error before "uoff_t" /mnt/files/dovecot-1.0-test80/src/lib/istream.h:51: error: syntax error before "uoff_t" /mnt/files/dovecot-1.0-test80/src/lib/istream.h:54: error: syntax error before "uoff_t" In file included from deliver.c:15: /mnt/files/dovecot-1.0-test80/src/lib/ostream.h:7: error: syntax error before "uoff_t" /mnt/files/dovecot-1.0-test80/src/lib/ostream.h:57: error: syntax error before "uoff_t" *** Error code 1 Stop in /mnt/files/dovecot-lda-0.1/src. *** Error code 1 Stop in /mnt/files/dovecot-lda-0.1/src (line 384 of Makefile). *** Error code 1 Stop in /mnt/files/dovecot-lda-0.1 (line 283 of Makefile). *** Error code 1 Stop in /mnt/files/dovecot-lda-0.1 (line 188 of Makefile). -- Insanity in individuals is something rare - but in groups, parties, nations and epochs, it is the rule.

1 0

[Dovecot] how to migrate from one server to another?
by Bram Mertens 06 Sep '05

06 Sep '05

Hi I have purchased and installed a new PC and would like to transfer my mail (in Maildir format) to it. Are there any precautions I must take before copying the mail over? I will disable mail delivery temporarily so no new mail gets written to disk but I don't know if dovecot has to be stopped before copying/editing mail for backup or migrating purposes. Anything else I must pay attention to? TIA Bram

2 2

[Dovecot] dovecot + openwebmail
by Peter McEvoy 05 Sep '05

05 Sep '05

Hi, I'm trying to add some sanity to a badly thought out mail system that, for various reasons, cant be fixed from the bottom up at this moment in time. The system is debian sarge, exim 4.5, doing virtual domains and delivering into mboxes in /var/spool/virtual/$domain/$user , there is webmail access and this allows user to create folders in (dont shoot me!) /etc/openwebmail/users/$domain/$username/mail/ , the files in this directory appear to be mboxes in that each mail begins with a From: line, the naming of these files is completely arbitrary. Im trying to add imap access that would ideally give users access to the mail in /var , and also in the openwebmail dirs, though the latter is not essential, just desirable. All mails are owned by user mail. I've installed dovecot-imapd version 0.99.14-1, but if this doesnt have the namespace additions from version 1.0-test, I can easily install that. Reading the wiki, it seems I can achieve this with namespaces, something like namespace private { separator = / inbox = yes prefix = location = mbox:/etc/openwebmail/users/%d/%u/mail:INBOX=/var/spool/virtual/%d/%u } But, Im not quite sure where this would go in the config file, going by the example config you can just shoehorn them into the middle of the file, but I'm not 100% sure... I had been trying to use things like.. default_mail_env = mbox:/var/folders/%d/%u:INBOX=/var/spool/virtual/%d/%u:INDEX=/var/indexes/%d/%n Having created the necessary folders in /var , but I didnt have much success (the authentication part worked straight away using my passwd file), And having read more and been told about namespaces on the irc channel, it seemed like I should go that way anyway. If anyone could give me a steer in the right direction, or even tell me i'm wasting my time (tho dont bother telling me how much better maildir etc is, i know!) Thanks for your time. -- Pete

1 1

[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