Cyrus imap delivery is abstracted from unix user, you can have imap
users who doesn't exist in unix passwd or equivalent cause cyrus support
a great variety of auth backends.
While is always user cyrus that, under O.S. aspects runs imapd and sieve
processes, in its internal cyrus respect the im
Hi Rob,
Adding the p permission to the mailbox sorted out the problem. I must
admit it seems strange as it is cyrus user that is running at the time
i.e. sieve, and it could post to the user.mark folder but not any
subfolders. Even though they had the same permissions. I dont quite
understand how
Hi Mark
I think that in INBOX.XXX the "p" permission is missing so the user mark
can't post messages in INBOX.XXX
Try to change permission to "lrswicdp"
bye
Paolo
Mark Clarke wrote:
Hi there,
I am new to cyrus and sieve. I have setup the following sieve script
require ["fileinto","reject"];
if ad
Mark,
A point of clarification: is the permissions problem writing to the
folder or executing the script? Also, is the folder user.mark.XXX
owned and writable by the cyrus user? You mat be looking at UNIX
system permission issues and not cyrus issues.
-- Rob
--On Monday, January 10, 2005 08:20
Hi there,
I am new to cyrus and sieve. I have setup the following sieve script
require ["fileinto","reject"];
if address :domain contains: "To" "XXX.abc.org"
{
fileinto "INBOX.XXX";
}
When i run this script I can see that the rule is applied but according
to the logs "permission is d
