[Dovecot] Deleting a message through IMAP
I have been having a problem with the test releases...I am now using Test 59. When I delete a message using SquirrelMail (IMAP) the message stays in the message list....but you can't open it anymore because it can't be found, if I logout and log back in...the message is gone from the list. I thought it could be a problem with the cache, so I added
mail_never_cache_fields = MessagePart Envelope Body
only to recieve
Dec 24 09:23:34 news dovecot: IMAP(admin): mail_never_cache_fields: Invalid cache field name 'Body', ignoring
Any ideas? This problem has plagued me for a while and I always go back to using the and older test like 22 and the problem isn't there...
Doug
Hello,
From: "Doug Eubanks" <doug@simflex.com> Subject: [Dovecot] Deleting a message through IMAP Date: Fri, 24 Dec 2004 10:19:18 -0500 (EST)
the cache, so I added
mail_never_cache_fields = MessagePart Envelope Body
only to recieve
Dec 24 09:23:34 news dovecot: IMAP(admin): mail_never_cache_fields: Invalid cache field name 'Body', ignoring
It seems to be a problem that dovecot-example.conf isn't updated with sources. Now, 'mail_cache_fields' and 'mail_never_cache_fields's field names are changed. Use a list of followings:
flags, date.sent, date.received, size.virtual, size.physical, imap.body, imap.bodystructure, imap.envelope, mime.parts, mail.uid
best regards,
Kazuo Moriwaka moriwaka@valinux.co.jp
On Fri, 2004-12-24 at 10:19 -0500, Doug Eubanks wrote:
mail_never_cache_fields = MessagePart Envelope Body
I updated its comment now:
# Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable.
participants (3)
-
Doug Eubanks
-
Kazuo Moriwaka
-
Timo Sirainen