Re: fetching spam from users junk folder

Marcus Schopen via Info-cyrus <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <[email protected]>
Hi Nic,

Am Dienstag, den 06.12.2016, 11:25 -0600 schrieb Nic Bernstein:
> Marcus,
> In my original response I forgot to mention that for this, or any
> similar approach, to work, you need to use the misnamed "proxyservers"
> setting in imapd.conf to grant access to an administrative user.
>        proxyservers: <none>
>             A list of users and groups that are allowed  to  proxy  for  other
>             users,  separated  by  spaces.   Any  user  listed in this will be
>             allowed to login for any other user: use with caution.
> For example:
>         proxyservers: adminuser
> Or, alternately, assign rights to the appropriate mailboxes in cyradm:
>         > sam user.%.Should\ Be\ Spam adminuser all

Without using proxyservers I tried 

 setaclmailbox [email protected] [email protected] all

This works fine to give testuserb full access to testusera's Junk
folder. But I run virtual domains where I get this error message

setaclmailbox [email protected] [email protected] all
setaclmailbox: [email protected]: lrswipkxtea: Invalid identifier

How do I solve that? I found this in doc/text/install-virtdomains

      * Domains are mutually exclusive - Users only have access to
        mailboxes within their own domain (intra-domain). The following
        example will not work: setacl [email protected]
        [email protected] read. 

I don't want to work with a "Global administrator" with access to all
mailboxes and put that password in a script.

Ciao!

-- 
 ,---- [ Marcus Schopen ] 
|  (0>   
|  //\ 
|  V_/_  D-33602 Bielefeld
|        
 `----

----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.