Re: Shared folder acl

Albert Shih <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <[email protected]>
Le 13/11/2024 à 13:02:28+0100, Michael Menge a écrit
> Hi,
> 
> Quoting Albert Shih <[email protected]>:
> 
> > Le 12/11/2024 à 15:57:19+0100, Jean Charles Delépine via Info a écrit
> > > Albert Shih <[email protected]> écrivait (wrote) :
> > 
> > Hi,
> > 
> > > > Is it correct the shared (in server side) mailbox need a
> > > >   anyone p
> > > > acl to be able to receive incoming mail ? I find that a little strange
> > > > knowing the configuration contain the user
> > > >
> > > > postuser: sharembxaccount
> > > >
> > > > why do we need allow «anyone» to post a email ? Why not just
> > > > sharembxaccount ?
> > > 
> > >   postuser: <empty string>
> > >        Userid  used  to  deliver messages to shared folders.  For
> > >        example, if set to "bb", email sent to "bb+shared.blah" would be
> > >        delivered to the "shared.blah" folder.  By default, an email
> > >        address of "+shared.blah" would be used.
> > > 
> > > postuser is just a cosmetic facility. If it's empty mail to
> > > "+shared.blah" are going to the shared box.
> > > 
> > > The anyone p right is to give cyrus's postuser the right to post in
> > > folders addressed with plus-address, like this "+shared.blah" :
> > > 
> > > Faq of cyrus 2.2 (I can't find the same info in modern doc) :
> > > https://web.mit.edu/ghudson/dev/nokrb/third/cyrus-imapd/doc/faq.html
> > > 
> > >  plus addressing - Plus addressing allows direct delivery to a
> > >  particular mailbox (other than an INBOX). This is done in two ways.
> > > 
> > >  The first way allows delviery to a subfolder of a specific user's
> > >  INBOX. This is done via an address of the form:
> > >  username+mailfolder@domain, which will deliver to the user's
> > >  INBOX.mailfolder folder (or altnamespace equivalent). This submailbox
> > >  must allow the posting user the 'p' right (generally, this means
> > >  'anyone' must have the 'p' right), otherwise the message will just be
> > >  filed into the user's INBOX.
> > > 
> > >  The second way is to form an address like [postuser]+mailfolder@domain.
> > >  This will deliver into the mailbox 'mailfolder'. [postuser] is the
> > >  string specified in the imapd.conf option of the same name, and may be
> > >  the empty string. As before, the posting user will need to have the 'p'
> > >  right on the mailbox.
> > > 
> > 
> > Yes...this is the way I find more satisfying (intellectually), I have
> > 
> >   root@imap:/etc# grep postuser imapd.conf
> >   postuser: cyrus_shared_account
> > 
> > and
> > 
> >   grep root@mx:~# grep test.share /etc/mail/aliases.all
> >   test.share:
> > [email protected]
> > 
> > and on the server
> > 
> >   127.0.0.1> lam shared.test_share
> >   cyrus_shared_account p
> > 
> > I've even try all right
> > 
> >   127.0.0.1> lam shared.test_share
> >   cyrus_shared_account lrswipkxtecdan
> >   127.0.0.1>
> > 
> > but not success either
> 
> the mail is not posted by cyrus_shared_account but by the unauthenticated
> lmtp or delivery process.

Ok. Understand. 

> also the "p" acl for anyone is not as problematic, as it is only used for
> mails delivered by lmtp or

Ok. But in that case why in «normal» mailbox :

  user.toto

we only need acl for toto and not anyone ? 

How cyrus will know «it's toto» who going to use lmtp to deliver the email
in the «user.toto» mailbox ? 

Of course it's not a big deal, I can live with acl “anyone p” on all my
shared mailbox, it's just I find that very weird. 


> the delivery binary. For Mails inserted by the APPEND or the COPY imap
> commands the "w" or "i" ALCs are
> checked

Ok thanks. 


Regards.

-- 
Albert SHIH 🦫 🐸
France
Heure locale/Local time:
jeu. 14 nov. 2024 11:18:49 CET

------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/T22db9b7c090b8bf6-Md01b145f4df7a74c3d6a0624
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
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.