Re: [Dovecot] Effects of going read-only on dovecot & pop/imap clients

2009-02-19 Thread Timo Sirainen
On Thu, 2009-02-19 at 17:10 +, Mark Zealey wrote: > > Are you talking about only POP3 clients? I suppose in theory it should > > be possible, but it's such a special case that I'm not going to bother > > making Dovecot support that. Dovecot really wants to create > > dovecot-uidlist files. But

Re: [Dovecot] Effects of going read-only on dovecot & pop/imap clients

2009-02-19 Thread Mark Zealey
> Are you talking about only POP3 clients? I suppose in theory it should > be possible, but it's such a special case that I'm not going to bother > making Dovecot support that. Dovecot really wants to create > dovecot-uidlist files. But I suppose you could just have it > create them > to some temp

Re: [Dovecot] Effects of going read-only on dovecot & pop/imap clients

2009-02-19 Thread Timo Sirainen
On Thu, 2009-02-19 at 14:17 +, Mark Zealey wrote: > 2009-02-19T14:03:19+00:00 mail2 dovecot: POP3(te...@markandruth.co.uk): > open() failed with file > /var/spool/mail/supplier_2/ma/rk/an/markandruth.co.uk/te/st/2_/test2/Mai > ldir/dovecot.index.log: Read-only file system .. > Even when I use :

[Dovecot] Effects of going read-only on dovecot & pop/imap clients

2009-02-19 Thread Mark Zealey
Hi all, We need to set our filestore to read-only for quite a while, and I want to mitigate the effects for our clients. First issue; dovecot. If we just change the nfs mounts to read-only, dovecot complains: 2009-02-19T14:03:19+00:00 mail2 dovecot: pop3-login: Login: user=, method=PLAIN, rip=10.