Re: [Dovecot] sporadic slow/non response, problems copying to sent folder
On Fri, 2007-05-04 at 09:23 -0700, Danno Coppock wrote: > May 3 21:32:08 tejas dovecot: IMAP(annie): Disconnected for inactivity I don't think these should happen. Do you have a stateful firewall killing the idling connections? The slowdowns would then be caused by the client waiting for a reply from the server which never comes because firewall is blocking the connection. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] sporadic slow/non response, problems copying to, sent folder
Danno Coppock wrote: facts: * There was only one active client. * The client was T'bird, v1.5.0.10, running on XP. Danno, I saw some issues like this for a while, months ago, but concluded that it was a Thunderbird issue rather than a Dovecot issue. For diagnostic purposes, can you try Outlook Express and see whether the same operations go faster? There are some strange IMAP and mail-server-related settings in Thunderbird - not well documented - which might be worth experimenting with. John -- John Allen Bofferdange, Luxembourg [EMAIL PROTECTED] http://www.homepages.lu/allen
Re: [Dovecot] sporadic slow/non response, problems copying to, sent folder
symptoms: 1. Coming back to the idle client, and clicking on a newly arrived message, often a long delay (seems like minutes, sometimes) will occur before the message loads from the server. 2. Sending messages, as often as not, the client will stall, sometimes indefinitely, on "copying message to sent folder". Does this happen when using a client which is on the same LAN as the server? This kind of behavior looks like a network issue. You called it. We access the server over the Internet. How did I forget to provide that small detail? However, that's not the slowness I speak of. Perhaps a better term is long delay, like waiting on some timeout, before message loadding (in symptom 1., above). So are there parameters to tune, that will make dovecot behave nicer? I do not believe this to be connectivity outages between our clients and the server. For one, we never experienced these symptoms with UW-IMAP. I just duplicated the stall on copying to Sent folder. This is probably the more prevalent, and annoying of the two problems. facts: * There was only one active client. * The client was T'bird, v1.5.0.10, running on XP. * This particular test had a 3Mb attachment. * The mail was delivered immediately to the single, remote recipient (after a ~20 seconds of 3Mb upload). * The "Copying to Sent Folder" dialog stayed up for (no exaggeration) 15-minutes, and then completed; the message is in the Sent folder now. suspicion, from months of experiencing the behavior: * Attachments are usually involved. How does the config look? Are the mbox lock settings appropriate? I was somewhat shooting in the dark there. * Sendmail 8.13.6/8.13.6 * $sudo sendmail -bt -d0.10 < /dev/null | grep HASFLOCK OS Defines: BSD4_4_SOCKADDR HASFCHOWN HASFCHMOD HASFLOCK mbox_read_locks = flock mbox_write_locks = flock What else can I provide? netstats? tcpdumps? Are there logs/debugging appropriate to enable? Thanks for any ideas, Danno
Re: [Dovecot] sporadic slow/non response, problems copying to sent folder
On Fri, 04 May 2007 09:23:02 -0700 Danno Coppock <[EMAIL PROTECTED]> wrote: > After experiencing these symptoms through many of the release > candidates, we've been at v1.0.0 now for a few weeks, and they're > still there. Perhaps a config issue with my setup (mbox locks?). > It's really too disrupting to continue using this way. I've included > symptoms, client info, mta info, log entries and config file. What > other information can I provide? Please advise. > > Thanks, Danno > > symptoms: > > 1. Coming back to the idle client, and clicking on a newly arrived > message, often a long delay (seems like minutes, sometimes) will > occur before the message loads from the server. > 2. Sending messages, as often as not, the client will stall, > sometimes indefinitely, on "copying message to sent folder". Does this happen when using a client which is on the same LAN as the server? This kind of behavior looks like a network issue. -- Marshal Newrock Ideal Solution, LLC - http://www.idealso.com
[Dovecot] sporadic slow/non response, problems copying to sent folder
After experiencing these symptoms through many of the release
candidates, we've been at v1.0.0 now for a few weeks, and they're still
there. Perhaps a config issue with my setup (mbox locks?). It's really
too disrupting to continue using this way. I've included symptoms,
client info, mta info, log entries and config file. What other
information can I provide? Please advise.
Thanks, Danno
symptoms:
1. Coming back to the idle client, and clicking on a newly arrived
message, often a long delay (seems like minutes, sometimes) will occur
before the message loads from the server.
2. Sending messages, as often as not, the client will stall, sometimes
indefinitely, on "copying message to sent folder".
client:
* usually not more than 2-3 clients running at any time.
* Thunderbird 1.5.0.10 (on XP)
* Thunderbird 1.5.0.5 (on FreeBSD 5.5)
mta:
* Sendmail 8.13.6/8.13.6
* $sudo sendmail -bt -d0.10 < /dev/null | grep HASFLOCK
OS Defines: BSD4_4_SOCKADDR HASFCHOWN HASFCHMOD HASFLOCK
=== log entries
May 3 21:27:09 tejas dovecot: imap-login: Login: user=,
method=PLAIN, rip=71.216.71.193, lip
=68.224.168.249, TLS
May 3 21:28:00 tejas dovecot: IMAP(annie): Disconnected
May 3 21:28:01 tejas dovecot: imap-login: Login: user=,
method=PLAIN, rip=71.216.71.193, lip
=68.224.168.249, TLS
May 3 21:32:08 tejas dovecot: IMAP(annie): Disconnected for inactivity
May 3 21:37:01 tejas dovecot: IMAP(annie): Disconnected
May 3 21:37:02 tejas dovecot: imap-login: Login: user=,
method=PLAIN, rip=71.216.71.193, lip
=68.224.168.249, TLS
May 3 21:37:55 tejas dovecot: IMAP(annie): Disconnected in IDLE
May 3 21:38:18 tejas dovecot: IMAP(annie): Disconnected in IDLE
May 3 21:56:02 tejas dovecot: imap-login: Login: user=,
method=PLAIN, rip=71.216.71.193, lip
=68.224.168.249, TLS
May 3 21:56:17 tejas dovecot: IMAP(annie): Disconnected for inactivity
May 3 21:58:32 tejas dovecot: IMAP(danno): Disconnected
May 3 22:02:31 tejas dovecot: imap-login: Login: user=,
method=PLAIN, rip=71.216.71.193, lip
=68.224.168.249, TLS
May 3 22:03:14 tejas dovecot: imap-login: Login: user=,
method=PLAIN, rip=71.216.71.193, lip
=68.224.168.249, TLS
May 3 22:14:10 tejas dovecot: IMAP(annie): Disconnected
May 3 22:14:38 tejas dovecot: IMAP(danno): Disconnected in IDLE
May 3 22:16:24 tejas dovecot: imap-login: Login: user=,
method=PLAIN, rip=71.216.71.193, lip
=68.224.168.249, TLS
May 3 22:16:33 tejas dovecot: imap-login: Login: user=,
method=PLAIN, rip=71.216.71.193, lip
=68.224.168.249, TLS
May 3 22:16:44 tejas dovecot: imap-login: Login: user=,
method=PLAIN, rip=71.216.71.193, lip
=68.224.168.249, TLS
May 3 22:18:36 tejas dovecot: imap-login: Login: user=,
method=PLAIN, rip=71.216.71.193, lip
=68.224.168.249, TLS
May 3 22:19:16 tejas dovecot: IMAP(danno): Disconnected
May 3 22:19:17 tejas dovecot: imap-login: Login: user=,
method=PLAIN, rip=71.216.71.193, lip
=68.224.168.249, TLS
= config
$grep -E -v '^ *(#|$)' dovecot.conf
protocols = imaps
login_process_size = 64
default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u
mail_extra_groups = mail
verbose_proctitle = yes
first_valid_uid = 100
first_valid_gid = 0
mbox_read_locks = flock
mbox_write_locks = flock
protocol imap {
imap_client_workarounds = delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
}
protocol pop3 {
pop3_uidl_format = %08Xu%08Xv
pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
}
protocol lda {
postmaster_address = [EMAIL PROTECTED]
sendmail_path = /usr/sbin/sendmail
}
auth default {
mechanisms = plain
passdb pam {
}
userdb passwd {
}
user = root
}
dict {
}
plugin {
}
