draft-ietf-acap-email-02.txt   draft-ietf-acap-email-03.txt 
Internet Draft R. Gellens Internet Draft R. Gellens
Document: draft-ietf-acap-email-02.txt QUALCOMM Document: draft-ietf-acap-email-03.txt QUALCOMM
Expires: 28 August 2000 28 February 2000
ACAP Email Account Dataset Class ACAP Email Account Dataset Class
Status of this Memo: Status of this Memo:
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as
skipping to change at page 9, line ? skipping to change at page 12, line ?
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
<http://www.ietf.org/shadow.html>. <http://www.ietf.org/shadow.html>.
A version of this draft document is intended for submission to the A version of this draft document is intended for submission to the
RFC editor as a Proposed Standard for the Internet Community. RFC editor as a Proposed Standard for the Internet Community.
Discussion and suggestions for improvement are requested. Discussion and suggestions for improvement are requested.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society 1999. All Rights Reserved. Copyright (C) The Internet Society 2000. All Rights Reserved.
Gellens Expires August 2000 [Page 1] Internet Draft ACAP Email Account Dataset Class February 2000
Table of Contents Table of Contents
1. Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in this Document . . . . . . . . . . . . . . 2 2. Conventions Used in this Document . . . . . . . . . . . . . 2
3. Comments . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3. Changes Since the Previous Version . . . . . . . . . . . . . 2
4. ACAP Standard Options . . . . . . . . . . . . . . . . . . . . 2 4. Comments . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. ACAP Email Account Dataset Class . . . . . . . . . . . . . . 3 5. ACAP Standard Options . . . . . . . . . . . . . . . . . . . 3
5.1. ACAP Email Account Dataset Class Prefix . . . . . . . . . 3 6. ACAP Email Account Dataset Class . . . . . . . . . . . . . 3
5.2. ACAP Email Account Dataset Hierarchy . . . . . . . . . . 3 6.1. ACAP Email Account Dataset Class Prefix . . . . . . . . 3
6. ACAP Email Account Dataset Attributes . . . . . . . . . . . . 3 6.2. ACAP Email Account Dataset Hierarchy . . . . . . . . . 3
6.1. Basic Attributes . . . . . . . . . . . . . . . . . . . . 4 7. ACAP Email Account Dataset Attributes . . . . . . . . . . . 4
6.2. Specific Attributes . . . . . . . . . . . . . . . . . . . 4 7.1. Basic Attributes . . . . . . . . . . . . . . . . . . . 4
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7.2. Specific Attributes . . . . . . . . . . . . . . . . . . 4
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. Dataset Class Capabilities . . . . . . . . . . . . . . . . 9
9. Security Considerations . . . . . . . . . . . . . . . . . . 8 9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 9
10. Author's Address . . . . . . . . . . . . . . . . . . . . . . 8 10. References . . . . . . . . . . . . . . . . . . . . . . . . 10
11. Full Copyright Statement . . . . . . . . . . . . . . . . . . 9 11. Security Considerations . . . . . . . . . . . . . . . . . . 11
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 11
13. Author's Address . . . . . . . . . . . . . . . . . . . . . . 11
14. Full Copyright Statement . . . . . . . . . . . . . . . . . 11
1. Abstract 1. Abstract
It has become common for Internet mail users to have more than one It has become common for Internet mail users to have more than one
account where mail is received, to access multiple accounts from the account where mail is received, to access multiple accounts from the
same machine, to access the same accounts from different machines, same machine, to access the same accounts from different machines,
and to use multiple programs which require email account and to use multiple programs which require email account
configuration information. configuration information.
The Application Configuration Access Protocol [ACAP] provides an The Application Configuration Access Protocol [ACAP] provides an
ideal mechanism for storage of email account data. ideal mechanism for storage of email account data.
This specification defines a standard ACAP dataset class for email This specification defines a standard ACAP dataset class for email
accounts, and a common option for indicating a default email accounts, and a common option for indicating a default email
account. account.
2. Conventions Used in this Document 2. Conventions Used in this Document
The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
in this document are to be interpreted as defined in "Key words for "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
use in RFCs to Indicate Requirement Levels" [KEYWORDS]. document are to be interpreted as described in RFC 2119 [KEYWORDS].
3. Comments 3. Changes Since the Previous Version
- Added attributes:
email.mailbox-prefix,
email.sieve.capability,
email.sieve.runtime.errors,
email.sieve.runtime.warnings,
Gellens Expires August 2000 [Page 2] Internet Draft ACAP Email Account Dataset Class February 2000
email.sieve.runtime.errtxt,
email.sieve.runtime.warntxt,
email.trash-folder.
- Fixed ABNF for email-sieve-errtxt.
- Added text for email.maximum.download-size regarding use with
IMAP [IMAP4].
- Added mention of multiple Sieve scripts.
- Clarified email vs. personalities datasets.
- Updated Sieve script examples.
- Added section on items in the "capabilities" dataset.
4. Comments
Public comments can be sent to the IETF ACAP mailing list, Public comments can be sent to the IETF ACAP mailing list,
<ietf-acap+@andrew.cmu.edu>. To subscribe, send a message to <ietf-acap+@andrew.cmu.edu>. To subscribe, send a message to
<ietf-acap-request+@andrew.cmu.edu> with the word SUBSCRIBE as the <ietf-acap-request+@andrew.cmu.edu> with the word SUBSCRIBE as the
body. Private comments should be sent to the author. body. Private comments should be sent to the author.
4. ACAP Standard Options 5. ACAP Standard Options
This specification defines the Message User Agent (MUA) Default This specification defines the Message User Agent (MUA) Default
Account standard option. This is a scaler option in the ACAP Account standard option. This is a scaler option in the ACAP
Standard Option ("/option") dataset. The entry name is Standard Option ("/option") dataset. The entry name is
"mua.default.account". The "option.value" attribute contains the "mua.default.account". The "option.value" attribute contains the
value, which is a URL. Generally, this will be an ACAP URL pointing value, which is a URL. Generally, this will be an ACAP URL pointing
to an entry in an Email Account dataset. to an entry in an Email Account dataset.
The standard option dataset class is specified in [ACAP-OPTIONS]. The standard option dataset class is specified in [ACAP-OPTIONS].
ACAP URLs are defined in [ACAP]. ACAP URLs are defined in [ACAP].
5. ACAP Email Account Dataset Class 6. ACAP Email Account Dataset Class
The ACAP Email Account dataset class defines a set of attributes The ACAP Email Account dataset class defines a set of attributes
which specify an email account; that is, configuration information which specify an email account; that is, configuration information
used for access to email on a POP [POP3] or IMAP [IMAP4] server. used for access to mail on a POP [POP3] or IMAP [IMAP4] server.
5.1. ACAP Email Account Dataset Class Prefix Configuration information related to composing and sending mail is
stored in the ACAP Email Personality Dataset Class
[ACAP-PERSONALITY].
6.1. ACAP Email Account Dataset Class Prefix
Datasets whose names begin with "/email" are assumed to contain Datasets whose names begin with "/email" are assumed to contain
email account entries as defined in this specification. email account entries as defined in this specification.
5.2. ACAP Email Account Dataset Hierarchy Gellens Expires August 2000 [Page 3] Internet Draft ACAP Email Account Dataset Class February 2000
6.2. ACAP Email Account Dataset Hierarchy
Each user may have a set of named email accounts. The default is Each user may have a set of named email accounts. The default is
pointed at by the "mua.default.account" standard option. (See pointed at by the "mua.default.account" standard option. (See
section 4 for more information.) section 5, ACAP Standard Options, for more information.)
Inheritance is likely to be useful both for inheriting site or group Inheritance is likely to be useful both for inheriting site or group
defaults (for example, POP or IMAP servers, and initial client defaults (for example, POP or IMAP servers, and initial client
configuration in general) as well as for inheriting user-specific configuration in general) as well as for inheriting user-specific
configuration when using different machines. configuration when using different machines.
6. ACAP Email Account Dataset Attributes 7. ACAP Email Account Dataset Attributes
An email account entry MUST have an "entry" attribute. All other An email account entry MUST have an "entry" attribute. All other
attributes are OPTIONAL. attributes are OPTIONAL.
Attributes are specified using Augmented Backus-Naur Form [ABNF]. Attributes are specified using Augmented Backus-Naur Form [ABNF].
All attributes are single-valued and textual (non-binary) unless All attributes are single-valued and textual (non-binary) unless
otherwise stated. otherwise stated.
The ABNF defines the content of the attribute values prior to their The ABNF defines the content of the attribute values prior to their
encoding as an ACAP string. Clients MUST conform to the syntax when encoding as an ACAP string. Clients MUST conform to the syntax when
generating these attributes, but MUST NOT assume that the attribute generating these attributes, but MUST NOT assume that the attribute
values will conform to this syntax on access. Servers MUST NOT values will conform to this syntax on access. Servers MUST NOT
enforce the syntax. enforce the syntax.
6.1. Basic Attributes 7.1. Basic Attributes
These attributes are defined in ACAP [ACAP] and have meaning in all These attributes are defined in ACAP [ACAP] and have meaning in all
dataset classes. The section describes how they are used in an dataset classes. The section describes how they are used in an
email account dataset. email account dataset.
entry entry
The "entry" attribute is used to hold a unique name for the The "entry" attribute is used to hold a unique name for the
email account. This name is used for inheritance, so when email account. This name is used for inheritance, so when
customizing an account which has an entry in an inherited customizing an account which has an entry in an inherited
dataset, the entry name needs to remain the same. The name dataset, the entry name needs to remain the same. The name
should also be descriptive, as it is suitable for user display. should also be descriptive, as it is suitable for user display.
subdataset subdataset
The "subdataset" attribute indicates that there is a subdataset The "subdataset" attribute indicates that there is a subdataset
of this entry. The value of this attribute specifies the actual of this entry. The value of this attribute specifies the actual
location of the subdataset, per [ACAP] section 3.1.1. location of the subdataset, per [ACAP] section 3.1.1.
6.2. Specific Attributes 7.2. Specific Attributes
These attributes are specific to the Email Account dataset class. These attributes are specific to the Email Account dataset class.
Gellens Expires August 2000 [Page 4] Internet Draft ACAP Email Account Dataset Class February 2000
email.boring-headers
This multi-valued attribute is a list of header prefixes. If
the client has a mode where it suppresses display of certain
headers and/or properties of messages, headers which start with
a prefix included in this attribute are candidates for
suppression. Prefix strings are case-insensitive.
email-boring = 1*VCHAR
email.check-interval email.check-interval
This specifies the interval, in seconds, between checks (polls) This specifies the interval, in seconds, between checks (polls)
for new mail. A value of 0 indicates that automatic mail checks for new mail. A value of 0 indicates that automatic mail checks
SHOULD NOT be done. SHOULD NOT be done.
email-check-int = 1*DIGIT email-check-int = 1*DIGIT
email.connection-type email.connection-type
This contains a token indicating the type of connection used for This contains a token indicating the type of connection used for
this email account. Clients might use this information to this email account. Clients might use this information to
skipping to change at page 9, line ? skipping to change at page 12, line ?
email.imap.download-type email.imap.download-type
This specifies which elements of messages are to be downloaded This specifies which elements of messages are to be downloaded
when populating or resynchronizing a mailbox. This is only when populating or resynchronizing a mailbox. This is only
useful when accessing messages via IMAP [IMAP4]. "Headers" useful when accessing messages via IMAP [IMAP4]. "Headers"
indicates only minimal message information, such as sender, indicates only minimal message information, such as sender,
recipient, and subject. "Structure" specifies important headers recipient, and subject. "Structure" specifies important headers
and body structure information. "Body" means headers, body and body structure information. "Body" means headers, body
structure information and the contents of body parts, but not structure information and the contents of body parts, but not
attachments. "Attachments" indicates all elements of messages. attachments. "Attachments" indicates all elements of messages.
email-dload = "headers" / "structure" / "body" / "inline" / email-dload = "headers" / "structure" / "body" /
"attachments" "inline" / "attachments"
email.leave-on-server.flag email.leave-on-server.flag
This specifies if the client should delay deleting mail from the This specifies if the client should delay deleting mail from the
server after downloading. This is generally useful only with server after downloading. This is generally useful only with
POP servers [POP3] which support this. POP servers [POP3] which support this.
email-lmos-flag = "0" / "1" email-lmos-flag = "0" / "1"
email.leave-on-server.days email.leave-on-server.days
When email.leave-on-server.flag is set (value is "1"), this When email.leave-on-server.flag is set (value is "1"), this
attribute specifies the number of days messages should remain on attribute specifies the number of days messages should remain on
the server before being deleted by the client. This is the server before being deleted by the client. This is
generally useful only with POP servers [POP3] which support generally useful only with POP servers [POP3] which support
leaving mail on the server. Note that a value of "0" indicates leaving mail on the server. Note that a value of "0" indicates
that clients should never automatically delete mail from the that clients SHOULD never automatically delete mail from the
server. server.
Gellens Expires August 2000 [Page 5] Internet Draft ACAP Email Account Dataset Class February 2000
email-lmos-days = 1*DIGIT email-lmos-days = 1*DIGIT
email.maximum.download-size email.maximum.download-size
This contains the maximum size (in octets) of messages to be This contains the maximum size (in octets) of messages to be
downloaded. This is most useful when accessing messages via POP downloaded. This is most useful when accessing messages via POP
[POP3]. A value of "0" indicates no limit. [POP3], although it might also be used with IMAP [IMAP4] to
specify a limit on the size of attachments to be downloaded. A
value of "0" indicates no limit.
email-max-dsize = 1*DIGIT email-max-dsize = 1*DIGIT
email.mailbox-prefix
This attribute contains a prefix required to access this
account's IMAP folders. This is only useful when accessing
messages via IMAP [IMAP4].
email-prefix = 1*CHAR
email.personality email.personality
This specifies the default personality to assign to messages This specifies the default personality to assign to messages
received via this email account. It is generally an ACAP URL to received via this email account. It is generally an ACAP URL to
an entry in an Email Personality dataset. The ACAP Email an entry in an Email Personality dataset. The ACAP Email
Personality dataset class is specified in [ACAP-PERSONALITY]. Personality dataset class is specified in [ACAP-PERSONALITY].
ACAP-URLs are defined in [ACAP]. ACAP-URLs are defined in [ACAP].
email-personality = url ;defined in [URL-BASIC] email-personality = url ;defined in [URL-BASIC]
email.server.IMAP email.server.IMAP
skipping to change at page 9, line ? skipping to change at page 12, line ?
email-pop = url ;defined in [URL-BASIC] email-pop = url ;defined in [URL-BASIC]
email.server.Local email.server.Local
This indicates that this email account refers to a mailstore on This indicates that this email account refers to a mailstore on
the local client. When set to "1", the "email.server.IMAP" and the local client. When set to "1", the "email.server.IMAP" and
"email.server.POP" attributes are ignored. "email.server.POP" attributes are ignored.
email-local = "0"/"1" email-local = "0"/"1"
email.sieve.capability
This multivalued attribute contains a list of Sieve capability
strings for extensions supported by the Sieve execution engine
which processes the Sieve script contained in
"email.sieve.script".
Gellens Expires August 2000 [Page 6] Internet Draft ACAP Email Account Dataset Class February 2000
Note that this attribute SHOULD NOT be modified except by the
Sieve execution engine or its agent. Normally, this attribute
is inherited from a site-specific dataset.
email-sieve-cap = 1*CHAR
email.sieve.script email.sieve.script
This specifies the text of a Sieve script which will be applied This specifies the text of a Sieve script which will be applied
by the delivery agent (if supported) to mail arriving at this by the delivery agent (if supported) to mail arriving at this
email account. Sieve is specified in [SIEVE]. email account. Sieve is specified in [SIEVE].
Note that multiple Sieve scripts may be stored. The active
script is always called "email.sieve.script", while additional
scripts may be stored in names of the form
"email.account.sieve.foo", where "foo" is the name of a
non-active script.
email-sieve = 1*UTF8-CHAR email-sieve = 1*UTF8-CHAR
email.sieve.syntax.errors email.sieve.runtime.errors
If supported by the Sieve implementation, this attribute If supported by the Sieve implementation (see section 8), this
contains the count of syntax errors detected in the most attribute contains the count of runtime errors detected in the
recently stored Sieve script. Sieve is specified in [SIEVE]. currently active Sieve script. This count SHOULD be cleared
when a new script is stored. It MAY be reset at other times, at
the discretion of the server. Sieve is specified in [SIEVE].
email-sieve-synerr = 1*DIGIT email-sieve-runerr = 1*DIGIT
email.sieve.syntax.warnings email.sieve.runtime.warnings
If supported by the Sieve implementation, this attribute If supported by the Sieve implementation (see section 8), this
contains the count of syntax warnings detected in the most attribute contains the count of runtime warnings detected in the
recently stored Sieve script. Sieve is specified in [SIEVE]. currently active Sieve script. This count SHOULD be cleared
when a new script is stored. It MAY be reset at other times, at
the discretion of the server. Sieve is specified in [SIEVE].
email-sieve-synwarn = 1*DIGIT email-sieve-runwarn = 1*DIGIT
email.sieve.syntax.errtxt email.sieve.runtime.errtxt
If supported by the Sieve implementation, this attribute If supported by the Sieve implementation (see section 8), this
contains the text of syntax errors detected in the most recently attribute contains the text of runtime errors detected in the
stored Sieve script. The error text is formated into currently active Sieve script. The error text is formated into
CRLF-separated lines, one line per error. Each line contains CRLF-separated lines, one line per error. Each line contains
named attributes of the error, in a MIME-header-like format. named attributes of the error, in a MIME-header-like format.
The currently specified attributes are: line, offset, length, The currently specified attributes are: line, offset, length,
and text. Text MUST always be the last attribute. Sieve is and text. Text MUST always be the last attribute. This
specified in [SIEVE]. attribute SHOULD be cleared when a new script is stored. It MAY
be reset at other times, at the discretion of the server. Sieve
is specified in [SIEVE].
The format is intended to be easy for a Sieve execution agent to The format is intended to be easy for a Sieve execution agent to
generate, and easy for a Sieve user agent to parse. The Sieve generate, and easy for a Sieve user agent to parse. The Sieve
user agent could use the information to highlight the indicated user agent could use the information to highlight the indicated
Gellens Expires August 2000 [Page 7] Internet Draft ACAP Email Account Dataset Class February 2000
section of the Sieve script text, as specified by the line, section of the Sieve script text, as specified by the line,
offset, and length. offset, and length.
email-sieve-errtxt = *(non-text-sieve-att ";" SP) text-sieve-att email-sieve-errtxt = *(non-text-sieve-att ";" SP)
text-sieve-att CRLF
non-text-sieve-att = sieve-att-line / sieve-att-off / non-text-sieve-att = sieve-att-line / sieve-att-off /
sieve-att-len / sieve-att-ext sieve-att-len / sieve-att-ext
text-sieve-att = "text" ":" 1*UTF8-CHAR text-sieve-att = "text" ":" SP 1*UTF8-CHAR
sieve-att-line = "line" ":" 1*DIGIT ;MAY use ":" or ";"
sieve-att-off = "offset" ":" 1*DIGIT ;MUST NOT use CRLF
sieve-att-len = "length" ":" 1*DIGIT sieve-att-line = "line" ":" SP 1*DIGIT
sieve-att-ext = 1*UTF8-CHAR ":" 1*UTF8-CHAR sieve-att-off = "offset" ":" SP 1*DIGIT
; MUST not use ":" or ";" sieve-att-len = "length" ":" SP 1*DIGIT
sieve-att-ext = 1*UTF8-CHAR ":" SP 1*UTF8-CHAR
;MUST NOT use ":" or ";"
email.sieve.syntax.warntxt email.sieve.runtime.warntxt
If supported by the Sieve implementation, this attribute If supported by the Sieve implementation (see section 8), this
contains the text of syntax warnings detected in the most attribute contains the text of runtime warnings detected in the
recently stored Sieve script. The warning text is formated into currently active Sieve script. The warning text is formated
CRLF-separated lines, one line per warning. Each line contains into CRLF-separated lines, one line per warning, as specified
named attributes of the warning, in a MIME-header-like format. for "email.sieve.runtime.errtxt". This attribute SHOULD be
The currently specified attributes are: line, offset, length, cleared when a new script is stored. It MAY be reset at other
and text. Text MUST always be the last attribute. Sieve is times, at the discretion of the server. Sieve is specified in
specified in [SIEVE]. [SIEVE].
email-sieve-warntxt = email-sieve-errtxt email-sieve-warntxt = email-sieve-errtxt
email.boring-headers email.sieve.syntax.errors
This multi-valued attribute is a list of header prefixes. If If supported by the Sieve implementation (see section 8), this
the client has a mode where it suppresses display of certain attribute contains the count of syntax errors detected in the
headers and/or properties of messages, headers which start with most recently stored Sieve script. Sieve is specified in
a prefix included in this attribute are candidates for [SIEVE].
suppression. Prefix strings are case-insensitive.
email-boring = 1*VCHAR email-sieve-synerr = 1*DIGIT
7. Examples email.sieve.syntax.warnings
If supported by the Sieve implementation (see section 8), this
attribute contains the count of syntax warnings detected in the
most recently stored Sieve script. Sieve is specified in
[SIEVE].
email-sieve-synwarn = 1*DIGIT
email.sieve.syntax.errtxt
If supported by the Sieve implementation (see section 8), this
attribute contains the text of syntax errors detected in the
most recently stored Sieve script. The error text is formated
into CRLF-separated lines, one line per error, as specified for
"email.sieve.runtime.errtxt". Sieve is specified in [SIEVE].
Gellens Expires August 2000 [Page 8] Internet Draft ACAP Email Account Dataset Class February 2000
email-sieve-synerrtxt = email-sieve-errtxt
email.sieve.syntax.warntxt
If supported by the Sieve implementation (see section 8), this
attribute contains the text of syntax warnings detected in the
most recently stored Sieve script. The warning text is formated
into CRLF-separated lines, one line per warning, as specified
for "email.sieve.runtime.errtxt". Sieve is specified in
[SIEVE].
email-sieve-synwarntxt = email-sieve-errtxt
email.trash-folder
This attribute contains the name of a folder to which messages
SHOULD be moved in lieu of immediately marking them deleted. If
empty, messages SHOULD be marked deleted. This is only useful
when accessing messages via IMAP [IMAP4].
email-trash = 1*CHAR
8. Dataset Class Capabilities
Certain attributes in the Email Account dataset class are only
available if there is integrated server support or an active client
providing them. Availability of such attributes is indicated by
corresponding attributes in the "email" entry of the "capability"
dataset. The capability attribute has the name of the attribute in
the Email dataset, prefixed with "capability.", and has a value of
"1" if the corresponding attribute in the Email dataset is
supported.
capability.email.sieve.runtime.errors
capability.email.sieve.runtime.warnings
capability.email.sieve.runtime.errtxt
capability.email.sieve.runtime.warntxt
capability.email.sieve.syntax.errors
capability.email.sieve.syntax.warnings
capability.email.sieve.syntax.errtxt
capability.email.sieve.syntax.warntxt
Note that these attributes SHOULD NOT be modified except by the
server or an active client responsible for supporting the underlying
capability. These attributes are normally inherited from a
site-specific dataset.
9. Examples
entry = "home" entry = "home"
email.connection-type = "phone-modem" email.connection-type = "phone-modem"
email.personality = "home" email.personality = "home"
Gellens Expires August 2000 [Page 9] Internet Draft ACAP Email Account Dataset Class February 2000
email.server.pop = "POP://jru;AUTH=APOP@pop.isp.com" email.server.pop = "POP://jru;AUTH=APOP@pop.isp.com"
email.sieve.script = "IF SIZE OVER 100k email.sieve.capability = ("vacation" "mark")
DISCARD;" email.sieve.script = "if header :matches "subject"
[ "*make*money*fast*",
"*university*dipl*mas*" ]
{
discard;
}
email.boring-headers = ("received" "message" "x400") email.boring-headers = ("received" "message" "x400")
entry = "work entry = "work
email.connection-type = "direct email.connection-type = "direct
email.personality = "work email.personality = "work
email.server.imap = "IMAP://jru@mail.bigcorp.com email.server.imap = "IMAP://jru@mail.bigcorp.com
email.sieve.capability = ("fileinto" "vacation" "envelope")
email.sieve.script = {47} email.sieve.script = {47}
IF HEADER "FROM" IS "BOSS" if header :is "Sender"
FILEINTO "STUFF" "BigCheese@example.com"
{
fileinto "Blatherings";
}
email.trash-folder = "Trash"
8. References 10. References
[ABNF] Crocker, Overell, "Augmented BNF for Syntax Specifications: [ABNF] Crocker, Overell, "Augmented BNF for Syntax Specifications:
ABNF", RFC 2234, Internet Mail Consortium, Demon Internet Ltd., ABNF", RFC 2234, Internet Mail Consortium, Demon Internet Ltd.,
November 1997. <ftp://ftp.isi.edu/in-notes/rfc2234.txt> November 1997. <ftp://ftp.isi.edu/in-notes/rfc2234.txt>
[ACAP] Newman, Myers, "ACAP -- Application Configuration Access [ACAP] Newman, Myers, "ACAP -- Application Configuration Access
Protocol", RFC 2244, Innosoft, Netscape, November 1997. Protocol", RFC 2244, Innosoft, Netscape, November 1997.
<ftp://ftp.isi.edu/in-notes/rfc2244.txt> <ftp://ftp.isi.edu/in-notes/rfc2244.txt>
[ACAP-OPTIONS] Hole, "ACAP Application Options Dataset Class", The [ACAP-OPTIONS] Hole, "ACAP Application Options Dataset Class", The
Esys Corporation, Work in Progress, February 1998. Esys Corporation, Work in Progress, February 1998.
<ftp://ftp.ietf.org/internet-drafts/draft-ietf-acap-options-xx.txt> <ftp://ftp.ietf.org/internet-drafts/draft-ietf-acap-options-xx.txt>
[ACAP-PERSONALITY] Gellens, "ACAP Email Personality Dataset Class", [ACAP-PERSONALITY] Gellens, "ACAP Email Personality Dataset Class",
QUALCOMM Incorporated, Work in Progress. QUALCOMM Incorporated, Work in Progress.
<ftp://ftp.ietf.org/internet-drafts/draft-ietf-acap-pers-xx.txt> <ftp://ftp.ietf.org/internet-drafts/draft-ietf-acap-pers-xx.txt>
[IMAP4] Crispin, "Internet Message Access Protocol - Version 4rev1", [IMAP4] Crispin, "Internet Message Access Protocol - Version 4rev1",
RFC 2060, University of Washington, December 1996. RFC 2060, University of Washington, December 1996.
skipping to change at page 9, line ? skipping to change at page 12, line ?
QUALCOMM Incorporated, Work in Progress. QUALCOMM Incorporated, Work in Progress.
<ftp://ftp.ietf.org/internet-drafts/draft-ietf-acap-pers-xx.txt> <ftp://ftp.ietf.org/internet-drafts/draft-ietf-acap-pers-xx.txt>
[IMAP4] Crispin, "Internet Message Access Protocol - Version 4rev1", [IMAP4] Crispin, "Internet Message Access Protocol - Version 4rev1",
RFC 2060, University of Washington, December 1996. RFC 2060, University of Washington, December 1996.
[KEYWORDS] Bradner, "Key words for use in RFCs to Indicate [KEYWORDS] Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, Harvard University, March 1997. Requirement Levels", RFC 2119, Harvard University, March 1997.
<ftp://ftp.isi.edu/in-notes/rfc2119.txt> <ftp://ftp.isi.edu/in-notes/rfc2119.txt>
Gellens Expires August 2000 [Page 10] Internet Draft ACAP Email Account Dataset Class February 2000
[POP3] Myers, Rose, "Post Office Protocol -- Version 3", RFC 1939, [POP3] Myers, Rose, "Post Office Protocol -- Version 3", RFC 1939,
Carnegie Mellon, Dover Beach Consulting, Inc., May 1996. Carnegie Mellon, Dover Beach Consulting, Inc., May 1996.
<ftp://ftp.isi.edu/in-notes/rfc1939.txt> <ftp://ftp.isi.edu/in-notes/rfc1939.txt>
[SIEVE] Showalter, "Sieve -- a Mail Filtering Language", Carnegie [SIEVE] Showalter, "Sieve -- a Mail Filtering Language", Carnegie
Mellon, Work in Progress. Mellon, Work in Progress.
<ftp://ftp.ietf.org/internet-drafts/draft-showalter-sieve-xx.txt>\ <ftp://ftp.ietf.org/internet-drafts/draft-showalter-sieve-xx.txt>\
[URL-BASIC] Berners-Lee, Masinter, McCahill, "Uniform Resource [URL-BASIC] Berners-Lee, Masinter, McCahill, "Uniform Resource
Locators (URL)", RFC 1738, CERN, Xerox Corporation, University of Locators (URL)", RFC 1738, CERN, Xerox Corporation, University of
skipping to change at page 9, line ? skipping to change at page 12, line ?
[URL-IMAP] Newman, "IMAP URL Scheme", RFC 2192, Innosoft, September [URL-IMAP] Newman, "IMAP URL Scheme", RFC 2192, Innosoft, September
1997. <ftp://ftp.isi.edu/in-notes/rfc2192.txt> 1997. <ftp://ftp.isi.edu/in-notes/rfc2192.txt>
[URL-POP] Gellens, "POP URL Scheme", RFC 2384, QUALCOMM [URL-POP] Gellens, "POP URL Scheme", RFC 2384, QUALCOMM
Incorporated, August 1998. <ftp://ftp.isi.edu/in-notes/rfc2384.txt> Incorporated, August 1998. <ftp://ftp.isi.edu/in-notes/rfc2384.txt>
[UTF8] Yergeau, F. "UTF-8, a transformation format of ISO 10646", [UTF8] Yergeau, F. "UTF-8, a transformation format of ISO 10646",
RFC 2279, Alis Technologies, January 1998. RFC 2279, Alis Technologies, January 1998.
<ftp://ftp.isi.edu/in-notes/rfc2279.txt> <ftp://ftp.isi.edu/in-notes/rfc2279.txt>
9. Security Considerations 11. Security Considerations
As with ACAP datasets in general, it is important that access As with ACAP datasets in general, it is important that access
controls are set correctly on Email Account datasets. Besides the controls are set correctly on Email Account datasets. Besides the
server URLs, the Sieve script may contain highly personal server URLs, the Sieve script may contain highly personal
information which should not be disclosed except by explicit owner information which should not be disclosed except by explicit owner
request. request.
10. Author's Address 12. Acknowledgments
Randall Gellens +1 619 651 5115 Many thanks to the participants of the IETF ACAP working group for
QUALCOMM Incorporated Randy@Qualcomm.Com their help, comments, and suggestions.
6455 Lusk Blvd.
13. Author's Address
Randall Gellens +1 858 651 5115
QUALCOMM Incorporated randy@qualcomm.com
5775 Morehouse Drive
San Diego, CA 92121-2779 San Diego, CA 92121-2779
U.S.A. U.S.A.
11. Full Copyright Statement 14. Full Copyright Statement
Copyright (C) The Internet Society 1999. All Rights Reserved. Copyright (C) The Internet Society 2000. All Rights Reserved.
Gellens Expires August 2000 [Page 11] Internet Draft ACAP Email Account Dataset Class February 2000
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 49 change blocks. 
85 lines changed or deleted 258 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/