- dovecot - dovecot.org

[Dovecot] Need to move mail
by Brent Clark 15 Nov '05

15 Nov '05

Hi all My imap server is getting to the stange where I need to start worring about the disk usage. Due to the number of users we seem to be hiring, I need to start looking at a new mail server, suppose its a blessing in disguise too. Would it be ok to just tar my current users mail (there home directory, I dont use virtual setup) and the untar it on the new mail server. Is there anything that dovecot on the new machine will complain about. Obviously I would tar everything, indexes etc. Just something I was wondering. Kind Regards Brent Clark

2 1

[Dovecot] a proposal to increase the stability
by Udo Rader 15 Nov '05

15 Nov '05

Hi, we've been using dovecot for the past 2 years or so for our 3K+ mail accounts and have never regretted our step. Yet from time to time there appear to be, how shall I say, "major" problems in the daemon that of course are no reason to whine and complain about because dovecot is OSS and everybody can do something about it. And that's where I would like to make a suggestion. From our own software projects I am used to the usage of extensive testing frameworks, like junit for java based applications. I almost completely lack knowledge about C/C++ programming, so I have no idea if something like this could be done for dovecot. For "the other end" of the mail chain I know dumbster, which is a fake SMTP server used for testing MUAs. So maybe something similar could be done for IMAP/POP3 servers? What I am thinking of is to run those tests before anything new is released. On the other hand I cannot even estimate how much work would be needed for this ... Udo Rader -- bestsolution.at EDV Systemhaus GmbH http://www.bestsolution.at

3 5

[Dovecot] Leftover mbox behavior from uw transition
by Adam Porter 15 Nov '05

15 Nov '05

Currently running dovecot 0.99.12 on a RHEL 3 server. This system used to use UW imap with mbox mailboxes, is now using dovecot with Maildir. (Actual user shell logins are not permitted.) Performance is tremendously improved. However, we still have users that have their client imap root set to the "mail" or "mail/" directory. (Can't reach/change them all easily.) As a result, people are still (inadvertently) creating/using mbox-style mailboxes (sent mail folders most often) on the dovecot server (dovecot of course handles them without complaining) which grow and hurt server performance. Now that we've figured this out, I think we could use mb2md in a script to convert these big mbox files to Maildir. (Is there a better way?) But what would be the smart way to prevent people from creating these mbox files and still have their client work correctly with their imap root set to "mail"? We currently use: default_mail_env = maildir:~/Maildir Thanks! -Adam

1 0

[Dovecot] entourage pop to dovecot imap migration
by wagner 15 Nov '05

15 Nov '05

I'm beginning to migrate my years of mail stuck in Entourage 2004 (MacOSX) to dovecot imap on Fedora FC4. No matter how I have tried I cannot get the status flags to migrate. Eg: all the mail, once transfered from the pop archive to the imap server looses all Status: and X-Status: flags and ends up being marked "new" on the imap side. After lots of testing it appears that, while simply having both pop and imap configured Entourage and dragging messages from the pop config to the imap area does move messages, all flags are lost. This also is the case if I export Entourage folders as mbox files and then import them into the imap server with Entourage or Mail.app. Has anyone else came upon this obstacle? Any advice? I am in the process now of gathering information to facilitate my own "migration utility". It seems the Entourage DB keeps the read/flagged/replied flags for each message in its own internals and doesn't deem it worthwhile to export them as part of it's mbox export nor retain them as Status or X-Status flags when moving messages from its pop DB to the imap server. I believe I can write a script to work on a set of found, for example, "replied to" messages to add an "X-Status: A" to their headers before moving them to the imap server. Same for "read" and "flagged" MS DB internals to Status/X-Status headers. With these headers added, moving them to the imap server, from my limited testing would seem to be the method to keep those status flags per message? Does dovecot use those flags or does it have its own means of storing that status information? Will it at least use those in the messages to populate its DB if it does have its own method? Flags I've identified so far: Status: O - old Status: RO - recent old(?) X-Status: A - replied to X-Status: F - flagged Thanks for any insight or suggestions. Mike -- "Beware the fury of the patient man."-Bukowski

2 1

[Dovecot] file istream-raw-mbox.c: line 450 (istream_raw_mbox_get_body_size): assertion failed: (rstream->mail_size != (uoff_t)-1)
by Tilman Linneweh 15 Nov '05

15 Nov '05

Hi list, Today i tried upgrading my dovecot server from 0.99.14 to 1.0alpha3. Unfortunately the new version does not work. The log file says: Oct 2 20:40:02 knut dovecot: imap-login: Login: user=<arved>, method=PLAIN, rip=213.225.30.218, lip=213.9.70.XXX, TLS Oct 2 20:40:02 knut dovecot: imap(arved): file istream-raw-mbox.c: line 450 (istream_raw_mbox_get_body_size): assertion failed: (rstream->mail_size != (uoff_t)-1) Oct 2 20:40:02 knut dovecot: child 98766 (imap) killed with signal 6 The Server is running on FreeBSD 5.4-STABLE, Client is Apple Mail 1.3.11 connecting via imaps. any ideas, whats wrong? regards tilman

3 2

[Dovecot] Dovecot IMAP error
by Marian Hercek 15 Nov '05

15 Nov '05

I am running Dovecot (IMAP and IMAPS), but still getting this error message in Outlook Express: "Access denied Code: 800cccd2". Code 800cccd2 means IMAP_TAGGED_NO_RESPONSE Message tagged. There are no errors in log files. What's the problem?

2 4

[Dovecot] process imap SIGSEGVs when getting STATUS on mbox box
by Andreas Fuchs 15 Nov '05

15 Nov '05

Hi, I just added an "archive" mbox namespace to my dovecot setup, so that people can put their old mail into a slightly more inode-friendly box. When querying the STATUS on one of these boxes, I got a sigsegv: Program received signal SIGSEGV, Segmentation fault. 0x0000000000454d24 in message_parse_header_next (ctx=0x59e500, hdr_r=0x7fbffff420) at message-parser.c:759 759 if (msg[0] == '\n' || (gdb) bac #0 0x0000000000454d24 in message_parse_header_next (ctx=0x59e500, hdr_r=0x7fbffff420) at message-parser.c:759 #1 0x00000000004297bb in mbox_sync_parse_next_mail (input=0x59e218, ctx=0x7fbffff670) at mbox-sync-parse.c:455 #2 0x000000000042ab9e in mbox_sync_loop (sync_ctx=0x7fbffff590, mail_ctx=0x7fbffff670, partial=0) at mbox-sync.c:118 #3 0x000000000042c187 in mbox_sync (mbox=0x597c70, flags=Variable "flags" is not available. ) at mbox-sync.c:1445 #4 0x000000000042cf3c in mbox_storage_sync_init (box=0x597c70, flags=0) at mbox-sync.c:1770 #5 0x000000000041a000 in imap_sync_nonselected (box=Variable "box" is not available. ) at imap-sync.c:177 #6 0x0000000000413022 in cmd_status (cmd=0x590ab8) at cmd-status.c:68 #7 0x0000000000414319 in _client_input (context=Variable "context" is not available. ) at client.c:338 #8 0x000000000045e4a6 in io_loop_handler_run (ioloop=0x58eca0) at ioloop-poll.c:190 #9 0x000000000045d9cf in io_loop_run (ioloop=0x58eca0) at ioloop.c:230 #10 0x000000000041b841 in main (argc=Variable "argc" is not available. ) at main.c:232 Mail server runs dovecot 1.0alpha4, is an amd64, linux 2.6.8-11 (debian testing). Mutt can parse the mailbox in question ok; seems that dovecot's mail header parser is broken somewhere. If there's anything else you need to debug this, shout (-: Thanks, -- Andreas Fuchs, <asf(a)boinkor.net>, asf(a)jabber.at, antifuchs

1 0

[Dovecot] inetd mode
by Alexander Sabourenkov 15 Nov '05

15 Nov '05

Hi. Inetd mode is broken as of cvs-20051111 After logging in on POP3 port imap binary is started. Seems like somehow master process receives wrong protocol id and thus starts wrong binary. -- ./lxnt

1 0

[Dovecot] problem with content-length and mbox parsing
by Glenn Leavell 15 Nov '05

15 Nov '05

The stars aligned recently such that I sent someone a message that contained a line similar to this in the message body: From glenn(a)usg.edu Thu Jun 20 16:48:11 2002 (Except that there wasn't that space character *before* the From; I've added it here to avoid any problems with this message). Dovecot wrote a copy of the message in my "sent mail" folder under the direction of my imap client. But when I went back to *read* that folder (still through Dovecot), it was broken and was presented as two corrupted mail messages. About a year ago, there was a thread on the list about the fact that Dovecot does not perform >From quoting when writing to mbox folders: http://dovecot.org/list/dovecot/2004-October/004865.html Timo, in that thread you mentioned the following about Dovecot's use of the content-length header: On Tue, Oct 05, 2004 at 05:13:36PM +0300, Timo Sirainen wrote: > Dovecot (and eg. mutt) uses Content-Length header to figure out how > large the message body is, so clients can't mess anything by sending > From-lines. Also Dovecot requires that From-line has correct syntax and > valid timestamp or it's not treated as From-line. In the example above, the message *does* include a valid content-length header after it is initially written, but Dovecot seems to ignore the header when reading the folder, and it treats the "From " line in the body as a message separator. For example, a SELECT on the folder will return "2 EXISTS" even if the single message described above is the only message in the folder. I'm currently at CVS 20051104. Glenn

1 0

[Dovecot] IMAP limitation
by Tom Allison 15 Nov '05

15 Nov '05

I was trying to delete a LOT of email messages in one shot from Thunderbird. I selected everything in a folder (>10,000) and then hit DELETE. I received an IMAP error. It clearly implied a limitation to just how many UIDS I can submit on an IMAP request at a time. Is this a limitation of dovecot? (I'm assuming it is). I can work around this, I think, because I haven't found a limitation to retrieving a list of email message UIDS as yet. I could thereby send splices or chunks of that list of UIDS to delete. I ran into this while trying to do a variety of obscene things in my attempts to develop a web mail application. Because of the number of strange tests I have, I don't really "blame" anything since I'm not sure that anyone really expects to delete 10,000 messages at one command.

1 0