9 Dec 2002 20:00
managesieve comments
Cyrus Daboo <daboo <at> cyrusoft.com>
2002-12-09 19:00:10 GMT
2002-12-09 19:00:10 GMT
Some comments on the managesieve -04 draft based on client implementation
experience:
Comments on Manage SIEVE
- According to the current IANA registry port 2000 is already assigned to
'callbook'. Looks like we have to pick another default port?
- STARTTLS command description still has text stating that server must send
capability items.
- 'sieve-name' item in formal syntax is just defined as 'string'. Why not
just use 'string' instead? If you want to impose the semantic script name
requirement, then the 'sieve-name' item should have a comment with a
reference to section 1.7.
- 'command-authenticate' is missing the mandatory CRLF at the end. The
correct syntax should be:
command-authenticate = "AUTHENTICATE" SP auth-type [SP string]
*(CRLF string) CRLF
- 'extension-data' in 'resp-code-ext' is not defined in this document. It
is in ACAP, but there is no comment about dependency on ACAP formal syntax
for undefined items here. Either add 'extension-data' in this doc or add
reference to ACAP in the formal syntax introduction paragraph.
- There is no support for disconnected/multi-access behaviour. In
particular, a client has to always upload a script before making it active
(Continue reading)
, you could do
require ["fileinto", "regex", "stringexpand"];
if header :regex ["date"] ", ([0-3]?[0-9]) ([A-Z][a-z]{2}) ([0-9]{4})" {
let "year" "${3}";
let "month" "${2}";
let "day" "${1}";
fileinto "INBOX.${year}-${month}-${day}";
}
this is a bit awkward, though, and you are not guaranteed that the
Date header will comply with RFC 2822 grammar. (most of the bogus
Date headers would probably be found in spam messages, though.)
perhaps the extension should include built-in variable names for time
RSS Feed