I have experienced this on all versions of Dovecot that Ive used (1.0 -
1.1b6) using IMAP (its difficult to test if its also there with POP3).
What I see is that if there is a peak in disk usage at the time of a
specific request that requests stalls.
The saturation of disk I/O is momentary but
Im experiencing write activity thats somewhat different from my previous
qmail/courier-imap/Maildir setup.
This more outspoken in v.1.1.x than v1.0.x (Im using Maildir).
Write activity is about half that of read activity when measuring throughput.
But when measuring operations its about 5-7
Sorry for spamming the list today:)
Im getting a lot of these errors in the deliver log:
deliver([recipient]): [date] Info: sieve runtime error: Fileinto: Generic
Error
deliver([recipient]): [date]:18 Error:
sieve_execute_bytecode([path-to-sieve]) failed
deliver([recipient]): [date] Info:
On Sun, 2007-11-04 at 13:02 +0100, [EMAIL PROTECTED] wrote:
Write activity is about half that of read activity when measuring throughput.
But when measuring operations it’s about 5-7 times as high (measured with
zpool iostat on ZFS).
Have you tried with fsync_disable=yes? ZFS's fsyncing
On Sun, November 4, 2007 1:51 pm, Timo Sirainen wrote:
On Sun, 2007-11-04 at 13:02 +0100, [EMAIL PROTECTED] wrote:
Write activity is about half that of read activity when measuring
throughput. But when measuring operations itâs about 5-7 times as high
(measured with
zpool iostat on ZFS).
On Sun, 2007-11-04 at 14:10 +0100, [EMAIL PROTECTED] wrote:
Write activity is about half that of read activity when measuring
throughput. But when measuring operations it’s about 5-7 times as high
(measured with
zpool iostat on ZFS).
Have you tried with fsync_disable=yes? ZFS's
On Sun, November 4, 2007 2:20 pm, Timo Sirainen wrote:
Well, if you use only clients that don't really need indexes they could
just slow things down. You could try disabling indexes to see how it works
then (:INDEX=MEMORY to mail_location).
I tried that earlier and it did result in less
On Sun, November 4, 2007 2:54 pm, [EMAIL PROTECTED] wrote:
You could truss the hanging process to see what it's doing.
It's not an easy task since the delay is sometimes just a few (5-10)
seconds. And when there is a complete stall the client aborts before I can
find the process. But I'll
On Sun, 2007-11-04 at 15:27 +0100, [EMAIL PROTECTED] wrote:
chown([path]/Maildir/dovecot-uidlist, 105, -1) = 0
stat64([path]/Maildir/dovecot-uidlist, 0xFFBFF2F0) = 0
stat64([path]/Maildir/dovecot.index.log, 0xFFBFDAE0) = 0
chown([path]/Maildir/dovecot.index.log, 105, -1) = 0
Timo Sirainen wrote:
On Sat, 2007-11-03 at 14:20 +0100, Tom Sommer wrote:
After updating Dovecot,
From what version?
1.0 IIRC
one of my servers keep spamming these errors in
the log:
dovecot: Nov 03 14:14:18 Error: POP3([EMAIL PROTECTED]): Getting size of
message UID=4402
Tom Sommer wrote:
dovecot: Nov 03 14:14:18 Error: POP3([EMAIL PROTECTED]): Getting size of
message UID=4402 failed
dovecot: Nov 03 14:14:18 Error: POP3([EMAIL PROTECTED]): Getting size of
message UID=4402 failed
dovecot: Nov 03 14:14:18 Error: POP3([EMAIL PROTECTED]): Couldn't init
INBOX:
On Fri, Nov 02, 2007 at 12:12:05PM -0400, Adam McDougall wrote:
On Fri, Nov 02, 2007 at 06:04:12PM +0200, Timo Sirainen wrote:
On Mon, 2007-10-29 at 17:15 -0400, Adam McDougall wrote:
Sometimes when I login to dovecot and read a message from an imap maildir
folder,
the message
On Sun, Nov 04, 2007 at 11:28:36AM -0500, Adam McDougall wrote:
I noticed some sluggish message body fetches today that I don't think I've
seen before.
Each time I fetch a message from this particular mailbox (network/2007/01-Jan
for
my own record) it takes a few seconds, and mutt makes
Religious wars about which is best aside - some mail clients seem to
default to using Sent Items folder for saving sent mail, and others
(many) default to Sent.
Seems that in the interests of compatibility and doing the right thing
(tm) that a symlink from one folder to the other name would
Andrew Sackville-West wrote:
[SNIPPED]
actually, assuming you now have unstable in your sources.list, those
are packages currently installed for which there are updates available
(probably unstable updates...). Be careful or you'll end up farther
than you want.
I can't answer to the specifics
Jeff Grossman wrote:
Andrew Sackville-West wrote:
[SNIPPED]
actually, assuming you now have unstable in your sources.list, those
are packages currently installed for which there are updates available
(probably unstable updates...). Be careful or you'll end up farther
than you want.
I can't
Just a quick note: The new 1.1-b6 is working fine on OS X 10.5.
smime.p7s
Description: S/MIME cryptographic signature
17 matches
Mail list logo
