1. SIEVE Mail Filtering WG IETF 68, Prague WG Chairs: Cyrus Daboo, Alexey Melnikov Mailing List: Jabber: sieve@jabber.ietf.org

2. Agenda Introduction (blue sheets, scribe etc)(1 min) Agenda Bashing(1 min) Document status review(3 min) Editheader status(5 min) Sieve Notify WGLC status (10 min) Sieve Notify Mailto issues (30 min) Sieve MIME Loops (20 min) Other (non-WG) documents: –Environment, date-time, ihave,... (15 min) –Mailbox metadata access (15 min) –Externally stored lists (10 min) –ManageSieve protocol (5 min) –draft-gulbrandsen-collation-basic-XX.txt (5 min) Total: 120 minutes

3. Working Group Status Drafts approved: –Vacation, Variables, Relational update, Spamtest update, IMAPFlags, Sub-address update These are in the RFC Editor Queue blocked on 3028bis –draft-newman-i18n-comparator-14.txt is almost an RFC (!!!) IETF LC Completed: –draft-ietf-sieve-3028bis-12 (!!) WGLC Completed: –Body (sent to IESG) –Edit header (interaction with mail loop prevention, otherwise ready for IESG) –Notify extension (should be ready for IESG) Others: –Mailto Notification method (in WGLC) –Refuse/Reject – no update (sorry!) –MIME Loops – late update

4. Interaction between editheader and redirect / reject Philip posted draft-ietf-sieve-editheader-08.txt that has some text about removing of the Received headers with editheader Ned found some issue with the text: –Reject action should send the original message as received, but the new text seems to say that the modified message must be used to generate MDN/DSNs. –The text seems to allow for implementations that add dummy Received headers in order not to break loop control, which seems silly

5. Notification Draft (1/3) Current drafts: –Draft-ietf-sieve-notify-07 Editorial changes since the WGLC: Fixed XMPP URI in one example Minor corrections to the IANA registration as a result of other changes Deleted markers for open issues from the document Removed extract_text (a replacement will appear in Sieve MIME loops)

6. Notification Draft (2/3) Non-editorial changes since the WGLC: –Changed tagged :method argument to positional argument –Renamed "valid_notif_method" to "valid_notify_method" –Addressed Michael's issue with how timestamp is described –Added text about truncation of a textual part when it is stored in a variable using extract_text –Added text about notification throttling, identifying notification source and restricting values of the :from parameter –Added a requirement on documents describing notification methods to list which URI parameters must be ignored. Clarified that a notification mechanism can treat some URI parameters as errors –Added notify_method_capability test and example A script can now test if a user is “online”

7. Notification Draft (3/3) Unless authors hear otherwise, the document will be sent to IESG

8. MIME Loops Current draft: draft-ietf-sieve-mime-loop-01 – no changes since the last IETF! Various issues outstanding: –TBD: Security and IANA considerations. –Better explanation of message/rfc822 nesting (with examples). –Extend editheader and body with :mime :anychild? –Do Original- headers need to be registered? –Make sure that replaced/enclosed parts are valid 2822/MIME. –Move extract_text action (or its replacement as an extension to the body test) here

9. Date Draft draft-freed-sieve-date-index-04.txt in pseudo- WGLC Issues raised so far, accepted: –Minor typos found by Dylian –Dave Cridland: Suggested some text regarding which comparators are applicable to which date keywords Suggested to allow operating on unstructured fields Remaining issues: –Should allow for leap seconds :-) –Useful examples are needed! A new revision would be needed, but no major issues with the document

10. Environment & Notary extension Ned missed the deadline, but submitted draft- freed-sieve-environment-notary-00.txt to the mailing list Environment extension addressed previously raised issues –Ready for IETF LC? New extension is defined: Notary –Allows to extract DSN parameters of the SMTP envelope –Should this extension be defined in the same draft as the “environment”?

11. Accessing IMAP per-mailbox annotations from Sieve (Overview) Currently draft-melnikov-sieve-imapext-metadata-01.txt –Provides ability to read per-mailbox annotations - metadata test –Allows to test for annotation existence - metadata_exists test –Allows to test for mailbox existence - mailbox_exists test –Allows to explicitly create mailboxes on delivery - ":create" argument to fileinto action

12. Accessing IMAP per-mailbox annotations from Sieve (Example) require ["vacation", "mboxmetadata"]; if metadata :is :private "INBOX" "/vendor/isode/vacation" "1" { vacation :handle "holidays" text: I'm on holidays and will reply to your mail upon return.. ; }

13. Accessing IMAP per-mailbox annotations from Sieve (Open Issues) Do we need a test for server annotations? –Probably yes Add support for LIST-EXTENDED options? ACL :-)? Add :nocreate parameter to fileinto? –Probably not, can be emulated using the mailbox_exists test

14. Externally stored lists (Overview) An idea discussed with Alexandros Vellis –no draft yet Why? –Want to have externally stored whitelists/ blacklists/ greylists –Want to implement personal mailing lists –Don't want to change the script every time the list member changes

15. Externally stored lists (Overview) How? –Extend the header & envelope tests to accept a new tagged argument :list, which changes the last parameter into one or more names of lists of users –Extend the redirect action with a new tagged argument :list that changes the last parameter to be a name of a list of users

16. Externally stored lists (Example) # Submission from list members is sent to all members if allof ( envelope :detail :list "to" "mylist", header :contains :list "from" "mylist" ) { redirect :list "mylist"; }

17. ManageSIEVE Current draft: draft-martin-managesieve-07 Changes since -06: –Clarified meaning of the QUOTA response code –Clarified which characters are not allowed in script names and the maximum script name length –Clarified that the empty list of SASL mechanisms is allowed –Clarified that PUTSCRIPT must not store data after anonymous authentication –Move text about NOTIFY capability into this document (for draft-ietf-sieve-notify-XX) –Additional examples –Updated ABNF, References, Contact information

18. ManageSIEVE (Open Issues) Reference implementation doesn't implement nonsynchronizing literals as described in the spec –ABNF and examples in the spec will be fixed to match Suggestion to remove special handling of the “anonymous script verification mode” –Why would a client use a server to verify a script without storing it after? IANA registry for response codes is needed Many other minor issues, mostly editorial

19. Milestones - overdue Again! Proposed an update, but already missed some of its milestones

20. Other Business Have you signed the blue sheet? Have you tried Czech beer?