Am 28.06.2004 um 12:42 Uhr +0300 schrieb Timo Sirainen:
Oh. This all pretty much sounds like Dovecot sees users INBOX as read-only so it won't modify flags and won't expunge messages.
You could check this with eg. telnet:
telnet localhost imap2 x login user pass x select inbox
and see if it sends READ-ONLY or READ-WRITE tag.
I think the only reason for it to be treated as read-only is if the file permissions really are such.
From /etc/dovecot.conf:
# Sync this with "DEFAULT" in /etc/courier/maildroprc default_mail_env = mbox:~/Mail/:INBOX=%h/Mail/INBOX
[hf@bounce] ~ > cd Mail [hf@bounce] ~/Mail > ll INBOX 27008 -rw------- 1 hf spgmit 27610472 Jun 28 12:00 INBOX [hf@bounce] ~/Mail > telnet localhost imap2 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'.
- OK dovecot ready. x login hf XXXXXXXX x OK Logged in. x select inbox
- FLAGS (\Answered \Flagged \Deleted \Seen \Draft NotJunk Junk NonJunk)
- OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NotJunk Junk NonJunk \*)] Flags permitted.
- 604 EXISTS
- 3 RECENT
- OK [UNSEEN 573] First unseen.
- OK [UIDVALIDITY 1054653796] UIDs valid
- OK [UIDNEXT 5280] Predicted next UID x OK [READ-WRITE] Select completed.
Hum...
hauke-- Institut für Nachrichtentechnik /~\ The ASCII Ribbon Campaign FG Signalverarbeitung \ / No HTML/RTF in email TU Darmstadt X No Word docs in email Ruf +49-6151-16-3281, Fax -3778 / \ Respect for open standards