July 2003 - dovecot - dovecot.org

RE: [Dovecot] Loadable module
by Maikel Verheijen 22 Jul '03

22 Jul '03

Hi Timo, [snipped possible scenario's] > OK. 3) is the best idea :) But it requires a few changes to > make it work. I wouldn't expect it to work out of the box :) But if I read your suggestions right, you propose a "fixed" change in the maildir functions that call the quota update functions if necessary. So perhaps we should make a quota_enabled = yes|no flag int the config file, and use that? I would still be trying to make the quota update functions for you, and try to put them in. > Actually, I think this is exactly how I want quota and ACLs > to be implemented. No extra interface changes for either one of them. > > For quota, you'd want to do something like: > > expunge(): nothing special, just update the quota file after expunges Expunge should recalculate the whole mailfolder? > save_next(): Check data istream's size and if it's over quota, fail. Ok. So this one can be "easy". Just check if mailsize + current usage < max_quota. :) > copy(): this is somewhat problematic, if there wasn't the > maildir hardlinks you wouldn't have to touch it at all.. A copy can duplicate a message in the same store, but do hardlinks work on nfs? If not, we should add the message to the quota list. And maybe we should just add size of the email anyway, it won't be that much of a loss to the user, and it would save us a lot of checking. :) And how about a user that has no quota file (yet), can we "recreate" them? Maybe do a quota lookup for the user (database or file)? This can be done using a module I guess, so it could be "user configurable". Regards, Maikel Verheijen.

2 1

[Dovecot] Outlook Express 6.0.280.1123 SSL and dovecot .
by Xavier Beaudouin 22 Jul '03

22 Jul '03

Hello there, First many thanks for dovecot, this is marvelous piece of software :) One of my users is using Outlook Express 6.0.280.1123 on XP with SSL. I have lots of this in the syslog : Jul 22 16:25:31 kiwi imap-login: Login: fptarget [62.4.1.170] Jul 22 16:25:32 kiwi imap-login: SSL_read() syscall failed: EOF [62.4.1.170] Jul 22 16:25:59 kiwi imap-login: SSL_read() syscall failed: EOF [62.4.1.170] Jul 22 16:26:43 kiwi imap-login: Login: fptarget [62.4.1.170] Jul 22 16:26:45 kiwi imap-login: SSL_read() syscall failed: EOF [62.4.1.170] Jul 22 16:26:47 kiwi imap-login: Login: fptarget [62.4.1.170] Jul 22 16:26:48 kiwi imap-login: SSL_read() syscall failed: EOF [62.4.1.170] Is there any way to avoid that ? (except telling this user to stop using outlook ?). Thanks, /Xavier

2 1

RE: [Dovecot] Loadable module
by Maikel Verheijen 22 Jul '03

22 Jul '03

Hi Timo, When you have time to create the hooks to the various locations within dovecot, I am willing to try to make a module to support Maildir quota's. Would that be possible with the hooks, and can that be done using a plugin as well? Kind regards, Maikel Verheijen. > -----Original Message----- > From: Timo Sirainen [mailto:tss@iki.fi] > Sent: Saturday, July 19, 2003 12:14 AM > To: Maikel Verheijen > Cc: 'dovecot(a)procontrol.fi' > Subject: Re: [Dovecot] Loadable module > > > On Saturday, Jul 19, 2003, at 00:40 Europe/Helsinki, Maikel Verheijen > wrote: > > > I read a post about moving a .mailbixlist to a > .subscriptionfile when > > a user did not have one, but did have a .mailboxlist file. Timo > > emailed a module for that purpose, so it could be done for > this user. > > > > My question is: > > > > - Where and how does dovecot call this function? > > <module name>_init(); is called after initializing Dovecot's > core code, > but before opening any message store or creating client structure. I > think I'd have to add some hooks for store creation and > client creation > so you wouldn't need kludges if you want to modify them in some way. > > You'll have to enable modules of course in configuration file > and place > the module to right directory. > > > - Would it be easy to use a module to a) create a mailpath (can be > > done as the mailuser's id, I use one uid, and my path is > all owned by > > that uid), and b) simply remove a quota file? > > Yes, the modules can do whatever they want. Just use mkdir() and > unlink(). >

2 1

[Dovecot] migrating from uw imapd
by Craig 21 Jul '03

21 Jul '03

Hi, I'm trying to migrate from uw imapd to dovecot. I'm having two problems at the moment. 1. uw imapd grabs new mail from /var/mail/user and then shoves it into ~/mbox, is there any way to make dovecot handle this kind of setup or am I better off merging ~/mbox back into /var/mail/user? If merging is better are what tools are best for this? 2. While I did have have everything in ~/Mail coming up dovetail stopped working and logs the following error: syslog:Jul 19 23:01:07 epsilon3 imap-login: Login: haakon [192.168.0.107] syslog:Jul 19 23:01:07 epsilon3 imap(haakon): Failed to create storage with data: ~/Mail/:INBOX=/var/mail/haakon syslog:Jul 19 23:01:07 epsilon3 dovecot: child 10417 (imap) returned error 89 any idea what is causing this? Regards, Craig.

7 6

Re: [Dovecot] How to use SASL2?
by Matthew Reimer 19 Jul '03

19 Jul '03

Timo Sirainen wrote: > On Fri, 2003-07-18 at 02:02, grpmind+dovecot(a)boromir.vpop.net wrote: > >>How does one use SASL2 for authentication? I looked for docs but found >>none. > > There's some code for supporting Cyrus' SASL library, but it hasn't been > tested for a while and I doubt that it works. I don't really have plans > to make it work either. > > Why do you want it anyway? Dovecot supports PLAIN, DIGEST-MD5 and > ANONYMOUS SASL mechanisms internally. Most important missing one is > Kerberos 5 I think. I'm not really interested in using SASL for its own sake, but because it's a way to get dovecot to authenticate against my mysql users db. I might try to write a patch to implement mysql support for dovecot, hopefully good enough for you to commit. Matt

1 0

[Dovecot] Loadable module
by Maikel Verheijen 19 Jul '03

19 Jul '03

Hi List! I read a post about moving a .mailbixlist to a .subscriptionfile when a user did not have one, but did have a .mailboxlist file. Timo emailed a module for that purpose, so it could be done for this user. My question is: - Where and how does dovecot call this function? - Would it be easy to use a module to a) create a mailpath (can be done as the mailuser's id, I use one uid, and my path is all owned by that uid), and b) simply remove a quota file? Thank you for your time, Maikel Verheijen. Ps: the email I am referring to has: Subject: Re: [Dovecot] 0.99.10-rc3 Message-Id: <1056538261.8144.38.camel@hurina> Date: 25 Jun 2003 13:51:01 +0300

2 1

[Dovecot] Status of database integration / Willing to help
by Gregory Hartman 18 Jul '03

18 Jul '03

I a PhD student here at Carnegie Mellon. I have ten years of experience working in C in industry. I am working on a research project here at Carnegie Mellon that needs to integrate a database with mail clients. We are planning to use the IMAP protocol to communicate with the mail client. After I spent some time looking at the code of various IMAP server implementations, I got very interested in Dovecot. Then I noticed that you were planning to integrate Dovecot with a SQL database. Is this work in progress? Do you have a schema? Is there some way that I could help? -- Gregory Hartman <gghartma(a)cs.cmu.edu>

2 1

[Dovecot] How to use SASL2?
by grpmind+dovecot＠boromir.vpop.net 18 Jul '03

18 Jul '03

How does one use SASL2 for authentication? I looked for docs but found none. Thanks in advance. Matt

2 1

[Dovecot] Dovecot on Linux 2.6.0-test1-ac1
by Grahame Bowland 16 Jul '03

16 Jul '03

Hi all For various reasons I was looking into 2.6, so I installed a copy on my desktop. Everything works fine, except for dovecot - errors such as this appeared in the syslog: Jul 15 14:41:09 typhaon dovecot: Dovecot starting up Jul 15 14:41:12 typhaon imap-login: setuid(113) failed: Resource temporarily unavailable Jul 15 14:41:12 typhaon dovecot: Login process died too early - shutting down I can imagine why setuid() should ever fail, I've confirmed that the daemon is running as UID zero at the time it makes the call. However, the call succeeds if I comment out: restrict_process_size((unsigned int)-1, 1); on line 134 of src/login-common/main.c it starts to work again. It's very strange - I got the idea to try this from the list archives. I'm willing to track this down if anyone can suggest possible things in restrict_process_size() that might be causing this failure. All the other daemons that I run that need to drop root privileges work fine.. Cheers Grahame -- Grahame Bowland Email: grahame(a)ucs.uwa.edu.au University Communications Services Phone: +61 8 9380 1175 The University of Western Australia Fax: +61 8 9380 1109 CRICOS: 00126G

2 3

[Dovecot] Indexes again
by Timo Sirainen 16 Jul '03

16 Jul '03

A bit quiet here, so here's some more thoughts about indexes. Even though I was thinking only how to make them usable with NFS (I wrote it to doc/nfs.txt), it then occured to me that exactly the same tricks would help with local filesystem indexes as well. Especially the lockless reading would help with lock contention issues I was worrying about earlier with shared mailboxes. Also it occured to me that keeping maildir filenames fully synchronized in index file probably isn't very good idea from performance point of view.. BTW. I almost committed the .tree removal code to CVS today. Then I noticed that expunging ignores about half of the deleted messages. This could have been actually happening with the old code in some situations as well, although it probably would have skipped only a couple of messages. Anyway, fixing this properly takes some more time.. -------- Ideas how to make indexes work pretty well with NFS: Reading shouldn't require locks, so modifying should be done using only atomic operations. These include: - Replacing the file completely using rename() - We probably can't assume that writing more than one byte at a time is atomic. If we have to modify a larger dataset, we could do: - struct { bit_t use_first; dataset_t first; dataset_t second; } - when reading, we use first if use_first is set, second if it's unset - when writing, we first write to the non-used variable, only then we update the flag. - This of course requires twice the amount of space for dataset plus one extra bit, so it shouldn't be used too much - If data can be only set, but never changed, we need only one extra bit to specify if the data is set. - Appending new data to end of file. We'd have to have used_file_size variable in header, done like described above. - Each cached message record would have a pointer to next part, so more cached data could be appended to file. Message flags are the most commonly modified data. If we just modify them directly, a simultaneous read might catch the change only partially. But luckily for us, this is accepted behaviour so we can do it. Another commonly modified data is maildir filenames. We probably want to store only the base name in index and keep the full name synchronized only locally. Compressing unused data from index files would have to be done by rewriting the index into index.lock file and renaming it over the index file. All file operations should probably be done with lseek(), read() and write() to avoid extra network traffic. There should be some clever read-ahead caching however.

1 0