In your previous mail you wrote:
People, have you been reading the posts? The stubby SMTP daemon is not
an SMTP server, it is simply a program that returns the following set of
responses TO ANYTHING THAT IS PASSED TO IT.
= IMHO it should reject SMTP connection from the beginning
*This message was transferred with a trial version of CommuniGate(tm) Pro*
I've was uncomfortable when Verisign got into the register business
since having your Certificate from someone who can also mess with your
registration is liking having the same person do your accounting and
auditing...
On Wed, 17 Sep 2003, Keith Moore wrote:
Your mail client was making a false assumption. That is a bug in the
software. The mail client shouldn't be looking up domains. It should be
sending it to the relay.
No, you're making an incorrect assumption. It's perfectly valid for a
mail
% % Wildcard records make a global assertion for an entire zone. This is not
% % an assertion that VeriSign is entitled to make. VeriSign does not have
% the% right to make assertions about all unregistered domains in NET or COM.
% %
% Can you back up your assertion that Verisign is
On Wed, 17 Sep 2003 [EMAIL PROTECTED] wrote:
On Wed, 17 Sep 2003, Dean Anderson wrote:
Your mail client was making a false assumption. That is a bug in the
software. The mail client shouldn't be looking up domains. It should be
sending it to the relay. The relay then decides where to
The machines that serve the IETF are located in the track of Hurricane
Isabel, which is expected to impact the East Coast of the United States on
Thursday. There are currently two servers:
www1.ietf.org (in Reston, Virginia)
www2.ietf.org (in Natick, Massachusetts)
The Reston site hosts the
On Wed, 17 Sep 2003, Keith Moore wrote:
People keep saying that something has been broken. But in fact, nothing
has been broken, except false assumptions that were false to begin with.
You're simply wrong, and there have been numerous examples of this.
Sounds like a canard.
NXDOMAIN
ok, what about DoC ICANN agreements w/ VSGN giving them
the authority to continue to register in and publish
the .COM and .NET domains? That looks like an entitlment to me.
Hm, to me publishing all registered entities of a domain
is not the same as publishing that the
At 2:14 PM +0200 9/18/03, Francis Dupont wrote:
= IMHO it should reject SMTP connection from the beginning with
the 521 greeting described in RFC 1846...
People are unhappy about VeriSign breaking the rules. But here you
are proposing that they follow an *experimental* RFC whose rules were
not
On Thu, 18 Sep 2003 11:45:14 EDT, Dean Anderson said:
I think you have pointed out that this is indeed the function of a mail
server, not a mail client. It is a bug.
OK Dean, let's go back and look at the original message.
On Wed, 17 Sep 2003, Doug Royer wrote:
Before the change if I email
On Thu, 18 Sep 2003 12:04:31 EDT, Dean Anderson said:
You have yet explain how is it misreporting anything. It in fact
reporting that the domain is available for purchase. How is that
misreporting?
Well.. let's follow this line of reasoning. If I mail to a domain, *and it gets
a pointer to a
ok, what about DoC ICANN agreements w/ VSGN giving them
the authority to continue to register in and publish
the .COM and .NET domains? That looks like an entitlment to me.
the very purpose of those agreements - hell, the primary purpose of ICANN, is
to constrain how
On Thu, 18 Sep 2003 09:22:15 -0700
Paul Hoffman / IMC [EMAIL PROTECTED] wrote:
At 2:14 PM +0200 9/18/03, Francis Dupont wrote:
= IMHO it should reject SMTP connection from the beginning with
the 521 greeting described in RFC 1846...
People are unhappy about VeriSign breaking the rules. But
No, its not valid for a mail client to make direct connections. There are
many ISPs that block this. Are they doing something wrong?
IMHO yes, but that's between them and their customers.
Mail clients
are supposed to connect to their configured mail relays, which has the
responsibility
Dean Anderson wrote:
It did that if you sent to any other toplevel domain that had wildcards,
and others do.
The behavior hasn't changed.
Your mail client was making a false assumption. That is a bug in the
software. The mail client shouldn't be looking up domains. It should be
sending it to
No, its not valid for a mail client to make direct connections.
Can you site any RFC that says that?
There are
many ISPs that block this. Are they doing something wrong?
Orthogonal and unrelated.
Mail clients
are supposed to connect to their configured mail relays, which has the
16 matches
Mail list logo
