On Wed, 2011-09-14 at 09:12 +0200, Jan-Frode Myklebust wrote: > One of our dovecot-servers (v2.0.14) got a bit too busy last evening: > > Sep 13 20:39:18 popimap1 dovecot: master: Warning: service(pop3-login): > process_limit reached, client connections are being dropped > > then logged a few: > > Sep 13 20:39:20 popimap1 dovecot: pop3(xxxxxx...@yyyyy.yy): Warning: > I/O leak: 0x3829233d20 (10) > Sep 13 20:39:20 popimap1 dovecot: pop3(xxxxxx...@yyyyy.yy): Warning: > Timeout leak: 0x3829233ce0
Could you show the output of: gdb /usr/local/libexec/dovecot/pop3 # or whatever path it is in x 0x3829233d20 x 0x3829233ce0 I guess the client isn't being destroyed properly for some reason.. > but what has me a bit worried is these: > > imap(u...@xxx.xxx): Warning: Subscriptions file > /path/to/u...@xxx.xxx/subscriptions: Removing invalid entry: .Sent > imap(u...@xxx.xxx): Warning: Subscriptions file > /path/to/u...@xxx.xxx/subscriptions: Removing invalid entry: .Spam > imap(u...@xxx.xxx): Warning: Subscriptions file > /path/to/u...@xxx.xxx/subscriptions: Removing invalid entry: .Drafts > imap(u...@xxx.xxx): Warning: Subscriptions file > /path/to/u...@xxx.xxx/subscriptions: Removing invalid entry: .Trash These are simply broken subscription entries that have never worked. They're not supposed to begin with a ".". In older Dovecot versions they were shown to clients, but I don't know what clients would have done with such broken entries. I guess some could have shown them "correctly", some could have shown them in a broken way and some could have just ignored them.
