[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: So here it is one year later...
- To: Hector Santos <hsantos@xxxxxxxxxxxxxx>
- Subject: Re: So here it is one year later...
- From: Jim Fenton <fenton@xxxxxxxxx>
- Date: Tue, 01 Feb 2005 09:57:00 -0800
- Cc: IETF MARID WG <ietf-mxcomp@xxxxxxx>
- Iim-sig: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs"; t:"1107280367.934286"; x:"432200"; a:"rsa-sha1"; b:"nofws:1045"; e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p" "XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC" "50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc="; s:"RdlUOMPBw3+IEnqiiZCWitTvVqZevTAr1+G22w0wJ28reV5TPC6frmKYkNfAe++L9jp4intT" "FMDlbVJlMLOLT7Q55PINJaCrEz6UBjjMVPqlULDhjX9zSuuP9Q0e7LxDB/TgHll9WjonU6S5rHE" "oYcu7bu/x6SxT+TZ3tKsv0uc="; c:"Date: Tue, 01 Feb 2005 09:57:00 -0800"; c:"From: Jim Fenton <email@example.com>"; c:"Subject: Re: So here it is one year later..."
- Iim-verify: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com"; c:"message from imail.cisco.com verified; "
- In-reply-to: <>
- List-archive: <http://www.imc.org/ietf-mxcomp/mail-archive/>
- List-id: <ietf-mxcomp.imc.org>
- List-unsubscribe: <mailto:firstname.lastname@example.org?body=unsubscribe>
- References: <> <> <> <>
- Sender: owner-ietf-mxcomp@xxxxxxxxxxxx
- User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)
I think I'll stick with the "in layman terms" part of the message
because that's most clearly stated:
Hector Santos wrote:
In layman terms:IMO, it will be a very long time (if ever) before a "typical" mail
server will be able to take some action such as rejecting a message
based on a missing signature, except possibly when the originating
domain advertises that it signs all of its mail.
What if my SMTP mail server detects a non-DK/IIM ready message?
You need to answer that question otherwise what is the use of using DK/IIMIt's another message classification criterion, and when present enables
reputation and accreditation based on who the signer is.
if a system still needs to work and be ready for non-DK/IIM messages?
Now of course, it might work well in an exclusive CISCO corporate/enterpriseI hope it's obvious that's not Cisco's intent. But it should be
possible with standards-based message authentication for anyone to more
accurately whitelist their suppliers, customers, and partners, to make
sure that their messages never get lost.
settings, a big pat on the back, an exciting marketing and promotion largely
based on "hope" I can imagine for your big customer base. But this is not
a standard across the board.