I have been getting these assertion failures every couple days, killing
the IMAP process. After it happens, I can login immediately and
everything is fine until it happens again. Here is the log entry:
Sep 10 10:03:41 mailbox-4 dovecot: nh: IMAP(username): file
mail-index-view-sync.c: line 6
On Thu, 6 Sep 2007, Marcin Michal Jessa wrote:
I do use prefetch, I have an separate query, too. Without that the
quota fails completely.
Having both statements and prefetch, the quota works fine with IMAP
and deliver when I have no quota line in the plugin section, when I
add the line (see !!MA
Dovecot 1.0.2 patches and compiles fine with the quota warning patch
(http://www.dovecot.org/patches/quota-warning.patch). But, when parsing
the configuration file , deliver now seems to strip all of the spaces in
the QUOTA_WARNING environment variable, generating an error.
This is the plugin
On Thu, 12 Jul 2007, Timo Sirainen wrote:
So still nothing usable. Updated nfstest.c once again to include
fdatasync() test. It has to work.
fdatasync() isn't implemented in FreeBSD (see
http://www.freebsd.org/cgi/query-pr.cgi?pr=64875). It defaults to
mapping fdatasync() to fsync().
Resul
On Thu, 12 Jul 2007, Timo Sirainen wrote:
Thanks, could you try once more with an updated nfstest.c version? I
added "dup+close" which works for data and write cache flushing with
Linux. I really hope it works with Solaris+FreeBSD too.
I didn't expect fchown() to flush write cache, but since du
On Thu, 12 Jul 2007, Timo Sirainen wrote:
On Wed, 2007-07-11 at 15:43 -0700, Doug Council wrote:
Here are the results for FreeBSD 6.2-RELEASE-p5 and a NetApp NFS server.
FYI, the fcntl errors also appeared on the server instance.
..
Error: fcntl(setlk, read) failed: Operation not supported
On Thu, 12 Jul 2007, Timo Sirainen wrote:
Hmm. I updated the nfstest.c to now just retry if this happens. Does it
help?
Yes, that worked.
Here are the results for FreeBSD 6.2-RELEASE-p5 and a NetApp NFS server.
FYI, the fcntl errors also appeared on the server instance.
Info: Connected: cli
On Thu, 12 Jul 2007, Timo Sirainen wrote:
On Wed, 2007-07-11 at 22:21 +0300, Timo Sirainen wrote:
http://dovecot.org/tools/nfstest.c
I've done several updates for this. Updated results for Linux 2.6:
Different result this time:
Info: Connected: client
Info: O_EXCL works
Info: Testing attribu
On Wed, 11 Jul 2007, Timo Sirainen wrote:
http://dovecot.org/tools/nfstest.c
Results for FreeBSD 6.2-RELEASE-p5 clients using a NetApp NFS server:
Info: Connected: client
Info: Testing attribute cache..
Info: Attr cache flush fchown(-1, -1): OK
Info: Attr cache flush fchown(uid, -1): OK
Info:
On Jun 21, 2007, at 7:56 PM, Tony Tsang wrote:
I have some machines running FreeBSD and dovecot deployed. User's home
dir is on NFS mount and I've found that dovecot only works with
dotlock file locking mechanism, fcntl and flock failed. Now it causes
problem with thunderbird (thunderbird is cach
On Fri, 25 May 2007, Nicolas Boullis wrote:
As I wrote the patch, I do. ;-)
Always good to go to the source :)
The warning is triggered when the free space goes below the specified value,
not when the used space goes above. Hence, if you have no limit on the
message count, no warning on the
I am testing out the unofficial quota warning patch with Dovecot 1.0.0,
and no matter what values I use for the storage or messages values, the
warning script is never executed.
My plugin settings are:
plugin {
quota = maildir:storage=20480
quota_warning = storage=80%:messages=10 /usr/loca
On May 20, 2007, at 5:43 PM, Timo Sirainen wrote:
If the lock file is really stale, updating mtime might cause the
lock to
never be overwritten.
Would it work if you chown()ed the lock file to its current uid/gid
(that lstat() returned) instead?
Yes, that worked as well. I've attached the
thing
has worked as expected for all Dovecot control files, including indexes.
Does anyone know of any side effects the forced mtime update may have
that I may not be seeing?
Thanks again for any assistance.
-Doug
file-dotlock.c.diff
Description: Binary data
On May 17, 2007, at 10:4
We are in the process of migrating away from Courier-IMAP/POP3 and
Maildrop. I want to use Dovecot (LDA, IMAP, POP3). During my testing, it
has worked great except for dotlocking on the dovecot-uidlist file.
The problem:
When a delivery is being made with deliver and a mail client has the
m
15 matches
Mail list logo
