[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
draft-ietf-sieve-managesieve-00.txt is to replace draft-martin-managesieve-12.txt
I've posted draft-ietf-sieve-managesieve-00.txt yesterday.
It has some relatively minor changes from draft-martin-managesieve-12.txt:
1). Addition of the WARNINGS response code (as per comment from Stephan
2). Addition of the MAXREDIRECTS capability (as per discussion on the
3). Updates/fixes to some examples (as per Chris Newman's review, etc.)
4). Added IANA registrations of some missing response codes
I only have 2 open issues outstanding:
1). Update to Sieve URL scheme based on Chris Newman's proposal. Based
on the discussion on the mailing list I believe there is rough consensus
to make the change, i.e. to add "authorized user" just before the script
name, but it would be optional. I will send a separate message on this
so that it is clear to everyone what change I will be implementing.
2). Stephan Bosch suggested that some deployments would like to have
script verification mode, without allowing SASL ANONYMOUS. I.e. only to
allow script verification by registered users of the service (SASL
ANONYMOUS would allow *any* user, even not registered on the system, to
perform script validation). ManageSieve used to have such mode by
allowing the empty string as the script name in PUTSCRIPT, but it was
taken out, because I felt at the time that SASL ANONYMOUS was a cleaner
design. Now that I understand that the two mechanisms have different
applicability, I would like to hear WG opinion on this issue.