Archive of ietf-822, by thread

• draft-welzl-expires-00, Alfred Hönes
  • Re: draft-welzl-expires-00, Michael Welzl
• 5321 and 5322 are published!, Tony Hansen
  • Re: 5321 and 5322 are published!, SM
  • Re: 5321 and 5322 are published!, Hector Santos
  • <Possible follow-ups>
  • Re: 5321 and 5322 are published!, John C Klensin
  • Re: 5321 and 5322 are published!, Arnt Gulbrandsen
    • Re: 5321 and 5322 are published!, Keith Moore
    • Re: 5321 and 5322 are published!, Charles Lindsey
      • Re: 5321 and 5322 are published!, Tony Hansen
• Re: Fw: requested tweak to 2822upd grammar - consensus call, Charles Lindsey
• On ABNF in 5322: Advice needed, Pete Resnick
  • Re: On ABNF in 5322: Advice needed, Alessandro Vesely
  • Re: On ABNF in 5322: Advice needed, Abhijit Menon-Sen
  • Re: On ABNF in 5322: Advice needed, Arnt Gulbrandsen
    • Re: On ABNF in 5322: Advice needed, ned+ietf-822
      • Re: On ABNF in 5322: Advice needed, Dave CROCKER
      • Re: On ABNF in 5322: Advice needed, Tony Finch
      • Re: On ABNF in 5322: Advice needed, Dave CROCKER
      • Re: On ABNF in 5322: Advice needed, Tony Finch
      • Re: On ABNF in 5322: Advice needed, Pete Resnick
  • Message not available
    • Re: On ABNF in 5322: Advice needed, Bill McQuillan
      • Re: On ABNF in 5322: Advice needed, Tony Hansen
  • Re: On ABNF in 5322: Advice needed, SM
  • <Possible follow-ups>
  • Re: On ABNF in 5322: Advice needed, Charles Lindsey
    • Re: On ABNF in 5322: Advice needed, Arnt Gulbrandsen
• fyi re 2821bis and 2822upd, Tony Hansen
• subscribe1, Gabriel Bendayan
• Fw: requested tweak to 2822upd grammar, Tony Hansen
  • Re: Fw: requested tweak to 2822upd grammar, Dave CROCKER
    • Re: Fw: requested tweak to 2822upd grammar, Abhijit Menon-Sen
  • Re: Fw: requested tweak to 2822upd grammar, Arnt Gulbrandsen
  • Re: Fw: requested tweak to 2822upd grammar, Jeff Macdonald
  • Re: requested tweak to 2822upd grammar, Frank Ellermann
    • Re: requested tweak to 2822upd grammar, Frank Ellermann
    • Re: requested tweak to 2822upd grammar, Charles Lindsey
  • Re: Fw: requested tweak to 2822upd grammar, SM
  • Re: Fw: requested tweak to 2822upd grammar - consensus call, Tony Hansen
    • Re: Fw: requested tweak to 2822upd grammar - consensus call, Dave CROCKER
      • Re: Fw: requested tweak to 2822upd grammar - consensus call, ned+ietf-822
      • Re: Fw: requested tweak to 2822upd grammar - consensus call, Pete Resnick
      • Re: Fw: requested tweak to 2822upd grammar - consensus call, Tony Hansen
      • Re: Fw: requested tweak to 2822upd grammar - consensus call, Pete Resnick
      • Re: Fw: requested tweak to 2822upd grammar - consensus call, Arnt Gulbrandsen
      • Re: Fw: requested tweak to 2822upd grammar - consensus call, Tony Hansen
      • Re: Fw: requested tweak to 2822upd grammar - consensus call, Pete Resnick
      • Re: Fw: requested tweak to 2822upd grammar - consensus call, Pete Resnick
      • Re: Fw: requested tweak to 2822upd grammar - consensus call, Pete Resnick
• [Fwd: Protocol Action: 'Internet Message Format' to Draft Standard], Tony Hansen
  • Re: Protocol Action: 'Internet Message Format' to Draft Standard], Frank Ellermann
    • Re: Protocol Action: 'Internet Message Format' to Draft Standard], Pete Resnick
      • Re: Protocol Action: 'Internet Message Format' to Draft Standard], Frank Ellermann
• 2822upd approved, Frank Ellermann
  • Re: 2822upd approved, Tony Hansen
• Re: I-D Action:draft-reschke-rfc2231-in-http-00.txt, Julian Reschke
• mini BOF on mail standard maintenance, Tony Hansen
• Re: mail relay was: Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Arnt Gulbrandsen
  • Re: mail relay was: Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Tony Finch
  • Re: mail relay was: Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Dave Crocker
    • Re: mail relay was: Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, ned+ietf-822
• [no subject], arnt
• [no subject], arnt
• Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
  • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Frank Ellermann
    • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Frank Ellermann
  • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
    • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Lisa Dusseault
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Dave Crocker
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Tony Finch
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Tony Finch
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Tony Finch
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • MUA auto-configuration, was Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Tony Finch
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
    • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Charles Lindsey
  • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Jeff Macdonald
    • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
  • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
    • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
  • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Chris Haynes
    • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Paul Smith
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Frank Ellermann
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Paul Smith
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Paul Smith
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Frank Ellermann
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Chris Eastlund
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Bill McQuillan
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Bill McQuillan
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, ned+ietf-822
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Paul Smith
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, ned+ietf-822
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Paul Smith
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Pete Resnick
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Bill McQuillan
      • Re[2]: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Chris Haynes
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Charles Lindsey
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, ned+ietf-822
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re[2]: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Chris Haynes
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Charles Lindsey
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Charles Lindsey
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Arnt Gulbrandsen
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Frank Ellermann
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Frank Ellermann
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Pete Resnick
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, ned+ietf-822
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Tony Hansen
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Frank Ellermann
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, ned+ietf-822
      • Re: Intent to revive "expires" header - now: draft-welzl-expires-00.txt, Michael Welzl
      • Re: Intent to revive "expires" header - now: draft-welzl-expires-00.txt, Frank Ellermann
      • Re: Intent to revive "expires" header - now: draft-welzl-expires-00.txt, Michael Welzl
      • Re: Intent to revive "expires" header - now: draft-welzl-expires-00.txt, Frank Ellermann
      • Re: Intent to revive "expires" header - now: draft-welzl-expires-00.txt, Charles Lindsey
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Frank Ellermann
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, ned+ietf-822
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Russ Allbery
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Frank Ellermann
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Paul Smith
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Bill McQuillan
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Russ Allbery
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Russ Allbery
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Bill McQuillan
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Russ Allbery
      • Re: Intent to revive "expires" header fromdraft-ietf-mailext-new-fields-15, Charles Lindsey
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Charles Lindsey
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Charles Lindsey
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Chris Eastlund
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Frank Ellermann
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Expires: vs. Supersedes: (was: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15), Frank Ellermann
      • Re: Expires: vs. Supersedes:, Keith Moore
      • Re: Expires: vs. Supersedes:, Frank Ellermann
      • Re: Expires: vs. Supersedes:, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Charles Lindsey
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, ned+ietf-822
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Jeff Macdonald
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, ned+ietf-822
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Jeff Macdonald
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, ned+ietf-822
      • Expire header for Various Mail Processes, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Jeff Macdonald
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Arnt Gulbrandsen
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Tony Finch
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Arnt Gulbrandsen
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Tony Finch
      • mail relay was: Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Jeff Macdonald
      • Re: mail relay was: Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Keith Moore
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, ned+ietf-822
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Hector Santos
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Charles Lindsey
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
    • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
      • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Alessandro Vesely
    • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Charles Lindsey
  • Message not available
    • Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15, Michael Welzl
• 2822 implementation report request, Tony Hansen
• 2822upd <obs-FWS>, Frank Ellermann
• header un-folding & encoded headers, Paul Smith
  • Re: header un-folding & encoded headers, Paul Smith
  • Re: header un-folding & encoded headers, Keith Moore
• C-T-E: base64 and the real world.. what should an MUA do?, Valdis . Kletnieks
  • Re: C-T-E: base64 and the real world.. what should an MUA do?, Tony Hansen
    • Re: C-T-E: base64 and the real world.. what should an MUA do?, Florian Weimer
      • Re: C-T-E: base64 and the real world.. what should an MUA do?, Tony Hansen
      • Re: C-T-E: base64 and the real world.. what should an MUA do?, Arnt Gulbrandsen
  • Re: C-T-E: base64 and the real world.. what should an MUA do?, Arnt Gulbrandsen
• Conference on Email and Anti-Spam final call for papers, Barry Leiba
• Multiple message-ids., Dave Crocker
  • Re: Multiple message-ids., Frank Ellermann
  • Re: Multiple message-ids., Hector Santos
  • Re: Multiple message-ids., SM
  • Re: Multiple message-ids., Arnt Gulbrandsen
  • Re: Multiple message-ids., Tony Finch
    • Re: Multiple message-ids., Dave Crocker
      • Re: Multiple message-ids., Hector Santos
      • Re: Multiple message-ids., Mark Martinec
  • <Possible follow-ups>
  • Re: Multiple message-ids., Gary Welles
• monthly password reminders -- default to yes vs. no?, Dave Crocker
  • Re: monthly password reminders -- default to yes vs. no?, Alessandro Vesely
    • Re: monthly password reminders -- default to yes vs. no?, Ingo Klöcker
      • Re: monthly password reminders -- default to yes vs. no?, Dave Crocker
      • Re: monthly password reminders -- default to yes vs. no?, SM
  • <Possible follow-ups>
  • Re: monthly password reminders -- default to yes vs. no?, Arnt Gulbrandsen
• Re: I-D Action:draft-crocker-email-arch-10.txt, Frank Ellermann
• [Fwd: STD 68, RFC 5234 on Augmented BNF for Syntax Specifications: ABNF], Dave Crocker
• 2822upd-06 Sender, Frank Ellermann
  • Re: 2822upd-06 Sender, Hector Santos
  • Re: 2822upd-06 Sender, Pete Resnick
    • Re: 2822upd-06 Sender, Frank Ellermann
• 2822upd-06 submitted, Pete Resnick
  • Re: 2822upd-06 submitted, Frank Ellermann
    • Re: 2822upd-06 submitted, Pete Resnick
      • Re: 2822upd-06 submitted, Frank Ellermann
  • Re: 2822upd-06 submitted, Charles Lindsey
    • Re: 2822upd-06 submitted, Pete Resnick
  • <Possible follow-ups>
  • Re: Re: 2822upd-06 submitted, Arnt Gulbrandsen
    • Re: 2822upd-06 submitted, Tony Hansen
      • Re: 2822upd-06 submitted, Pete Resnick
    • Re: 2822upd-06 submitted, Charles Lindsey
  • Re: 2822upd-06 submitted, Arnt Gulbrandsen
• Local copies (html/txt/xml) always on home page, Pete Resnick
• 2822upd-05 just submitted, Pete Resnick
  • obs-commas (was: 2822upd-05 just submitted), Frank Ellermann
    • Re: obs-commas (was: 2822upd-05 just submitted), Frank Ellermann
    • Re: obs-commas (was: 2822upd-05 just submitted), Pete Resnick
      • Re: obs-commas (was: 2822upd-05 just submitted), Pete Resnick
      • Re: obs-commas (was: 2822upd-05 just submitted), Pete Resnick
      • Re: obs-commas (was: 2822upd-05 just submitted), Frank Ellermann
      • Re: obs-commas (was: 2822upd-05 just submitted), Pete Resnick
      • Re: obs-commas, Frank Ellermann
      • Re: obs-commas, Frank Ellermann
      • Re: obs-commas, Frank Ellermann
• 2822upd-04 body content restrictions, Bruce Lilly
  • Re: 2822upd-04 body content restrictions, Frank Ellermann
    • 2822upd-04 body content restrictions, Bruce Lilly
      • Re: 2822upd-04 body content restrictions, Pete Resnick
      • 2822upd-04 body content restrictions, Bruce Lilly
      • Re: 2822upd-04 body content restrictions, Frank Ellermann
      • Re: 2822upd-04 body content restrictions, Pete Resnick
      • Re: 2822upd-04 body content restrictions, Frank Ellermann
      • 2822upd-04 body content restrictions, Bruce Lilly
      • Re: 2822upd-04 body content restrictions, Frank Ellermann
  • Re: 2822upd-04 body content restrictions, ned+ietf-822
• 2822upd-04 field-name vs. line length and obs-optional, Bruce Lilly
  • Re: 2822upd-04 field-name vs. line length and obs-optional, Frank Ellermann
  • Re: 2822upd-04 field-name vs. line length and obs-optional, Pete Resnick
• 2822upd-04 definition of terms needed, Bruce Lilly
  • Re: 2822upd-04 definition of terms needed, Frank Ellermann
    • 2822upd-04 "local" time and zone offsets, Bruce Lilly
      • Re: 2822upd-04 "local" time and zone offsets, Pete Resnick
      • Re: 2822upd-04 "local" time and zone offsets, Frank Ellermann
      • Re: 2822upd-04 "local" time and zone offsets, ned+ietf-822
      • Re: 2822upd-04 "local" time and zone offsets, Dave Crocker
      • Re: 2822upd-04 "local" time and zone offsets, Frank Ellermann
      • Re: 2822upd-04 "local" time and zone offsets, Charles Lindsey
      • Re: 2822upd-04 "local" time and zone offsets, Tony Finch
  • Re: 2822upd-04 definition of terms needed, Pete Resnick
    • Re: 2822upd-04 definition of terms needed, Bruce Lilly
      • Re: 2822upd-04 definition of terms needed, Pete Resnick
      • Re: 2822upd-04 definition of terms needed, ned+ietf-822
      • Re: 2822upd-04 definition of terms needed, Dave Crocker
      • Re: 2822upd-04 definition of terms needed, SM
  • Re: 2822upd-04 definition of terms needed, SM
• 2822upd-04 line length limits, Bruce Lilly
  • Re: 2822upd-04 line length limits, Pete Resnick
    • typos in 2822upd-04, Bruce Lilly
      • Re: typos in 2822upd-04, Pete Resnick
  • Re: 2822upd-04 line length limits, Tony Hansen
    • Re: 2822upd-04 line length limits, Bruce Lilly
      • Re: 2822upd-04 line length limits, Tony Hansen
      • 2822upd-04 line length limits, Bruce Lilly
• 2822upd-04 "field" vs. "line", Bruce Lilly
  • Re: 2822upd-04 "field" vs. "line", Pete Resnick
• 2822upd-04 section 1 vs. section 4.1 discrepancy, Bruce Lilly
  • Re: 2822upd-04 section 1 vs. section 4.1 discrepancy, Pete Resnick
    • Re: 2822upd-04 section 1 vs. section 4.1 discrepancy, Frank Ellermann
      • Re: 2822upd-04 section 1 vs. section 4.1 discrepancy, Charles Lindsey
• Comma-seperated lists, Pete Resnick
  • Re: Comma-seperated lists, Frank Ellermann
    • Re: Comma-seperated lists, Pete Resnick
      • Re: Comma-seperated lists, Frank Ellermann
      • Comma-seperated lists, Bruce Lilly
      • Re: Comma-seperated lists, Frank Ellermann
      • Comma-seperated [sic] lists, Bruce Lilly
      • Re: Comma-seperated [sic] lists, Frank Ellermann
  • Re: Comma-seperated lists, Dave Crocker
    • Re: Comma-seperated lists, Pete Resnick
      • Re: Comma-seperated lists, Dave Crocker
• Space after colon - text requested, Pete Resnick
  • Re: Space after colon - text requested, Mark Martinec
    • Re: Space after colon - text requested, Frank Ellermann
    • Re: Space after colon - text requested, Charles Lindsey
• Remove quoted-pair domain literals, Pete Resnick
• rfc2822bis: "originator of the message" and "transmitter" not defined, Mark Martinec
  • Re: rfc2822bis: "originator of the message" and "transmitter" not defined, Pete Resnick
• New 2822upd-04 - obs-NO-WS-CTL, Pete Resnick
  • Re: New 2822upd-04 - obs-NO-WS-CTL, Charles Lindsey
    • Re: New 2822upd-04 - obs-NO-WS-CTL, Pete Resnick
      • Re: New 2822upd-04 - obs-NO-WS-CTL, ned+ietf-822
      • Re: New 2822upd-04 - obs-NO-WS-CTL, Charles Lindsey
      • quoted-pair in dcontent / Space after colon (Was: New 2822upd-04 - obs-NO-WS-CTL), Pete Resnick
      • Re: quoted-pair in dcontent / Space after colon (Was: New 2822upd-04 - obs-NO-WS-CTL), Charles Lindsey
      • Re: quoted-pair in dcontent / Space after colon, Mark Martinec
      • Re: quoted-pair in dcontent / Space after colon, Charles Lindsey
      • Re: quoted-pair in dcontent / Space after colon, Frank Ellermann
      • Re: quoted-pair in dcontent / Space after colon, Charles Lindsey
      • Re: quoted-pair in dcontent / Space after colon, Frank Ellermann
      • Re: quoted-pair in dcontent / Space after colon (Was: New 2822upd-04 - obs-NO-WS-CTL), Dave Crocker
      • Re: quoted-pair in dcontent / Space after colon (Was: New 2822upd-04 - obs-NO-WS-CTL), Tony Hansen
      • Re: quoted-pair in dcontent / Space after colon (Was: New 2822upd-04 - obs-NO-WS-CTL), Arnt Gulbrandsen
      • Re: quoted-pair in dcontent / Space after colon, Frank Ellermann
      • Re: quoted-pair in dcontent / Space after colon (Was: New 2822upd-04 - obs-NO-WS-CTL), Charles Lindsey
      • Re: quoted-pair in dcontent / Space after colon, Frank Ellermann
      • Space after colon, Bruce Lilly
      • Re: quoted-pair in dcontent / Space after colon (Was: New 2822upd-04 - obs-NO-WS-CTL), Graham Klyne
      • Re: quoted-pair in dcontent / Space after colon (Was: New 2822upd-04 - obs-NO-WS-CTL), Charles Lindsey
      • Re: quoted-pair in dcontent / Space after colon (Was: New 2822upd-04 - obs-NO-WS-CTL), Arnt Gulbrandsen
      • Re: quoted-pair in dcontent / Space after colon (Was: New 2822upd-04 - obs-NO-WS-CTL), Tony Finch
      • Re: New 2822upd-04 - obs-NO-WS-CTL, Frank Ellermann
    • Re: New 2822upd-04 - obs-NO-WS-CTL, SM
  • Re: New 2822upd-04 - obs-NO-WS-CTL, Pete Resnick
    • Re: New 2822upd-04 - obs-NO-WS-CTL, Frank Ellermann
      • Re: New 2822upd-04 - obs-NO-WS-CTL, Pete Resnick
      • Re: New 2822upd-04 - obs-NO-WS-CTL, Frank Ellermann
      • Re: New 2822upd-04 - obs-NO-WS-CTL, Nick Shelness
      • Re: New 2822upd-04 - obs-NO-WS-CTL, Tony Hansen
• rfc2822bis -- adding clarifying Sender: text, Dave Crocker
  • Re: rfc2822bis -- adding clarifying Sender: text, ned+ietf-822
  • Re: rfc2822bis -- adding clarifying Sender: text, Pete Resnick
    • Re: rfc2822bis -- adding clarifying Sender: text, Frank Ellermann
      • Re: rfc2822bis -- adding clarifying Sender: text, Charles Lindsey
      • Re: rfc2822bis -- adding clarifying Sender: text, Frank Ellermann
      • Re: rfc2822bis -- adding clarifying Sender: text, Charles Lindsey
      • Re: rfc2822bis -- adding clarifying Sender: text, ned+ietf-822
    • Re: rfc2822bis -- adding clarifying Sender: text, Dave Crocker
      • Re: rfc2822bis -- adding clarifying Sender: text, Dave Crocker
    • Re: rfc2822bis -- adding clarifying Sender: text, Mark Martinec
      • Re: rfc2822bis -- adding clarifying Sender: text, Pete Resnick
      • Re: rfc2822bis -- adding clarifying Sender: text, Nick Shelness
      • Re: rfc2822bis -- adding clarifying Sender: text, Pete Resnick
      • Re: rfc2822bis -- adding clarifying Sender: text, Nick Shelness
      • Re: rfc2822bis -- adding clarifying Sender: text, SM
      • Re: rfc2822bis -- adding clarifying Sender: text, Pete Resnick
      • Re: rfc2822bis -- adding clarifying Sender: text, SM
      • Re: rfc2822bis -- adding clarifying Sender: text, Dave Crocker
  • <Possible follow-ups>
  • Re: rfc2822bis -- adding clarifying Sender: text, Gary Welles
• I-D Action:draft-resnick-2822upd-04.txt, Internet-Drafts
• Please comment on draft-duerst-mailto-bis-04.txt, Martin Duerst
  • Re: Please comment on draft-duerst-mailto-bis-04.txt, Frank Ellermann
• Re: [ietf-dkim] Mailing lists as 2822-Sender (was: Responsibility vs. Validity), Pete Resnick
  • Re: [ietf-dkim] Mailing lists as 2822-Sender (was: Responsibility vs. Validity), ned+ietf-822
    • Re: [ietf-dkim] Mailing lists as 2822-Sender (was: Responsibility vs. Validity), Tony Finch
  • Re: [ietf-dkim] Mailing lists as 2822-Sender (was: Responsibility vs. Validity), Hector Santos
  • Re: [ietf-dkim] Mailing lists as 2822-Sender (was: Responsibility vs. Validity), Dave Crocker
    • Re: [ietf-dkim] Mailing lists as 2822-Sender (was: Responsibility vs. Validity), Tony Finch
      • Re: [ietf-dkim] Mailing lists as 2822-Sender (was: Responsibility vs. Validity), Dave Crocker
      • Re: [ietf-dkim] Mailing lists as 2822-Sender (was: Responsibility vs. Validity), Hector Santos
      • Re: [ietf-dkim] Mailing lists as 2822-Sender (was: Responsibility vs. Validity), Tony Finch
    • Re: [ietf-dkim] Mailing lists as 2822-Sender (was: Responsibility vs. Validity), Steve Dorner
      • Re: [ietf-dkim] Mailing lists as 2822-Sender (was: Responsibility vs. Validity), Hector Santos
• Handling of NO-WS-CTL in 2822bis, ned+ietf-822
  • Re: Handling of NO-WS-CTL in 2822bis, Tony Hansen
    • Re: Handling of NO-WS-CTL in 2822bis, Charles Lindsey
  • Re: Handling of NO-WS-CTL in 2822bis, Pete Resnick
    • Re: Handling of NO-WS-CTL in 2822bis, Dave Crocker
    • Re: Handling of NO-WS-CTL in 2822bis, Frank Ellermann
    • Re: Handling of NO-WS-CTL in 2822bis, Philip Guenther
    • Re: Handling of NO-WS-CTL in 2822bis, Tony Finch
• Unquoted "@" in From still in the wild?, Mikel Lindsaar
  • Re: Unquoted "@" in From still in the wild?, ned+ietf-822
  • Re: Unquoted "@" in From still in the wild?, Tony Finch
• Re: [ietf-dkim] Mailing lists as 2822-Sender, Hector Santos
• 2821bis, 2822upd, email-arch, Frank Ellermann
• Authentication-Results: header draft, Murray S. Kucherawy
  • <Possible follow-ups>
  • Re: Authentication-Results: header draft, Frank Ellermann
    • Re: Authentication-Results: header draft, Frank Ellermann
    • Re: Authentication-Results: header draft, Murray S. Kucherawy
      • Re: Authentication-Results: header draft, Frank Ellermann
• New Disposition type: Inline Subordinate, Qian Sun
  • Re: New Disposition type: Inline Subordinate, ned+ietf-822
    • Re: New Disposition type: Inline Subordinate, Arnt Gulbrandsen
      • Re: New Disposition type: Inline Subordinate, Hector Santos
  • Re: New Disposition type: Inline Subordinate, SM
• Non destructive folding/unfolding (ie, no insertion of whitespace in unfolding), Mikel Lindsaar
  • Re: Non destructive folding/unfolding (ie, no insertion of whitespace in unfolding), Bill McQuillan
  • Re: Non destructive folding/unfolding (ie, no insertion of whitespace in unfolding), Frank Ellermann
  • Re: Non destructive folding/unfolding (ie, no insertion ofwhitespace in unfolding), Paul Smith
  • Re: Non destructive folding/unfolding (ie, no insertion of whitespace in unfolding), Pete Resnick
• Re: Missing ABNF terms in 2821bis?, Pete Resnick
  • Re: Missing ABNF terms in 2821bis?, Valdis . Kletnieks
    • Re: Missing ABNF terms in 2821bis?, Frank Ellermann
  • Re: Missing ABNF terms in 2821bis?, Valdis . Kletnieks
  • Re: Missing ABNF terms in 2821bis? (#1507), Frank Ellermann
  • Re: Missing ABNF terms in 2821bis?, Charles Lindsey
  • Re: Missing ABNF terms in 2821bis?, John C Klensin
    • Re: Missing ABNF terms in 2821bis?, ned+ietf-822
      • Re: Missing ABNF terms in 2821bis?, Pete Resnick
      • Re: Missing ABNF terms in 2821bis?, Frank Ellermann
      • Re: Missing ABNF terms in 2821bis?, Charles Lindsey
      • Re: Missing ABNF terms in 2821bis?, Frank Ellermann
      • Re: Missing ABNF terms in 2821bis?, Charles Lindsey
      • Re: Missing ABNF terms in 2821bis?, John C Klensin
    • Re: Missing ABNF terms in 2821bis?, Frank Ellermann
• Mailing List Last Call now open for draft-klensin-rfc2821bis-05.txt, Tony Hansen
• How long does approval take?, Steve Mills
• Fwd: New Version Notification for draft-resnick-2822upd-03, Pete Resnick
  • Re: New Version Notification for draft-resnick-2822upd-03, Frank Ellermann
    • Re: New Version Notification for draft-resnick-2822upd-03, Russ Allbery
  • Re: Fwd: New Version Notification for draft-resnick-2822upd-03, Charles Lindsey
• registering new MIME types for an application, Steve Mills
  • <Possible follow-ups>
  • registering new MIME types for an application, Steve Mills
    • Re: registering new MIME types for an application, Pete Resnick
      • Re: registering new MIME types for an application, Steve Mills
• Fwd: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard, Lisa Dusseault
• Comments on draft-resnick-2822upd-02.txt, Charles Lindsey
  • Re: Comments on draft-resnick-2822upd-02.txt, SM
    • Re: Comments on draft-resnick-2822upd-02.txt, Charles Lindsey
  • Re: Comments on draft-resnick-2822upd-02.txt, ned+ietf-822
    • Re: Comments on draft-resnick-2822upd-02.txt, Alan Barrett
      • Re: Comments on draft-resnick-2822upd-02.txt, Charles Lindsey
    • Re: Comments on draft-resnick-2822upd-02.txt, Charles Lindsey
    • Re: Comments on draft-resnick-2822upd-02.txt, Dave Crocker
      • Re: Comments on draft-resnick-2822upd-02.txt, Tony Hansen
      • Re: Comments on draft-resnick-2822upd-02.txt, Charles Lindsey
      • Re: Comments on draft-resnick-2822upd-02.txt, ned+ietf-822
      • Re: Comments on draft-resnick-2822upd-02.txt, Charles Lindsey
      • Re: Comments on draft-resnick-2822upd-02.txt, ned+ietf-822
      • Re: Comments on draft-resnick-2822upd-02.txt, Charles Lindsey
      • Re: Comments on draft-resnick-2822upd-02.txt, ned+ietf-822
      • Re: Comments on draft-resnick-2822upd-02.txt, Barry Leiba
      • Re: Comments on draft-resnick-2822upd-02.txt, Dave Crocker
  • Re: Comments on draft-resnick-2822upd-02.txt, Pete Resnick
    • Re: Comments on draft-resnick-2822upd-02.txt, Charles Lindsey
  • <Possible follow-ups>
  • Re: Comments on draft-resnick-2822upd-02.txt, Gary Welles
• draft-resnick-2822upd-02 and Netnews, Charles Lindsey
  • Re: draft-resnick-2822upd-02 and Netnews, Pete Resnick
    • Re: draft-resnick-2822upd-02 and Netnews, Russ Allbery
    • Re: draft-resnick-2822upd-02 and Netnews, Charles Lindsey
      • Re: draft-resnick-2822upd-02 and Netnews, Pete Resnick
      • Re: draft-resnick-2822upd-02 and Netnews, Russ Allbery
      • Re: draft-resnick-2822upd-02 and Netnews, Charles Lindsey
      • Re: draft-resnick-2822upd-02 and Netnews, Russ Allbery
      • Re: draft-resnick-2822upd-02 and Netnews, Frank Ellermann
      • Re: draft-resnick-2822upd-02 and Netnews, Charles Lindsey
      • Re: draft-resnick-2822upd-02 and Netnews, Frank Ellermann
      • Re: draft-resnick-2822upd-02 and Netnews, Charles Lindsey
    • Re: draft-resnick-2822upd-02 and Netnews, ned+ietf-822
    • Re: draft-resnick-2822upd-02 and Netnews, Tony Finch
    • Re: draft-resnick-2822upd-02 and Netnews, Dave Crocker
      • Re: draft-resnick-2822upd-02 and Netnews, Tony Finch
      • Re: draft-resnick-2822upd-02 and Netnews, Dave Crocker
      • Re: draft-resnick-2822upd-02 and Netnews, Charles Lindsey
      • Re: draft-resnick-2822upd-02 and Netnews, Arnt Gulbrandsen
      • Re: draft-resnick-2822upd-02 and Netnews, Charles Lindsey
      • Re: draft-resnick-2822upd-02 and Netnews, SM
      • Re: draft-resnick-2822upd-02 and Netnews, Charles Lindsey
• Mailing List Last Call for 2822 update internet-draft, Tony Hansen
  • Re: Mailing List Last Call for 2822 update internet-draft, Alan Barrett
    • Re: Mailing List Last Call for 2822 update internet-draft, SM
      • Re: Mailing List Last Call for 2822 update internet-draft, Alan Barrett
      • Re: Mailing List Last Call for 2822 update internet-draft, SM
      • Re: Mailing List Last Call for 2822 update internet-draft, Charles Lindsey
      • Re: Mailing List Last Call for 2822 update internet-draft, Alan Barrett
    • Re: Mailing List Last Call for 2822 update internet-draft, Pete Resnick

The web site for this mailing list is sponsored by the Internet Mail Consortium. If you have any suggestions for additions or corrections to this Web page, please send them to phoffman@imc.org.