- dovecot - dovecot.org

[Dovecot] why wont /usr/pkg/libexec/dovecot/imap see my Maildir
by Charlie Allom 04 Aug '03

04 Aug '03

When I invoke /usr/pkg/libexec/dovecot/imap from the command loine on the mail host, it logs me in, but won't see my emails: 13:22 yeled@lazy:~$ /usr/pkg/libexec/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND * UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED] Logged in * as yeled 0 select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] * Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1059959635] UIDs valid * OK [UIDNEXT 1] Predicted next UID 0 OK [READ-WRITE] Select completed. I know I have many emails in there, and I can see them when I login via telnet localhost 443. Any tips? would be nice to use fetchmail with ssh here. C. -- charlie(a)rubberduck.com - Melbourne, Australia http://rubberduck.com/~yeled/ PGP: 0x14AA7941 || finger yeled(a)lazy.spodder.com

2 2

[Dovecot] Confusion
by Alejandro Martinez 02 Aug '03

02 Aug '03

Hi, I have a great confusion about mbox, maildir. I use a passwd-file to authenticate users, because I want to use non local users. I have a test user in that file that is this: test:VGRAafc3NHJwI:502:100:Usuario Virtual:/var/spool/mail/virtual/test:/no/shell I create inside /var/spool/mail/virtual/test a folder Maildir and inside Maildir /var/spool/mail/virtual/test/Maildir/cur/ /var/spool/mail/virtual/test/Maildir/new/ /var/spool/mail/virtual/test/Maildir/tmp/ I get an error when I login to the server admin@slk90 /$ telnet localhost 143 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. * OK dovecot ready. . login test test . OK Logged in. Connection closed by foreign host. The /var/spool/mail/error is this "Aug 2 08:46:46 slk90 imap(test): Failed to create storage with data: /var/spool/mail/virtual/test/Maildir" I've tried setting default_mail_env = maildir:~/Maildir and mbox:~/Maildir, but nothing work. Any help ? Regards. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.506 / Virus Database: 303 - Release Date: 01/08/2003

2 1

RE: [Dovecot] corrupt mbox, mailboxes not found, and message rea d status
by Maikel Verheijen 31 Jul '03

31 Jul '03

[SNIP] > http://dovecot.procontrol.fi/list/dovecot/2002> -October/000774.html ) > > on the mailing list where Timo said he was intending to use the > > X-Keywords trick. Did this ever get implemented? > > X-Keywords have been used for a long time now. It's possible > to set \Seen flag for messages downloaded with POP3, but I > don't know if it's worth the trouble. Who uses POP3 and IMAP > mixed anyway? > A lot of our customers, since we only supported pop3 in the past, and our new webmail uses imap. :) And a lot of people don't click on "This is an imap server" when creating their account in for instance outlook-express. Kind regards, Maikel Verheijen.

3 2

[Dovecot] New index file code
by Timo Sirainen 31 Jul '03

31 Jul '03

I just had to write this even while it's not just yet in CVS, but it's only a few fixes away from being committed.. My year long dream has finally came true :) [Summary: Next release will have REALLY kickass indexes] Previously the biggest problem with caching message data in indexes was that we had to do it while syncing the mailbox, before client even saw those messages. This caused index rebuilds to be very slow since it had to go through all mails and cache all of them, even if client never would access them. Alternative was to not cache anything at all, but that wasn't really good idea either. Now Dovecot caches the data when client is actually requesting it. That way it will never do any extra work for caching something that client isn't currently interested in. There's still the anticipatory caching for data that client is likely to be interested in later, but that is done only when it doesn't cause extra disk I/O. The reason why it took this long was because it was previously too difficult with read/write locking that indexes required. I couldn't have relied on it working since changing from read lock -> write lock could deadlock and dropping the lock in the middle would have caused even more problems. So, what I did was to rewrite the cache file handling completely: - It doesn't require any locking to read from it. - It will be NFS-safe without being too costly. - The file format itself is now architecture-independent. - Uses less space than before - OpenBSD support is now worse than before, even worse than NFS-support. They should get that unified cache done. Cached data is also selected better: - Specifically requested message headers are cached (FETCH, SEARCH, SORT, THREAD, etc.) - IMAP ENVELOPE isn't treated in any special way anymore. It's treated just as if you had requested HEADER.FIELDS (Date Subject From ...etc.). - Maildir filenames aren't constantly updated in the cache file anymore. This takes more memory now, but should reduce disk I/O. There's a few more tweaks that I'll probably add later: - Maildir: When compressing cache file we update mail's filename to current one so if message's flags aren't changed often, it won't use any extra memory either. - A normal text/plain message doesn't need to have it's IMAP BODYSTRUCTURE cached. It only needs a single bit set in flags. Should reduce used space quite a lot. - Message with only one body part doesn't need to have it's body structure stored at all since it's mostly just useful for fetching body parts. Plus the body structure could be generated if message sizes were known. All this work was only for index cache file (ex. .data file). There's still the main .imap.index file and modify log files. Modify log should be easy to make NFS-safe - I'm currently using some stupid file locking to figure out when the file is safe to overwrite, but I should have simply replaced the old file with rename(). That will solve some other problems as well as make the code simpler. It should be possible to be made read-lockless as well. The main index file is more problematic though. It contains a lot of changing fields in the header, such as number of messages, number of seen messages, etc. I can't think of any way to make it safe to read these fields without locks (my previous ideas didn't actually work). Lockless reads are pretty much a must for scalable NFS-safety. I think it could be done by simply removing all the constantly changing headers. If you want to know how many seen messages there are, just read all the records in the file and count them. Expunging would be done by rewriting the file and rename()ing it over the old file. Appending new messages is a bit tricky to do safely, but I think I know how to do that too.. read/write locks allow the changing headers, but there's locking contention problems with shared mailboxes.. I think I'll make it optional how to do this. Oh, and I also thought how indexes would work with shared mailboxes. You could use one shared cache file, but each user would have their own main index and modify log. That would allow storing per-user flags in the index file and also expunge (hide) messages by removing them from user's index.

1 0

[Dovecot] Is dovecot NFS safe?
by Adam Shand 29 Jul '03

29 Jul '03

I'm migrating our mailserver from cyrus 2.0 to Postfix and Dovecot. We're using maildirs delivered to /var/maildir, which is mounted via NFS from a Netapp. My understanding was that maildir was completely happy in an NFS environment but I've seen a couple messages here recently which mention the dovecot index files not being NFS safe. Are their any caveats or gotcha's that I need to be aware of? Thanks, Adam.

4 5

[Dovecot] Namespaces
by Timo Sirainen 27 Jul '03

27 Jul '03

0.99.11-test4 release: http://dovecot.procontrol.fi/test/ Finally namespaces somewhat working. Example: namespace private { separator = / prefix = INBOX/ location = maildir:~/Maildir } namespace private { separator = / prefix = #mbox/ location = mbox:~/mail } Problems: - Mailbox listing lists only the first namespace unless you clearly ask mailboxes under some namespace. Not really a problem, but related to: - There should be only one common subscriptions file for all namespaces. This needs some thinking how to do it well. - Having multiple different mailbox formats in one namespace still isn't possible. Needs some more thinking as well.

1 0

[Dovecot] API changes and plugins
by Timo Sirainen 26 Jul '03

26 Jul '03

There's been quite a lot of changes in CVS lately, mostly related to API changes but also some index file changes. They've both had very little testing, so there's probably a few bugs left. Especially mbox users should be careful. pop3 might also be deleting wrong messages.. Anyway. The new mail storage API should allow plugins to hook into pretty much any operation they want to. It's not exactly pretty with C syntax, but I think conceptually it's nice object oriented design :) There's example (non-working) quota plugin at: http://dovecot.procontrol.fi/patches/quota.c I also built 0.99.11-test3 from current CVS: http://dovecot.procontrol.fi/test/

1 0

[Dovecot] Dovecot on Mac OS X?
by jennyw 25 Jul '03

25 Jul '03

Just wondering if anyone has successfully gotten Dovecot to run on Mac OS X? If so, I'd love to hear what your experience has been! Thanks! Jen

2 1

FW: [Dovecot] Is dovecot NFS safe?
by Maikel Verheijen 25 Jul '03

25 Jul '03

This was ment for the list :) Sorry Stuart, for the double email... Regards, Maikel. > -----Original Message----- > From: Maikel Verheijen > Sent: Friday, July 25, 2003 3:40 PM > To: 'Stuart Henderson' > Subject: RE: [Dovecot] Is dovecot NFS safe? > > > Hi, > > Be aware that also your .subscriptions file and .customflags > are not nfs safe (yet) in dovecot-0.99.10. > > I know Timo is working on that though :) > > Kind regards, > > Maikel Verheijen. > > Ps: I have a "crude" patch to make .subscriptions and > .customflags nfs aware (I can not guarentee it is nfs safe ;-). > My own setup runs on nfs with the indexes in memory. > > > -----Original Message----- > > From: Stuart Henderson [mailto:stu@spacehopper.org] > > Sent: Friday, July 25, 2003 2:13 PM > > To: Adam Shand; dovecot(a)procontrol.fi > > Subject: Re: [Dovecot] Is dovecot NFS safe? > > > > > > > I'm migrating our mailserver from cyrus 2.0 to Postfix > and Dovecot. > > > > > > We're using maildirs delivered to /var/maildir, which is > > mounted via > > > NFS from a Netapp. My understanding was that maildir was > > completely > > > happy in an NFS environment but I've seen a couple messages here > > > recently which mention the dovecot index files not being NFS safe. > > > > > > Are their any caveats or gotcha's that I need to be aware of? > > > > You'll probably want to keep them in memory or on local disk. See > > <http://dovecot.procontrol.fi/doc/nfs.txt> for more information - > > default_mail_env needs either ":INDEX=/local/path/to/indexes/%u" or > > ":INDEX=MEMORY", all machines accessing the mailstore should have > > sync'd clocks, and all imap servers need separate hostnames. > > > > --Stu > > >

1 0

[Dovecot] phpgroupware's imap client with dovecot
by Farkas Levente 24 Jul '03

24 Jul '03

hi, we try to use http://www.phpgroupware.org/ imap client with dovecot, but it doesn't working. is there any way to get it working with dovecot? there are a few possibbilities for imap type: courier or cyrus WUash WU-maildir but none of them seems to be working, although pop3 is working. any tip? can I send any log? thanks in advance. -- Levente "Si vis pacem para bellum!"

2 2