-----Original Message-----
From: owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
[mailto:owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com] On Behalf Of
Hector Santos
Sent: donderdag 14 april 2005 14:06
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: Re: [spf-discuss] IESG and
To flag an identity, put the string
*ID* after the declared name.
HELO my-company.com *ID*
MAIL FROM: bob(_at_)sales(_dot_)my-company(_dot_)com
Second, if a systems must make an significant non-backward compatible
change, when why bother with any of this at all and just change SMTP
altogether?
If you want to do stuff like this then use the ESMTP
framework. That is what it is there for: to provide
Extended SMTP (ESMTP) commands.
C: EHLO my-company.com
S: 220-domain, Hi there!
S: 220-MYID
S: 220 HELP
C: MYID *ID*
S: 250 Cool!
C: MAIL FROM: bob(_at_)sales(_dot_)my-company(_dot_)com
"MYID" is, of course, not a valid SMTP Service Extensions either (nor an
RFC1869 4.3 compliant SMTP Service Extensions, for that matter). I have
always advocated using ENVID for this sort of practices. You could use
that right now if you wanted to, as the 'infrastructure' for it is already
there.
- Mark
System Administrator Asarian-host.org
---
"If you were supposed to understand it,
we wouldn't call it code." - FedEx