Debian Codegraph @

rfc3865.html

raw
1 <pre>Network Working Group C. Malamud
2 Request for Comments: 3865 Memory Palace Press
3 Category: Standards Track September 2004
4
5
6 <span class="h1">A No Soliciting Simple Mail Transfer Protocol (SMTP)</span>
7 <span class="h1">Service Extension</span>
8
9 Status of this Memo
10
11 This document specifies an Internet standards track protocol for the
12 Internet community, and requests discussion and suggestions for
13 improvements. Please refer to the current edition of the "Internet
14 Official Protocol Standards" (STD 1) for the standardization state
15 and status of this protocol. Distribution of this memo is unlimited.
16
17 Copyright Notice
18
19 Copyright (C) The Internet Society (2004).
20
21 Abstract
22
23 This document proposes an extension to Soliciting Simple Mail
24 Transfer Protocol (SMTP) for an electronic mail equivalent to the
25 real-world "No Soliciting" sign. In addition to the service
26 extension, a new message header and extensions to the existing
27 "received" message header are described.
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Malamud Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
60 <a href="#section-1.1">1.1</a>. The Spam Pandemic. . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
61 <a href="#section-1.2">1.2</a>. No Soliciting in the Real World. . . . . . . . . . . . . <a href="#page-4">4</a>
62 <a href="#section-1.3">1.3</a>. No Soliciting and Electronic Mail. . . . . . . . . . . . <a href="#page-5">5</a>
63 <a href="#section-2">2</a>. The No-Soliciting SMTP Service Extension . . . . . . . . . . . <a href="#page-6">6</a>
64 <a href="#section-2.1">2.1</a>. The EHLO Exchange. . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
65 <a href="#section-2.2">2.2</a>. Solicitation Class Keywords. . . . . . . . . . . . . . . <a href="#page-7">7</a>
66 <a href="#section-2.2.1">2.2.1</a>. Note on Choice of Solicitation Class Keywords. . <a href="#page-8">8</a>
67 <a href="#section-2.3">2.3</a>. The MAIL FROM Command. . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
68 <a href="#section-2.4">2.4</a>. Error Reporting and Enhanced Mail Status Codes . . . . . <a href="#page-10">10</a>
69 <a href="#section-2.5">2.5</a>. Solicitation Mail Header . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
70 <a href="#section-2.6">2.6</a>. Insertion of Solicitation Keywords in Trace Fields . . . <a href="#page-11">11</a>
71 <a href="#section-2.7">2.7</a>. Relay of Messages. . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
72 <a href="#section-2.8">2.8</a>. No Default Solicitation Class. . . . . . . . . . . . . . <a href="#page-12">12</a>
73 <a href="#section-3">3</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
74 <a href="#section-4">4</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
75 <a href="#section-4.1">4.1</a>. The Mail Parameters Registry . . . . . . . . . . . . . . <a href="#page-13">13</a>
76 <a href="#section-4.2">4.2</a>. Trace Fields . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
77 <a href="#section-4.3">4.3</a>. The Solicitation Mail Header . . . . . . . . . . . . . . <a href="#page-14">14</a>
78 <a href="#section-5">5</a>. Author's Acknowledgements . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
79 <a href="#section-6">6</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
80 <a href="#section-6.1">6.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
81 <a href="#section-6.2">6.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
82 <a href="#appendix-A">Appendix A</a>. Collected ABNF Descriptions (Normative) . . . . . . . <a href="#page-18">18</a>
83 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
84 Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Malamud Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. The Spam Pandemic</span>
116
117 Unsolicited Bulk Email (UBE), otherwise known as spam, has become as
118 one of the most pressing issues on the Internet. One oft-quoted
119 study estimated that spam would cost businesses $13 billion in 2003
120 [<a href="#ref-Ferris" title="&quot;Study: Spam costs businesses $13 billion&quot;">Ferris</a>]. In April 2003, AOL reported that it had blocked 2.37
121 billion pieces of UBE in a single day [<a href="#ref-CNET" title="&quot;AOL touts spam-fighting prowess&quot;">CNET</a>]. And, in a sure sign
122 that UBE has become of pressing concern, numerous politicians have
123 begun to issue pronouncements and prescriptions for fighting this
124 epidemic [<a href="#ref-Schumer" title="&quot;Schumer, Christian Coalition Team Up to Crack Down on Email Spam Pornography&quot;">Schumer</a>][FTC].
125
126 A variety of mechanisms from the technical community have been
127 proposed and/or implemented to fight UBE:
128
129 o Whitelists are lists of known non-spammers. For example, Habeas,
130 Inc. maintains a Habeas User List (HUL) of people who have agreed
131 to not spam. By including a haiku in email headers and enforcing
132 copyright on that ditty, they enforce their anti-spamming terms of
133 service [<a href="#ref-Habeas" title="&quot;Habeas Compliance Message&quot;">Habeas</a>].
134
135 o Blacklists are lists of known spammers or ISPs that allow spam
136 [<a href="#ref-ROKSO" title="&quot;Register of Known Spam Operations&quot;">ROKSO</a>].
137
138 o Spam filters run client-side or server-side to filter out spam
139 based on whitelists, blacklists, and textual and header analysis
140 [<a href="#ref-Assassin" title="&quot;Spamassassin - Mail Filter to Identify Spam Using Text Analysis&quot;">Assassin</a>].
141
142 o A large number of documents address the overall technical
143 considerations for the control of UBE [<a href="#ref-crocker-spam-techconsider">crocker-spam-techconsider</a>],
144 operational considerations for SMTP agents [<a href="./rfc2505" title="&quot;Anti-Spam Recommendations for SMTP MTAs&quot;">RFC2505</a>], and various
145 extensions to the protocols to support UBE identification and
146 filtering [<a href="#ref-danisch-dns-rr-smtp">danisch-dns-rr-smtp</a>][daboo-sieve-spamtest][crouzet-
147 amtp].
148
149 o Various proposals have been advanced for "do not spam" lists, akin
150 to the Federal Trade Commission's "Do Not Call" list for
151 telemarketers [<a href="#ref-FTC.TSR" title="&quot;Telemarketing Sales Rule&quot;">FTC.TSR</a>].
152
153 Terminology
154
155 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
156 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
157 document are to be interpreted as described in <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>
158 [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
159
160
161
162
163
164 <span class="grey">Malamud Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
167
168
169 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. No Soliciting in the Real World</span>
170
171 Municipalities frequently require solicitors to register with the
172 town government. And, in many cases, the municipalities prohibit
173 soliciting in residences where the occupant has posted a sign. The
174 town of West Newbury, Massachusetts, for example, requires:
175
176 "It shall be unlawful for any canvasser or solicitor to enter the
177 premises of a resident or business who has displayed a 'No
178 Trespassing' or 'No Soliciting' sign or poster. Further, it shall
179 be unlawful for canvassers or solicitors to ignore a resident or
180 business person's no solicitation directive or remain on private
181 property after its owner has indicated that the canvasser or
182 solicitor is not welcome" [<a href="#ref-Newbury" title="&quot;Soliciting/ Canvassing By-Law&quot;">Newbury</a>].
183
184 Registration requirements for solicitors, particularly those
185 soliciting for political or religious reasons, have been the subject
186 of a long string of court cases. However, the courts have generally
187 recognized that individuals may post "No Soliciting" signs and the
188 government may enforce the citizen's desire. In a recent case where
189 Jehovah's Witnesses challenged a registration requirement in the city
190 of Stratton, Connecticut, saying they derived their authority from
191 the Scriptures, not the city. However, the court noted:
192
193 "A section of the ordinance that petitioners do not challenge
194 establishes a procedure by which a resident may prohibit
195 solicitation even by holders of permits. If the resident files a
196 'No Solicitation Registration Form' with the mayor, and also posts
197 a 'No Solicitation' sign on his property, no uninvited canvassers
198 may enter his property... " [<a href="#ref-Watchtower" title="&quot;Watchtower Bible &amp; Tract Society of New York, Inc., et al. v. Village of Stratton et al.&quot;">Watchtower</a>].
199
200 Even government, which has a duty to promote free expression, may
201 restrict the use of soliciting on government property. In one case,
202 for example, a school district was allowed to give access to its
203 internal electronic mail system to the union that was representing
204 teachers, but was not required to do so to a rival union that was
205 attempting to gain the right to represent the teachers. The court
206 held that where property is not a traditional public forum "and the
207 Government has not dedicated its property to First Amendment
208 activity, such regulation is examined only for reasonableness"
209 [<a href="#ref-Perry" title="&quot;Perry Education Association v. Perry Local Educators' Association&quot;">Perry</a>].
210
211 The courts have consistently held that the state has a compelling
212 public safety reason for regulating solicitation. In Cantwell v.
213 Connecticut, the Supreme Court held that "a State may protect its
214 citizens from fraudulent solicitation by requiring a stranger in the
215 community, before permitting him publicly to solicit funds for any
216 purpose, to establish his identity and his authority to act for the
217
218
219
220 <span class="grey">Malamud Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
223
224
225 cause which he purports to represent" [<a href="#ref-Cantwell" title="&quot;Cantwell v. State of Connecticut&quot;">Cantwell</a>]. And, in Martin v.
226 City of Struthers, the court noted that "burglars frequently pose as
227 canvassers, either in order that they may have a pretense to discover
228 whether a house is empty and hence ripe for burglary, or for the
229 purpose of spying out the premises in order that they may return
230 later" [<a href="#ref-Martin" title="&quot;Martin v. City of Struthers, Ohio&quot;">Martin</a>]. The public safety issue applies very much to email,
231 where viruses can easily be delivered, in contrast to telephone
232 solicitations where public safety is not nearly as much an issue.
233
234 This analysis is U.S.-centric, which is partly due to the background
235 of the author. However, the concept of prohibiting unwanted
236 solicitation does carry over to other countries:
237
238 o In Hong Kong, offices frequently post "no soliciting" signs.
239
240 o In the United Kingdom, where door-to-door peddlers are fairly
241 common, "no soliciting" signs are also common.
242
243 o In Australia, where door-to-door does not appear to be a pressing
244 social problem, there was legislation passed which outlawed the
245 practice of placing ads under wipers of parked cars.
246
247 o In France, which has a long tradition of door-to-door
248 solicitation, apartment buildings often use trespass laws to
249 enforce "no solicitation" policies.
250
251 o In the Netherlands, where door-to-door solicitation is not a
252 pressing issue, there is a practice of depositing free
253 publications in mailboxes. The postal equivalent of "no spam"
254 signs are quite prevalent and serve notice that the publications
255 are not desired.
256
257 <span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. No Soliciting and Electronic Mail</span>
258
259 Many of the anti-spam proposals that have been advanced have great
260 merit, however none of them give notice to an SMTP agent in the
261 process of delivering mail that the receiver does not wish to receive
262 solicitations. Such a virtual sign would serve two purposes:
263
264 o It would allow the receiving system to "serve notice" that a
265 certain class of electronic mail is not desired.
266
267 o If a message is properly identified as belonging to a certain
268 class and that class of messages is not desired, transfer of the
269 message can be eliminated. Rather than filtering after delivery,
270 elimination of the message transfer can save network bandwidth,
271 disk space, and processing power.
272
273
274
275
276 <span class="grey">Malamud Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
279
280
281 This memo details a series of extensions to SMTP that have the
282 following characteristics:
283
284 o A service extension is described that allows a receiving Mail
285 Transport Agent (MTA) to signal the sending MTA that no soliciting
286 is in effect.
287
288 o A header field for the sender of the message is defined that
289 allows the sender to flag a message as conforming to a certain
290 class.
291
292 o Trace fields for intermediate MTAs are extended to allow the
293 intermediate MTA to signal that a message is in a certain class.
294
295 Allowing the sender of a message to tag a message as being, for
296 example, unsolicited commercial email with adult content, allows
297 "good" spammers to conform to legal content labelling requirements by
298 governmental authorities, license agreements with service providers,
299 or conventions imposed by "whitelist" services. For senders of mail
300 who choose not to abide by these conventions, the intermediate trace
301 fields defined here allow the destination MTAs to perform appropriate
302 dispositions on the received message.
303
304 This extension provides a simple mean for senders, MTAs, and
305 receivers to assert keywords. This extension does not deal with any
306 issues of authentication or consent.
307
308 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The No-Soliciting SMTP Service Extension</span>
309
310 Per [<a href="./rfc2821" title="&quot;Simple Mail Transfer Protocol&quot;">RFC2821</a>], a "NO-SOLICITING" SMTP service extension is defined.
311 The service extension is declared during the initial "EHLO" SMTP
312 exchange. The extension has one optional parameter, consisting of
313 zero or more solicitation class keywords. Using the notation as
314 described in the Augmented BNF [<a href="./rfc2234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC2234</a>], the syntax is:
315
316 No-Soliciting-Service = "NO-SOLICITING"
317 [ SP Solicitation-keywords ]
318
319 As will be further described below, the "Solicitation-keywords"
320 construct is used to indicate which classes of messages are not
321 desired. A keyword that is presented during the initial "EHLO"
322 exchange applies to all messages exchanged in this session. As will
323 also be further described below, additional keywords may be specified
324 on a per-recipient basis as part of the response to a "RCPT TO"
325 command.
326
327
328
329
330
331
332 <span class="grey">Malamud Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
335
336
337 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. The EHLO Exchange</span>
338
339 Keywords presented during the initial exchange indicate that no
340 soliciting in the named classes is in effect for all messages
341 delivered to this system. It is equivalent to the sign on the door
342 of an office building announcing a company-wide policy. For example:
343
344 R: &lt;wait for connection on TCP port 25&gt;
345 S: &lt;open connection to server&gt;
346 R: 220 trusted.example.com SMTP service ready
347 S: EHLO untrusted.example.com
348 R: 250-trusted.example.com says hello
349 R: 250-ENHANCEDSTATUSCODES
350 R: 250-NO-SOLICITING net.example:ADV
351 R: 250 SIZE 20480000
352
353 The "net.example:ADV" parameter to the "NO-SOLICITING" extension is
354 an example of a solicitation class keyword, the syntax of which is
355 described in the following section.
356
357 Historical Note:
358
359 A similar proposal was advanced in 1999 by John Levine and Paul
360 Hoffman. This proposal used the SMTP greeting banner to specify
361 that unsolicited bulk email is prohibited on a particular system
362 through the use of the "NO UCE" keyword [<a href="#ref-Levine" title="&quot;Anti-UBE and Anti-UCE Keywords in SMTP Banners&quot;">Levine</a>]. As the authors
363 note, their proposal has the potential of overloading the
364 semantics of the greeting banner, which may also be used for other
365 purposes (see, e.g., [<a href="#ref-Malamud" title="&quot;An Internet Prayer Wheel&quot;">Malamud</a>]).
366
367 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Solicitation Class Keywords</span>
368
369 The "NO-SOLICITING" service extension uses solicitation class
370 keywords to signify classes of solicitations that are not accepted.
371 Solicitation class keywords are separated by commas.
372
373 There is no default solicitation class keyword for the service. In
374 other words, the following example is a "no-op":
375
376 R : 250-NO-SOLICITING
377
378 While the above example is a "no-op" it is useful for an MTA that
379 wishes to pass along all messages, but would also like to pass along
380 "SOLICIT=" parameters on a message-by-message basis. The above
381 example invokes the use of the extension but does not signal any
382 restrictions by class of message.
383
384
385
386
387
388 <span class="grey">Malamud Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
391
392
393 The initial set of solicitation class keywords all begin with a
394 domain name with the labels reversed, followed by a colon. For
395 example, the domain name "example.com" could be used to form the
396 beginning of a solicitation class keyword of "com.example:". The
397 solicitation class keyword is then followed by an arbitrary set of
398 characters drawn from the following construct:
399
400 Solicitation-keywords = word
401 0*("," word)
402 ; length of this string is limited
403 ; to &lt;= 1000 characters
404 word = ALPHA 0*(wordchar)
405 wordchar = ("." / "-" / "_" / ":" / ALPHA / DIGIT)
406
407 A solicitation class keyword MUST be less than 1000 characters. Note
408 however that a set of keywords used in the operations defined in this
409 document must also be less than 1000 characters. Implementors are
410 thus advised to keep their solicitation class keywords brief.
411
412 Any registrant of a domain name may define a solicitation class
413 keyword. Discovery of solicitation class keywords is outside the
414 scope of this document. However, those registrants defining keywords
415 are advised to place a definition of their solicitation class
416 keywords on a prominent URL under their control such that search
417 engines and other discovery mechanisms can find them.
418
419 While this document defines solicitation class keywords as beginning
420 with a reversed domain name followed by a colon (":"), future RFCs
421 may define additional mechanisms that do not conflict with this
422 naming scheme.
423
424 <span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>. Note on Choice of Solicitation Class Keywords</span>
425
426 This document does not specify which solicitation class keywords
427 shall or shall not be used on a particular message. The requirement
428 to use a particular keyword is a policy decision well outside the
429 scope of this document. It is expected that relevant policy bodies
430 (e.g., governments, ISPs, developers, or others) will specify
431 appropriate keywords, the definition of the meaning of those
432 keywords, and any other policy requirements, such as a requirement to
433 use or not use this extension in particular circumstances.
434
435 During discussions of this proposal, there were several suggestions
436 to do away with the solicitation class keywords altogether and
437 replace the mechanism with a simple boolean (e.g., "NO-SOLICITING
438 YES" or "ADV" or "UBE"). Under a boolean mechanism, this extension
439 would have to adopt a single definition of what "YES" or other label
440
441
442
443
444 <span class="grey">Malamud Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
447
448
449 means. By using the solicitation class keywords approach, the mail
450 infrastructure remains a neutral mechanism, allowing different
451 definitions to co-exist.
452
453 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. The MAIL FROM Command</span>
454
455 "SOLICIT" is defined as a parameter for the "MAIL FROM" command. The
456 "SOLICIT" parameter is followed by an equal sign and a comma
457 separated list of solicitation class keywords. The syntax for this
458 parameter is:
459
460 Mail-From-Solicit-Parameter = "SOLICIT"
461 "=" Solicitation-keywords
462 ; Solicitation-keywords, when used in MAIL FROM command
463 ; MUST be identical to those in the Solicitation: header.
464
465 Note that white space is not permitted in this production.
466
467 As an informational message, the "550" or "250" replies to the "RCPT
468 TO" command may also contain the "SOLICIT" parameter. If a message
469 is being rejected due to a solicitation class keyword match,
470 implementations SHOULD echo which solicitation classes are in effect.
471 See <a href="#section-2.4">Section 2.4</a> for more on error reporting.
472
473 The receiving system may decide on a per-message basis the
474 appropriate disposition of messages:
475
476 R: &lt;wait for connection on TCP port 25&gt;
477 S: &lt;open connection to server&gt;
478 R: 220 trusted.example.com SMTP service ready
479 S: EHLO untrusted.example.com
480 R: 250-trusted.example.com says hello
481 R: 250-NO-SOLICITING net.example:ADV
482 S: MAIL FROM:&lt;[email protected]&gt; SOLICIT=org.example:ADV:ADLT
483 S: RCPT TO:&lt;[email protected]&gt;
484 R: 250 &lt;[email protected]&gt;... Recipient ok
485 S: RCPT TO:&lt;[email protected]&gt;
486 R: 550 &lt;[email protected]&gt; SOLICIT=org.example:ADV:ADLT
487
488 In the previous example, the receiving MTA returned a "550" status
489 code, indicating that one message was being rejected. The
490 implementation also echoes back the currently set keywords for that
491 user on the "550" status message. The solicitation class keyword
492 which is echoed back is "org.example:ADV:ADLT" which illustrates how
493 this per-recipient solicitation class keyword has supplemented the
494 base "net.example:ADV" class declared in the "EHLO" exchange.
495
496
497
498
499
500 <span class="grey">Malamud Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
503
504
505 It is the responsibility of a receiving MTA to maintain a consistent
506 policy. If the receiving MTA will reject a message because of
507 solicitation class keywords, the MTA SHOULD declare those keywords
508 either in the initial "EHLO" exchange or on a per-recipient basis.
509 Likewise, a receiving MTA SHOULD NOT deliver a message where the
510 "Solicitation:" matches a solicitation class keyword that was
511 presented during the initial "EHLO" exchange or on a per-recipient
512 basis.
513
514 Developers should also note that the source of the solicitation class
515 keywords used in the "MAIL FROM" command MUST be the "Solicitation:"
516 header described in <a href="#section-2.5">Section 2.5</a> and MUST NOT be supplemented by
517 additional solicitation class keywords derived from the "Received:"
518 header trace fields which are described in <a href="#section-2.6">Section 2.6</a>.
519
520 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Error Reporting and Enhanced Mail Status Codes</span>
521
522 If a session between two MTAs is using both the "NO-SOLICITING"
523 extension and the Enhanced Mail Status Codes as defined in [<a href="./rfc3463" title="&quot;Enhanced Mail System Status Codes&quot;">RFC3463</a>]
524 and a message is rejected based on the presence of a "SOLICIT"
525 parameter, the correct error message to return will usually be
526 "5.7.1", defined as "the sender is not authorized to send to the
527 destination... (because) of per-host or per-recipient filtering."
528
529 Other codes, including temporary status codes, may be more
530 appropriate in some circumstances and developers should look to
531 [<a href="./rfc3463" title="&quot;Enhanced Mail System Status Codes&quot;">RFC3463</a>] on this subject. An example of such a situation might be
532 the use of quotas or size restrictions on messages by class. An
533 implementation MAY impose limits such as message size restrictions
534 based on solicitation classes, and when such limits are exceed they
535 SHOULD be reported using whatever status code is appropriate for that
536 limit.
537
538 In all cases, an implementation SHOULD include a "Mail-From-Solicit-
539 Parameter" on a "550" or other reply that rejects message delivery.
540 The parameter SHOULD includes the solicitation class keyword(s) that
541 matched. In addition to the solicitation class keyword(s) that
542 matched, an implementation MAY include additional solicitation class
543 keywords that are in effect.
544
545 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Solicitation Mail Header</span>
546
547 Per [<a href="./rfc2822" title="&quot;Internet Message Format&quot;">RFC2822</a>], a new "Solicitation:" header field is defined which
548 contains one or more solicitation class keywords.
549
550 Solicitation-header = "Solicitation:" 1*SP Solicitation-keywords
551
552
553
554
555
556 <span class="grey">Malamud Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
559
560
561 An example of this header follows:
562
563 To: Coupon Clipper &lt;[email protected]&gt;
564 From: Spam King &lt;[email protected]&gt;
565 Solicitation: net.example:ADV,org.example:ADV:ADLT
566
567 Several proposals, particularly legal ones, have suggested requiring
568 the use of keywords in the "Subject:" header. While embedding
569 information in the "Subject:" header may provide visual cues to end
570 users, it does not provide a straightforward set of cues for computer
571 programs such as mail transfer agents. As with embedding a "no
572 solicitation" message in a greeting banner, this overloads the
573 semantics of the "Subject:" header. Of course, there is no reason
574 why both mechanisms can't be used, and in any case the
575 "Solicitation:" header could be automatically inserted by the
576 sender's Mail User Agent (MUA) based on the contents of the subject
577 line.
578
579 <span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Insertion of Solicitation Keywords in Trace Fields</span>
580
581 The "Solicitation:" mail header is only available to the sending
582 client. RFCs 2821 and 2822 are quite specific that intermediate MTAs
583 shall not change message headers, with the sole exception of the
584 "Received:" trace field. Since many current systems use an
585 intermediate relay to detect unsolicited mail, an addition to the
586 "Received:" header is described.
587
588 [<a id="ref-RFC2821">RFC2821</a>] documents the following productions for the "Received:"
589 header in a mail message:
590
591 ; From <a href="./rfc2821">RFC 2821</a>
592 With = "WITH" FWS Protocol CFWS
593 Protocol = "ESMTP" / "SMTP" / Attdl-Protocol
594
595 Additionally, [<a href="./rfc2822" title="&quot;Internet Message Format&quot;">RFC2822</a>] defines a comment field as follows:
596
597 ; From <a href="./rfc2822">RFC 2822</a>
598 comment = "(" *([FWS] ccontent) [FWS] ")"
599 ccontent = ctext / quoted-pair / comment
600
601 The "Mail-From-Solicit-Parameter" defined in <a href="#section-2.3">Section 2.3</a> above is a
602 restricted form of ctext, yielding the following production:
603
604 With-Solicit = "WITH" FWS Protocol
605 "(" [FWS] comment [FWS] ")"
606 comment = "(" *([FWS] ccontent) [FWS] ")"
607 ccontent = ctext / quoted-pair /
608 comment / Mail-From-Solicit-Parameter
609
610
611
612 <span class="grey">Malamud Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
615
616
617 ; The Mail-From-Solicit-Parameter
618 ; is a restricted form of ctext
619
620 An example of a Received: header from a conforming MTA is as follows:
621
622 Received: by foo-mta.example.com with
623 ESMTP (SOLICIT=net.example:ADV,org.example:ADV:ADLT) ;
624 Sat, 9 Aug 2003 16:54:42 -0700 (PDT)
625
626 It should be noted that keywords presented in trace fields may not
627 agree with those found in the "Solicitation:" header and trace fields
628 may exist even if the header is not present. When determining which
629 keywords are applicable to a particular exchange of messages,
630 implementors SHOULD examine any keywords found in the "Solicitation:"
631 header. Implementors MAY examine other keywords found in the trace
632 fields.
633
634 <span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Relay of Messages</span>
635
636 The "NO-SOLICITING" service extension, if present, applies to all
637 messages handled by the receiving Message Transfer Agent (MTA),
638 including those messages intended to be relayed to another system.
639
640 Solicitation class keywords supplied by a client on a "SOLICIT"
641 parameter on a "MAIL FROM" command SHOULD be obtained from the
642 "Solicitation:" field in the message header. An SMTP client SHOULD,
643 however, verify that the list of solicitation class keywords obtained
644 from the "Solicitation:" field uses valid syntax before conveying its
645 contents. An SMTP server SHOULD set this parameter after detecting
646 the presence of the "Solicitation:" header field when receiving a
647 message from a non-conforming MTA.
648
649 <span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. No Default Solicitation Class</span>
650
651 Implementations of "NO-SOLICITING" service extension SHOULD NOT
652 enable specific solicitation class keywords as a default in their
653 software. There are some indications that some policy makers may
654 view a default filtering in software as a prior restraint on
655 commercial speech. In other words, because the person installing and
656 using the software did not make an explicit choice to enable a
657 certain type of filtering, some might argue that such filtering was
658 not desired.
659
660 Likewise, it is recommended that a system administrator installing
661 software SHOULD NOT enable additional per-recipient filtering by
662 default for a user. Again, individual users should specifically
663 request any additional solicitation class keywords.
664
665
666
667
668 <span class="grey">Malamud Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
671
672
673 The mechanism for an individual user to communicate their desire to
674 enable certain types of filtering is outside the scope of this
675 document.
676
677 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
678
679 This extension does not provide authentication of senders or other
680 measures intended to promote security measures during the message
681 exchange process.
682
683 In particular, this document does not address the circumstances under
684 which a sender of electronic mail should or should not use this
685 extension and does not address the issues of whether consent to send
686 mail has been granted.
687
688 This might lead to a scenario in which a sender of electronic mail
689 begins to use this extension well before the majority of end users
690 have begun to use it. In this scenario, the sender might wish to use
691 the absence of the extension on the receiving MTA as an implication
692 of consent to receive mail. Non-use of the "NO-SOLICITING" extension
693 by a receiving MTA SHALL NOT indicate consent.
694
695 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
696
697 There are three IANA considerations presented in this document:
698
699 1. Addition of the "NO-SOLICITING" service extension to the Mail
700 Parameters registry.
701
702 2. Documentation of the use of comments in trace fields.
703
704 3. Creation of a "Solicitation:" mail header.
705
706 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. The Mail Parameters Registry</span>
707
708 The IANA Mail Parameters registry documents SMTP service extensions.
709 The "NO-SOLICITATION" service extension has been added to this
710 registry as follows.
711
712 Keywords Description Reference
713 ------------ ------------------------------ ---------
714 NO-SOLICITING Notification of no soliciting. <a href="./rfc3865">RFC3865</a>
715
716 The parameters subregistry would need to be modified as follows:
717
718 Service Ext EHLO Keyword Parameters Reference
719 ----------- ------------ ----------- ---------
720 No Soliciting NO-SOLICITING Solicitation-keywords <a href="./rfc3865">RFC3865</a>
721
722
723
724 <span class="grey">Malamud Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
727
728
729 The maximum length of Solicitation-keywords is 1000 characters. The
730 "SOLICIT=" parameter is defined for use on the MAIL FROM command.
731 The potential length of the MAIL FROM command is thus increased by
732 1007 characters.
733
734 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Trace Fields</span>
735
736 The Mail Parameters registry would need to be modified to note the
737 use of the comment facility in trace fields to indicate Solicitation
738 Class Keywords.
739
740 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. The Solicitation Mail Header</span>
741
742 Per [<a href="./rfc3864" title="&quot;Registration Procedures for Message Header Fields&quot;">RFC3864</a>], the "Solicitation:" header field is added to the IANA
743 Permanent Message Header Field Registry. The following is the
744 registration template:
745
746 o Header field name: Solicitation
747 o Applicable protocol: mail
748 o Status: standard
749 o Author/Change controller: IETF
750 o Specification document(s): <a href="./rfc3865">RFC3865</a>
751 o Related information:
752
753 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Author's Acknowledgements</span>
754
755 The author would like to thank Rebecca Malamud for many discussions
756 and ideas that led to this proposal and to John C. Klensin and
757 Marshall T. Rose for their extensive input on how it could be
758 properly implemented in SMTP. Eric Allman, Harald Alvestrand, Steven
759 M. Bellovin, Doug Barton, Kent Crispin, Dave Crocker, Ned Freed,
760 Curtis Generous, Arnt Gulbrandsen, John Levine, Keith Moore, Hector
761 Santos, Ted Hardie, Paul Vixie, and Pindar Wong kindly provided
762 reviews of the document and/or suggestions for improvement.
763 Information about soliciting outside the U.S. was received from Rob
764 Blokzijl, Jon Crowcroft, Christian Huitema, Geoff Huston, and Pindar
765 Wong. John Levine pointed out the contrast between this proposal and
766 "do not spam" lists. As always, all errors and omissions are the
767 responsibility of the author.
768
769
770
771
772
773
774
775
776
777
778
779
780 <span class="grey">Malamud Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
783
784
785 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
786
787 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
788
789 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
790 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
791
792 [<a id="ref-RFC2234">RFC2234</a>] Crocker, D., Ed. and P. Overell, "Augmented BNF for
793 Syntax Specifications: ABNF", <a href="./rfc2234">RFC 2234</a>, November 1997.
794
795 [<a id="ref-RFC2821">RFC2821</a>] Klensin, J., Ed., "Simple Mail Transfer Protocol", <a href="./rfc2821">RFC</a>
796 <a href="./rfc2821">2821</a>, April 2001.
797
798 [<a id="ref-RFC2822">RFC2822</a>] Resnick, P., Ed., "Internet Message Format", <a href="./rfc2822">RFC 2822</a>,
799 April 2001.
800
801 [<a id="ref-RFC3463">RFC3463</a>] Vaudreuil, G., "Enhanced Mail System Status Codes", <a href="./rfc3463">RFC</a>
802 <a href="./rfc3463">3463</a>, January 2003.
803
804 [<a id="ref-RFC3864">RFC3864</a>] Klyne, G., Nottingham, M., and J. Mogul, "Registration
805 Procedures for Message Header Fields", <a href="https://www.rfc-editor.org/bcp/bcp90">BCP 90</a>, <a href="./rfc3864">RFC 3864</a>,
806 September 2004.
807
808 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
809
810 [<a id="ref-Assassin">Assassin</a>] Mason, J., "Spamassassin - Mail Filter to Identify Spam
811 Using Text Analysis", Version 2.55, May 2003,
812 &lt;<a href="http://www.mirror.ac.uk/sites/spamassassin.taint.org/spamassassin.org/doc/spamassassin.html">http://www.mirror.ac.uk/sites/spamassassin.taint.org/</a>
813 <a href="http://www.mirror.ac.uk/sites/spamassassin.taint.org/spamassassin.org/doc/spamassassin.html">spamassassin.org/doc/spamassassin.html</a>&gt;
814
815 [<a id="ref-CNET">CNET</a>] CNET News.Com, "AOL touts spam-fighting prowess", April
816 2003, &lt;<a href="http://news.com.com/2100-1025-998944.html">http://news.com.com/2100-1025-998944.html</a>&gt;.
817
818 [<a id="ref-Cantwell">Cantwell</a>] U.S. Supreme Court, "Cantwell v. State of Connecticut",
819 310 U.S. 296 (1940), May 1940,
820 &lt;<a href="http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=US&amp;vol=310&amp;invol=296">http://caselaw.lp.findlaw.com/scripts/</a>
821 <a href="http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=US&amp;vol=310&amp;invol=296">getcase.pl?court=US&amp;vol=310&amp;invol=296</a>&gt;
822
823 [<a id="ref-FTC">FTC</a>] Federal Trade Commission, "Federal, State, Local Law
824 Enforcers Target Deceptive Spam and Internet Scams",
825 November 2002,
826 &lt;<a href="http://www.ftc.gov/opa/2002/11/nenetforcema.htm">http://www.ftc.gov/opa/2002/11/nenetforcema.htm</a>&gt;.
827
828 [<a id="ref-FTC.TSR">FTC.TSR</a>] Federal Trade Commission, "Telemarketing Sales Rule",
829 Federal Register Vol. 68, No. 19, January 2003,
830 &lt;<a href="http://www.ftc.gov/os/2002/12/tsrfinalrule.pdf">http://www.ftc.gov/os/2002/12/tsrfinalrule.pdf</a>&gt;.
831
832
833
834
835
836 <span class="grey">Malamud Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
839
840
841 [<a id="ref-Ferris">Ferris</a>] Associated Press, "Study: Spam costs businesses $13
842 billion", January 2003,
843 &lt;<a href="http://www.cnn.com/2003/TECH/biztech/01/03/spam.costs.ap/index.html">http://www.cnn.com/2003/TECH/biztech/01/03/</a>
844 <a href="http://www.cnn.com/2003/TECH/biztech/01/03/spam.costs.ap/index.html">spam.costs.ap/index.html</a>&gt;
845
846 [<a id="ref-Habeas">Habeas</a>] Habeas, Inc., "Habeas Compliance Message", 2004,
847 &lt;<a href="http://www.habeas.com/servicesComplianceStds.html">http://www.habeas.com/servicesComplianceStds.html</a>&gt;
848
849 [<a id="ref-crocker-spam-techconsider">crocker-spam-techconsider</a>]
850 Crocker, D., "Technical Considerations for Spam Control
851 Mechanisms", Work in Progress, February 2004.
852
853 [<a id="ref-crouzet-amtp">crouzet-amtp</a>]
854 Crouzet, B., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22Authenticated+Mail+Transfer+Protocol%22'>"Authenticated Mail Transfer Protocol"</a>,
855 Work in Progress, May 2004.
856
857 [<a id="ref-daboo-sieve-spamtest">daboo-sieve-spamtest</a>]
858 Daboo, C., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22SIEVE+Spamtest+and+Virustest+Extensions%22'>"SIEVE Spamtest and Virustest Extensions"</a>,
859 Work in Progress, October 2003.
860
861 [<a id="ref-danisch-dns-rr-smtp">danisch-dns-rr-smtp</a>]
862 Danisch, H., "The RMX DNS RR and method for lightweight
863 SMTP sender authorization", Work in Progress, August
864 2004.
865
866 [<a id="ref-Levine">Levine</a>] Levine, J. and P. Hoffman, "Anti-UBE and Anti-UCE
867 Keywords in SMTP Banners", Revision 1.1, March 1999,
868 &lt;<a href="http://www.cauce.org/proposal/smtp-banner-rfc.shtml">http://www.cauce.org/proposal/smtp-banner-rfc.shtml</a>&gt;.
869
870 [<a id="ref-Malamud">Malamud</a>] Malamud, C., "An Internet Prayer Wheel", Mappa.Mundi
871 Magazine, August 1999,
872 &lt;<a href="http://mappa.mundi.net/cartography/Wheel/">http://mappa.mundi.net/cartography/Wheel/</a>&gt;.
873
874 [<a id="ref-Martin">Martin</a>] U.S. Supreme Court, "Martin v. City of Struthers, Ohio",
875 319 U.S. 141 (1943), May 1943,
876 &lt;<a href="http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=US&amp;vol=319&amp;invol=141">http://caselaw.lp.findlaw.com/scripts/</a>
877 <a href="http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=US&amp;vol=319&amp;invol=141">getcase.pl?court=US&amp;vol=319&amp;invol=141</a>&gt;
878
879 [<a id="ref-Newbury">Newbury</a>] The Town of West Newbury, Massachusetts, "Soliciting/
880 Canvassing By-Law", Chapter 18 <a href="#section-10">Section 10</a>, March 2002,
881 &lt;<a href="http://www.town.west-newbury.ma.us/Public_Documents/WestNewburyMA_Bylaws/000A1547-70E903AC">http://www.town.west-newbury.ma.us/Public_Documents/</a>
882 <a href="http://www.town.west-newbury.ma.us/Public_Documents/WestNewburyMA_Bylaws/000A1547-70E903AC">WestNewburyMA_Bylaws/000A1547-70E903AC</a>&gt;
883
884 [<a id="ref-Perry">Perry</a>] U.S. Supreme Court, "Perry Education Association v.
885 Perry Local Educators' Association", 460 U.S. 37 (1983),
886 February 1983, &lt;<a href="http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=US&amp;vol=460&amp;invol=37">http://caselaw.lp.findlaw.com/scripts/</a>
887 <a href="http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=US&amp;vol=460&amp;invol=37">getcase.pl?court=US&amp;vol=460&amp;invol=37</a>&gt;
888
889
890
891
892 <span class="grey">Malamud Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
895
896
897 [<a id="ref-RFC2505">RFC2505</a>] Lindberg, G., "Anti-Spam Recommendations for SMTP MTAs",
898 <a href="https://www.rfc-editor.org/bcp/bcp30">BCP 30</a>, <a href="./rfc2505">RFC 2505</a>, February 1999.
899
900 [<a id="ref-ROKSO">ROKSO</a>] Spamhaus.Org, "Register of Known Spam Operations",
901 November 2003,
902 &lt;<a href="http://www.spamhaus.org/rokso/index.lasso">http://www.spamhaus.org/rokso/index.lasso</a>&gt;.
903
904 [<a id="ref-Schumer">Schumer</a>] Charles, C., "Schumer, Christian Coalition Team Up to
905 Crack Down on Email Spam Pornography", June 2003,
906 &lt;<a href="http://www.senate.gov/~schumer/SchumerWebsite/pressroom/press_releases/PR01782.html">http://</a>
907 <a href="http://www.senate.gov/~schumer/SchumerWebsite/pressroom/press_releases/PR01782.html">www.senate.gov/~schumer/SchumerWebsite/pressroom/</a>
908 <a href="http://www.senate.gov/~schumer/SchumerWebsite/pressroom/press_releases/PR01782.html">press_releases/PR01782.html</a>&gt;.
909
910 [<a id="ref-Watchtower">Watchtower</a>] U.S. Supreme Court, "Watchtower Bible &amp; Tract Society of
911 New York, Inc., et al. v. Village of Stratton et al.",
912 122 S.Ct. 2080 (2002), June 2002,
913 &lt;<a href="http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=US&amp;vol=000&amp;invol=00-1737">http://caselaw.lp.findlaw.com/scripts/</a>
914 <a href="http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=US&amp;vol=000&amp;invol=00-1737">getcase.pl?court=US&amp;vol=000&amp;invol=00-1737</a>&gt;
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948 <span class="grey">Malamud Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
951
952
953 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Collected ABNF Descriptions (Normative)</span>
954
955 Solicitation-keywords = word
956 0*("," word)
957 ; length of this string is limited
958 ; to &lt;= 1000 characters
959 word = ALPHA 0*(wordchar)
960 wordchar = ("." / "-" / "_" / ":" / ALPHA / DIGIT)
961
962 ; used in the initial EHLO exchange
963 No-Soliciting-Service = "NO-SOLICITING"
964 [ SP Solicitation-keywords ]
965
966 ; used on the Solicitation: message header
967 Solicitation-header = "Solicitation:" 1*SP Solicitation-keywords
968
969 ; used on the MAIL FROM command and replies,
970 ; and on Received: headers.
971 Mail-From-Solicit-Parameter =
972 "SOLICIT" "=" Solicitation-keywords
973 ; Solicitation-keywords, when used in
974 ; the MAIL FROM command MUST be identical
975 ; to those in the Solicitation: header.
976
977 ; Used on Received: headers
978 With-Solicit = "WITH" FWS Protocol
979 "(" [FWS] comment [FWS] ")"
980 ; From <a href="./rfc2822">RFC 2822</a>
981 comment = "(" *([FWS] ccontent) [FWS] ")"
982 ccontent = ctext / quoted-pair /
983 comment / Mail-From-Solicit-Parameter
984 ; The Mail-From-Solicit-Parameter
985 ; is a restricted form of ctext
986 ; From <a href="./rfc2821">RFC 2821</a>
987 With = "WITH" FWS Protocol CFWS
988 Protocol = "ESMTP" / "SMTP" / Attdl-Protocol
989 Attdl-Protocol = Atom
990
991 Author's Address
992
993 Carl Malamud
994 Memory Palace Press
995 PO Box 300
996 Sixes, OR 97476
997 US
998
999 EMail: [email protected]
1000
1001
1002
1003
1004 <span class="grey">Malamud Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc3865">RFC 3865</a> No Soliciting September 2004</span>
1007
1008
1009 Full Copyright Statement
1010
1011 Copyright (C) The Internet Society (2004). This document is subject
1012 to the rights, licenses and restrictions contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and
1013 except as set forth therein, the authors retain all their rights.
1014
1015 This document and the information contained herein are provided on an
1016 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1017 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
1018 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
1019 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
1020 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1021 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1022
1023 Intellectual Property
1024
1025 The IETF takes no position regarding the validity or scope of any
1026 Intellectual Property Rights or other rights that might be claimed to
1027 pertain to the implementation or use of the technology described in
1028 this document or the extent to which any license under such rights
1029 might or might not be available; nor does it represent that it has
1030 made any independent effort to identify any such rights. Information
1031 on the procedures with respect to rights in RFC documents can be
1032 found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
1033
1034 Copies of IPR disclosures made to the IETF Secretariat and any
1035 assurances of licenses to be made available, or the result of an
1036 attempt made to obtain a general license or permission for the use of
1037 such proprietary rights by implementers or users of this
1038 specification can be obtained from the IETF on-line IPR repository at
1039 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
1040
1041 The IETF invites any interested party to bring to its attention any
1042 copyrights, patents or patent applications, or other proprietary
1043 rights that may cover technology that may be required to implement
1044 this standard. Please address the information to the IETF at ietf-
1045 [email protected].
1046
1047 Acknowledgement
1048
1049 Funding for the RFC Editor function is currently provided by the
1050 Internet Society.
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060 Malamud Standards Track [Page 19]
1061 </pre>