Hello Arnt,
> Why are these independent? Why would you want to have lots of
> different user names and passwords for owner-N2, N2,
> N2-unsub... etc?
>
> It seems to me that what you really want is an extended setactive
> command or cross-user includes.
owner-N2 and N2-request are not users, but addresses. To upload scripts
over managesieve it is not possible to give an address, one has first to
authenticate and then username=address. The "username" does not have to
belong to some user, as far as one authenticates with the "master user"
who can install global and private scripts for other users. There is no
password for the non-existent users N2-request, owner-N2. The latter are
addresses.
N2 is a mailing list and in consequence the addresses owner-N2,
N2-unsub... etc do exist. The scripts for that addresses do not have to
be independent, it can be the same script, however this are different
addresses, uncoupled from IMAP. Under this circumstances, the sieve
interpretation has either to find out that owner-N2 and N2-request are
supposed to have the same script (transited to imap terms, the addresses
end in the same mailbox), or to install scripts for each user
independently. In the latter case the sieve interpretation can consider
the owner-N2, N2-request etc as normal recipients and obtain their
scripts in the usual way. If the interpretation has to find out that
owner-N2 and N2-request are related, then it is first more difficult (to
integrate this information when uploading the script), and second the
scripts for owner-N2, N2-request etc are supposed to coincide. This is
not necessary.
About reauthentification:
> That makes it possible to drop privileges on authentication.
Could you explain this with a little bit more words?
Със здраве,
Дилян
Arnt Gulbrandsen schrieb:
Another response, independent.
Дилян Палаузов writes:
If for some reason a lot of sieve scripts are generated and need to be
uploaded, then the uploading application has to make several
connections to the managesieve server (using the same master authname
that can edit all scripts and different usernames). E.g. when the
scripts for a mailing list N2 are generated, the users owner-N2@, N2@,
N2-unsubscribe-request@, N2-subscribe-request@, N2-request@ need to be
uploaded in different connections to the managesieve server.
Why are these independent? Why would you wat to have lots of different
user names and passwords for owner-N2, N2, N2-unsub... etc?
It seems to me that what you really want is an extended setactive
command or cross-user includes.
Arnt