Hello,
When a message is copied or newly-delivered to a folder, it does not
have the "recent" flag set. Is there something in the configuration to
activate it ?
Thanks.
# dovecot -n
# 1.0.9: /usr/local/etc/dovecot.conf
protocols: imap
login_dir: /var/run/dovecot/login
login_executable: /usr/local/libexec/dovecot/imap-login
mail_location: mbox:~/mail:INBOX=~/mail/INBOX:INDEX=/var/cache/dovecot
mbox_write_locks: fcntl
auth default:
passdb:
driver: pam
userdb:
driver: passwd
The MUA which shows it is Alpine 0.999999.
--
Nicolas
On Wed, 2007-12-12 at 12:06 +0100, Nicolas KOWALSKI wrote:> When a message is copied or newly-delivered to a folder, it does not > have the "recent" flag set. Is there something in the configuration to > activate it ?Looks like it's buggy with v1.0 + mbox + mbox_lazy_writes=yes. I think I won't bother trying to fix it for v1.0, since it probably requires too large changes. I did now fix one related bug for v1.1, and I've yet to fix it for maildir with v1.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20071221/e31d9d16/attachment-0002.bin>
On Fri, 21 Dec 2007, Timo Sirainen wrote:> On Wed, 2007-12-12 at 12:06 +0100, Nicolas KOWALSKI wrote: > > > When a message is copied or newly-delivered to a folder, it does not > > have the "recent" flag set. Is there something in the configuration > > to activate it ? > > Looks like it's buggy with v1.0 + mbox + mbox_lazy_writes=yes. I think > I won't bother trying to fix it for v1.0, since it probably requires > too large changes. > > I did now fix one related bug for v1.1, and I've yet to fix it for > maildir with v1.1.Ok, I will use the 1.1 series. Thanks for your reply, -- Nicolas