Archive of ietf-mailsig, by thread

• RE: DKIM BOF -- draft charter and agenda, Hallam-Baker, Phillip
• DKIM BOF Chair Appointments, Russ Housley
  • Re: [ietf-dkim] DKIM BOF Chair Appointments, Stephen Farrell
  • DKIM BOF -- draft charter and agenda, Barry Leiba
    • Re: DKIM BOF -- draft charter and agenda, Barry Leiba
    • Re: DKIM BOF -- draft charter and agenda, Barry Leiba
      • Re: DKIM BOF -- draft charter and agenda, Barry Leiba
• draft-otis-mass-reputation-03, Douglas Otis
• MASS/DKIM interim minutes posted, Jim Fenton
  • Re: MASS/DKIM interim minutes posted, Douglas Otis
    • Re: MASS/DKIM interim minutes posted, Jim Fenton
      • Re: MASS/DKIM interim minutes posted, Douglas Otis
      • Re: MASS/DKIM interim minutes posted, Jim Fenton
• Re: [ietf-dkim] Purpose and sequence for DKIM specification anddeployment, Arvel Hathcock
• Re: [ietf-dkim] Purpose and sequence forDKIM specification and deployment, Arvel Hathcock
  • <Possible follow-ups>
  • RE: [ietf-dkim] Purpose and sequence forDKIM specification and deployment, Hallam-Baker, Phillip
• Re: [ietf-dkim] Not exactly not a threat analysis, william(at)elan.net
  • Re: Not exactly not a threat analysis, Frank Ellermann
  • Re: Not exactly not a threat analysis, Florian Weimer
• RE: replay, revocation, repudiation, was RE: [ietf-dkim] On per-user-keying, Hallam-Baker, Phillip
  • Re: replay, revocation, repudiation, was RE: [ietf-dkim] On per-user-keying, Earl Hood
• Design approach to MASS (was Re: [ietf-dkim] On per-user-keying), Earl Hood
• RE: [ietf-dkim] On per-user-keying, Hallam-Baker, Phillip
  • replay, revocation, repudiation, was RE: [ietf-dkim] On per-user-keying, Tony Finch
    • Re: replay, revocation, repudiation, was RE: [ietf-dkim] On per-user-keying, SM
      • Re: replay, revocation, repudiation, was RE: [ietf-dkim] On per-user-keying, Earl Hood
• How to solve replay with no specification changes, Hallam-Baker, Phillip
  • Re: How to solve replay with no specification changes, william(at)elan.net
• Re: [ietf-dkim] Replay isn't the problem, spam is the problem, wayne
  • <Possible follow-ups>
  • RE: [ietf-dkim] Replay isn't the problem, spam is the problem, Hallam-Baker, Phillip
• RE: Replay attacks and ISP business models, Hallam-Baker, Phillip
  • RE: Replay attacks and ISP business models, John R Levine
  • <Possible follow-ups>
  • Re: Replay attacks and ISP business models, Douglas Otis
  • RE: Replay attacks and ISP business models, Hallam-Baker, Phillip
    • RE: Replay attacks and ISP business models, John R Levine
  • RE: Replay attacks and ISP business models, Hallam-Baker, Phillip
    • Re: Replay attacks and ISP business models, wayne
  • RE: Replay attacks and ISP business models, Hallam-Baker, Phillip
• Moving DKIM standardization discussion to ietf-dkim@mipassoc.org, Dave Crocker
  • Re: Moving DKIM standardization discussion to ietf-dkim@mipassoc.org, Earl Hood
• Please update your account information, update@xxxxxxxxxx
• eBay Fraud Mediation Request, aw-comfirm@xxxxxxxx
• One space proposal, Bryan Costales
  • Re: One space proposal, Tony Hansen
  • Re: One space proposal, wayne
    • Re: One space proposal, Earl Hood
      • Re: One space proposal, Frank Ellermann
• The DKIM Vision, Hallam-Baker, Phillip
• MASS/DKIM BOF Summary, Dave Crocker
  • Re: MASS/DKIM BOF Summary, wayne
    • Re: MASS/DKIM BOF Summary, Dave Crocker
  • Re: MASS/DKIM BOF Summary, Arvel Hathcock
    • Re: MASS/DKIM BOF Summary, william(at)elan.net
    • Re: MASS/DKIM BOF Summary, Andrew Newton
      • Re: MASS/DKIM BOF Summary, Michael Thomas
      • Re: MASS/DKIM BOF Summary, Earl Hood
      • Re: MASS/DKIM BOF Summary, Dave Crocker
  • <Possible follow-ups>
  • RE: MASS/DKIM BOF Summary, Hallam-Baker, Phillip
    • Re: MASS/DKIM BOF Summary, Eliot Lear
      • Re: MASS/DKIM BOF Summary, Dave Crocker
      • Re: MASS/DKIM BOF Summary, wayne
  • RE: MASS/DKIM BOF Summary, Hallam-Baker, Phillip
  • RE: MASS/DKIM BOF Summary, Hallam-Baker, Phillip
  • Re: MASS/DKIM BOF Summary, Dave Crocker
    • Re: MASS/DKIM BOF Summary, Earl Hood
  • RE: MASS/DKIM BOF Summary, Hallam-Baker, Phillip
    • Re: MASS/DKIM BOF Summary, wayne
  • Re: MASS/DKIM BOF Summary, Dave Crocker
    • Re: MASS/DKIM BOF Summary, william(at)elan.net
    • On per-user-keying, Jon Callas
  • Re: MASS/DKIM BOF Summary, Dave Crocker
  • RE: MASS/DKIM BOF Summary, Hallam-Baker, Phillip
    • Re: MASS/DKIM BOF Summary, Eliot Lear
  • RE: MASS/DKIM BOF Summary, Hallam-Baker, Phillip
    • RE: MASS/DKIM BOF Summary, Tony Finch
• Version identifier, Hallam-Baker, Phillip
  • Re: Version identifier, Tony Finch
    • Re: Version identifier, John Levine
      • Re: Version identifier, Ned Freed
      • Re: Version identifier, Andrew Newton
• Proposals Re: DoS and Replay protection for message signatures, Amir Herzberg
  • Re: Proposals Re: DoS and Replay protection for message signatures, Tony Finch
  • Re: Proposals Re: DoS and Replay protection for message signatures, Jim Fenton
    • Re: Proposals Re: DoS and Replay protection for message signatures, Amir Herzberg
• RE: wildcards, was Re: dkim technology?, Hallam-Baker, Phillip
• in regards to chapter, william(at)elan.net
  • Re: in regards to chapter, Ned Freed
  • <Possible follow-ups>
  • RE: in regards to chapter, Hallam-Baker, Phillip
• jabber address for bof, Dave Crocker
  • jabber address for bof (correction), Dave Crocker
  • Re: jabber address for bof, Tony Hansen
• Fw: conduct on the list, Hector Santos
  • Re: Fw: conduct on the list, william(at)elan.net
    • Re: Fw: conduct on the list, Jim Fenton
      • Re: Fw: conduct on the list, Hector Santos
      • Re: Fw: conduct on the list, william(at)elan.net
      • Re: conduct on the list, Jon Callas
      • Re: conduct on the list, Hector Santos
  • Re: Fw: conduct on the list, Sam Hartman
  • <Possible follow-ups>
  • RE: conduct on the list, Hallam-Baker, Phillip
• DKIM: key identification and shared keys, Amir Herzberg
  • Re: DKIM: key identification and shared keys, Eric Allman
  • Re: DKIM: key identification and shared keys, Michael Thomas
    • Re: DKIM: key identification and shared keys, Jim Fenton
    • Re: DKIM: key identification and shared keys, Amir Herzberg
  • <Possible follow-ups>
  • RE: DKIM: key identification and shared keys, Hallam-Baker, Phillip
• DKIM Verification Algorithm, Hector Santos
  • Re: DKIM Verification Algorithm, william(at)elan.net
    • Re: DKIM Verification Algorithm, Hector Santos
      • Re: DKIM Verification Algorithm, william(at)elan.net
      • Re: DKIM Verification Algorithm, Hector Santos
    • Re: DKIM Verification Algorithm, Jim Fenton
  • <Possible follow-ups>
  • RE: DKIM Verification Algorithm, Graham Finlayson
    • Re: DKIM Verification Algorithm, Jim Fenton
  • RE: DKIM Verification Algorithm, Graham Finlayson
    • Re: DKIM Verification Algorithm, Jim Fenton
• bof scribe and jabber scribes will be solicited, Dave Crocker
• DoS and Replay protection for message signatures, Douglas Otis
  • Re: DoS and Replay protection for message signatures, Tony Finch
    • Re: DoS and Replay protection for message signatures, Douglas Otis
  • Re: DoS and Replay protection for message signatures, Arvel Hathcock
    • Re: DoS and Replay protection for message signatures, Earl Hood
      • Re: DoS and Replay protection for message signatures, Douglas Otis
      • Re: DoS and Replay protection for message signatures, william(at)elan.net
      • Re: DoS and Replay protection for message signatures, Earl Hood
      • Re: DoS and Replay protection for message signatures, Earl Hood
      • Re: DoS and Replay protection for message signatures, Douglas Otis
      • Re: DoS and Replay protection for message signatures, Earl Hood
  • <Possible follow-ups>
  • RE: DoS and Replay protection for message signatures, Hallam-Baker, Phillip
• Will user-keys cause DNS cache to explode?, Douglas Otis
  • Re: Will user-keys cause DNS cache to explode?, Tony Finch
    • Re: Will user-keys cause DNS cache to explode?, Douglas Otis
  • <Possible follow-ups>
  • RE: Will user-keys cause DNS cache to explode?, Hallam-Baker, Phillip
    • Re: Will user-keys cause DNS cache to explode?, Douglas Otis
      • Re: Will user-keys cause DNS cache to explode?, william(at)elan.net
  • RE: Will user-keys cause DNS cache to explode?, Hallam-Baker, Phillip
    • RE: Will user-keys cause DNS cache to explode?, Tony Finch
  • RE: Will user-keys cause DNS cache to explode?, Hallam-Baker, Phillip
• ] Replay attacks and ISP business models, Sam Hartman
  • Re: ] Replay attacks and ISP business models, Jim Fenton
    • Re: ] Replay attacks and ISP business models, william(at)elan.net
    • Re: ] Replay attacks and ISP business models, Tony Finch
      • Re: ] Replay attacks and ISP business models, Andrew Newton
      • Re: ] Replay attacks and ISP business models, william(at)elan.net
      • Re: ] Replay attacks and ISP business models, Tony Finch
      • Re: ] Replay attacks and ISP business models, william(at)elan.net
      • Re: ] Replay attacks and ISP business models, Michael Thomas
      • Re: ] Replay attacks and ISP business models, Douglas Otis
      • Re: ] Replay attacks and ISP business models, Douglas Otis
      • Re: Replay attacks and ISP business models, John Levine
      • Re: Replay attacks and ISP business models, Andrew Newton
      • Re: Replay attacks and ISP business models, John R Levine
      • Re: Replay attacks and ISP business models, wayne
      • Re: Replay attacks, what's that?, John Levine
      • Re: Replay attacks, what's that?, Douglas Otis
      • Re: [ietf-dkim] Re: Replay attacks, what's that?, Tony Finch
      • Re: [ietf-dkim] Re: Replay attacks, what's that?, Douglas Otis
      • Re: Replay attacks and ISP business models, Andrew Newton
      • Re: Replay attacks and ISP business models, John R Levine
      • Re: Replay attacks and ISP business models, Andrew Newton
      • Re: Replay attacks and ISP business models, John R Levine
      • Re: Replay attacks and ISP business models, Michael Thomas
      • Re: Replay attacks and ISP business models, wayne
      • Re: Replay attacks and ISP business models, Michael Thomas
      • Re: Replay attacks and ISP business models, wayne
      • Re: Replay attacks and ISP business models, Michael Thomas
      • Re: Replay attacks and ISP business models, Douglas Otis
      • Message not available
      • Message not available
      • Re: [ietf-dkim] Re: Replay attacks and ISP business models, Douglas Otis
      • Re: [ietf-dkim] Re: Replay attacks and ISP business models, John R Levine
      • Re: [ietf-dkim] Re: Replay attacks and ISP business models, Douglas Otis
      • Re: [ietf-dkim] Re: Replay attacks and ISP business models, Amir Herzberg
      • Re: [ietf-dkim] Re: Replay attacks and ISP business models, Amir Herzberg
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Replay isn't the problem, spam is the problem, wayne
  • Re: ] Replay attacks and ISP business models, Michael Thomas
  • Re: ] Replay attacks and ISP business models, Tony Finch
  • Re: ] Replay attacks and ISP business models, Miles Libbey
  • <Possible follow-ups>
  • RE: ] Replay attacks and ISP business models, Hallam-Baker, Phillip
• Typo in html version of draft-allman-dkim-base-00, Amir Herzberg
• Comments on draft-allman-dkim-base-00.txt, EKR
  • Re: Comments on draft-allman-dkim-base-00.txt, Earl Hood
    • Re: Comments on draft-allman-dkim-base-00.txt, EKR
      • Re: Comments on draft-allman-dkim-base-00.txt, Michael Thomas
      • PEM and mail signature DNS public key verification, william(at)elan.net
      • Re: PEM and mail signature DNS public key verification, Earl Hood
      • Re: PEM and mail signature DNS public key verification, william(at)elan.net
      • Re: PEM and mail signature DNS public key verification, william(at)elan.net
      • Re: Comments on draft-allman-dkim-base-00.txt, Earl Hood
      • Re: Comments on draft-allman-dkim-base-00.txt, Ned Freed
      • Re: Comments on draft-allman-dkim-base-00.txt, EKR
      • Re: Comments on draft-allman-dkim-base-00.txt, Hector Santos
    • Re: Comments on draft-allman-dkim-base-00.txt, Thomas Roessler
      • Re: Comments on draft-allman-dkim-base-00.txt, Michael Thomas
      • Re: Comments on draft-allman-dkim-base-00.txt, Thomas Roessler
      • Re: Comments on draft-allman-dkim-base-00.txt, Michael Thomas
      • Re: Comments on draft-allman-dkim-base-00.txt, william(at)elan.net
    • Re: Comments on draft-allman-dkim-base-00.txt, william(at)elan.net
  • Re: Comments on draft-allman-dkim-base-00.txt, Florian Weimer
    • Re: Comments on draft-allman-dkim-base-00.txt, Michael Thomas
  • Re: Comments on draft-allman-dkim-base-00.txt, Jon Callas
    • Re: Comments on draft-allman-dkim-base-00.txt, Eric Rescorla
      • RE: Comments on draft-allman-dkim-base-00.txt, Scott Kitterman
      • Re: Comments on draft-allman-dkim-base-00.txt, Eric Rescorla
      • Re: Comments on draft-allman-dkim-base-00.txt, domainkeys-feedbackbase02
      • Re: Comments on draft-allman-dkim-base-00.txt, Eric Rescorla
      • Re: Comments on draft-allman-dkim-base-00.txt, Scott Kitterman
      • Re: Comments on draft-allman-dkim-base-00.txt, Jon Callas
    • Re: Comments on draft-allman-dkim-base-00.txt, Douglas Otis
  • <Possible follow-ups>
  • RE: Comments on draft-allman-dkim-base-00.txt, Hallam-Baker, Phillip
    • Re: Comments on draft-allman-dkim-base-00.txt, Jon Callas
    • Re: Comments on draft-allman-dkim-base-00.txt, Jon Callas
      • Re: Comments on draft-allman-dkim-base-00.txt, Thomas Roessler
  • RE: Comments on draft-allman-dkim-base-00.txt, Hallam-Baker, Phillip
  • RE: Comments on draft-allman-dkim-base-00.txt, Hallam-Baker, Phillip
• MASS BOF: things to accomplish, Sam Hartman
  • <Possible follow-ups>
  • RE: MASS BOF: things to accomplish, Hallam-Baker, Phillip
• RE: SSP - 3rd party Signers - Definition/Usage, Hallam-Baker, Phillip
  • Re: SSP - 3rd party Signers - Definition/Usage, Michael Thomas
    • Re: SSP - 3rd party Signers - Definition/Usage, Earl Hood
      • Re: SSP - 3rd party Signers - Definition/Usage, Michael Thomas
    • Re: SSP - 3rd party Signers - Definition/Usage, william(at)elan.net
  • Re: SSP - 3rd party Signers - Definition/Usage, Hector Santos
• 3rd party Signers - Definition/Usage, Hector Santos
  • Re: 3rd party Signers - Definition/Usage, Earl Hood
  • SSP - 3rd party Signers - Definition/Usage, Arvel Hathcock
    • Re: SSP - 3rd party Signers - Definition/Usage, Dave Crocker
      • Re: SSP - 3rd party Signers - Definition/Usage, Arvel Hathcock
      • Re: SSP - 3rd party Signers - Definition/Usage, Michael Thomas
      • Re: SSP - 3rd party Signers - Definition/Usage, Earl Hood
    • Re: SSP - 3rd party Signers - Definition/Usage, Earl Hood
    • Re: SSP - 3rd party Signers - Definition/Usage, Hector Santos
      • Re: SSP - 3rd party Signers - Definition/Usage, Earl Hood
      • Re: SSP - 3rd party Signers - Definition/Usage, Hector Santos
      • Re: SSP - 3rd party Signers - Definition/Usage, Earl Hood
      • Re: SSP - 3rd party Signers - Definition/Usage, Hector Santos
• FIT : Fraud Investigations Team : case 1281 / 2005, support@xxxxxxxx
• SSP - flags field, Arvel Hathcock
• SSP - policy location compatibility with DK, Arvel Hathcock
  • Re: SSP - policy location compatibility with DK, Hector Santos
    • Re: SSP - policy location compatibility with DK, Arvel Hathcock
      • Re: SSP - policy location compatibility with DK, Arvel Hathcock
      • Re: SSP - policy location compatibility with DK, Arvel Hathcock
      • Re: SSP - policy location compatibility with DK, Jim Fenton
      • Re: SSP - policy location compatibility with DK, Arvel Hathcock
      • Re: SSP - policy location compatibility with DK, william(at)elan.net
      • Re: SSP - policy location compatibility with DK, Andrew Newton
      • Re: SSP - policy location compatibility with DK, Ned Freed
    • Re: SSP - policy location compatibility with DK, Michael Thomas
  • <Possible follow-ups>
  • RE: SSP - policy location compatibility with DK, Hallam-Baker, Phillip
    • RE: SSP - policy location compatibility with DK, william(at)elan.net
  • RE: SSP - policy location compatibility with DK, Hallam-Baker, Phillip
• FYI: Searchable ietf-mailsig archives available, Earl Hood
• Charter issues list, 7/27/2005, Jim Fenton
  • Re: Charter issues list, 7/27/2005, Earl Hood
    • Re: Charter issues list, 7/27/2005, Jim Fenton
  • Re: Charter issues list, 7/27/2005, Andrew Newton
  • Re: Charter issues list, 7/27/2005, Frank Ellermann
• SSP - specifying the third-parties, Arvel Hathcock
  • Re: SSP - specifying the third-parties, Arvel Hathcock
    • RE: SSP - specifying the third-parties, James Scott
      • Re: SSP - specifying the third-parties, Earl Hood
      • RE: SSP - specifying the third-parties, James Scott
      • Re: SSP - specifying the third-parties, Jim Fenton
      • RE: SSP - specifying the third-parties, James Scott
      • RE: SSP - specifying the third-parties, william(at)elan.net
      • Re: SSP - specifying the third-parties, Arvel Hathcock
• SSP - when to perform, Arvel Hathcock
  • Re: SSP - when to perform, Earl Hood
    • Re: SSP - when to perform, Arvel Hathcock
    • Re: SSP - when to perform, Hector Santos
  • Re: SSP - when to perform, Jim Fenton
• SSP outbound signing policy, Arvel Hathcock
  • Re: SSP outbound signing policy, Hector Santos
    • Re: SSP outbound signing policy, Earl Hood
      • Re: SSP outbound signing policy, Arvel Hathcock
      • Re: SSP outbound signing policy, Hector Santos
      • Re: SSP outbound signing policy, Earl Hood
      • Re: SSP outbound signing policy, Michael Thomas
      • Re: SSP outbound signing policy, Earl Hood
      • Re: SSP outbound signing policy, Michael Thomas
      • Re: SSP outbound signing policy, Jim Fenton
      • Re: SSP outbound signing policy, Jim Fenton
      • Re: SSP outbound signing policy, Earl Hood
      • Re: SSP outbound signing policy, Jim Fenton
      • Re: SSP outbound signing policy, Earl Hood
      • Re: SSP outbound signing policy, Jim Fenton
• Spoofing revisited, Earl Hood
  • Re: Spoofing revisited, Arvel Hathcock
    • Re: Spoofing revisited, Arvel Hathcock
    • Re: Spoofing revisited, Earl Hood
      • Re: Spoofing revisited, william(at)elan.net
      • Re: Spoofing revisited, Arvel Hathcock
      • RE: Spoofing revisited, James Scott
      • Re: Spoofing revisited, Earl Hood
      • Re: Spoofing revisited, Arvel Hathcock
      • RE: Spoofing revisited, James Scott
• dkim support for identity "assessment" mechanisms, Dave Crocker
  • Re: dkim support for identity "assessment" mechanisms, John Levine
  • Re: dkim support for identity "assessment" mechanisms, Arvel Hathcock
  • <Possible follow-ups>
  • RE: dkim support for identity "assessment" mechanisms, Hallam-Baker, Phillip
    • RE: dkim support for identity "assessment" mechanisms, william(at)elan.net
  • RE: dkim support for identity "assessment" mechanisms, Hallam-Baker, Phillip
• alternate key server mechanisms, Dave Crocker
  • Re: alternate key server mechanisms, John Levine
  • <Possible follow-ups>
  • RE: alternate key server mechanisms, Hallam-Baker, Phillip
    • Re: alternate key server mechanisms, Arvel Hathcock
    • Re: alternate key server mechanisms, Arvel Hathcock
  • RE: alternate key server mechanisms, Hallam-Baker, Phillip
    • Re: alternate key server mechanisms, Arvel Hathcock
      • Re: alternate key server mechanisms, Douglas Otis
      • Re: alternate key server mechanisms, Frank Ellermann
    • RE: alternate key server mechanisms, Dave Crocker
  • RE: alternate key server mechanisms, Hallam-Baker, Phillip
    • Re: alternate key server mechanisms, Arvel Hathcock
      • Re: alternate key server mechanisms, Earl Hood
    • RE: alternate key server mechanisms, Dave Crocker
  • RE: alternate key server mechanisms, Hallam-Baker, Phillip
  • RE: alternate key server mechanisms, Hallam-Baker, Phillip
    • Re: alternate key server mechanisms, John Levine
  • RE: Re: alternate key server mechanisms, Hallam-Baker, Phillip
  • RE: alternate key server mechanisms, Hallam-Baker, Phillip
    • RE: alternate key server mechanisms, John R Levine
  • RE: alternate key server mechanisms, Hallam-Baker, Phillip
    • RE: alternate key server mechanisms, william(at)elan.net
  • RE: alternate key server mechanisms, Hallam-Baker, Phillip
• alternate key server mechanism(s) vs. accreditation, Dave Crocker
  • alternate key server mechanism(s) vs. accreditation, Dave Crocker
  • <Possible follow-ups>
  • RE: alternate key server mechanism(s) vs. accreditation, Hallam-Baker, Phillip
• NOTE WELL: IETF-MailSig List Participation Rules, Dave Crocker
  • Re: NOTE WELL: IETF-MailSig List Participation Rules, william(at)elan.net
    • Re: NOTE WELL: IETF-MailSig List Participation Rules, Dave Crocker
      • Re: NOTE WELL: IETF-MailSig List Participation Rules, william(at)elan.net
      • Re: NOTE WELL: IETF-MailSig List Participation Rules, Andrew Newton
      • Re: NOTE WELL: IETF-MailSig List Participation Rules, Dave Crocker
      • Re: NOTE WELL: IETF-MailSig List Participation Rules, Andrew Newton
      • Re: NOTE WELL: IETF-MailSig List Participation Rules, Dave Crocker
      • Re: NOTE WELL: IETF-MailSig List Participation Rules, Andrew Newton
      • Re: NOTE WELL: IETF-MailSig List Participation Rules, Michael Thomas
      • Re: QUERY: Key Server Choices, Dave Crocker
      • Re: QUERY: Key Server Choices, Andrew Newton
      • Re: NOTE WELL: IETF-MailSig List Participation Rules, Frank Ellermann
  • Re: NOTE WELL: IETF-MailSig List Participation Rules, Tony Hansen
    • Re: NOTE WELL: IETF-MailSig List Participation Rules, Ned Freed
  • <Possible follow-ups>
  • RE: NOTE WELL: IETF-MailSig List Participation Rules, Kuhtz, Christian
  • RE: NOTE WELL: IETF-MailSig List Participation Rules, Hallam-Baker, Phillip
  • Re: NOTE WELL: IETF-MailSig List Participation Rules, Miles Libbey
• Policy Mechanisms, Hallam-Baker, Phillip
  • Re: Policy Mechanisms, Michael Thomas
    • Re: Policy Mechanisms, Douglas Otis
      • Re: Policy Mechanisms, william(at)elan.net
      • Re: Policy Mechanisms, Douglas Otis
      • Re: Policy Mechanisms, Arvel Hathcock
  • <Possible follow-ups>
  • RE: Policy Mechanisms, Hallam-Baker, Phillip
  • RE: Policy Mechanisms, Hallam-Baker, Phillip
• RE: The cost of choices, Hallam-Baker, Phillip
  • Re: The cost of choices, Michael Thomas
    • Re: The cost of choices, Dave Crocker
      • Re: The cost of choices, Arvel Hathcock
      • Re: The cost of choices, Dave Crocker
      • RE: The cost of choices, James Scott
      • Re: The cost of choices, Arvel Hathcock
      • Re: The cost of choices, Earl Hood
      • Re: The cost of choices, Arvel Hathcock
      • Re: The cost of choices, Jim Fenton
      • Re: The cost of choices, Hector Santos
      • Re: The cost of choices, Jim Fenton
      • DKIM KEY SSP Override Option [was Re: The cost of choices], Hector Santos
      • Re: DKIM KEY SSP Override Option [was Re: The cost of choices], Michael Thomas
      • Re: DKIM KEY SSP Override Option [was Re: The cost of choices], Jim Fenton
      • Re: DKIM KEY SSP Override Option [was Re: The cost of choices], Jim Fenton
      • Re: The cost of choices, Earl Hood
      • Re: The cost of choices, Arvel Hathcock
      • Re: The cost of choices, Earl Hood
      • Re: The cost of choices, Arvel Hathcock
      • Re: The cost of choices, Jim Fenton
      • Re: The cost of choices, Earl Hood
      • Re: The cost of choices, Earl Hood
      • Re: The cost of choices, Michael Thomas
      • Re: The cost of choices, Earl Hood
      • Re: The cost of choices, Michael Thomas
      • Re: The cost of choices, Earl Hood
      • Re: The cost of choices, Michael Thomas
      • Re: The cost of choices, Dave Crocker
      • Re: The cost of choices, Earl Hood
      • RE: The cost of choices, Dave Crocker
      • RE: The cost of choices, James Scott
• Better DKIM Verification Example Needed, Hector Santos
  • Re: Better DKIM Verification Example Needed, Arvel Hathcock
    • Re: Better DKIM Verification Example Needed, Arvel Hathcock
      • Re: Better DKIM Verification Example Needed, Earl Hood
      • Re: Better DKIM Verification Example Needed, Michael Thomas
      • Re: Better DKIM Verification Example Needed, Earl Hood
      • Re: Better DKIM Verification Example Needed, Arvel Hathcock
      • Re: Better DKIM Verification Example Needed, Michael Thomas
      • Re: Better DKIM Verification Example Needed, Ned Freed
      • Re: Better DKIM Verification Example Needed, Arvel Hathcock
      • Re: Better DKIM Verification Example Needed, Earl Hood
      • Re: Better DKIM Verification Example Needed, Hector Santos
      • Re: Better DKIM Verification Example Needed, Michael Thomas
      • Re: Better DKIM Verification Example Needed, Hector Santos
      • Re: Better DKIM Verification Example Needed, Michael Thomas
      • Re: Better DKIM Verification Example Needed, Hector Santos
      • Re: Better DKIM Verification Example Needed, Arvel Hathcock
      • Re: Better DKIM Verification Example Needed, Michael Thomas
      • Re: Better DKIM Verification Example Needed, Arvel Hathcock
      • Re: Better DKIM Verification Example Needed, Hector Santos
• RE: QUERY: Key Server Choices, Hallam-Baker, Phillip
  • <Possible follow-ups>
  • RE: QUERY: Key Server Choices, Hallam-Baker, Phillip
    • Re: QUERY: Key Server Choices, Michael Thomas
  • RE: QUERY: Key Server Choices, Hallam-Baker, Phillip
• QUERY: Relationshipt to other IETF work, Hallam-Baker, Phillip
  • Re: QUERY: Relationshipt to other IETF work, Hector Santos
    • Re: QUERY: Relationshipt to other IETF work, Hector Santos
  • Re: QUERY: Relationshipt to other IETF work, Frank Ellermann
  • Re: QUERY: Relationshipt to other IETF work, Arvel Hathcock
  • Message not available
    • Re: QUERY: Relationshipt to other IETF work, SM
  • Re: QUERY: Relationshipt to other IETF work, Thomas Roessler
  • Re: QUERY: Relationshipt to other IETF work, Ned Freed
  • Re: QUERY: Relationshipt to other IETF work, Earl Hood
  • RE: QUERY: Relationshipt to other IETF work, Edward Shallow
  • <Possible follow-ups>
  • RE: QUERY: Relationshipt to other IETF work, Hallam-Baker, Phillip
    • RE: QUERY: Relationshipt to other IETF work, Dave Crocker
• PROCEDURAL ISSUE: RE: QUERY: Key Server Choices, Hallam-Baker, Phillip
  • Re: PROCEDURAL ISSUE: RE: QUERY: Key Server Choices, Thomas Roessler
    • Re: PROCEDURAL ISSUE: RE: QUERY: Key Server Choices, domainkeys-feedbackbase02
  • Re: PROCEDURAL ISSUE: RE: QUERY: Key Server Choices, Arvel Hathcock
• RE: QUERY: Key Server Choices, Hallam-Baker, Phillip
  • Re: QUERY: Key Server Choices, Arvel Hathcock
  • RE: QUERY: Key Server Choices, domainkeys-feedbackbase02
    • RE: QUERY: Key Server Choices, william(at)elan.net
      • RE: QUERY: Key Server Choices, Ned Freed
      • RE: QUERY: Key Server Choices, william(at)elan.net
      • Re: QUERY: Key Server Choices, wayne
      • Re: QUERY: Key Server Choices, Michael Thomas
      • Header field canonicalzation question, Bryan Costales
      • Re: Header field canonicalzation question, Arvel Hathcock
      • Re: Header field canonicalzation question, Arvel Hathcock
      • Re: QUERY: Key Server Choices, william(at)elan.net
      • Re: QUERY: Key Server Choices, wayne
      • Re: QUERY: Key Server Choices, Tony Finch
    • Re: QUERY: Key Server Choices, Earl Hood
  • <Possible follow-ups>
  • RE: QUERY: Key Server Choices, Hallam-Baker, Phillip
    • Re: QUERY: Key Server Choices, Michael Thomas
  • RE: QUERY: Key Server Choices, Hallam-Baker, Phillip
    • RE: QUERY: Key Server Choices, James Scott
    • RE: QUERY: Key Server Choices, domainkeys-feedbackbase02
      • The cost of choices, Dave Crocker
      • Re: The cost of choices, william(at)elan.net
      • Re: The cost of choices, Hector Santos
      • Re: The cost of choices, Arvel Hathcock
      • Re: QUERY: Key Server Choices, Hector Santos
      • Re: QUERY: Key Server Choices, Thomas Roessler
    • Message not available
      • RE: QUERY: Key Server Choices, SM
  • RE: QUERY: Key Server Choices, Hallam-Baker, Phillip
  • Re: QUERY: Key Server Choices, John R Levine
    • Re: QUERY: Key Server Choices, Arvel Hathcock
  • RE: QUERY: Key Server Choices, Hallam-Baker, Phillip
    • RE: QUERY: Key Server Choices, domainkeys-feedbackbase02
      • Is DKIM only for boundary MTAs? (was Re: QUERY: Key Server Choices), Earl Hood
      • Re: Is DKIM only for boundary MTAs? (was Re: QUERY: Key Server Choices), Michael Thomas
  • RE: QUERY: Key Server Choices, Hallam-Baker, Phillip
  • RE: QUERY: Key Server Choices, Hallam-Baker, Phillip
• RE: accreditation, Hallam-Baker, Phillip
  • Re: accreditation, Michael Thomas
  • <Possible follow-ups>
  • RE: accreditation, Hallam-Baker, Phillip
    • Re: accreditation, Michael Thomas
  • RE: accreditation, Hallam-Baker, Phillip
• DKIM Body Count/Length, Hector Santos
  • Re: DKIM Body Count/Length, Michael Thomas
    • Re: DKIM Body Count/Length, Hector Santos
      • Re: DKIM Body Count/Length, Michael Thomas
• DKIM - New form of Social Engineering Spam?, Hector Santos
• RE: DKIM: c=simple is aspirational, Hallam-Baker, Phillip
  • Re: DKIM: c=simple is aspirational, Hector Santos
  • <Possible follow-ups>
  • RE: DKIM: c=simple is aspirational, Hallam-Baker, Phillip
• Suggestion: assigning DKIM o= policy names, Hector Santos
  • Re: Suggestion: assigning DKIM o= policy names, Arvel Hathcock
  • Re: Suggestion: assigning DKIM o= policy names, Jim Fenton
    • Re: Suggestion: assigning DKIM o= policy names, Arvel Hathcock
• DKIM x= Signature Expiration - Domain Expiration Required?, Hector Santos
  • Re: DKIM x= Signature Expiration - Domain Expiration Required?, Michael Thomas
• DKIM o=$ Outbound Signing Policy Suggestion, Hector Santos
  • Re: DKIM o=$ Outbound Signing Policy Suggestion, Jim Fenton
    • Re: DKIM o=$ Outbound Signing Policy Suggestion, Hector Santos
    • Restricted Third Party Signing Policy, James Scott
      • Re: Restricted Third Party Signing Policy, Jim Fenton
• RE: Issue tracking (was: revised Proposed Charter), Hallam-Baker, Phillip
  • RE: Issue tracking (was: revised Proposed Charter), Dave Crocker
• revised Proposed Charter, Dave Crocker
  • Re: revised Proposed Charter, Ned Freed
    • Re: revised Proposed Charter, Dave Crocker
      • Re: revised Proposed Charter, Dave Crocker
      • Issue tracking (was: revised Proposed Charter), Ned Freed
  • Re: revised Proposed Charter, william(at)elan.net
  • Re: revised Proposed Charter, Frank Ellermann
    • Re: revised Proposed Charter, Thomas Roessler
      • Re: revised Proposed Charter, Dave Crocker
      • Re: revised Proposed Charter, wayne
    • Re: revised Proposed Charter, Ned Freed
      • Re: revised Proposed Charter, william(at)elan.net
  • Re: revised Proposed Charter, Sam Hartman

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.