- dovecot - dovecot.org

[Dovecot] Setting location for indexes
by dovecot.7.signal11＠spamgourmet.com 08 May '05

08 May '05

We have NFS-mounted user directories which cause significant problems with stale file handles: dovecot: IMAP(uid): fstat() failed with file /home/uid/mail/.imap/INBOX/dovecot.index.log: Stale NFS file handle (a) why can't it just close the file and re-open ? (b) is there a way to specify with the 'default_mail_env' (or in some other way) the location of **only** the indexes (and let dovecot autodetect all else?). I have already tried 'mmap_disable = yes', but that does not solve the problem, and if I set 'default_mail_env = INDEX=/var/spool/mail/INDEX/%u', I get errors like: IMAP(uid): Failed to create storage with data: INDEX=/var/spool/mail/INDEX/uid I don't want to specify mbox:~/mail/ or mbox:~/Mail/, because some users have one and some the other.

6 6

Re: [Dovecot] headers don't match message
by Brian Bartholomew 08 May '05

08 May '05

Kevin <angrycoggy(a)gmail.com> wrote: > once i had everything moved and dovecot running i checked my mail > via imap. all the messages appeared however when i try to read a > message the message body doesn't match the header info that's showed > in the message list. Gregory Bond <gnb(a)itga.com.au> wrote: > I see this a lot using Thunderbird & an old-ish dovecot (test-46 I > think). it is triggered by leaving thunderbird connected at work, > going home and accessing the same IMAP server from mutt at home. If > I use mutt in read-only mode it's fine, but if I delete any messages > in mutt, then the work Thunderbird gets very very confused. I'm using one of the stable 1.0 releases for 184 accounts on Gentoo Linux on Sparc. I too am seeing the message header/body mismatch in Thunderbird. Is the index file handling sufficiently robust against surprises that I can delete the dovecot index files every night out from under the logged-in imap sessions? Brian

2 1

[Dovecot] pop vs. imap inconsistancy
by jeff sacksteder 08 May '05

08 May '05

I am converting from courier and have noticed change in behaviour with Dovecot. I use maildirs with squirrelmail connecting by imap as well as a POP3 client. Courier would set the 'mail status-read' flag for any message which was downloaded with the POP3 interface. Dovecot apparently does not. Is this a bug or intended behaviour? If it is intentional, can it be changed with the config file?

1 0

[Dovecot] Help configuring dovecot for SSL
by Knute Johnson 04 May '05

04 May '05

Hi: I'm running dovecot on a Fedora 3 box and would like to be able to make a TLS connection to it with my Pegasus Mail program running on my Winblows machine. Does anybody know if it is possible? If it is I could really use some help configuring my dovecot. I have tried for several days but I really don't know what I'm doing and need a direction to start. Thanks, -- Knute Johnson Molon Labe...

2 2

[Dovecot] Multiple Logins - Single Mail Account
by Net Cerebrum 04 May '05

04 May '05

I have a mail account which needs to be accessed by 4-5 people simultaneously through IMAP. As of now I have configured it on the respective clients using the same username and password so we have multiple people accessing the same account through their mail clients simultaneously and it is working flawlessly. Is this alright or can it lead to some problems or corruption of data later ? What is the best way to allow multiple people to access a single mailbox for read as well as write operations ? Thanks,

3 4

[Dovecot] Segfault in imap
by Todd Burroughs 04 May '05

04 May '05

I'm running the current CVS version, as of April 26. There have been a few of these with the same problem. There was a NULL pointer dereference at mail-index-view.c:603 view->map == NULL Here's the log entry, etc. dovecot: May 03 08:30:08 Error: 10195 IMAP(support): UIDVALIDITY changed (1115122813 -> 1115123383) in mbox file /mailhome/new/m/2/support/mbox dovecot: May 03 08:30:13 Error: child 10195 (imap) killed with signal 11 Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. (gdb) bt full #0 mail_index_view_open (index=0x80c2fc0) at mail-index-view.c:603 view = (struct mail_index_view *) 0x80c5608 #1 0x08077ccd in index_storage_mailbox_init (ibox=0x80c3bc8, index=0x80c2fc0, name=0x80a6cfe "INBOX", flags=Variable "flags" is not available. ) at index-storage.c:345 storage = Variable "storage" is not available. (gdb) bt #0 mail_index_view_open (index=0x80c2fc0) at mail-index-view.c:603 #1 0x08077ccd in index_storage_mailbox_init (ibox=0x80c3bc8, index=0x80c2fc0, name=0x80a6cfe "INBOX", flags=Variable "flags" is not available. ) at index-storage.c:345 #2 0x080679c2 in mbox_alloc (storage=0x80bc788, index=0x80c2fc0, name=0x80a6cfe "INBOX", flags=0) at mbox-storage.c:500 #3 0x080684e0 in mbox_open (storage=0x80bc788, name=0x80a6cfe "INBOX", flags=0) at mbox-storage.c:545 #4 0x0806863f in mbox_mailbox_open (_storage=0x80bc788, name=0x80a6cfe "INBOX", input=0x0, flags=0) at mbox-storage.c:603 #5 0x0808ce88 in mailbox_open (storage=0x0, name=0x80a6cfe "INBOX", input=0x0, flags=0) at mail-storage.c:295 #6 0x08057f9f in _cmd_select_full (cmd=0x80bcb98, readonly=0) at cmd-select.c:32 #7 0x08058171 in cmd_select (cmd=0x80bcb98) at cmd-select.c:97 #8 0x08059635 in _client_input (context=0x80bcb58) at client.c:334 #9 0x0809e04a in io_loop_handler_run (ioloop=0x80bb9b0) at ioloop-poll.c:184 #10 0x0809d769 in io_loop_run (ioloop=0x80bb9b0) at ioloop.c:218 #11 0x08060537 in main (argc=1, argv=0xbffffa44, envp=0xbffffa4c) at main.c:228 (gdb) p view->map $1 = (struct mail_index_map *) 0x0 (gdb) p index->map $2 = (struct mail_index_map *) 0x0 (gdb) p index->indexid $3 = 0

1 0

[Dovecot] Error in rename uidlist while fetching through pop3
by James Berry 03 May '05

03 May '05

My dovecot server seems to randomly begin giving errors to pop3 users who try to fetch their email. Once this begins, they see no more new mail, though the mail is in cur. Running: dovecot-stable 20050501, Mac OS X 10.3.9 Log entries like this: May 2 19:35:18 caddy dovecot: pop3-login: Login: kim [24.22.16.169] May 2 19:35:18 caddy dovecot: POP3(kim): rename(/Users/kim/Maildir/ dovecot-uidlist.lock, /Users/kim/Maildir/dovecot-uidlist) failed: Input/output error May 2 19:35:18 caddy dovecot: POP3(kim): file_dotlock_replace(/Users/ kim/Maildir/dovecot-uidlist) failed: Input/output error Is this a known problem, and/or is there a known way to recover from such a situation? I'm managed to throw out the uidlist, but that means they get a whole dump of new mail. -jdb

2 1

[Dovecot] How to try dovecot-lda
by Joakim Verona 02 May '05

02 May '05

Hello, I'm interested in trying the dovecot-lda with sieve support. What would be the proper way to test it? I'm currently using a Fedore core 2 server, with spamassassin and procmail. To get the same effect with dovecot-lda, would I put a line like this in my .forward? spamassassin|dovecot-lda I'm just guessing, so please correct me if im wrong. Im thinking of setting up a separate mail account and copy my mail there to test the ported procmail to sieve recipies also. -- Joakim Verona www.verona.se

1 0

[Dovecot] disabling indexes?
by Marten Lehmann 02 May '05

02 May '05

Hello, I recently had the problem, that an index was corrupt. Thus, messages haven't been listed (talking about POP3), but still remained in the filesystem. As there is no SEARCH-command in POP3, dovecot didn't notice that the index is corrupt and didn't rebuild it. The problem is, that a user can't delete messages through POP3 which aren't listed by dovecot. If the maildir size increases, the arrival of new messages will be blocked because the mailbox is full. And the user has no chance to delete it. Regards Marten

1 0

[Dovecot] Blank lines in mailboxes
by Jakob Curdes 30 Apr '05

30 Apr '05

Hello, we use dovecot on a regular basis. Sometimes I end up with a user telling me he does not get mail. When I look after the problem, I always find leading blank lines in the mbox file. We are using postfix with dovecot and amavisd as spam scanner. Amavisd never accesses the mbox files directly so this can be ruled out. I suspected procmail but now it happened also with accounts where no procmail is active. I found only a list thread where this happened always, i.e. it was a configuration error. (Meaning the mailbox was correct but dovecot would not read it). Here ist is only occasionally and therefore hard to track . Does anybody have the same problem or has hints to a solution ? We are running postfix 2.1.4 and dc 0.99.10.6 ; just now I am upgrading to pf 2.2.2. and dc 0.99.14. Yours, Jakob Curdes

5 21