>>>...
>
>Hi,
>
>what is the problem with putting a single computer into a hosting center, name
>it mycompany.com,
>and also let it helo as mycompany.com?
>Of course it should have reasonable dns entries but that's a different story
>
>Wolfgang Hamann
>
None. In the last year I have received valid email from slightly
over 1K sites which HELO/EHLO'd with a single dot. Admittedly about 1/3
of these were from spammers (not spam, but from spam domains). But included
in the list are all of the HotPop domains (I have mail from ~15-20 different
ones), atitech.com, atheros.com, hotmail.com, hyperlinktech.com, intel.com,
jameco.com, megapath.net, minicircuits.com, minicircuits.com, mit.edu,
parago.com, roxette.org, s-mail.com, taos-it.nl, ucsc.edu, ups.com,
uswest.net, win-host.net, winserver.com, and zipzoomfly.com plus hundreds
of smaller sites which I recognize and know people at the companies or the
admin/owners of and many who don't want to be idenitified and those like my
attorney and accountants who no one else would recognize and I shouldn't
identify.
I'm quite convinced that the single dot rule would cause far too
many FPs, at least for me - and I'm a rather small business/site. If Kai
would like, I'd give him the list (and I culled out the domains like sun.com
and ibm.com who no longer use the base domain name for external HELO's, but
do seem to still use it internally - i.e. it appears in valid "Received:"
headers before reaching me). I can see a valid reason for refusing the
"free-mail" accounts and domains, but medium and large electronics firms
would end up killing me with overhead of whitelisting.
Paul Shupak
[EMAIL PROTECTED] (no 'A' RR but MXs and an SOA plus FCrDNS and SPF)
