Re: [Dovecot] Errors in Dovecot 1.0.5
On Tue, Oct 30, 2007 at 04:23:36PM -0400, Jeff Tucker wrote: Hello, I am running Dovecot 1.0.5 and seem to have lots of errors in my Dovecot logs. The worst errors are things like: Oct 30 16:11:42 delta2 dovecot: IMAP(x): Corrupted transaction log file /home/spamcop-net2/deputies/dovecot.index.log: end_offset (392) > current sync_offset (388) Oct 30 16:11:42 delta2 dovecot: IMAP(x): file mail-index-sync-update.c: line 841 (mail_index_sync_update_index): assertion failed: (view->hdr.messages_count == map->hdr.messages_count) Oct 30 16:11:42 delta2 dovecot: IMAP(x): Raw backtrace: imap [0x462a7e] -> imap [0x46234c] -> imap(mail_index_sync_update_index+0x7b2) [0x44a982] -> imap(mail_index_sync_commit+0xe7) [0x447f87] -> imap(maildir_sync_index_finish+0xd2) [0x420b32] -> imap [0x4225af] -> imap(maildir_storage_sync_init+0x63) [0x4227b3] -> imap(imap_sync_nonselected+0xf) [0x41be9f] -> imap(_cmd_select_full+0xc5) [0x413f95] -> imap(cmd_select+0xb) [0x41411b] -> imap [0x415a87] -> imap [0x415b2c] -> imap(_client_input+0x75) [0x415cd5] -> imap(io_loop_handler_run+0xee) [0x4684ce] -> imap(io_loop_run+0x2d) [0x46797d] -> imap(main+0x3e3) [0x41d7b3] -> /lib/libc.so.6(__libc_start_main+0xdb) [0x2ace049b] -> imap [0x410cca] When this happens, my users just get timeouts trying to do stuff. I have my messages (maildirs) and indices all stored on NFS. For locking, I have mmap_disable = yes and lock_method = dotlock Do you have any idea what is going on here? In general, I get tons of errors about corrupted transaction log files for all users. Is this normal? Thanks Jeff Do you have more than one server accessing the same indexes on NFS? Without turning off the NFS access cache on each server (slow) thats a bad idea in 1.0. To get around this, I use this: mail_location = maildir:~/Maildir:CONTROL=%h/Maildir/dovecot/private/control:INDEX=/cache/dovecot/%u/private/indexes Where CONTROL is shared on NFS but INDEX is on a local partition. If the user doesn't access mail very often and logs into random servers, they run the chance of having an empty cache, but thats better than corruption and this has been working solidly for me. I'll be testing out 1.1 soon which when setup properly should allow sharing INDEX on NFS safely, not to mention more self healing. I would delete that users index files at the minimum.
[Dovecot] imaptest.c
Timo, can you, please, update imaptest.c to be compatible with recent 1.1 beta5 dovecot sources? -- WBR, Sergey Ivanov.
[Dovecot] MANAGESIEVE patch v8 for dovecot 1.0.7
Hello dovecot users, I have updated the MANAGESIEVE patch to the latest stable version of dovecot (1.0.7). This new version also adds extra configuration settings to explicitly specify the location of the sieve storage and the active sieve script. Additionally, the README now more clearly explains the configuration of the daemon. It currently won't compile with 1.1 due to significant changes in the master code. However, because 1.1 now approaches a stable release, the next version is going to be updated to version 1.1. Change Log V8 - + Fixed a few incompatibilities with 1.0.7 version. For instance, the "Logged in" message is now sent by the -login process and not by the managesieve daemon anymore. This caused a segfault every once in a while. + Probably fixed the settings problem reported by Steffen Kaiser regarding login_dir. 'dovecot -n' now reports correct results, but testing will show whether the whole problem is solved. + The managesieve daemon now accepts the sieve_storage and sieve configuration settings, so it is now possible to explicitly configure the location of the sieve storage and the active script respectively. The daemon still falls back to using the mail_location (MAIL) settings if nothing else is specified. + The cyrus timsieved does not use the + character in string literals and many clients have adopted to this behaviour. The latest managesieve (08) advises to accept a missing + from clients. The server should not send any + characters as well. This behavior is now implemented on the server. + Cleaned up sieve-storage.c: split up the sieve_storage_create function in various sub-functions for obtaining the various paths and directories. + Forced manual intervention if rescueing a non-symlink file at the active script path fails somehow. Previously, this presented the admin with a log message that it had just eaten the script, which is not very nice. + Restructured the README.managesieve file and added some more explanation with regard to the configuration of the daemon. This patch still includes (yet another) instance of the CMU Sieve source, as explained in one of my previous e-mails (http://dovecot.org/list/dovecot/2006-July/015016.html). The patch can be downloaded at: http://sinas.rename-it.nl/~sirius/dovecot-1.0.7-MANAGESIEVE-v8.diff.gz The README.managesieve is located in the root of the dovecot source tree after applying the patch. Have fun testing the patch. Don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch [EMAIL PROTECTED] IRC: Freenode, #dovecot, S[r]us
[Dovecot] Errors in Dovecot 1.0.5
Hello, I am running Dovecot 1.0.5 and seem to have lots of errors in my Dovecot logs. The worst errors are things like: Oct 30 16:11:42 delta2 dovecot: IMAP(x): Corrupted transaction log file /home/spamcop-net2/deputies/dovecot.index.log: end_offset (392) > current sync_offset (388) Oct 30 16:11:42 delta2 dovecot: IMAP(x): file mail-index-sync-update.c: line 841 (mail_index_sync_update_index): assertion failed: (view->hdr.messages_count == map->hdr.messages_count) Oct 30 16:11:42 delta2 dovecot: IMAP(x): Raw backtrace: imap [0x462a7e] -> imap [0x46234c] -> imap(mail_index_sync_update_index+0x7b2) [0x44a982] -> imap(mail_index_sync_commit+0xe7) [0x447f87] -> imap(maildir_sync_index_finish+0xd2) [0x420b32] -> imap [0x4225af] -> imap(maildir_storage_sync_init+0x63) [0x4227b3] -> imap(imap_sync_nonselected+0xf) [0x41be9f] -> imap(_cmd_select_full+0xc5) [0x413f95] -> imap(cmd_select+0xb) [0x41411b] -> imap [0x415a87] -> imap [0x415b2c] -> imap(_client_input+0x75) [0x415cd5] -> imap(io_loop_handler_run+0xee) [0x4684ce] -> imap(io_loop_run+0x2d) [0x46797d] -> imap(main+0x3e3) [0x41d7b3] -> /lib/libc.so.6(__libc_start_main+0xdb) [0x2ace049b] -> imap [0x410cca] When this happens, my users just get timeouts trying to do stuff. I have my messages (maildirs) and indices all stored on NFS. For locking, I have mmap_disable = yes and lock_method = dotlock Do you have any idea what is going on here? In general, I get tons of errors about corrupted transaction log files for all users. Is this normal? Thanks Jeff
Re: [Dovecot] Outlook can't see namespace folders
On Sat, Oct 27, 2007 at 08:30:57PM +0300, Timo Sirainen wrote: On Fri, 2007-10-05 at 12:12 -0700, James wrote: > Hi guys i understand that you can't subscribe to the Prefix names of > namespace folders right now with dovecot. > But for instance if i user outlook express and it can't see the prefix > name then it can't see the subfolders of that "prefix folder" either. > So even though it can detect and see the subfolders it won't display > them cause it can't see the "parent" > > Is there any fix for this? it's also kind of annoying in thunderbird but > at least you can still see the subfolders. Changed in v1.1: http://hg.dovecot.org/dovecot/rev/0511e301acbc There's no simple fix for v1.0 though. I am glad to see a patch. For 1.0, I was concerned with the same thing, and it turns out that the way our helpdesk was setting up Outlook Express was the same as the workaround I was going to suggest: Setup a seperate Account/profile in OE, set the mail folder prefix to your namespace prefix, then that seperate account will have an Inbox plus all of the folders in that prefix will be available for subscription and stay there. Also, as an alternative (not a very good one) I think you can see the folders in the subscribe window and double click to see them, then OE shows the whole tree for just that session until logout.
[Dovecot] Sieve 1.1.2 -> special chars
I'm unable to use local chars in vacation/auto replies with sieve. .dovecot.sieve.err gives the same error as when there's a parse error. Example of error: line 25: string 'æ ø å ö ä ü é á. ': My dovecot is v. 1.1b5 and sieve is v. 1.1.2. This issue was also present with dovecot 1.0.x Is there a way around this? - Mikkel
Re: [Dovecot] Sometimes Dovecot v1.0.3 does not accept new connections
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 29 Oct 2007, Timo Sirainen wrote:
On Mon, 2007-10-29 at 12:27 +0100, Steffen Kaiser wrote:
Do you have login_greeting_capability=yes?
No, I don't.
Then those patches probably don't help. How did you figure out it wasn't
giving a greeting? By manually with telnet or something? Did it show
that the connection was accepted?
Figure out:
I'm working with the MUA, when checking mail of different incoming folders
the connection (or better to open a new folder) becomes very slow or times
out. I do use another MUA for different things, which cannot connect at
all.
At this time I ssh to the mail server and telnet to local port 143. I get
a connect ("Connected to localhost"), but no greeting. When I keep the
telnet open, nothing happens. There is no greeting, even if the server
gets back into "normal" state, the telnet session simply stays so.
But if the connection doesn't even get accepted, then it sounds like
there are too few login processes for too many users and changing the
settings could help.
This is a) worth a try and b) not that bad anyway, because we have several
times a day about 30 users are instructed to read their mails
simultaneously.
Maybe, the connections come in too fast.
Bye,
- --
Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBRybtdi9SORjhbDpvAQLFjwgAoji6QJPJhTLAg+dSm9vSnG+1nFvlf524
5zQk5mS2fdfQy3zkD9q9odxOpZ+6T1MPnDoM2Ax8fJPLCsu2VVeranOAg1Cf8/mL
l/7+fF4QXX2efHaPzDdpyQe6iIzclyGEIaRTqolHESpp3QG9a6c7Mzz66UKQoHt5
w5NP07NQQI0Yqjt0V3SQLNzf7i4zMi41UGqZBDxvEjjtRmEkXHsTD+A7WU9y/Cfl
NsthjosVlcHf4TqMl+LTDkLDrX/TcKBA0wYxLbHhI42uEsz6ZffyVyqtFkJs0hrU
bqOpspYKzTIDfxqXF+Fg9H0TIeYeUS3eM1hDYj647el9ZTtgkAuA6g==
=DRzm
-END PGP SIGNATURE-
