IETF SMTP (date)

IETF SMTP (date)

[Thread Index] [Top] [All Lists]

May 31, 2007

Re: rfc2821bis-04, Issue 38: MX queuing behavior with options, SM, 21:40
Re: rfc2821bis-04, Issue 38: MX queuing behavior with options, SM, 17:14
Re: rfc2821bis-04, Issue 38: MX queuing behavior with options, Randall Gellens, 16:29
rfc2821bis-04, Issue 38: MX queuing behavior with options, John C Klensin, 13:57

May 25, 2007

draft-hutzler-spamops-07, SM, 14:32

May 22, 2007

Re: Criteria for "interoperability" for email-arch, ned+ietf-smtp, 10:24

May 21, 2007

Re: Criteria for "interoperability" for email-arch, Dave Crocker, 16:36
Re: Criteria for "interoperability" for email-arch, Lisa Dusseault, 15:43
Re: Criteria for "interoperability" for email-arch, Dave Crocker, 11:25
Re: Criteria for "interoperability" for email-arch, Lisa Dusseault, 11:15
Re: Consensus call: draft-crocker-email-arch -- envelope vs. trace vs. ...?, Tony Hansen, 10:59
Re: Consensus call: draft-crocker-email-arch -- envelope vs. trace vs. ...?, Dave Crocker, 09:26

May 20, 2007

new email-arch version, Dave Crocker, 18:27
Re: 2821bis open issues, Alexey Melnikov, 13:12

May 16, 2007

Re: Criteria for "interoperability" for email-arch, Arnt Gulbrandsen, 02:40

May 15, 2007

Re: Criteria for "interoperability" for email-arch, Dave Crocker, 16:43
Re: Criteria for "interoperability" for email-arch, ned+ietf-smtp, 13:16
Re: Criteria for "interoperability" for email-arch, John Leslie, 08:15
Criteria for "interoperability" for email-arch, Dave Crocker, 07:23
Re: Consensus call: draft-crocker-email-arch -- envelope vs. trace vs. ...?, Dave Crocker, 07:09

May 14, 2007

Re: Consensus call: draft-crocker-email-arch -- envelope vs. trace vs. ...?, John C Klensin, 22:54
Consensus call: draft-crocker-email-arch -- envelope vs. trace vs. ...?, Dave Crocker, 22:35
2821bis open issues, Tony Hansen, 21:20
Re: rfc2821bis-04, Tony Hansen, 21:05
rfc2821bis-04, John C Klensin, 11:01
Re: 2821bis + CONVERT, Frank Ellermann, 10:18
Re: 2821bis + CONVERT, John C Klensin, 08:33
2821bis + CONVERT, Frank Ellermann, 07:29
Re: Final draft: draft-crocker-email-arch, Alexey Melnikov, 04:38

May 13, 2007

Re: Final draft: draft-crocker-email-arch, SM, 11:47

May 12, 2007

Re: Final draft: draft-crocker-email-arch, Dave Crocker, 10:51

May 11, 2007

Re: Final draft: draft-crocker-email-arch, Frank Ellermann, 20:27
Re: Final draft: draft-crocker-email-arch, Frank Ellermann, 20:26
Message-ID (was: Final draft: draft-crocker-email-arch), Frank Ellermann, 18:08
Re: Final draft: draft-crocker-email-arch, Alexey Melnikov, 04:20
Re: rfc2821bis-01 Issue 19: Explanatory text after literal in EHLO, Alexey Melnikov, 04:19

May 10, 2007

Re: rfc2821bis-01 Issue 19: Explanatory text after literal in EHLO, Tony Finch, 00:16

May 09, 2007

Re: rfc2821bis-01 Issue 19: Explanatory text after literal in EHLO, Matti Aarnio, 17:14
Re: rfc2821bis-01 Issue 19: Explanatory text after literal in EHLO, John C Klensin, 15:35
Re: rfc2821bis-01 Issue 19: Explanatory text after literal in EHLO, Tony Hansen, 12:05
Re: Final draft: draft-crocker-email-arch, John Leslie, 10:33
Re: Final draft: draft-crocker-email-arch, Dave Crocker, 10:33
Re: Final draft: draft-crocker-email-arch, Dave Crocker, 09:17
Re: rfc2821bis-01 Issue 19: Explanatory text after literal in EHLO, John Leslie, 09:07
Re: Final draft: draft-crocker-email-arch, Tony Finch, 00:49

May 08, 2007

Re: Final draft: draft-crocker-email-arch, Dave Crocker, 22:23
Re: rfc2821bis-01 Issue 19: Explanatory text after literal in EHLO, ned+ietf-smtp, 19:03
Re: rfc2821bis-01 Issue 19: Explanatory text after literal in EHLO, Tony Finch, 16:50
Re: Final draft: draft-crocker-email-arch, Peter J. Holzer, 15:27
Re: Final draft: draft-crocker-email-arch, Dave Crocker, 13:25
Re: Final draft: draft-crocker-email-arch, Tony Finch, 13:12
Re: Final draft: draft-crocker-email-arch, Hector Santos, 12:55
Re: Final draft: draft-crocker-email-arch, Dave Crocker, 12:23
Re: Final draft: draft-crocker-email-arch, Tony Finch, 12:08
Re: Final draft: draft-crocker-email-arch, Dave Crocker, 11:42
Re: Final draft: draft-crocker-email-arch, Mark E. Mallett, 11:26

May 07, 2007

Re: Final draft: draft-crocker-email-arch, Dave Crocker, 09:07
Re: Final draft: draft-crocker-email-arch, Dave Crocker, 08:05
Re: Final draft: draft-crocker-email-arch, John Leslie, 05:58

May 06, 2007

Final draft: draft-crocker-email-arch, Dave Crocker, 15:21

May 03, 2007

Re: DNS VRFY (was: Somewhat OT: Re: rfc2821bis-03 Issue 35: remove source routes from example D.3), ned+ietf-smtp, 14:40
Re: Restrictive ~ priority, Peter J. Holzer, 13:53
Re: DNS VRFY (was: Somewhat OT: Re: rfc2821bis-03 Issue 35: remove source routes from example D.3), Frank Ellermann, 13:50
Re: Restrictive ~ priority, Hector Santos, 13:23
Restrictive ~ priority (was: Somewhat OT: Re: rfc2821bis-03 Issue 35: remove source routes from example D.3), Frank Ellermann, 12:42
Re: rfc2181bis-01 Issue 20: General security considerations overhaul, Tony Hansen, 12:15
Re: rfc2821bis-01 Issue 19: Explanatory text after literal in EHLO, Tony Hansen, 12:08
Re: Updated status on 2821bis 4/24, Tony Hansen, 12:07
Re: Recap: 2821bis-01 Issue 3: EHLO validation in sect 4.1.4, para 6, Tony Hansen, 12:06
Re: Recap: 2821bis-01 Issue 3: EHLO validation in sect 4.1.4, para 6, Tony Hansen, 11:54
Re: DNS VRFY (was: Somewhat OT: Re: rfc2821bis-03 Issue 35: remove source routes from example D.3), ned+ietf-smtp, 11:32

May 02, 2007

Re: Recap: Re: RFC2821bis-02 Issue 30: Deprecate use of source routes completely and remove text, Tony Hansen, 23:12
Re: Recap: Re: rfc2821bis-03: Issue 31: Retain new FTP comparison text in 4.2.1, Tony Hansen, 22:42
Re: rfc2821bis-03 Issue 33: SMTP-Sender, etc., Tony Hansen, 22:37
Recap 2: Re: Recap Issues 0b/21/25, Tony Hansen, 22:34
Re: OT Brainstorm: Email Validation among different systems, Dave Crocker, 15:38
Re: OT: 5xy - Do we need a "I MEAN IT!" do not retry response code?, Jeff Macdonald, 13:21
Re: OT Brainstorm: Email Validation among different systems, Robert A. Rosenberg, 13:18
Re: OT: Re: DNS VRFY, SM, 10:36
Re: OT Brainstorm: Email Validation among different systems, Hector Santos, 10:02
Re: OT: Re: DNS VRFY, Alex van den Bogaerdt, 08:55
Re: OT Brainstorm: Email Validation among different systems, David F. Skoll, 08:26
Re: OT Brainstorm: Email Validation among different systems, Hector Santos, 07:52
OT: Re: DNS VRFY, David F. Skoll, 07:22
Re: OT: 5xy - Do we need a "I MEAN IT!" do not retry response code?, Hector Santos, 06:12
Re: OT Brainstorm: Email Validation among different systems, David F. Skoll, 05:43
Re: OT: 5xy - Do we need a "I MEAN IT!" do not retry response code?, Arnt Gulbrandsen, 04:20
Re: OT: 5xy - Do we need a "I MEAN IT!" do not retry response code?, John C Klensin, 03:54
Re: OT: 5xy - Do we need a "I MEAN IT!" do not retry response code?, Peter J. Holzer, 03:27
Re: Somewhat OT: Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, Hector Santos, 03:10
OT: 5xy - Do we need a "I MEAN IT!" do not retry response code?, Hector Santos, 02:42
Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, Peter J. Holzer, 02:03
Re: Somewhat OT: Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, Peter J. Holzer, 01:44
Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, Arnt Gulbrandsen, 01:43

May 01, 2007

DNS VRFY (was: Somewhat OT: Re: rfc2821bis-03 Issue 35: remove source routes from example D.3), SM, 21:54
OT Brainstorm: Email Validation among different systems, Hector Santos, 21:48
Re: "for" clause on Received: header field, Robert A. Rosenberg, 21:48
Somewhat OT: Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, David F. Skoll, 20:18
Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, Hector Santos, 19:40
Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, David F. Skoll, 18:52
Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, SM, 18:32
Re: "for" clause on Received: header field, ned+ietf-smtp, 17:25
Re: "for" clause on Received: header field, Philip Guenther, 16:50
Re: "for" clause on Received: header field, Robert A. Rosenberg, 16:16
Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, Arnt Gulbrandsen, 15:56
Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, Peter J. Holzer, 14:28
Re: Recap Issues 0b/21/25, ned+ietf-smtp, 13:43
Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, John C Klensin, 11:22
Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, Frank Ellermann, 10:08
Re: rfc2821bis-03 Issue 35: remove source routes from example D.3, Frank Ellermann, 09:57
Re: Recap Issues 0b/21/25, ned+ietf-smtp, 09:41
Re: Recap: Re: rfc2821bis-03 Issue 32: "MUST take responsibility", Frank Ellermann, 09:24
Re: Recap Issues 0b/21/25, SM, 07:57
Re: "for" clause on Received: header field, ned+ietf-smtp, 06:54
Re: Recap Issues 0b/21/25, Alexey Melnikov, 06:43
Re: Retries - may be related to closed issue 12 4yz behavior, Hector Santos, 05:46
Re: Retries - may be related to closed issue 12 4yz behavior, Peter J. Holzer, 03:46
Re: Recap Issues 0b/21/25, Hector Santos, 03:20
Re: Recap: Re: rfc2821bis-03 Issue 32: "MUST take responsibility", Hector Santos, 02:49
Re: Retries - may be related to closed issue 12 4yz behavior, Hector Santos, 01:53
Re: Retries - may be related to closed issue 12 4yz behavior, SM, 01:06
Re: Recap Issues 0b/21/25, SM, 00:20
Re: new issue: non-2606 domains, Arnt Gulbrandsen, 00:02