- dovecot - dovecot.org

[Dovecot] RE: [dovecot-cvs] dovecot/src/lib-storage/index index-mail.c, 1.102, 1.103
by Bill Boebel 03 Jul '06

03 Jul '06

Fyi, after this patch I started seeing the error below: Jul 3 09:46:55 mail11a dovecot: IMAP(user(a)example.com): file mail-cache-lookup.c: line 270 (mail_cache_field_exists): assertion failed: (field < view->cache->fields_count) Bill On Mon, July 3, 2006 7:12 am, tss-movial(a)dovecot.org said: > Update of /var/lib/cvs/dovecot/src/lib-storage/index > In directory talvi:/tmp/cvs-serv31265/lib-storage/index > > Modified Files: > index-mail.c > Log Message: > Crashfix: Added missing date.save field. > > > > Index: index-mail.c > =================================================================== > RCS file: /var/lib/cvs/dovecot/src/lib-storage/index/index-mail.c,v > retrieving revision 1.102 > retrieving revision 1.103 > diff -u -d -r1.102 -r1.103 > --- index-mail.c 29 Jun 2006 11:08:55 -0000 1.102 > +++ index-mail.c 3 Jul 2006 11:12:15 -0000 1.103 > @@ -21,6 +21,8 @@ > sizeof(struct mail_sent_date), 0 }, > { "date.received", 0, MAIL_CACHE_FIELD_FIXED_SIZE, > sizeof(time_t), 0 }, > + { "date.save", 0, MAIL_CACHE_FIELD_FIXED_SIZE, > + sizeof(time_t), 0 }, > { "size.virtual", 0, MAIL_CACHE_FIELD_FIXED_SIZE, > sizeof(uoff_t), 0 }, > { "size.physical", 0, MAIL_CACHE_FIELD_FIXED_SIZE, > >

2 1

[Dovecot] deliver roadmap
by Jorge Salamero Sanz 03 Jul '06

03 Jul '06

hi all, what is the roadmap to the dovecot deliver in 1.0 ? will be dovecot 1.0 released with the current no-filtering, no-vacation and no-quota deliver ? will include the dovecot-sieve which has these features ? thanks for your answers.

3 2

[Dovecot] Re: Error compiling on Solaris 10
by Joseph Tam 03 Jul '06

03 Jul '06

On Sun, 2 Jul 2006 Dirk Essl wrote: > fiction:/tmp# gcc test.c -o test > In file included from /usr/include/sys/signal.h:34, > from /usr/include/signal.h:26, > from test.c:2: > ... You get this error if you use a Solaris9 version of gcc rather than Solaris 10 (header incompatibility). What do you get when you do gcc -v Joseph Tam <tam(a)math.ubc.ca>

1 0

[Dovecot] User Mailbox Backups
by Fintec 03 Jul '06

03 Jul '06

I realise it is very easy server-side but we have some Outlook users who are use to creating PST backups of their mail. What is a good open source alternative to the MS PST file? Does it just come down to what the Mail client supports? Keen to hear recommendations and thoughts on the topic... Gavin

1 0

[Dovecot] rc1: Questions about ssl-build-param!!??
by Jeff A. Earickson 02 Jul '06

02 Jul '06

Timo, My setup: Solaris 9, 1.0rc1, built like so: CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include \ LDFLAGS=-L/opt/openssl/lib ./configure --prefix=/opt/dovecot.1.0rc1 \ --with-ssl=openssl --with-ssldir=/opt/openssl/ssl \ --with-sql-drivers=no --disable-ipv6 using gcc 4.1.0. Protocols are imap and imaps. My system paniced and crashed in the middle of the night, and after it came up the ssl-parameters.dat file was messed up. >From syslog: child 1965 (login) returned error 89 imap-login: Can't open SSL parameter file ssl-parameters.dat: Permission denied Nobody was getting their email via imap. So I removed the directories /opt/dovecot/var and /var/run/dovecot to get dovecot to rebuild the ssl-parameters.dat file. Questions: 1) Why on Earth does ssl-build-param take so long??!! (> 12 minutes on my E220R) What is it doing? How to speed this process up, and/or tune it? 2) Where does ssl-parameters.dat get written to? I found one copy in the /opt/dovecot/var/lib/dovecot directory, and one copy in /var/run/dovecot/login. Which copy gets used? 3) What are the permissions supposed to be for ssl-parameters.dat? The copy in /var/run was chown root:other and chmod 640. I could not get rid of the syslog "permission denied" until I made it chmod 644. 4) Likewise the directories /opt/dovecot/var and below get created chown root:other and chmod 750, with ssl-parameters.dat chmod 640. What should these perms be? Jeff Earickson Colby College

2 1

[Dovecot] writing a plugin for LDA to chain Unix pipes
by martin f krafft 02 Jul '06

02 Jul '06

Hi, I've spent some part of the last week on trying to figure out whether dovecot LDA meets our requirements for a new mail server infrastructure (the IMAP and POP servers, as well as the SASL backend certainly do; thanks a lot!). The one thing that's holding me back is that we need per-user integration of SpamAssassin and some other, custom content filters, all of which are implemented as Unix pipe filters. My conclusion is that since dovecot LDA cannot yet integrate such filters in the delivery chain, but it supports plugins, that such a plugin must be written. Conceptually, it's very simple: a configuration file option specifying the Unix pipe, and a plugin that does the proper popen() (or whatever is to be used these days) call, checking for errors and doing the right thing. Unfortunately, I do not have much time at my hands -- basically it all boils down to Sunday evening and a little bit of Monday, and then it's got to be done. My C is rusty, but I do have a lot of experience with it, so I am confident... ... but what would really help is if someone who knows the internals of Dovecot would give me a starting point, or even some more information. How do I conceive to write such a plugin? I could not find the information online, and I'd rather not reverse engineer existing plugins, for that approach usually leads to ugly and hence unstable/insecure/unusable code. Any feedback is thus warmly appreciated! Also, if someone is online on IRC on Sunday and Monday and wouldn't mind if I asked a question now and then, please let me know. It goes without saying that I will happily submit my plugin (once its tested) to Dovecot upstream under the Artistic Licence, or if that doesn't work, another licence of your choosing. Thanks, -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck spamtraps: madduck.bogus(a)madduck.net "common sense is the collection of prejudices acquired by age eighteen." -- albert einstein

4 8

[Dovecot] Error compiling on Solaris 10
by Dirk Essl 02 Jul '06

02 Jul '06

Hi, I'm trying to compile dovecot 1.0rc1 on a V250, Solaris 10 installed. -- configure: CPPFLAGS=-I/usr/local/ssl/include LDFLAGS='-L/usr/local/ssl/lib -R/usr/local/ssl/lib' ./configure --with-ssl=openssl --with-file-offset-size=32 -- gcc Version 3.3.2 from Sunfreeware Error Message: # make make all-recursive Making all in src Making all in lib if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/ssl/include -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -MT file-dotlock.o -MD -MP -MF ".deps/file-dotlock.Tpo" -c -o file-dotlock.o file-dotlock.c; \ then mv -f ".deps/file-dotlock.Tpo" ".deps/file-dotlock.Po"; else rm -f ".deps/file-dotlock.Tpo"; exit 1; fi In file included from /usr/include/sys/signal.h:34, from /usr/include/signal.h:26, from file-dotlock.c:13: /usr/include/sys/siginfo.h:259: error: parse error before "ctid_t" /usr/include/sys/siginfo.h:292: error: parse error before '}' token /usr/include/sys/siginfo.h:294: error: parse error before '}' token /usr/include/sys/siginfo.h:390: error: parse error before "ctid_t" /usr/include/sys/siginfo.h:392: error: conflicting types for `__proc' /usr/include/sys/siginfo.h:261: error: previous declaration of `__proc' /usr/include/sys/siginfo.h:398: error: conflicting types for `__fault' /usr/include/sys/siginfo.h:267: error: previous declaration of `__fault' /usr/include/sys/siginfo.h:404: error: conflicting types for `__file' /usr/include/sys/siginfo.h:273: error: previous declaration of `__file' /usr/include/sys/siginfo.h:420: error: conflicting types for `__prof' /usr/include/sys/siginfo.h:287: error: previous declaration of `__prof' /usr/include/sys/siginfo.h:424: error: conflicting types for `__rctl' /usr/include/sys/siginfo.h:291: error: previous declaration of `__rctl' /usr/include/sys/siginfo.h:426: error: parse error before '}' token /usr/include/sys/siginfo.h:428: error: parse error before '}' token /usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t" /usr/include/sys/siginfo.h:437: error: parse error before '}' token In file included from /usr/include/signal.h:26, from file-dotlock.c:13: /usr/include/sys/signal.h:85: error: parse error before "siginfo_t" In file included from file-dotlock.c:13: /usr/include/signal.h:111: error: parse error before "siginfo_t" /usr/include/signal.h:113: error: parse error before "siginfo_t" *** Error code 1 make: Fatal error: Command failed for target `file-dotlock.o' Current working directory /tmp/dovecot-1.0.beta8/src/lib *** Error code 1 The following command caused the error: set fnord $MAKEFLAGS; amf=$2; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='lib lib-dict lib-sql lib-ntlm lib-settings lib-charset lib-mail lib-imap lib-index lib-storage lib-auth auth dict master login-common imap-login imap pop3-login pop3 util plugins'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || case "$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /tmp/dovecot-1.0.beta8/src *** Error code 1 The following command caused the error: set fnord $MAKEFLAGS; amf=$2; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='src doc'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || case "$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /tmp/dovecot-1.0.beta8 *** Error code 1 make: Fatal error: Command failed for target `all' -- Can anybody halp, please? TIA dirk

3 3

[Dovecot] 1.0.rc1 released
by Timo Sirainen 02 Jul '06

02 Jul '06

I think the code is now stable enough to be called the first release candidate. Please report any bugs, new and old. The filesystem quota numbers should be correct now? http://dovecot.org/releases/dovecot-1.0.rc1.tar.gz http://dovecot.org/releases/dovecot-1.0.rc1.tar.gz.sig * PAM: If user's password is expired, give "Password expired" error message to the user. Now actually working thanks to Vaidas Pilkauskas * Relicensed dovecot-auth, lib-sql and lib-ntlm to MIT license. See COPYING file for more information. * Abuse prevention: When creating a mailbox, limit the number of hierarchies (up to 20) and the length of the mailbox name within a hierarchy (up to 200 characters). * mbox: If saved mail doesn't end with LF, add it ourself so that the mails always have one empty line before the next From-line. + Added --with-statedir configure option which defaults to $localstatedir/lib/dovecot. ssl-parameters.dat is permanently stored in that directory and is copied to login_dirs from there. + IMAP: Support SASL-IR extension (SASL initial response) + Support initial SASL response with LOGIN mechanism. Patch by Anders Karlsson + Added PLAIN-MD4 password scheme. Patch by Andrey Panin. + Added support for XFS disk quotas. Patch by Pawel Jarosz + If another process deletes the opened mailbox, try to handle it without writing errors to log file. Handles the most common cases. + Added TLS support for LDAP if the library supports it. - SEARCH command was more or less broken with OR and NOT conditions - Dovecot corrupted mbox files which had CR+LF linefeeds in headers - MySQL code could have crashed while escaping strings - MD4 code with NTLM authentication was broken with 64bit systems. Patch by Andrey Panin - Plugin loading was broken in some OSes (eg. FreeBSD) - Several fixes to handling empty values in configuration file - Several fixes to dictionary quota backend and dict server. Also changed how they're configured. - deliver: Fixed plugin handling settings - mbox_min_index_size handling was somewhat broken - passdb passwd-file: extra_args field wasn't read unless the file was also used as userdb.

5 7

[Dovecot] SSL proxy rewrite
by Timo Sirainen 02 Jul '06

02 Jul '06

Last time I committed my SSL proxy rewrite people complained that it got broken. Now that I'm finally trying to fix it, it seems to work perfectly with me. Both downloading lots of messages and saving lots of messages works fine. I added SSL alerts and something else to be logged now with verbose_ssl=yes. With that enabled, could you people try if the rewritten code works with you, and if not, what do the logs say? To test it you'll need the latest CVS code or the latest nightly snapshot and this patch: http://dovecot.org/patches/ssl-rewrite.diff

1 2

[Dovecot] Secure connection from "localhost" in jails
by Dirk Engling 02 Jul '06

02 Jul '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear dovecot developers, first: thanks for this really cool imapd, on my server it serves some hundred domains, all in all some thousand users, some having hundred thousand mails in their Maildirs (their spam boxes mostly). Since I put this installation in an FreeBSD geli encrypted disc image I had no choice but to choose an imapd with clever indexes - dovecot was perfect. However, since I reconfigured the disc image to work as a FreeBSD jail, I had some trouble with my web mail solution. Squirrelmail does not work with imaps (or at least not smoothly, out of the box, or whatever) and I didn't like to hack php to support SSL. Plus: there is no point in using ssl for a local connection. In a FreeBSD jail a sockets source address is always rewritten to the jails address, so squirrelmail opening a connection to dovecot will not come from 127.0.0.1 but from the same (jails) address, dovecot listens to. Still, dovecot only considers 'localhost' addresses as secure and allows LOGIN or PLAIN auth. With the little patch below dovecot allows clients from the jail to authenticate via LOGIN, when they connect from the IP it accepts connections at. Something similar is lurking around in pop3 auth code, I am sure, you get the point. Regards erdgeist ======== 8< ======== 8< ======== 8< ======== 8< ======== 8< ======== 8< dovecot-1.0.rc1/src/imap-login 18:59:44 #> diff -u client.c* - --- client.c Thu Jun 29 18:59:39 2006 +++ client.c_new Thu Jun 29 18:59:19 2006 @@ -411,7 +411,7 @@ const struct ip_addr *ip) { struct imap_client *client; - - const char *addr; + const char *addr, *local_addr; if (max_logging_users > CLIENT_DESTROY_OLDEST_COUNT && hash_size(clients) >= max_logging_users) { @@ -429,8 +429,10 @@ client->common.tls = ssl; addr = net_ip2addr(ip); + local_addr = net_ip2addr(local_ip); client->common.secured = ssl || (IPADDR_IS_V4(ip) && strncmp(addr, "127.", 4) == 0) || + (IPADDR_IS_V4(ip) && strncmp(addr, local_addr, strlen(local_addr)) == 0) || (IPADDR_IS_V6(ip) && (strcmp(addr, "::1") == 0 || strncmp(addr, "::ffff:127.", 11) == 0)); -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFEpAu4ImmQdUyYEgkRAnC8AJ9W3L5XwjdTuLvGfUwmIjEfyq8sAQCdErPc v6JW46e9dfYBsKzAWprg2zw= =/IWt -----END PGP SIGNATURE-----

3 4