[Top] [All Lists]

Re: Re: Strict RFC x821 Compliant: HELO/EHLO

2005-07-04 06:27:48

From: <willemien(_at_)amidatrust(_dot_)com>

So we have the domain-literal,  for 2821bis, we need to make sure it
clearly defines what are all the possibilities.

I think that will be an impossibility.


You cannot fix in stone what people in 2525 have to do.

Like what?  Fix their TCP problems?  I fail to see what the price of rice
in china has anthing to do with dealing with the issue of HELO?

But an list of all the current posibilities is possible and advisable.

(How about the misformed IP6 literal/name of
[BAD3:ABBA:BAD1:ABBA:BAD3:ABBA:BAD4:ABBA] for abba dislikers)

What about it?

Remember, in my view, for proposals, like SPF and CSV to have any hope
success in the future, the client domain name will have to be clearly
out, with some level of enforcement.   For example, before I can make
presumption the client domain is CSV or SPF ready, I need to make sure
it is
syntax/value ready first.

Maybe you just have to do all tests.
precumption 1 it is a domain
presumption 2 it is a IP4 literal.
presumption 3 it is a IP6 litersl
presumption 4 it is an other General-address-literal

Ok? what's the problem?

And hope that only one exsist or all that exsist refer to the same
 "place on the internet"

(Hand flying over head! Zoommmm!)

and the price of rice in china is what again?

I fail to see your point.  Are you saying basically "Status Quo?"

Hector Santos, Santronics Software, Inc.

<Prev in Thread] Current Thread [Next in Thread>