similar to: mail looping

Under Dovecot 1.0-rc27 on Solaris 10 we noticed this error today affecting one of our users repeatedly: Mar 28 14:02:01 myhost dovecot: IMAP(myuser): file mbox-sync-rewrite.c: line 423 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 28 14:02:01 myhost dovecot: IMAP(myuser): Raw backtrace: 0x7ac54 -> 0x42cd4 -> 0x3e968 -> 0x3f54c -> 0x3f980

Okay, to convince myself that quota handling was working okay with Dovecot 1.0-rc27 on Solaris 10, I tested sending a message to an account that was purposely over-quota. The account in question had a vacation message set up. For the first test, there was no $HOME/.imap directory at all. I received the vacation message, but the message which was supposed to be delivered locally queued in Postfix

I just upgraded our test server from rc6 to rc10... ISSUE #1 I noticed that we no longer are getting two "From_" lines. However, the one that was good (had the original sender e-mail address) is now gone. The one with "dovecot.deliver" remains. I attempted to add "-d test" to the mailbox_command line in main.cf as follows: mailbox_command =

We've seen two issues come up with Dovecot LDA, both of which have caused us problems: 1) If the user's home directory does not exist, or is not owned by them, deliver fails and causes the mail message to bounce back to the originator. In our environment this happens when our user is moved to another server (where we move their files, but for up to 24 hours afterwards,

Here is another crash we've been seeing recently in rc15 on Solaris 10. (gdb) bt full #0 0xff1c12a4 in ?? () No symbol table info available. #1 0xff140040 in ?? () No symbol table info available. #2 0x000786a8 in t_buffer_alloc (size=688976) at data-stack.c:346 __PRETTY_FUNCTION__ = "file %s: line %" #3 0x00078190 in t_pop () at data-stack.c:149 frame_block = (struct

I am having difficulting getting to www.dovecot.org and wiki.dovecot.org. My browser tells me it can't find them. Anyone know what's up? -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs at umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

A few RC releases ago we had a problem where a user's restored home directory contained a .imap folder either from a previous RC release or perhaps it was a different server. In any event, restoration of the user caused problems since Dovecot choked on the restored .imap index files. Removing those index files cleared the problem. I'm wondering if this is still an issue, and therefore

We are running Dovecot 1.0-rc15 on Solaris 10 and are starting to ramp up our user count and ran into a file descriptor limit: Jan 1 19:38:54 <hostname> dovecot: IMAP(username): Newly created index file is corrupted: /home/username/.imap/foldername/dovecot.index.tmp Jan 1 19:38:54 <hostname> dovecot: IMAP(username): file mail-index.c: line 1806 (mail_index_move_to_memory): assertion

Anyone running Dovecot on Solaris, requiring only SSL connections, and servicing thousands of simultaneous users? Our past attempts to do so have failed due to dovecot-auth using up all 256 of its file descriptors. I say 256 since we are limited to that by the 32-bit libraries. We are looking at either compiling Dovecot in 64-bit and letting dovecot-auth file descriptors accumulate (not ideal),

On Sun, Oct 08, 2006 at 10:25:53PM +0300, Timo Sirainen wrote: > On Fri, 2006-10-06 at 21:00 -0500, Steven F Siirila wrote: > > I am running Dovecot 1.0-rc6 along with dovecot-sieve from 2006-10-05 CVS. > > I am calling dovecot deliver from Postfix (main.cf): > > > > mailbox_command = /opt/dovecot/libexec/dovecot/deliver > > > > Upon switching to dovecot

Upon rebooting our Dovecot server, I got these: Mar 16 09:49:16 peridot.tc.umn.edu dovecot: [ID 195972 local6.info] Dovecot v1.0.rc27 starting up Mar 16 09:49:18 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 16 09:49:18 myhost.mydomain last message repeated 1 time Mar 16 09:49:18 myhost.mydomain dovecot: pop3-login: Can't connect to

We are running Dovecot 1.0.0 using mbox format (currently in the midst of conversion from UW IMAP). We discovered today that the Dovecot LDA is accessing the user's INBOX at delivery time! Not only do our users rely on this access time being when they last accessed their e-mail, we also rely on it to migrate "inactive" users to cheaper disk. I consider this a major bug for us and

Running Dovecot 1.0-rc27 on Solaris 10.. We have been noticing intermittent messages of this sort and wondered if this indicates whether we need to add more dovecot-auth worker processes: Mar 28 03:15:41 myhost dovecot: pop3-login: Can't connect to auth server at default: Connection refused Mar 28 08:10:20 myhost dovecot: imap-login: Can't connect to auth server at default: Connection

Dovecot version: 1.0-0_33.rc15 built by atrpms Operating system: Redhat EL4 CPU architecture: x86 Filesystem you used: mailboxs via nfs to fileserver using xfs Just upgraded from 1.0-0_20.rc7 to 1.0-0_33.rc15 built by atrpms and we had previously set mbox_min_index_size to 1024 (1Mb) and now all mailboxes (mbox format) that are under this size are not able to be opened and throw an "Internal

We have been increasing our user count and have only run across these errors so far (dovecot-1.0.rc27): Mar 18 02:50:14 myhost.mydomain dovecot: pop3-login: Can't connect to auth server at default: Connection refused Mar 18 04:07:13 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 18 05:43:14 myhost.mydomain dovecot: pop3-login:

Hello, I have searched but have not found any information on logging imap actions. I want to log when someone uses imap to delete, move, copy, etc. This would greatly help me when someone deletes an email and asks where it went. I get this fairly often from a few users. Any help would be greatly appreciated. Thank you, Michael A. Painter Jr. -------------- next part

http://dovecot.org/releases/dovecot-1.0.rc31.tar.gz http://dovecot.org/releases/dovecot-1.0.rc31.tar.gz.sig mbox + NFS combination shouldn't break anymore. v1.0 still planned to be released next friday. - mbox: Give "mbox file was modified while we were syncing" error only if we detect some problems in the mbox file. The check can't be trusted with NFS. - Convert

http://dovecot.org/releases/dovecot-1.0.rc31.tar.gz http://dovecot.org/releases/dovecot-1.0.rc31.tar.gz.sig mbox + NFS combination shouldn't break anymore. v1.0 still planned to be released next friday. - mbox: Give "mbox file was modified while we were syncing" error only if we detect some problems in the mbox file. The check can't be trusted with NFS. - Convert

Abstract from http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy > > host=s: The destination server's *IP address*. This field is required. > Note that currently it's required to use an IP address since no DNS > resolving is done. > Hello Timo, Here goes one more item for the v2.0 wishlist: Will it become possible to do dovecot imap proxying based on a

Hi, Would anyone know what these errors mean? Running DoveCot RC15 on RedHat ES 4 Dec 1 17:30:53 serv-01 dovecot: pop3-login: file client.c: line 423 (client_unref): assertion failed: (client->destroyed) Dec 1 17:31:21 serv-01 dovecot: pop3-login: file client.c: line 423 (client_unref): assertion failed: (client->destroyed) Dec 1 17:31:25 serv-01 dovecot: pop3-login: file client.c: