<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.ietf.mta-filters">
    <title>gmane.ietf.mta-filters</title>
    <link>http://blog.gmane.org/gmane.ietf.mta-filters</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5206"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5202"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5199"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5195"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5184"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5165"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5164"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5160"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5155"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5154"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5155"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5154"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5155"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5154"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5137"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5130"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5129"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5128"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5127"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.mta-filters/5122"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5206">
    <title>Protocol Action: 'Sieve Email Filtering: Include Extension'toProposed Standard (draft-ietf-sieve-include-15.txt)</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5206</link>
    <description>&lt;pre&gt;The IESG has approved the following document:
- 'Sieve Email Filtering: Include Extension'
  (draft-ietf-sieve-include-15.txt) as a Proposed Standard

This document is the product of the Sieve Mail Filtering Language Working
Group.

The IESG contact persons are Pete Resnick and Peter Saint-Andre.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-sieve-include/




Technical Summary

   The Sieve Email Filtering "include" extension permits users to
   include one Sieve script inside another. This can make managing large
   scripts or multiple sets of scripts much easier, and allows a site
   and its users to build up libraries of scripts. Users are able to
   include their own personal scripts or site-wide scripts.

Working Group Summary

   This was a popular extension within the working group. It was under
   active development for about a year and a half, during which time a
   number of suggestions were discussed, and issues were ironed out. It
   then went dormant for a year be&lt;/pre&gt;</description>
    <dc:creator>The IESG</dc:creator>
    <dc:date>2012-03-07T04:14:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5202">
    <title>RFC 6468 on Sieve Notification Mechanism: SIP MESSAGE</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5202</link>
    <description>&lt;pre&gt;
A new Request for Comments is now available in online RFC libraries.

        
        RFC 6468

        Title:      Sieve Notification Mechanism: SIP MESSAGE 
        Author:     A. Melnikov, B. Leiba, K. Li
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2012
        Mailbox:    Alexey.Melnikov&amp;lt; at &amp;gt;isode.com, 
                    barryleiba&amp;lt; at &amp;gt;computer.org, 
                    likepeng&amp;lt; at &amp;gt;huawei.com
        Pages:      10
        Characters: 21331
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sieve-notify-sip-message-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6468.txt

This document describes a profile of the Sieve extension for
notifications, to allow notifications to be sent over SIP MESSAGE.
[STANDARDS-TRACK]

This document is a product of the Sieve Mail Filtering Language Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for t&lt;/pre&gt;</description>
    <dc:creator>rfc-editor&lt; at &gt;rfc-editor.org</dc:creator>
    <dc:date>2012-02-29T18:58:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5199">
    <title>notify-sip-message and convert actions</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5199</link>
    <description>&lt;pre&gt;Hi folks,
Regarding the recent IETF last calls on the notify-sip-message and convert 
drafts in relation to the late IPR disclosures. The WG chairs have 
determined to proceed as follows based on feedback from the last call and 
discussions with the AD. This decision was reached on the basis of a 
process violation by one of the document editors of the documents, by 
failing to disclose IPR as required by BCP 79 (RFC 3979), and as per RFC 
2418 Section 6.1, the WG Chairs have the authority to take appropriate 
action.

We will request the RFC Editor to move ahead with publication of these two 
drafts. However, we have decided that Qian Sun will no longer be a document 
editor for those two drafts and we will have the RFC Editor remove his name 
from the author/editor list at the top of the documents and the Authors' 
Addresses sections at the end. We will require them to add Qian Sun to the 
Acknowledgements section of both drafts to identify that he did contribute 
text to the drafts.

If anyone objects to &lt;/pre&gt;</description>
    <dc:creator>Cyrus Daboo</dc:creator>
    <dc:date>2012-02-16T19:29:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5195">
    <title>I-D Action: draft-ietf-sieve-include-15.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5195</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

Title           : Sieve Email Filtering: Include Extension
Author(s)       : Cyrus Daboo
                          Aaron Stone
Filename        : draft-ietf-sieve-include-15.txt
Pages           : 17
Date            : 2012-01-31

   The Sieve Email Filtering "include" extension permits users to
   include one Sieve script inside another.  This can make managing
   large scripts or multiple sets of scripts much easier, and allows a
   site and its users to build up libraries of scripts.  Users are able
   to include their own personal scripts or site-wide scripts.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-include-15.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draf&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-01-31T18:08:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5184">
    <title>IPR issues</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5184</link>
    <description>&lt;pre&gt;Hi folks,
As I am sure you are aware IETF last calls on the sip-message and convert 
documents were re-issued in order to get IETF-wide feedback on the IPR 
issues. Much debate on this is going on on the IETF list and I have been 
approving messages to the SIEVE list coming from non-subscribers who are 
cross-posting, to make sure SIEVE WG can see some of that debate.

I think we really need SIEVE implementors to speak up on this issue at 
least in regard to whether these specifications can still be used as-is in 
products, or whether the current IPR terms would preclude that. I realize 
that probably means getting a formal legal review done, but chances are 
that is going to be needed regardless. Knowledge of this would help 
simplify the debate in terms of whether the current documents should be 
published at all, irrespective of any additional action on the part of the 
IETF on the actual failure in the IPR process.

So please, if possible, reply to the current thread on the second last 
call, and please &lt;/pre&gt;</description>
    <dc:creator>Cyrus Daboo</dc:creator>
    <dc:date>2012-01-26T16:42:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5165">
    <title>Second Last Call: &lt;draft-ietf-sieve-convert-06.txt&gt; (SieveExtensionfor Converting Messages Before Delivery) toProposed Standard</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5165</link>
    <description>&lt;pre&gt;
The IESG has received a request from the Sieve Mail Filtering Language WG
(sieve) to consider the following document:
- 'Sieve Extension for Converting Messages Before Delivery'
  &amp;lt;draft-ietf-sieve-convert-06.txt&amp;gt; as a Proposed Standard

Last calls were earlier issued on version -05 of this document and this
document was approved by the IESG on 2011-12-01. Subsequently,
an IPR disclosure statement for this draft was submitted.
This Second Last Call is intended to determine whether the community
is still comfortable with publication of this document in light of the IPR statement.
The relevant IPR statement is available at:

https://datatracker.ietf.org/ipr/1657/

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf&amp;lt; at &amp;gt;ietf.org mailing lists by 2012-02-08. Exceptionally, comments may be
sent to iesg&amp;lt; at &amp;gt;ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


 &lt;/pre&gt;</description>
    <dc:creator>The IESG</dc:creator>
    <dc:date>2012-01-25T20:19:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5164">
    <title>Second Last Call:&lt;draft-ietf-sieve-notify-sip-message-08.txt&gt;(SieveNotification Mechanism: SIP MESSAGE) to Proposed Standard</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5164</link>
    <description>&lt;pre&gt;
The IESG has received a request from the Sieve Mail Filtering Language WG
(sieve) to consider the following document:
- 'Sieve Notification Mechanism: SIP MESSAGE'
  &amp;lt;draft-ietf-sieve-notify-sip-message-08.txt&amp;gt; as a Proposed Standard

Last calls were earlier issued on version -05 of this document and this
document was approved by the IESG on 2011-10-06. Subsequently,
an IPR disclosure statement for this draft was submitted.
This Second Last Call is intended to determine whether the community
is still comfortable with publication of this document in light of the IPR statement.
The relevant IPR statement is available at:

https://datatracker.ietf.org/ipr/1658/

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf&amp;lt; at &amp;gt;ietf.org mailing lists by 2012-02-08. Exceptionally, comments may be
sent to iesg&amp;lt; at &amp;gt;ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   T&lt;/pre&gt;</description>
    <dc:creator>The IESG</dc:creator>
    <dc:date>2012-01-25T20:17:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5160">
    <title>Sieve include: interactions with MIME loops</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5160</link>
    <description>&lt;pre&gt;I am looking at the new text in draft-ietf-sieve-include-14.txt:

3.5.  Interaction with Other Extensions

         When "include" is used with the Editheader extension [RFC5293], 
any
         changes made to headers in a script MUST be propagated both to and
         from included scripts.  By way of example, if a script deletes one
         header and add another, then includes a second script, the 
included
         script MUST NOT see the removed header, and MUST see the added
         header.  Likewise, if the included script adds or removes a 
header,
         upon returning to the including script, subsequent actions MUST 
see
         the added headers and MUST NOT see the removed headers.

         When "include" is used with the MIME extension [RFC5703]
         "foreverypart" control structure, the included script MUST be
         presented with the current MIME part as though it were the entire
         message.  A script SHALL NOT have any special control over the
         control structure it &lt;/pre&gt;</description>
    <dc:creator>Alexey Melnikov</dc:creator>
    <dc:date>2012-01-21T13:31:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5155">
    <title>[Editorial Errata Reported] RFC5233 (3079)</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5155</link>
    <description>&lt;pre&gt;
The following errata report has been submitted for RFC5233,
"Sieve Email Filtering: Subaddress Extension".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5233&amp;amp;eid=3079

--------------------------------------
Type: Editorial
Reported by: Aaron Stone &amp;lt;aaron&amp;lt; at &amp;gt;serendipity.cx&amp;gt;

Section: 4

Original Text
-------------
   A diagram showing the ADDRESS-PARTs of an email address where the
   detail information follows a separator character sequence of "+" is
   shown below:

          :user "+" :detail  "&amp;lt; at &amp;gt;" :domain
         \-----------------/
             :local-part

   A diagram showing the ADDRESS-PARTs of a email address where the
   detail information precedes a separator character sequence of "--" is
   shown below:

          :detail "--" :user  "&amp;lt; at &amp;gt;" :domain
         \------------------/
             :local-part

Corrected Text
--------------
   A diagram showing the ADDRESS-PARTs of an email address where the
   detail informatio&lt;/pre&gt;</description>
    <dc:creator>RFC Errata System</dc:creator>
    <dc:date>2012-01-05T15:14:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5154">
    <title>I-D Action: draft-ietf-sieve-include-14.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5154</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

Title           : Sieve Email Filtering: Include Extension
Author(s)       : Cyrus Daboo
                          Aaron Stone
Filename        : draft-ietf-sieve-include-14.txt
Pages           : 16
Date            : 2012-01-05

   The Sieve Email Filtering "include" extension permits users to
   include one Sieve script inside another.  This can make managing
   large scripts or multiple sets of scripts much easier, and allows a
   site and its users to build up libraries of scripts.  Users are able
   to include their own personal scripts or site-wide scripts.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-include-14.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draf&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-01-05T15:01:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5155">
    <title>[Editorial Errata Reported] RFC5233 (3079)</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5155</link>
    <description>&lt;pre&gt;
The following errata report has been submitted for RFC5233,
"Sieve Email Filtering: Subaddress Extension".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5233&amp;amp;eid=3079

--------------------------------------
Type: Editorial
Reported by: Aaron Stone &amp;lt;aaron&amp;lt; at &amp;gt;serendipity.cx&amp;gt;

Section: 4

Original Text
-------------
   A diagram showing the ADDRESS-PARTs of an email address where the
   detail information follows a separator character sequence of "+" is
   shown below:

          :user "+" :detail  "&amp;lt; at &amp;gt;" :domain
         \-----------------/
             :local-part

   A diagram showing the ADDRESS-PARTs of a email address where the
   detail information precedes a separator character sequence of "--" is
   shown below:

          :detail "--" :user  "&amp;lt; at &amp;gt;" :domain
         \------------------/
             :local-part

Corrected Text
--------------
   A diagram showing the ADDRESS-PARTs of an email address where the
   detail informatio&lt;/pre&gt;</description>
    <dc:creator>RFC Errata System</dc:creator>
    <dc:date>2012-01-05T15:14:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5154">
    <title>I-D Action: draft-ietf-sieve-include-14.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5154</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

Title           : Sieve Email Filtering: Include Extension
Author(s)       : Cyrus Daboo
                          Aaron Stone
Filename        : draft-ietf-sieve-include-14.txt
Pages           : 16
Date            : 2012-01-05

   The Sieve Email Filtering "include" extension permits users to
   include one Sieve script inside another.  This can make managing
   large scripts or multiple sets of scripts much easier, and allows a
   site and its users to build up libraries of scripts.  Users are able
   to include their own personal scripts or site-wide scripts.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-include-14.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draf&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-01-05T15:01:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5155">
    <title>[Editorial Errata Reported] RFC5233 (3079)</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5155</link>
    <description>&lt;pre&gt;
The following errata report has been submitted for RFC5233,
"Sieve Email Filtering: Subaddress Extension".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5233&amp;amp;eid=3079

--------------------------------------
Type: Editorial
Reported by: Aaron Stone &amp;lt;aaron&amp;lt; at &amp;gt;serendipity.cx&amp;gt;

Section: 4

Original Text
-------------
   A diagram showing the ADDRESS-PARTs of an email address where the
   detail information follows a separator character sequence of "+" is
   shown below:

          :user "+" :detail  "&amp;lt; at &amp;gt;" :domain
         \-----------------/
             :local-part

   A diagram showing the ADDRESS-PARTs of a email address where the
   detail information precedes a separator character sequence of "--" is
   shown below:

          :detail "--" :user  "&amp;lt; at &amp;gt;" :domain
         \------------------/
             :local-part

Corrected Text
--------------
   A diagram showing the ADDRESS-PARTs of an email address where the
   detail informatio&lt;/pre&gt;</description>
    <dc:creator>RFC Errata System</dc:creator>
    <dc:date>2012-01-05T15:14:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5154">
    <title>I-D Action: draft-ietf-sieve-include-14.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5154</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

Title           : Sieve Email Filtering: Include Extension
Author(s)       : Cyrus Daboo
                          Aaron Stone
Filename        : draft-ietf-sieve-include-14.txt
Pages           : 16
Date            : 2012-01-05

   The Sieve Email Filtering "include" extension permits users to
   include one Sieve script inside another.  This can make managing
   large scripts or multiple sets of scripts much easier, and allows a
   site and its users to build up libraries of scripts.  Users are able
   to include their own personal scripts or site-wide scripts.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-include-14.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draf&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-01-05T15:01:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5137">
    <title>IPR Disclosures on draft-ietf-sieve-include anddraft-ietf-sieve-notify-sip-message</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5137</link>
    <description>&lt;pre&gt;Folks,

As you have seen by now, the IETF has received 2 IPR disclosures, one 
regarding draft-ietf-sieve-convert and the other involving 
draft-ietf-sieve-notify-sip-message.

https://datatracker.ietf.org/ipr/1657/
https://datatracker.ietf.org/ipr/1658/


Unfortunately, we have been told that Qian Sun, one of the co-authors of 
the document, is the author of the patent in question, filed back in 
2008, and that he failed to disclose this at the time. I think this was 
pretty clearly a violation of RFC 3979, and the IESG will take up the 
question of what, if any, appropriate measures need to be taken because 
of that. Qian Sun is apparently no longer an active IETF participant, 
and his co-workers who are active IETF participants asked their company 
to disclose against the two documents as soon as they discovered what 
had happened. That's where were are now.

However, I did want to bring this to the attention of the working group 
and ask about the following:

Both of these drafts are already approved and&lt;/pre&gt;</description>
    <dc:creator>Pete Resnick</dc:creator>
    <dc:date>2011-12-15T21:26:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5130">
    <title>Sieve counterpart of IMAP SPECIAL-USE (RFC 6154) ?</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5130</link>
    <description>&lt;pre&gt;Hi,

On an IMAP server mailing list I participated in a discussion about the 
new the IMAP LIST Extension for Special-Use Mailboxes (RFC 6154). In a 
nutshell, this extension allows identifying special-use mailboxes to an 
IMAP client. Special-use can for instance be a junk, trash, drafts, or 
archive folder. This way clients can easily identify such folders and 
use them without explicit user configuration.

At some point, the idea was raised to extend the Sieve language with 
similar means. It could for instance be useful to have a special version 
of the fileinto command that files the message into the default folder 
for a particular special-use, e.g. `fileinto :special_use "\\Junk";'. 
This can be particularly useful for global scripts outside the user's 
control. Through metadata support it is already possible to find out 
whether a folder has a special-use tag, but conversely it is not 
possible to find out which folders have a particular tag or what folder 
would be the default choice for that tag (n&lt;/pre&gt;</description>
    <dc:creator>Stephan Bosch</dc:creator>
    <dc:date>2011-12-12T12:10:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5129">
    <title>Protocol Action: 'Sieve Extension for Converting MessagesBeforeDelivery' to Proposed Standard(draft-ietf-sieve-convert-06.txt)</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5129</link>
    <description>&lt;pre&gt;The IESG has approved the following document:
- 'Sieve Extension for Converting Messages Before Delivery'
  (draft-ietf-sieve-convert-06.txt) as a Proposed Standard

This document is the product of the Sieve Mail Filtering Language Working
Group.

The IESG contact persons are Pete Resnick and Peter Saint-Andre.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-sieve-convert/




Technical Summary

   This document describes how IMAP CONVERT can be used within Sieve to
   transform messages before final delivery.

Working Group Summary

    This extension started as an individual submission in 2008 and was
    adopted as a WG document in 2010. The basic premise has remained the
    same throughout all revisions of the document.

    This extension adds a new combined action and test to SIEVE to allow
    message parts to be converted to other types during delivery. One new
    behavior here is that this extension creates a new combined test and
    action. This is something new for&lt;/pre&gt;</description>
    <dc:creator>The IESG</dc:creator>
    <dc:date>2011-12-05T18:17:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5128">
    <title>I-D Action: draft-ietf-sieve-convert-06.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5128</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

Title           : Sieve Extension for Converting Messages Before Delivery
Author(s)       : Alexey Melnikov
                          Qian Sun
                          Barry Leiba
                          Kepeng Li
Filename        : draft-ietf-sieve-convert-06.txt
Pages           : 9
Date            : 2011-12-01

   This document describes how the "CONVERT" IMAP extension can be used
   within the Sieve mail filtering language to transform messages before
   final delivery.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-convert-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-sieve-convert-06.txt

_______________________________________________
sieve mail&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2011-12-01T17:43:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5127">
    <title>Last Call: &lt;draft-ietf-sieve-include-13.txt&gt; (Sieve EmailFiltering:Include Extension) to Proposed Standard</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5127</link>
    <description>&lt;pre&gt;
The IESG has received a request from the Sieve Mail Filtering Language WG
(sieve) to consider the following document:
- 'Sieve Email Filtering: Include Extension'
  &amp;lt;draft-ietf-sieve-include-13.txt&amp;gt; as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf&amp;lt; at &amp;gt;ietf.org mailing lists by 2011-12-15. Exceptionally, comments may be
sent to iesg&amp;lt; at &amp;gt;ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The Sieve Email Filtering "include" extension permits users to
   include one Sieve script inside another.  This can make managing
   large scripts or multiple sets of scripts much easier, and allows a
   site and its users to build up libraries of scripts.  Users are able
   to include their own personal scripts or site-wide scripts.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-sieve-include/

IESG discussion c&lt;/pre&gt;</description>
    <dc:creator>The IESG</dc:creator>
    <dc:date>2011-12-01T16:21:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5122">
    <title>speaking as user: automatically printing incoming mail?</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5122</link>
    <description>&lt;pre&gt;Hi,

I (as mere user) get some mail for which I want to print the appended 
PDFs, and I'm not good at such chores. But wait, I'm using sieve and as 
we all know, script interpreters are really good at chores, maybe I can 
print with sieve?

No I can't. Not only is there no implemented extension, but I also can't 
find any documented extension to print anything.

Are there any vendor-specific extensions for such things?

Arnt

_______________________________________________
sieve mailing list
sieve&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/sieve

&lt;/pre&gt;</description>
    <dc:creator>Arnt Gulbrandsen</dc:creator>
    <dc:date>2011-10-27T12:32:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.mta-filters/5119">
    <title>Last Call: &lt;draft-ietf-sieve-convert-05.txt&gt; (SieveExtension forConverting Messages Before Delivery) toProposed Standard</title>
    <link>http://comments.gmane.org/gmane.ietf.mta-filters/5119</link>
    <description>&lt;pre&gt;
The IESG has received a request from the Sieve Mail Filtering Language WG
(sieve) to consider the following document:
- 'Sieve Extension for Converting Messages Before Delivery'
  &amp;lt;draft-ietf-sieve-convert-05.txt&amp;gt; as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf&amp;lt; at &amp;gt;ietf.org mailing lists by 2011-11-09. Exceptionally, comments may be
sent to iesg&amp;lt; at &amp;gt;ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document describes how IMAP CONVERT can be used within Sieve to
   transform messages before final delivery.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-sieve-convert/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-sieve-convert/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
sieve mailing list&lt;/pre&gt;</description>
    <dc:creator>The IESG</dc:creator>
    <dc:date>2011-10-26T23:49:16</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.ietf.mta-filters">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.ietf.mta-filters</link>
  </textinput>
</rdf:RDF>

