Re: [Dovecot] Anyone successfully setup Continous Backup of mailboxes using rsync ?
On Fri, Jan 29, 2010 at 09:59:22AM +0200, Timo Sirainen wrote: If you didn't give --delete parameter to rsync, there could be duplicates, yes. Dovecot just logs about them and gives new UIDs to them, so you'll end up having duplicate mails. I suppose some day I should just change it to log a warning, but delete if the files are otherwise identical. Would this be easy to change? It solves this problem, although perhaps not in the most efficient way... Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] Anyone successfully setup Continous Backup of mailboxes using rsync ?
On Fri, Jan 29, 2010 at 10:21:39AM +0500, CoolAtt NNA wrote: Hi Alex, I mirror the mailboxes as follows: rsync -avt --log-file=$log_file /home/vmail/ 10.0.0.x:/home/vmail I run it in a script for e,g every 1 min. If running this from cron every minute, make sure to use a lockfile or something to make sure you don't end up with multiple rsync jobs running at the same time... Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] maildir/cur/ - file names
On Wed, Jan 27, 2010 at 02:45:09PM +0500, CoolAtt NNA wrote: Hi All. I want to know how filenames are changed by dovecot e,g more details on how it renames the files when a mail is read. For read mails i found that it appends an S. 1264579250.P22376Q0M765148.ecs,S=1161:2 1264579250.P22376Q0M765148.ecs,S=1161:2,S Want to know if other modifications done in file names in INBOX in SENT (maildir/.Sent/cur) Just read the specification, don't reverse engineer it. :-) Original spec from qmail: http://cr.yp.to/proto/maildir.html Dovecot implementation notes: http://wiki.dovecot.org/MailboxFormat/Maildir Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] Same filenames on different servers?
On Mon, Jan 11, 2010 at 02:18:07PM +0200, Alexander Chekalin wrote: Oh, I finally find out the problem. If Dovecot see in the IMAP mailbox two message files named equally (say in cur/ and new/ dirs) it renames one of them into new name dispute this is the same message. I'm not sure if this is intended behaviour. It is quite easy to see such situation when doing periodical rsync (SMTP put message to new/ dir, then rsync copy it to second server, then message on the first server move to cur/, and second rsync results in two files on second server). It there any workaround? You could use imapsync instead: http://www.linux-france.org/prj/imapsync/ It synchronizes two IMAP mailboxes (including message flags etc) independent of the underlying implementation. Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] First time Dovecot user, really impressed so far. What is best IMAP enabled webmail package to go with Dovecot?
On Tue, Jan 05, 2010 at 09:15:54AM -0200, Eduardo M KALINOWSKI wrote: On Ter, 05 Jan 2010, Stan Hoeppner wrote: I've looked a little at both now and am still reading. One thing I don't like is that I'm seeing requirements a SQL server. That adds unnecessary complexity to the system and I'd rather avoid it if possible. IIRC, one of the reasons I chose Squirrelmail a few years ago was that it's requirements were pretty simple, and that it didn't require a database backend for anything. IMP/Horde can work with a sqlite database, which is just a file and requires no running server. Same for Roundcube, btw. Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] DELE before QUIT
On Tue, Dec 08, 2009 at 10:53:01AM -0500, Davy Leon wrote: Hi Thanks for the reply. Definitelly IMAP is not a solution for me. All the emails for my user's domain are stored in a single account on my ISP. I have to fetch them and distribute them locally. In every fetch there are several emails and every time the link fails I have to start over again for the forst message wich I already downloaded. Tha's a problem. Any other solution? It's a problem of your POP client (although most clients work like this). According to the POP3 spec, an entire session is essentially a single transaction. So a client that downloaded 3 mails before the connection breaks down (even if it issued DELE), shouldn't store those messages but discard them, and download them again in the next session. A (ugly) workaround for flaky network connections is to setup a new session after every RETR/DELE pair. Beyond that, it's really a protocol problem... Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] IMAP folders' codepages problem ?
On Sat, Nov 14, 2009 at 03:22:58PM +0100, mich...@euroinfissi.eu wrote: Hi! I probably have a problem with the imap folders codepages. I use polish email clients such as MS Outlook and Windows Mail. The clients try to create folders like Wiadomości-Śmieci but Dovecot creates WiadomoAVs-ci-AVs-mieci No, this is exactly what the client passes to Dovecot. The IMAP standard allows only plain ASCII in foldernames and therefor uses a modified UTF-7 encoding for non-ASCII characters. See section 5.1.3 of RFC 3501. Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] UTF-8 mailbox names in filesystem
On Mon, Nov 09, 2009 at 09:11:23PM -0500, Timo Sirainen wrote: Currently mailbox names are stored in IMAP's modified-UTF-7 format in filesystem. I was wondering about changing this in v2.0. The default would still be to use mUTF-7 in filesystem, but just adding :UTF8 or something to mail_location could enable UTF-8. Any thoughts? Could this be dangerous somehow? UTF-8 enables a lot of weird characters, perhaps no one really wants to see them on filesystem since there's no way to type the characters? But for small systems this probably isn't a problem. What's the advantage? Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] testing needed
On Mon, Oct 19, 2009 at 05:55:20PM -0400, Timo Sirainen wrote: Can someone find an OS where the attached program doesn't work? It should print success. So far tested for success: Linux 2.6, Solaris 10, FreeBSD 7.2, OpenBSD 4.2. Success on NetBSD 5.0_STABLE on amd64 (64-bit). Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] Two passwords: One for Dovecot IMAP and One for Dovecot SASL? Is it possible?
On Wed, Oct 14, 2009 at 03:18:12PM -0400, Art Gray - Razorpoint wrote: Greetings, Can Dovecot can handle separate authentication for receiving mail (IMAPS) and sending mail (SMTPS)? In the past, we used Dovecot IMAP for the receiving part and Cyrus SASL for the sending part. This allowed us to use two passwords with mail. Cyrus has grown too old and isn't useful anymore. Can Dovecot give us this functionality: two passwords, one for IMAP authentication and one for SASL authentication? If so, could you point me in the right direction to get this working? If your authentication method supports multiple passwords (eg. LDAP with authentication binding) AND you allow your users to use either password for either server (ie. you're just providing backwards compatibility, not enforcing to use different passwords), it could work just like that. Otherwise I think you'd have to setup separate dovecot instances. Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] v2.0 configuration paths
On Mon, Aug 31, 2009 at 01:28:50PM -0400, Timo Sirainen wrote: # main config, basically says !include conf.d/*.conf /etc/dovecot/dovecot.conf # the actual configs /etc/dovecot/conf.d/*.conf Why in another subdir? Why not everything in /etc/dovecot? Also, conf.d sounds so Linuxy. :-) Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages! pgpWWdOzwMxoh.pgp Description: PGP signature
Re: [Dovecot] Are host names a secret?
On Thu, Jul 16, 2009 at 04:30:00PM -0400, Timo Sirainen wrote: Some time ago I added the ability for IMAP clients to fetch messages' GUIDs using FETCH X-GUID command. Because of a bug it wasn't working in 1.2.0 or 1.2.1, but I've fixed it now. But now I'm starting to wonder: With Maildirs the GUIDs are the maildir base filenames, which contain host names. Is it a bad idea to expose them to users? Why? Users can see hostnames in eg. Received headers as well? Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages! pgpkoCQJN7dXO.pgp Description: PGP signature
Re: [Dovecot] Sieve problem: No vacation message when mail is addressed to an alias of the mailbox.
On Mon, Jul 13, 2009 at 02:03:38PM +0200, Steffen Kaiser wrote: You have to enumerate all addresses in the :address tag of vacation. It's actually a real pain here. It's a feature, not a bug. This is to avoid auto-replies on messages not addressed directly to you (eg. sent via mailing lists). Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] Sieve problem: No vacation message when mail is addressed to an alias of the mailbox.
On Mon, Jul 13, 2009 at 02:21:39PM +0200, Steffen Kaiser wrote: This is to avoid auto-replies on messages not addressed directly to you (eg. sent via mailing lists). a) Mailing lists must set Precedence: bulk b) Many lists address you in To or CC. c) Why shall no vacation to be sent, if I'm BCC'ed ? d) You cannot enumerate all addresses for some accounts. It's RFC recommended practice, see RFC 3834: - Personal and Group responses whose purpose is to notify the sender of a message of a temporary absence of the recipient (e.g., vacation and out of the office notices) SHOULD NOT be issued unless a valid address for the recipient is explicitly included in a recipient (e.g., To, Cc, Bcc, Resent-To, Resent-Cc, or Resent- Bcc) field of the subject message. Since a recipient may have multiple addresses forwarded to the same mailbox, recipients SHOULD be able to specify a set of addresses to the responder which it will recognize as valid for that recipient. Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] Sieve problem: No vacation message when mail is addressed to an alias of the mailbox.
On Mon, Jul 13, 2009 at 03:42:31PM +0200, Steffen Kaiser wrote: On Mon, 13 Jul 2009, Geert Hendrickx wrote: It's RFC recommended practice, see RFC 3834: I know. Just for this I re-calcalculated my email address stats. There is a SHOULD two times. I have replied on this somewhen in the past already. My email domain can be written in 488 ways plus some wicked others. Now add the 87 aliases I have, minus some list-specific plus some others. This is not the case for the general user, so in general the advice is useful, and avoids a lot of useles backscatter and mailing list pollution. Yes I am able to specify a set of addresses to the responder which it will recognize as valid for that recipient. Yes, you can call this a mis-configuration, it won't bug me. Feel free to hack away the limitation in the code. You're not braking any laws by doing so. ;-) Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] Sieve/ManageSieve integration into pkgsrc
On Thu, Jun 25, 2009 at 03:43:09PM +0200, Edgar Fuß wrote: I'm integrating Sieve (the new one) and ManageSieve into wip/dovecot. Currently, this works as dovecot options because dovecot must be built before sieve can be configured and sieve must be built before managesieve can be configured/built. Now, the question arose what the long-term solution (in pkgsrc) should be. To my understanding, with dovecot 2.0, ManageSieve will no longer need to patch dovecot. But what about both Sieve and ManageSieve depending on doevcot sources in order to build (or on libraries dovecot only builds internally)? The preferred way (for pkgsrc) would be if both Sieve and ManageSieve could be built as stand-alone packages and not needing a dovecot source tree to build. What's the long-term plan for Sieve/ManageSieve in this respect? The pkgsrc infrastructure (intentionally) doesn't like a package depending on anothers package working directory in order to build. So with these cross-dependencies, the only pkgsrc ways to go would be either to build it all as one package with options (that's what I currently do) or extract, patch, configure and build dovecot inside a sieve package. See also http://www.dovecot.org/list/dovecot/2007-August/024504.html which enabled pkgsrc to build the dovecot-sieve plugin (the old one) against an installed dovecot instance with only liblib.a installed additionally. Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions
On Sun, Feb 22, 2009 at 11:58:01PM -0800, Linux Advocate wrote: Guys , 1. What is the benefit of using Dovecot' LDA as compared to postfix's LDA? Will there be better performance? With Dovecot's LDA, mailbox indexes are updated at mail delivery time instead of (only) at pop3/imap login time, which should result in faster logins when you have a lot of new mail. And Dovecot's LDA has extra functionality, most notably Sieve support. But if you don't use all that, Postfix' LDA works fine too. Geert -- Geert Hendrickx -=- g...@telenet.be -=- PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [Dovecot] MySQL as a storage only.?
On Wed, Dec 10, 2008 at 02:24:05PM -0600, Romer Ventura wrote: Hello, I was wondering is I could use MySQL as storage only..? Meaning that no user information, other than the obvious email address associated with an specific email so that each email can be showed to the right user, will be stored in a MySQL database instead of /home/vmail/DOMAIN/user Would I get any advantages.? Would it be better, faster? You may want to have a look at dbmail for this: http://www.dbmail.org/ AFAIK it's currently not in scope for Dovecot. Geert
Re: [Dovecot] Password authentication and character set
On Wed, Nov 19, 2008 at 08:44:21AM +0200, Fredrik Grönqvist wrote:
Yes, I agree that it should be in UTF-8. My specific problem is that about
80% (a rough estimate) of our users are on either Windows or webmail. Those
having passwords containing umlauts etc can log on, using their current
client, if the passwords are kept ISO-8859-1 encoded instead of UTF-8.
As Timo pointed out, the options to fix this on the server side are
currently quite limited, so it seems I have to stick to the lowest common
denominator in our password policy.
If you only have to support two or three different charsets, I think you could
use a clever MySQL passdb query to match either of them.
Have a look at http://wiki.dovecot.org/AuthDatabase/SQL under Password
verification by SQL server, and expand the password match to something like
(passwd = PASSWORD('%w') OR passwd = PASSWORD(CONVERT(_latin1'%w' USING utf8)))
assuming you store the passwords as UTF-8 and assume the input is either UTF-8
or ISO-8859-1.
Geert
Re: [Dovecot] Password authentication and character set
On Wed, Nov 19, 2008 at 01:54:48PM +0200, Fredrik Grönqvist wrote: Thanks for the info, a setup like this is what I opted for eventually. I added a note to that wiki page that the query also needs to return the nopassword -field for Dovecot 1.1+ to accept the NULL password: Ok, good catch (I hadn't actually tested the example). In case someone else is looking for info about this, this workaround works for DB backed accounts, as you mention, but will probably not work with an LDAP (or other) backend. Right, it's just a hack that fits your particular setup. :-) For a proper solution the IMAP specification would have to be updated to allow non-ASCII characters in logins/passwords, and apparantly they _are_ discussing that. But even if the IMAP protocol gets updated to allow it, this would also impact eg. POP3 and SMTP authentication which in many setups use the same passwords. And of course all IMAP (and other) client software (including webmails etc) would have to be adapted, too. Geert
Re: [Dovecot] Password authentication and character set
On Tue, Nov 18, 2008 at 05:51:05PM +0200, Timo Sirainen wrote: On Nov 18, 2008, at 5:32 PM, Fredrik Grönqvist wrote: Is there a setting that forces the authentication daemon to convert the provided password to a specific charset before the comparison takes place, or how should one handle this? Dovecot doesn't know the character set that the client is using, so it can't do charset conversion reliably. So the possibilities would be: a) UTF-8 vs. another 8bit charset can be detected pretty well by checking if the input string is valid UTF-8 or not. So there could be a setting to specify the fallback charset. b) Just brute force through all the configured charsets and test the password against all of them. I don't really like either solution and I don't have much interest in coding those myself. Feel free to do it yourself though, I might even accept patches. :) It seems like this is a limitation in the IMAP protocol. From RFC 3501: Characters are 7-bit US-ASCII unless otherwise specified. Other character sets are indicated using a CHARSET, as described in [MIME-IMT] and defined in [CHARSET]. CHARSETs have important additional semantics in addition to defining character set; refer to these documents for more detail. The SEARCH command has this optional CHARSET flag (to search in messages in non-ascii charsets) but it seems like the LOGIN command should accept only 7-bit ASCII arguments... Geert
Re: [Dovecot] Password authentication and character set
On Tue, Nov 18, 2008 at 07:03:04PM +0200, Timo Sirainen wrote: On Tue, 2008-11-18 at 17:26 +0100, Geert Hendrickx wrote: It seems like this is a limitation in the IMAP protocol. From RFC 3501: I remember reading something about using UTF-8 and stringprep in authentication strings, probably some SASL spec or something. Dovecot should implement it some day.. But that won't help in any way if the client doesn't send the password as UTF-8. There has recently been a discussion about this on the imap-protocol mailing list: http://mailman2.u.washington.edu/pipermail/imap-protocol/2008-February/thread.html (they talk about LOGIN as well) Geert
Re: [Dovecot] Password authentication and character set
On Tue, Nov 18, 2008 at 10:00:00PM +0200, Fredrik Grönqvist wrote: Yes, I see. So in light of this and the conversation on the imap-protocol -list http://mailman2.u.washington.edu/pipermail/imap-protocol/2008-February/000822.html our current options seem to boil down to having the passwords ISO-8859-1 encoded (given the demographics of our users). Those using operating systems with native UTF-8 clients have to use passwords containing only 7-bit characters. Actually I would do it the other way around. You can't really explain to your UTF-8 using users you should use that older client instead of this newer one to make your login work. And some day you'll have to switch to UTF-8 anyway. I didn't realise the specifications were so flexible on this password issue. s/flexible/vague/ :-) The consensus on the imap-protocol list, and particularly the message you refer to, seems to be we should replace ASCII with UTF-8 in the spec. Geert
Re: [Dovecot] v1.2.alpha1 released
On Fri, Sep 05, 2008 at 08:49:22PM +0300, Timo Sirainen wrote: http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz.sig This is the only v1.2.alpha announcement I'm going to send to dovecot-news list. Next announcement will be for either v1.2.beta1 or v1.2.rc1. FYI: pkgsrc users can find the 1.2 alpha series in pkgsrc-wip/dovecot-devel. dovecot-sieve can be used from pkgsrc/mail/dovecot-sieve since there is no sieve 1.2 plugin (the 1.1 plugin works with dovecot 1.2). Geert pgpqLgg9MnFAD.pgp Description: PGP signature
Re: [Dovecot] Webmail app ... again.
On Wed, Aug 13, 2008 at 04:37:11PM -0400, Timo Sirainen wrote: One thing that would be nice, that pretty much no webmail does, is to keep a stateful connection open all the time (or at least some of the time) instead of creating tons of short-lived connections that ask the same stuff over and over again. With a stateful connection you could basically run IDLE and wait for changes there instead of asking all the time is there new mail? is there new mail now? what about now?. AlphaMail has this: http://alphamail.sourceforge.net/ It's a webmail written in Perl that uses a C++ middleware which keeps a persistent connection to the backend IMAP server. But I'm afraid the project is dead... Geert pgpC97Qt1PfMU.pgp Description: PGP signature
Re: [Dovecot] 1.0.14 - 1.1.1: dovecot-uidlist errors
On Tue, Jun 24, 2008 at 07:36:44PM +0300, Timo Sirainen wrote: On Jun 24, 2008, at 7:31 PM, Amitai Schlair wrote: Jun 24 12:22:13 chicken-ac dovecot: Panic: IMAP(schmonz): file maildir-uidlist.c: line 1217 (maildir_uidlist_sync_update): assertion failed: (ctx-first_unwritten_pos != (unsigned int)-1) Still shouldn't crash even if the fsync fails, I'll see about fixing that. Apart from the design issue of fsync'ing read-only directory file handles, have you been able to look into fixing the assert panic? :-) A workaround for now would be to se fsync_disable=yes Personally, I don't like this since (I assume) it disables fsync'ing of tmp/ files (mails uploaded via imap) as well? Geert pgpnF43DG52Ce.pgp Description: PGP signature
Re: [Dovecot] dovecot as gmail imap proxy
On Tue, Jun 17, 2008 at 03:37:30PM -0700, Peter Hessler wrote: I 3 mutt. Easy enough, but lots of power is available. Yes, mutt is great! :-) Btw, you can use mutt with dovecot without running dovecot as a daemon/server, by putting this in your .muttrc: set tunnel=MAIL=/home/geert/mbox /usr/pkg/libexec/dovecot/imap (adapt paths for your own system) This way mutt will talk to the dovecot imap binary via stdin/stdout. This will also work over ssh. This way you don't need to run dovecot as a server and you still benefit from eg. the cache etc. Geert
Re: [Dovecot] FreeBSD port for 1.1, some bits more...
FWIW, pkgsrc users can find an up-to-date dovecot 1.1 package in pkgsrc-wip: http://pkgsrc.se/wip/dovecot http://pkgsrc.se/wip/dovecot-sieve Geert On Tue, Jun 03, 2008 at 10:41:42PM +0200, Geoffroy DESVERNAY wrote: I did (re-)compile dovecot (1.1rc8) today, with managesieve (0.10.2) and sieve-plugin (1.1.5). I did modify the existing dovecot-devel port, adding managesieve patch as an OPTION, and I added a 'dovecot-managesieve-devel' port, and a 'dovecot-sieve-devel' one to be complete... Not sure everything is very complete, but at least it works for me=E2=84=A2= , and if it can help anybody to save some time... The tree ports are there: http://dgeo.perso.ec-marseille.fr/dovecot Not sure I used the very good way of building FreeBSD ports... Cheers, Geoffroy --=20 ___ / Geoffroy DESVERNAY |\ /\`Service info`| Tel: (+33|0)4 91 05 45 24 /\ \/ Ecole Centrale de Marseille | Fax: (+33|0)4 91 05 45 98 \/ \ (ex-EGIM)| Mail: dgeo ec-marseille.fr / --- pgpolUaoPayJ6.pgp Description: PGP signature
Re: [Dovecot] v1.1.rc8 released
On Tue, Jun 03, 2008 at 10:27:32AM +0200, Jost Krieger wrote: On Tue, Jun 03, 2008 at 07:11:33AM +0100, Ed W wrote: Could do, but I was trying to expand to the case that the headers were different, but the body was the same (eg I suspect that mailing list managers might deliver emails one by one (verp), but the body is not customised. Anyway, just wanted to checksum the body of the message not the whole message That could lead to slight problems, like hardlinking totally unrelated messages, e.g. empty messages. Some Headers like From:, To:, Date:, Subject: should probably be identical. Message-ID perhaps? :-) For some consistency, just removing *locally* generated trace headers before fingerprinting might lead to better results. That may still leave identical messages not hard-linked thus wasting space. Eg. if they come from MTA's that do recipient splitting, or messages that are routed via different systems. The Received headers will be different but the body generally identical. I think a better solution is what was suggested here before, ie. to keep the (unique) message headers in a Maildir-like format, containing links to (single-instance stored) message bodies in a a separate location. Geert
Re: [Dovecot] v1.1.rc6 released won't compile
On Thu, May 29, 2008 at 11:16:55PM -0400, webbie wrote: I got a compile error with rc6, rc5 works fine. Exactly the same on NetBSD: mail-index-write.c: In function `mail_index_write': mail-index-write.c:179: error: structure has no member named `st_ctim' mail-index-write.c:179: error: structure has no member named `st_ctim' *** Error code 1 Geert amd64:dovecot-1.1.rc6# uname -a FreeBSD amd64.objtech.com 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #3: Fri Apr 18 02:18:13 EDT 2008 ./configure \ --prefix=/opt1/dovecot \ --localstatedir=/var \ --without-shadow \ --without-cyrus-sasl2 \ --without-pop3d \ --without-gssapi \ --disable-ipv6 \ --disable-debug \ --with-ioloop=kqueue \ --with-ssl=openssl make [trimmed] gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-mail -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT mail-index-view-sync.o -MD -MP -MF .deps/mail-index-view-sync.Tpo -c -o mail-index-view-sync.o mail-index-view-sync.c mv -f .deps/mail-index-view-sync.Tpo .deps/mail-index-view-sync.Po gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-mail -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT mail-index-write.o -MD -MP -MF .deps/mail-index-write.Tpo -c -o mail-index-write.o mail-index-write.c mail-index-write.c: In function 'mail_index_write': mail-index-write.c:179: error: 'struct stat' has no member named 'st_ctim' mail-index-write.c:179: error: 'struct stat' has no member named 'st_ctim' *** Error code 1 Stop in /opt1/source/dovecot-1.1.rc6/src/lib-index. *** Error code 1 Stop in /opt1/source/dovecot-1.1.rc6/src. *** Error code 1 Stop in /opt1/source/dovecot-1.1.rc6. *** Error code 1 Stop in /opt1/source/dovecot-1.1.rc6.
Re: [Dovecot] v1.1.rc6 released won't compile
On Fri, May 30, 2008 at 12:01:30PM +0300, Timo Sirainen wrote: Whops, I guess I'll make a rc7 release later today for you BSD people. For now these patches help (messed up the first one): http://hg.dovecot.org/dovecot-1.1/rev/0d842b055838 http://hg.dovecot.org/dovecot-1.1/rev/5766890f1275 Confirmed (on NetBSD). Geert pgpS95nIVvafX.pgp Description: PGP signature
Re: [Dovecot] reason to switch to 1.1
On Tue, Apr 29, 2008 at 09:42:10AM +0200, Cor Bosman wrote: Actually..it's 2 NetApp 6070s. But those are not just simple servers. They are very expensive, dedicated NFS boxes each taking up a full rack doing multiple terrabytes each, connected with multiple gbit links. It's 99.99% maildir, with a very small hidden mbox legacy namespace. How large are the (individual) mailboxes you're hosting there? Geert
Re: [Dovecot] reason to switch to 1.1
On Tue, Apr 29, 2008 at 11:49:43AM +0200, Cor Bosman wrote: How large are the (individual) mailboxes you're hosting there? Most of them are max 500MB, but average use is much less. It's a little difficult to calculate because almost all POP users empty their mailbox. We did some reports a few months ago where it showed that average mailbox size for POP users is less than 5MB, while average mailbox usage for IMAP was over 50MB. Ok, so you're probably not facing any filesystem bottlenecks w.r.t. number of files in a Maildir folder? Geert
Re: [Dovecot] FreeBSD port: port's patch for 1.1rc3
On Tue, Apr 01, 2008 at 12:00:30PM -0400, Adam McDougall wrote: Geoffroy Desvernay wrote: For those who wants testing 1.1rc3 on FreeBSD, this is a simple patch against /usr/ports/mail/dovecot. To apply: # cd /usr/ports/mail/dovecot # patch -p1 /tmp/patch_dovecot_1.0.13-1.1.rc3.diff Hope I did not forget something important... This is an adaptation of the existing port. PS: for port's maintainer: Which way will take 1.0 vs 1.1 upgrade ? a new mail/dovecot10 port or ? Hope this helps -- Geoffroy Desvernay I'm not the maintainer but I've also made a dovecot port for 1.1 as a separate port since it is still in development and may require a few config changes, I discussed that with the maintainers. I made it for work purposes and I have been keeping up with necessary changes to keep it working while I use 1.1, and intended to submit it for inclusion in the ports collection but haven't got around to it yet (I'd like to add a few compile options for new things since 1.1). Been really busy at work and haven't had time, but I guess if people show they are interested I could try to speed that up. While on the subject, I've been tracking dovecot 1.1.x beta's/rc's for NetBSD pkgsrc in pkgsrc-wip: http://pkgsrc.se/wip/dovecot Geert
Re: [Dovecot] Restrict user on IMAP or POP
On Fri, Feb 15, 2008 at 03:36:01PM +0100, Geert Hendrickx wrote: There are some clever tricks on that page to keep the LDAP/SQL database Dovecot-agnostic and putting the logic in the query. Do you know a similar trick for allow_nets; I have users stored in a PgSQL database and want to allow everyone from our local network (a combination of three CIDR blocks), and only some users from the Internet (0/0). Is it possible to do this using a simple boolean (y/n) remote column in my users table? i.e. remote=n should be mapped to allow_nets=x.y.z.0/24,a.b.c.0/24,d.e.0.0/16 and remote=y to allow_nets=0/0. If the %a (local port) variable where available in the imap service, this could be done by binding imap to two ports and using remote = true or '%a' = '143', and redirect the public port on the NAT-router to the other (non-standard) port on the server. Looks like PostgreSQL supports conditional expressions in queries which make this very easy: password_query = SELECT md5_pw AS password, CASE WHEN remote='t' THEN '0/0' ELSE 'ournetblocks' END AS allow_nets FROM imap_users WHERE email='%u' Geert
Re: [Dovecot] Restrict user on IMAP or POP
On Thu, Feb 14, 2008 at 06:17:51PM +0200, Timo Sirainen wrote: On Thu, 2008-02-14 at 11:12 -0500, Sebastien Roy wrote: Is it possible to deny a user on POP or IMAP! For example, on the primary server we use POP3 and IMAP but how I can force a user to use POP3 and be unable to authenticate on IMAP ? http://wiki.dovecot.org/Authentication/RestrictAccess There are some clever tricks on that page to keep the LDAP/SQL database Dovecot-agnostic and putting the logic in the query. Do you know a similar trick for allow_nets; I have users stored in a PgSQL database and want to allow everyone from our local network (a combination of three CIDR blocks), and only some users from the Internet (0/0). Is it possible to do this using a simple boolean (y/n) remote column in my users table? i.e. remote=n should be mapped to allow_nets=x.y.z.0/24,a.b.c.0/24,d.e.0.0/16 and remote=y to allow_nets=0/0. If the %a (local port) variable where available in the imap service, this could be done by binding imap to two ports and using remote = true or '%a' = '143', and redirect the public port on the NAT-router to the other (non-standard) port on the server. Geert
Re: [Dovecot] ldaps support in dovecot-ldap.conf?
On Fri, Feb 15, 2008 at 10:11:52AM -0600, Tim Tyler wrote: Dovecot experts, Does Dovecot support ldaps:\\ connections in dovecot-ldap.conf for ldap connections? I can get regular ldap:\\connections to work, but not ldaps:\\ connections. I have even downloaded the latest beta version of dovecot and it still doesn't work. If its not supported, will it be in the near future? Note: We are using Centos 5 and Redhat 5 systems. According to http://wiki.dovecot.org/AuthDatabase/LDAP just set tls=yes in your dovecot-ldap.conf. Geert
[Dovecot] building dovecot-sieve against installed dovecot
Hi Timo, may I request once more to consider the attached patch for dovecot 1.1, it enables the sieve plugin (incl. sievec and sieved, needed for pysieved) to be built against an installed dovecot package, if --enable-header-install additionally installs the liblib.a library in the same directory as dovecot-config. I have included this patch in the pkgsrc dovecot 1.1 package a while ago. Geert --- src/libsieve/Makefile.in.orig 2007-09-23 16:59:48.0 +0200 +++ src/libsieve/Makefile.in @@ -38,8 +38,8 @@ PRE_UNINSTALL = : POST_UNINSTALL = : build_triplet = @build@ host_triplet = @host@ [EMAIL PROTECTED]@pkglibexec_PROGRAMS = sievec$(EXEEXT) \ [EMAIL PROTECTED]@ sieved$(EXEEXT) +pkglibexec_PROGRAMS = sievec$(EXEEXT) \ + sieved$(EXEEXT) subdir = src/libsieve DIST_COMMON = README $(noinst_HEADERS) $(srcdir)/Makefile.am \ $(srcdir)/Makefile.in AUTHORS COPYING ChangeLog NEWS \ @@ -62,17 +62,21 @@ am__installdirs = $(DESTDIR)$(pkglibexe pkglibexecPROGRAMS_INSTALL = $(INSTALL_PROGRAM) PROGRAMS = $(pkglibexec_PROGRAMS) am__sievec_SOURCES_DIST = sievec.c ../map.c ../imparse.c [EMAIL PROTECTED]@am_sievec_OBJECTS = sievec.$(OBJEXT) \ [EMAIL PROTECTED]@ map.$(OBJEXT) imparse.$(OBJEXT) +am_sievec_OBJECTS = sievec.$(OBJEXT) \ + map.$(OBJEXT) imparse.$(OBJEXT) sievec_OBJECTS = $(am_sievec_OBJECTS) @[EMAIL PROTECTED] = libsieve.la \ @HAVE_DOVECOT_LIBS_TRUE@ $(dovecotdir)/src/lib/liblib.a [EMAIL PROTECTED]@sievec_DEPENDENCIES = libsieve.la \ [EMAIL PROTECTED]@ $(dovecotdir)/liblib.a am__sieved_SOURCES_DIST = sieved.c ../map.c ../imparse.c [EMAIL PROTECTED]@am_sieved_OBJECTS = sieved.$(OBJEXT) \ [EMAIL PROTECTED]@ map.$(OBJEXT) imparse.$(OBJEXT) +am_sieved_OBJECTS = sieved.$(OBJEXT) \ + map.$(OBJEXT) imparse.$(OBJEXT) sieved_OBJECTS = $(am_sieved_OBJECTS) @[EMAIL PROTECTED] = libsieve.la \ @HAVE_DOVECOT_LIBS_TRUE@ $(dovecotdir)/src/lib/liblib.a [EMAIL PROTECTED]@sieved_DEPENDENCIES = libsieve.la \ [EMAIL PROTECTED]@ $(dovecotdir)/liblib.a DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir) depcomp = $(SHELL) $(top_srcdir)/depcomp am__depfiles_maybe = depfiles @@ -267,10 +271,16 @@ noinst_HEADERS = \ @[EMAIL PROTECTED] = \ @HAVE_DOVECOT_LIBS_TRUE@ libsieve.la \ @HAVE_DOVECOT_LIBS_TRUE@ $(dovecotdir)/src/lib/liblib.a [EMAIL PROTECTED]@sievec_LDADD = \ [EMAIL PROTECTED]@ libsieve.la \ [EMAIL PROTECTED]@ $(dovecotdir)/liblib.a @[EMAIL PROTECTED] = \ @HAVE_DOVECOT_LIBS_TRUE@ libsieve.la \ @HAVE_DOVECOT_LIBS_TRUE@ $(dovecotdir)/src/lib/liblib.a [EMAIL PROTECTED]@sieved_LDADD = \ [EMAIL PROTECTED]@ libsieve.la \ [EMAIL PROTECTED]@ $(dovecotdir)/liblib.a @[EMAIL PROTECTED] = sievec.c sieved.c @[EMAIL PROTECTED] = pgpPcZc0eA2An.pgp Description: PGP signature
Re: [Dovecot] Security hole #4: Specific LDAP + auth cache configuration may mix up user logins
On Fri, Dec 21, 2007 at 12:38:12AM +0200, Timo Sirainen wrote: Somehow I doubt there are any Dovecot setups left that unknowingly have this problem, but it still counts as a security hole. The possibility to cause this problem exists in Dovecot v1.0.rc11 and later. [...] You can fix this by upgrading to v1.0.10 (to be released soon), or using this patch: http://hg.dovecot.org/dovecot-1.0/raw-rev/2cedab21cd6d Is Dovecot 1.1.x affected as well? Geert pgpiWwUkzpaye.pgp Description: PGP signature
Re: [Dovecot] Roadmap to future
On Thu, Dec 06, 2007 at 04:17:22PM +0200, Timo Sirainen wrote: Deliver / LMTP server - Currently deliver parses dovecot.conf using its own parser. This has caused all kinds of problems. v2.0's master rewrite helps with this, because deliver can then just ask the configuration from config process the same way as other processes are. Another problem is that people who use multiple user IDs have had to make deliver setuid-root. I really hate this, but currently there's no better way. Better fix for this would be to use LMTP server instead. There could be either a separate LMTP client or deliver could support LMTP protocol as well. I'm not sure which one is better. I'll weigh in 50 euro for the deliver LMTP interface. It's not much, but others may add to it. :-) Geert pgpop9nOKb96o.pgp Description: PGP signature
Re: [Dovecot] Released v1.1.beta2
On Sun, Sep 30, 2007 at 11:32:09PM +0300, Timo Sirainen wrote: http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta2.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta2.tar.gz.sig Several bug/crashfixes. deliver now supports -a parameter (see http://wiki.dovecot.org/LDA) which allows Sieve plugin v1.1.2 to use envelope :detail to checks. I also did one more API change for mailbox_transaction_commit*(). There's probably something still wrong with SORT command, but other than that I've fixed everything that's been reported. This builds fine on NetBSD (with GNU make as well as with BSD make). But I have a segfault with deliver+sieve. I took the Sieve vacation example from the Wiki and removed the fileinto/stop part so it reaches vacation: require [fileinto, vacation]; vacation # Reply at most once a day to a same sender :days 1 :subject Out of office reply # List of allowed recipient addresses from auto reply should be sent. :addresses [[EMAIL PROTECTED], [EMAIL PROTECTED]] I'm out of office, please contact Joan Doe instead. Best regards John Doe; deliver then segfaults with any message I feed it: (gdb) bt #0 0xbdb0d92d in shouldRespond (m=0xbfbfe6d0, interp=0x80f0580, numaddresses=2, bc=0x80f5f00, i=7, from=0xbfbfc17c, to=0xbfbfc180) at bc_eval.c:236 #1 0xbdb0fcc9 in sieve_eval_bc (exe=0x80ec2e0, is_incl=0, i=0x80f0580, body_cache=0x0, sc=0xbfbfe730, m=0xbfbfe6d0, imapflags=0xbfbfd688, actions=0x80f6500, notify_list=0x80e1760, errmsg=0xbfbfd684) at bc_eval.c:1243 #2 0xbdb1505c in sieve_execute_bytecode (exe=0x80ec2e0, interp=0x80f0580, script_context=0xbfbfe730, message_context=0xbfbfe6d0) at script.c:868 #3 0xbdb04996 in cmu_sieve_run (namespaces=0x80ef428, storage_r=0xbfbfe7fc, mail=0x8101428, script_path=0x80e2e00 /home/geert/.dovecot.sieve, username=0x80e2040 geert, mailbox=0x80d2905 INBOX) at sieve-cmu.c:966 #4 0xbdb02520 in cmusieve_deliver_mail (namespaces=0x80ef428, storage_r=0xbfbfe7fc, mail=0x8101428, username=0x80e2040 geert, mailbox=0x80d2905 INBOX) at cmusieve-plugin.c:76 #5 0x080595f1 in main () #6 0x080573cd in ___start () Geert pgpvV0M0YZVLI.pgp Description: PGP signature
Re: [Dovecot] Released v1.1.beta2
On Mon, Oct 01, 2007 at 01:40:58AM +0300, Timo Sirainen wrote: On Sun, 2007-09-30 at 23:24 +0200, Geert Hendrickx wrote: But I have a segfault with deliver+sieve. I took the Sieve vacation example from the Wiki and removed the fileinto/stop part so it reaches vacation: With Sieve plugin 1.1.2? I thought I fixed this crash for it.. Nope, 1.1.2 fixes it, thanks! Why don't you announce new Sieve plugin releases, btw? :-) Geert pgpMmg9M1F9HS.pgp Description: PGP signature
Re: [Dovecot] v1.1.beta1 released
On Sun, Sep 23, 2007 at 04:55:40PM +0300, Timo Sirainen wrote: http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz.sig 1.1beta1 builds and runs fine on NetBSD, and I've added dovecot 1.1beta1 and dovecot-sieve 1.1.0 packages to pkgsrc's work in progress repository. I still have to use GNU make to build it though because there's a Wiki file with brackets in its filename: doc/wiki/Migration.Vm(2d)pop3d.txt. Geert
Re: [Dovecot] v1.1.alpha6 released
On Mon, Sep 17, 2007 at 03:58:03PM +0300, Timo Sirainen wrote: On Mon, Sep 17, 2007 at 02:00:54PM +0200, Geert Hendrickx wrote: I guess this'll do it: http://hg.dovecot.org/dovecot/rev/92bce6a3fdad (without testing) No, the filename is wrong. The generated rquota_xdr.c has #include rquota.h. Oh, right. :) http://hg.dovecot.org/dovecot/rev/2ab3cb6af745 Seems like dovecot nightly 20070918 fixed the problems I reported except: - I still need to run make rquota_xdr.c manually, but only the first time. If I rm rquota_xdr.c and rquota.h and run make again, the are generated. - doc/wiki now contains a lot more files with brackets in their names. (2f) But these nightly snapshots are from the 2.0 development branch, not 1.1, right? Could you please send me an 1.1 alpha snapshot (or release another alpha) to test? Thanks, Geert
Re: [Dovecot] v1.1.alpha6 released
On Tue, Sep 18, 2007 at 06:16:22PM +0300, Timo Sirainen wrote: On 18.9.2007, at 17.54, Timo Sirainen wrote: - I still need to run make rquota_xdr.c manually, but only the first time. If I rm rquota_xdr.c and rquota.h and run make again, the are generated. Well, I can't really think of how to fix this anymore without being able to test it myself.. Looks like it was actually broken with Linux also. I tried yet another way to do this. A new snapshot should be done in a few minutes. Seems to work fine now, thanks! Geert pgpOVV2KqA3RH.pgp Description: PGP signature
Re: [Dovecot] v1.1.alpha6 released
On Mon, Sep 17, 2007 at 09:59:07AM +0300, Timo Sirainen wrote: On Sun, 2007-09-16 at 20:07 +0200, Geert Hendrickx wrote: - src/plugin/quota: *BSD rpcgen doesn't copy rquota.h when called with -c. The Makefile should either: cp the file as part of the rquota_xdr.c Makefile target, or change #include rquota.h to #include rpcsvc/rquota.h with sed. Neither does Linux's. My generated rquota_xdr.c contains: #include /usr/include/rpcsvc/rquota.h I'd think this is a problem with other software too. Any idea how they've solved it? I'll look into that (I'm not familiar with rpc myself). I think one possibility is to use rpcgen -h to generate the .h file. Better than cp at least. Sure! - apparantly the rquota_xdr.c target is not called automatically. ? I have to run make rquota_xdr.c manually, make all doesn't invoke it. - doc/wiki/Makefile: BSD make is confused by the brackets in wiki_DATA, Migration.Vm(2d)pop3d.txt on line 547: make: don't know how to make 2d. GNU make has no problem with this. Either the pkgsrc package should be configured to use GNU make instead, or the file should be renamed. Renamed. Thanks! Geert pgplbCvUap021.pgp Description: PGP signature
Re: [Dovecot] v1.1.alpha6 released
On Mon, Sep 17, 2007 at 10:41:38AM +0300, Timo Sirainen wrote: On Mon, 2007-09-17 at 09:23 +0200, Geert Hendrickx wrote: - apparantly the rquota_xdr.c target is not called automatically. ? I have to run make rquota_xdr.c manually, make all doesn't invoke it. Maybe this will do it: http://hg.dovecot.org/dovecot/rev/1672a4cb665e At least it doesn't break with GNU or Solaris make. Confirmed. Geert pgpvQv15aeiFt.pgp Description: PGP signature
Re: [Dovecot] v1.1.alpha6 released
On Mon, Sep 17, 2007 at 10:36:40AM +0300, Timo Sirainen wrote: On Sun, 2007-09-16 at 20:22 +0200, Geert Hendrickx wrote: In dovecot 1.1.x, ~ is apparantly not always expanded to the homedir anymore. I used to have this in my 1.0 configuration file: mail_location = mbox:~/mail:INBOX=~/mbox The first ~ works (I can browse folders) but the second doesn't (dovecot can't find my INBOX. Changing ~ to %h makes it work again. Fixed: http://hg.dovecot.org/dovecot/rev/7b745fb85975 Confirmed, thanks. Geert pgp7ZElNqEz3Z.pgp Description: PGP signature
Re: [Dovecot] v1.1.alpha6 released
On Mon, Sep 17, 2007 at 11:29:42AM +0300, Timo Sirainen wrote: On Mon, 2007-09-17 at 09:23 +0200, Geert Hendrickx wrote: On Mon, Sep 17, 2007 at 09:59:07AM +0300, Timo Sirainen wrote: On Sun, 2007-09-16 at 20:07 +0200, Geert Hendrickx wrote: - src/plugin/quota: *BSD rpcgen doesn't copy rquota.h when called with -c. The Makefile should either: cp the file as part of the rquota_xdr.c Makefile target, or change #include rquota.h to #include rpcsvc/rquota.h with sed. Neither does Linux's. My generated rquota_xdr.c contains: #include /usr/include/rpcsvc/rquota.h I'd think this is a problem with other software too. Any idea how they've solved it? I'll look into that (I'm not familiar with rpc myself). I think one possibility is to use rpcgen -h to generate the .h file. Better than cp at least. I guess this'll do it: http://hg.dovecot.org/dovecot/rev/92bce6a3fdad (without testing) No, the filename is wrong. The generated rquota_xdr.c has #include rquota.h. Geert pgpcHoN0KxixT.pgp Description: PGP signature
Re: [Dovecot] v1.1.alpha6 released
On Sun, Sep 16, 2007 at 03:07:02PM +0300, Timo Sirainen wrote:
http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha6.tar.gz
http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha6.tar.gz.sig
There are a few problems building this on NetBSD:
- src/master: master-settings.c requires sys/resource.h, see the attached
patch.
- src/plugin/quota: *BSD rpcgen doesn't copy rquota.h when called with -c.
The Makefile should either: cp the file as part of the rquota_xdr.c Makefile
target, or change #include rquota.h to #include rpcsvc/rquota.h with sed.
- apparantly the rquota_xdr.c target is not called automatically.
- doc/wiki/Makefile: BSD make is confused by the brackets in wiki_DATA,
Migration.Vm(2d)pop3d.txt on line 547: make: don't know how to make 2d.
GNU make has no problem with this. Either the pkgsrc package should be
configured to use GNU make instead, or the file should be renamed.
Seems to build and run fine, otherwise.
Geert
$NetBSD$
--- src/master/master-settings.c.orig 2007-09-16 17:18:22.0 +0200
+++ src/master/master-settings.c
@@ -24,6 +24,10 @@
#include pwd.h
#include grp.h
+#ifdef HAVE_SYS_RESOURCE_H
+# include sys/resource.h
+#endif
+
enum settings_type {
SETTINGS_TYPE_ROOT,
SETTINGS_TYPE_SERVER,
Re: [Dovecot] v1.1.alpha6 released
On Sun, Sep 16, 2007 at 03:07:02PM +0300, Timo Sirainen wrote: http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha6.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha6.tar.gz.sig Most importantly doesn't crash anymore if both pop3 and imap aren't used. :) I'm hoping people won't find anything too bad from this release anymore, so I'll release v1.1.beta1 in a week or so. In dovecot 1.1.x, ~ is apparantly not always expanded to the homedir anymore. I used to have this in my 1.0 configuration file: mail_location = mbox:~/mail:INBOX=~/mbox The first ~ works (I can browse folders) but the second doesn't (dovecot can't find my INBOX. Changing ~ to %h makes it work again. Was this intended? Geert
Re: [Dovecot] Dovecot + Sieve - and passdb/userdb
On Thu, Sep 06, 2007 at 05:24:08PM -0700, Daniel L. Miller wrote: Deliver + sieve is working great. By setting the sieve variable to sieve, a non-hidden file, it doesn't appear in the folder list. I made a similar change to pysieved to use a non-hidden folder - in combination with avelsieve and squirrelmail I now have a user-maintainable server-side filter solution. Awesome! Is there a hidden gotcha I'm missing here? It's doing exactly what I want! Other meta-data, like .dovecot.lda-dupes (autoreplied senders db for the vacation plugin) will still be visible as (corrupted) mailfolders in IMAP. Geert
Re: [Dovecot] Dovecot + Sieve
On Tue, Sep 04, 2007 at 10:34:23AM -0700, Daniel L. Miller wrote:
What is the format of your global setting? I tried -
plugin {
sieve = /var/mail/%d/%u
}
since my mail dirs are stored under /var/mail/domain/username. Does
that search for .dovecot.sieve in the specified folder? Or do I need
to add that to the path?
It's a filename. Either relative to the user's homedir or absolute.
So you should set sieve = /var/mail/%d/%u/.dovecot.sieve.
Geert
Re: [Dovecot] MANAGESIEVE patch v7 for dovecot 1.0.3
On Sat, Aug 18, 2007 at 01:06:37AM +0200, Stephan Bosch wrote: This patch still includes (yet another) instance of the CMU Sieve source, as explained in one of my previous e-mails. On Fri, Jul 28, 2006 at 12:10:35AM +0200, Stephan Bosch wrote: Considering the dovecot-sieve plugin, I noticed that you obviously do not want to include the cmu sieve code in the main dovecot source tree. Unfortunately I did not see any other way but to include this library in my patch to make it support checking the uploaded scripts (for now). IIRC pysieved[1] simply invokes dovecot's sievec on the uploaded script and checks the return value, can't you do that as well? Geert [1] http://woozle.org/~neale/src/pysieved/
Re: [Dovecot] MANAGESIEVE patch v7 for dovecot 1.0.3
On Mon, Aug 27, 2007 at 05:43:08PM +0200, Stephan Bosch wrote: Unless you or Timo have strong arguments to the opposite, I currently have no plans to change the current connection of sieve to the managesieve patch until dovecot(-sieve) 2.0. Ok. I just thought you wanted to get rid of the extra copy of cmusieve in the sources, and I understood from your previous e-mails that (with dovecot's current plugin architecture) it was not obvious to merge the two copies. Geert
Re: [Dovecot] Dovecot on different server than MTA
Timo, would you be interested in implementing an LMTP interface for deliver? That would make Dovecot a stand-alone mailstore server, no local MTA required. Geert On Sun, Aug 19, 2007 at 11:31:53PM +0200, FORMER 03|Baltasar Cevc wrote: Hi, I'm setting up our new mail system using dovecot as mailbox server. As our goal is to have many many small redundant (virtual) servers as components, for example a mailhub (just relaying mail) and a frontend smtp server (just accepting or denying mail in the first place and then forwarding it to the mailhub), etc. I want to run Dovecot on a different server than the main MTAs. The mailbox server is the only service that cannot be made redundant in an easy way (the servers don't have common storage and we can't add that easily), thus I prefer not to have it on the same server as the relay. Is there a best practice to do that? My current ideas are either to implement a stripped-down Postfix in the Dovecot server or to use some qpsmtpd setup there, both just to call the Dovecot delivery program. SMTP will be the communication protocol for the components except dovecot. (e.g. the virus scanner will be implemented as SMTP proxy). I'm quite bad at ASCII art, but I'll try anyways to illustrate the setup: I -- [public incoming MX] -\ N| T \|/ E -- [customer mailrelay] - [Postfix Mailhub] virusscanner R| | N ---outgoing mails-/ | E| T -- [dovecot mailstore] -mail delivery Each of the subsystems will be on a different virtual server in order to have small systems with distinct functions and to improve scalability. Everything except the dovecot server is planned to be duplicated on two different hardware machines (e.g. mx-in1 on server1, mx-in2 on server 2, mailhub1 on server1, mailhub2 on server2, virusscanner on server 2 and 3, etc. or something similar). Thanx, Baltasar -- _ FORMER 03 GmbH _ infanteriestra§e 19 haus 6 eg _ 80797 muenchen _ www.former03.de _ phone +49 - 176 - 23 22 08 22
Re: [Dovecot] about index cache
On Mon, Aug 13, 2007 at 06:06:38PM +0300, Timo Sirainen wrote: So Dovecot remembers what fields client is interested of and when header is being parsed it caches everything that it knows the client wants. For how long does dovecot remember which headers? e.g. what happens if a user switches to another mail client which downloads less headers? How long will the now unused headers still be indexed? Geert
Re: [Dovecot] BUG (and suggested fix) in maildir code
On Wed, Aug 08, 2007 at 01:14:39PM +0100, Tom Vajzovic wrote: Hi all I'm using dovecot 1.0.rc15 to serve a maildir by IMAP. I have an IMAP subdirectory called subscriptions. The messages are in maidir/.subscriptions/cur/ etc. Dovecot is renaming the directory .subscriptions/ to subscriptions/ This means that when my IMAP client requests this directory, it gets the message no such directory, and dovecot also gives the error message: dovecot: IMAP(tcv): read() failed with subscription file /var/mail/maildir/tcv/subscriptions: Is a directory The two should be able to live happily side by side, with the subscriptions file called subscriptions and the maildir called .subsciptions. The offending function is maildir_subscriptions_convert_099() in src/lib-storage/index/maildir/maildir-storage.c Can someone with developer access please change this so that rename() is not called if subscriptions is a directory. That only solves the problem for your particular setup. What with mbox installations? Call it .subscriptions again? And what with mixed maildir+mbox installations? How should a folder named subscriptions be called there? Geert
Re: [Dovecot] Disable IMAP for certain users, but not Webmailer
On Sun, Aug 05, 2007 at 10:20:02PM +0200, FORMER 03|Baltasar Cevc wrote: But I'd need some possibility to have two different IMAP listeners (e.g. one on port 144 for webmail) or something similar, as I currently disallow webmail (which connects to localhost via IMAP), too. You just need to accept IMAP from any IP for some, from localhost only for others, and from nowhere for the rest. No need for different ports. You just need one additional column in the database (with 'pop3'/'imap'/ 'webmail' or however you'd like to encode it) and then construct the right SQL-queries, see Angel Marin's hints for that. Geert
Re: [Dovecot] Disable IMAP for certain users, but not Webmailer
On Sun, Aug 05, 2007 at 09:53:52AM -0700, Don Russell wrote:
Not sure what your situation is, but in the USA laws are underway for
requiring corporations to keep ALL e-mail ... not sure what the state of
those laws are maybe they won't materialize but obviously people
are thinking along those lines...
Based on your e-mail address, I assume you are not subject to US laws
etc... but I think it's a sign of things to come in the corporate world.
Some possible future law in some silly country has nothing to do with
Baltasar's original technical question, which is completely legitimate;
offering POP3 access to all and IMAP only to some.
Baltasar:
You could use different passdb's under pop3 and imap, using the allow_nets
extra field: http://wiki.dovecot.org/PasswordDatabase/ExtraFields/AllowNets
You would allow pop3 access to all, imap access to some from any IP and to
others only from the webmail server(s) IP('s).
Geert
Re: [Dovecot] Password Encryption
On Fri, Aug 03, 2007 at 08:35:59AM -0400, Dave Morrow wrote: While everything seems to have gone right, I have been unable to successfully login to the IMAP server using Outlook Express. It seems that the problem may relate to PostfixAdmin storing passwords in the mysql database md5 encrypted, and Dovecot is not able to read them, but I am not certain. This wiki page may help you: http://wiki.dovecot.org/Debugging/Authentication Geert
Re: [Dovecot] Dovecot strong or not for a big Webmail architecture
On Fri, Aug 03, 2007 at 12:03:30PM -0400, Bill Boebel wrote: Do you think it's a good solution to use one synchronised local Openldap on each server Dovecot ? No. I'd replicate your ldap database on a few servers that are dedicated to that purpose, and on each mail server use Dovecot's auth_cach feature to minimize how often it needs to query ldap. A few OpenLDAP servers should be able to cope with the load easily. We're using 3 OpenLDAP servers for 1.000.000 mailboxes and they're mostly idle. Just make sure you setup the right indexes. Do you think It's possible to use Postgresql or MySQL instead of Openldap ? We use MySQL. MySQL handles frequent writes better than OpenLDAP from our experience. It is also simpler for us to do replication and troubleshooting because we employ several MysQL gurus already. Provisioning data usually is not written frequently, but read continously. This is where LDAP works better. And read-only replication is easy enough with OpenLDAP. Geert
Re: [Dovecot] Editing sieve files
On Wed, Aug 01, 2007 at 11:33:01PM +0200, jalal wrote: if i want to change the dovecot-sieve file to modify the rules (or even let my users do it at some point) then it has to been done by root. Is there a way to setup the sieve plugin so a user can create his own rules? sort of like ~/.procmailrc You may want to setup a ManageSieve server, so users can edit their Sieve script via a web-frontend or a local client (e.g. a thunderbird extension). http://wiki.dovecot.org/LDA/Sieve#head-f85f39f49af6057bb18c671d9b9b7df0122e51e5 Geert
Re: [Dovecot] [Dovecot-news] v1.0.3 released
On Wed, Aug 01, 2007 at 01:22:59PM +0300, Timo Sirainen wrote: http://dovecot.org/releases/1.0/dovecot-1.0.3.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.3.tar.gz.sig No dovecot-sieve-1.0.3 tarball (yet)? Geert
Re: [Dovecot] [Dovecot-news] v1.0.3 released
On Wed, Aug 01, 2007 at 02:41:44PM +0300, Timo Sirainen wrote: 1.0.2 works just fine with it. The version numbers just have happened to be the same earlier. Is this documented somewhere? Or how do we know which dovecot-sieve version matches which dovecot version(s)? I thought they always had to be the same... Otherwise you could just create dovecot-sieve-1.0.3.tar.gz as a symlink to dovecot-sieve-1.0.2.tar.gz... Geert
Re: [Dovecot] sieve discard
On Wed, Aug 01, 2007 at 03:02:38PM +0300, Timo Sirainen wrote: Or I guess since this hasn't been a problem normally I could just remove it unless it becomes a common problem. Updated the text: Use --with-dovecot=path to point to dovecot-config file's directory. There are two possibilities where this could exist: 1) If you configured Dovecot with --enable-header-install, you'll have dovecot-config installed in $prefix/lib/dovecot/ directory. 2) Compiled Dovecot sources' root directory. So for example: ./configure --with-dovecot=/usr/local/lib/dovecot make sudo make install sievec and sieved binaries are built only if you use 2) method, because they need to link with Dovecot's libraries. They can be used to compile and decompile Sieve scripts. You probably don't need these. (1) is very interesting from a packager's point of view (allows me to package dovecot-sieve for pkgsrc much easier), but e.g. pysieved (the python managesieve server) needs sievec for verifying sieve scripts while uploading... Geert
Re: [Dovecot] sieve discard
On Wed, Aug 01, 2007 at 10:52:18AM -0400, Tom Diehl wrote: I do not know what OS you are packaging for but if you are looking for rpms, fedora has released rpms that include seive in the same srpm as dovecot. I took their .src.rpm and rebuilt it on EL4/Centos4 and it spit out seperate dovecot and sieve binary rpms that so far work as advertised, at least for me. This is for pkgsrc (cross-platform, mainly NetBSD and Dragonfly BSD), which (currently) doesn't support creating multiple binary (sub-)packages from a single source package. But I can include the headers in the main dovecot package and have a sieve package depending on that (without sievec/sieved, but that's better than having no sieve package at all). Geert
Re: [Dovecot] sieve discard
On Wed, Aug 01, 2007 at 03:02:38PM +0300, Timo Sirainen wrote: sievec and sieved binaries are built only if you use 2) method, because they need to link with Dovecot's libraries. They can be used to compile and decompile Sieve scripts. You probably don't need these. According to the Makefile, they only need liblib.a to build. Can't this file be installed as well with --enable-header-install (you may want to rename this flag then), so that dovecot-sieve can fully be built against an installed dovecot package? Geert
Re: [Dovecot] Will pay $500 towards a Dovecot feature = calender ?
On Thu, May 24, 2007 at 08:50:11AM -0700, Marc Perkel wrote: Keep in mind that one of the reasons people buy Exchange is because Exchange does things that people want. A calendar is one of many examples. But to start with I'm thinking more in terms of controlling server side email settings. Also keep in mind that people dump Exchange because it's slow, complex and buggy, whereas Dovecot is mean and lean. Remember the old UNIX paradigm -- do one thing and do it well. Dovecot is an IMAP server, and does the job well. A calendaring server is an entirely different beast, and should be seperate from the pop3/imap server, even if only to improve security and reliability. Geert
Re: [Dovecot] dovecot.org moves to a new server
On Mon, May 21, 2007 at 10:04:11PM +0300, Timo Sirainen wrote: Yes, there were some problems with it. I think it should work now once DNS caches expire (max. 20h). Although I don't get it why the A record doesn't disappear from .org root servers. But looks like it doesn't cause problems there anyway. It's ok now, thanks! Geert
Re: [Dovecot] dovecot.org moves to a new server
On Sun, May 20, 2007 at 02:19:15PM -0700, Bill Landry wrote: Timo Sirainen wrote the following on 5/20/2007 1:45 PM -0800: On Sun, 2007-05-20 at 22:53 +0300, Timo Sirainen wrote: So, beginning the move by shutting down Postfix and Mailman.. Wonder if it's working. Wonder what all I forgot.. If things seem broken, please tell me. :) Well, got that posting - so far so good... ;-) One thing I noticed is that reverse DNS isn't properly configured for the new IP 82.118.211.50. This may trigger anti-spam measures at the receiver's end... Geert
Re: [Dovecot] How to use option allow_nets?
On Wed, May 02, 2007 at 03:19:36PM +0200, Bernd Kuhls wrote:
I tried to add the line
allow_nets=127.0.0.0/8,192.168.0.0/16
in the block
passdb pam {
which is the default enabled auth code in Debian.
allow_nets is a passdb field (for example in an SQL passdb), not a
dovecot.conf directive.
Geert
Re: [Dovecot] v1.0.0 released
On Fri, Apr 13, 2007 at 03:04:23PM +0300, Timo Sirainen wrote: http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. Good job, Timo! Congratulations with the very solid 1.0 release. It's in NetBSD pkgsrc. Geert pgpyZK1e0M9tp.pgp Description: PGP signature
Re: [Dovecot] 1.0.rc29 released
On Fri, Mar 30, 2007 at 05:47:30PM +0200, Robert Schetterer wrote: HI Timo, you added the wiki in txt format to the docs dir, this again brokes my suse spec *g What annoys me more (as dovecot maintainer for pkgsrc) is that the example config file changes with (almost) every release. The changes are mostly just in comments, but it makes users have to merge their configuration on every update. Geert pgpsI2rExOMQR.pgp Description: PGP signature
Re: [Dovecot] 1.0.rc29 released
On Fri, Mar 30, 2007 at 12:35:09PM -0400, John Peacock wrote: What part of Release Candidate isn't clear here... ;-) release candidate equals latest supported release in this case as well. If they were 2.0 rc's, I'd continue running the latest 1.whatever release until done. Geert
Re: [Dovecot] 1.0.rc29 released
On Fri, Mar 30, 2007 at 07:35:40PM +0300, Timo Sirainen wrote: I hate how badly the configuration file updating works everywhere (well, or at least in Debian). If the changes don't really change any existing settings and won't conflict with the modified parts of the config file, there's no need to ask anything about merging. Why couldn't it work by doing a diff of the old and new default config files, and then try to patch the changes into the current config. If the patch succeeds, that's your new config. Of course if the new config file really changes existing defaults, it shouldn't do this without asking. I'm actually doing a merge dovecot.conf old-default new-default every time, and it usually causes some conflicts due to changed comments. They're easy to resolve, of course, but it could be avoided. Geert pgpcP3Q3sMDjc.pgp Description: PGP signature
Re: [Dovecot] Version numbering
On Thu, Mar 29, 2007 at 10:30:24AM +0200, Nils Vogels wrote: On Thu, Mar 29, 2007 at 02:05:13AM +0300, Timo Sirainen (TS) wrote: TS TS I don't think packaging is going to be that big of a problem. If the packagers TS can't handle that, then just don't package it. Development versions don't TS really need binary packages anyway.. And for those using the binary packages, TS the alpha/beta/rc in the version make it pretty easy to understand what kind TS of a release it is. This will work just fine for FreeBSD ports! Same for pkgsrc. The most important thing though is that the latest format *release* is always supported with security/critical fixes, so people are not forced to track RC's as they are now with 1.0. But there can always be a parallel -devel package for those interested. Geert pgpb3P7rZNfWb.pgp Description: PGP signature
