On 11/16/2010 10:52 AM, Timo Sirainen wrote:
On Sat, 2010-11-13 at 11:27 -0800, RParr wrote:
I quess deliver still does not support include?
In v2.0 yes, in v1.x no.
Does deliver honor multiple -c options?
No.
Or does deliver's lack of include support mean I must put all dovecot
config in one file? (eg /etc/dovecot/dovecot.conf)
Yeah.
11/13/10 11:14:39 am n3 dovecot deliver(tarts): utime() failed
with mbox file /var/mail/public/SPAM/SPAMMM: Operation not permitted
Fixed for v2.0: http://hg.dovecot.org/dovecot-2.0/rev/3daec8435d29
http://hg.dovecot.org/dovecot-2.0/rev/586d549732f5
You can do basically the same for v1.2 (or just ignore the errors -
everything works anyway).
I applied the change referenced above to 1.2.9
src/lib-storage/index/mbox/mbox-file.c
I continued to get the errors.
I then expanded the error message output for all calls to utime() in all
files in src/lib-storage/index/mbox
and found the errors were coming from mbox-save.d and mbox-sync.c
11/23/10 04:40:55 pm n3 dovecot IMAP(tarts): mbox-save: utime()
failed with mbox file /var/mail/public/test4: Operation not permitted
11/23/10 04:40:55 pm n3 dovecot IMAP(tarts): mbox-sync: 2:
utime() failed with mbox file /var/mail/public/test4: Operation not
permitted
11/23/10 04:40:55 pm n3 dovecot IMAP(tarts): mbox-save: utime()
failed with mbox file /var/mail/public/test4: Operation not permitted
11/23/10 04:40:55 pm n3 dovecot IMAP(tarts): mbox-sync: 2:
utime() failed with mbox file /var/mail/public/test4: Operation not
permitted
11/23/10 04:40:55 pm n3 dovecot IMAP(tarts): mbox-save: utime()
failed with mbox file /var/mail/public/test4: Operation not permitted
11/23/10 04:40:55 pm n3 dovecot IMAP(tarts): mbox-sync: 2:
utime() failed with mbox file /var/mail/public/test4: Operation not
permitted
11/23/10 04:40:55 pm n3 dovecot IMAP(tarts): mbox-save: utime()
failed with mbox file /var/mail/public/test4: Operation not permitted
11/23/10 04:40:55 pm n3 dovecot IMAP(tarts): mbox-sync: 2:
utime() failed with mbox file /var/mail/public/test4: Operation not
permitted
Note the errors are only occuring when copying/moving a message into a
public box owned by someone else even though the box and both users are
part of the same group.
I can modify the calls to utime() in mbox-save.c and mbox-sync.c to
ignore the EPERM errors
but I first wanted to verify that was reasonable.
Please let me know if I should proceed with those changes or if there is
a better solution.
Thanks for all you help
R.Parr, RHCE, Temporal Arts
