I'm quitting this discussion right now but I still would really
appreciate it if someone can find the time to tell Bruce that he
cannot validate alex(_at_)slot(_dot_)hollandcasino(_dot_)net by
probing
alex(_at_)193(_dot_)172(_dot_)40(_dot_)25 (with or without brackets doesn't
seem to matter
according to bruce).
Of course, the brackets do matter, so I have to concentrate on the
legitimate form user(_at_)[ip(_dot_)ad(_dot_)dr(_dot_)es](_dot_) An
illegitimate RCPT format such
as user(_at_)ip(_dot_)ad(_dot_)dr(_dot_)es should always be rejected (though
it's not by many
MTAs, of course).
And I don't see where 193.172.40.25 is relevant to any discussion of
slot.hollandcasino.net, as it is neither an A nor an MX for the
domain. Whether or not it happens to be the domain's mailbox server is
unknowable (unless you use SRV records, et al., which is not germane).
But _even if_ you were dealing with 193.172.40.25 and had reason to
trust that it's a mailbox server for domain example.com, it does not
follow that user(_at_)[193(_dot_)172(_dot_)40(_dot_)25] will verify the
LHS against all
domains for which the box performs local delivery.
Bruce can verify this with his own virtual-hosting MTA. SMTPD32 will
only check its primary virtual host--the virtual host with the same
official host name as the global SMTPD32 installation--for address
literals. That is, you can have example.com, example2.com, and
example3.com all hosted independently on the same box. If the OHN is
example.com, then user(_at_)[ip(_dot_)ad(_dot_)dr(_dot_)es] will only perform
one lookup: in
the example.com userbase. A failure does not indicate that
user(_at_)example2(_dot_)com and user(_at_)example3(_dot_)com do not exist.
Perhaps this will help.
--Sandy
------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
e-mail: sandy(_at_)cypressintegrated(_dot_)com
------------------------------------