Re: Managesieve Reauthentification. Replication
2008-09-22 08:12:12
Дилян Палаузов wrote:
Hello,
Are there any reasons to include "Reauthentication is not supported by
ManageSieve protocol's profile of SASL. I.e. after a successfully
completed AUTHENTICATE command, no more AUTHENTICATE commands may be
issued in the same session." in draft-martin-managesieve-10/2.1
AUTHENTICATE Command ?
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. This is
less efficient than using the same managesieve connection and
reauthenticating from time to time. Now imagine that one wants to
regenrate the scripts for all lists on her server ... a lot of
connections need to be established. (A mailing list needs sieve script
that does SMTP rejects and hence saves one bounce at later time).
As per various discussions I've addressed your concern differently: I've
added a new UNAUTHENTICATE command/extension.
It is in extension, because I don't believe any existing client or
server would support the AUTHENTICATE command behavior you've suggested.
Moreover, if a domain has several MX DNS records, all scripts among
the mail servers shall be consistent to some extend. It would be
useful if the managesieve servers can use managesieve as protocol for
replication among each other. This could be achieved if the LISTSCRIPT
command (or a new command) can provide a timestamp when the script was
uploaded. And one more command shall allow the master user (the one
that can authenticate with different usernames) to list all users who
have uploaded scripts and the timestamp when the user last changed his
script. Going a step furhter, during the replication one server shall
be able to request the list of the users who changed their scripts
only after a given timestamp.
Speaking as an individual WG participant: if you write down a proposal
that includes ABNF, I would be happy to review it and to consider its
inclusion into the ManageSieve document.
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: Managesieve Reauthentification. Replication,
Alexey Melnikov <=
|
|
|