I would recommend taking a look at this RFC: http://www.faqs.org/rfcs/rfc2821.html Mark Fugatt MCT, MCSE, Microsoft Exchange MVP Pentech Office Solutions Inc Tel: 585 586 3890 Cell: 585 576 4750 Fax: 585 249 0316 www.4mcts.com www.exchangetrainer.com -----Original Message----- From: Mulnick, Al [mailto:Al.Mulnick@xxxxxxxxxx] Sent: Monday, September 15, 2003 12:06 PM To: [ExchangeList] http://www.MSExchange.org/ I'm starting to wonder if I'm reading the same RFC :) I see this part of the RFC : 6.2.3. DOMAIN TERMS A domain-ref must be THE official name of a registry, network, or host. It is a symbolic reference, within a name sub- domain. At times, it is necessary to bypass standard mechan- isms for resolving such references, using more primitive information, such as a network host address rather than its associated host name. To permit such references, this standard provides the domain- literal construct. Its contents must conform with the needs of the sub-domain in which it is interpreted. Domain-literals which refer to domains within the ARPA Inter- net specify 32-bit Internet addresses, in four 8-bit fields noted in decimal, as described in Request for Comments #820, "Assigned Numbers." For example: [10.0.3.19] Note: THE USE OF DOMAIN-LITERALS IS STRONGLY DISCOURAGED. It is permitted only as a means of bypassing temporary system limitations, such as name tables which are not complete. The names of "top-level" domains, and the names of domains under in the ARPA Internet, are registered with the Network Information Center, SRI International, Menlo Park, California. And especially notice the NOTE section which strongly discourages the use of domain literals. I have to question the use of that by any blacklist/blocklist/blockhead that says you have to have one of those, especially since that concept doesn't really scale well, does it? Multiple MX records are needed and if DNS is inoperable, then I suppose that reverse DNS checks would also be broken, right? I'm not trying to rant about this, but it makes no sense!! What is the value of a domain-literal/implicitly defined FQDN for host delivery? Better yet, is that not a bigger problem to specify such a thing with little return? I'd have to give away half the addresses (which arguably should be public, but the situation is if DNS is down). I think that the further use of the RFC which says that you should be able to fall back to trying an A RR for a domain is a far better use of the system than is domain-literal acceptance. Al -----Original Message----- From: Mark Fugatt [mailto:mark@xxxxxxxxx] Sent: Monday, September 15, 2003 10:27 AM To: [ExchangeList] Subject: [exchangelist] RE: address with brackets http://www.MSExchange.org/ Here is a link that should help you out: http://tinyurl.com/g8vq Mark Fugatt MCT, MCSE, Microsoft Exchange MVP Pentech Office Solutions Inc Tel: 585 586 3890 Cell: 585 576 4750 Fax: 585 249 0316 www.4mcts.com www.exchangetrainer.com -----Original Message----- From: giordanocontigiani@xxxxxxxxxxxxxxxxx [mailto:giordanocontigiani@xxxxxxxxxxxxxxxxx] Sent: Saturday, September 13, 2003 3:48 AM To: [ExchangeList] http://www.MSExchange.org/ RFC 822 require that SMTP server accept addres like "name@[1.2.3.4]", where mail domain is a dtext within brackets. My exchange 2000 server dont accept this type of address (there is a manner to configure this?), second question outlook client dont permit to send to this address (outlook express permit it) thanks for any info regards giordano contigiani sys admin ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: mark@xxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: al.mulnick@xxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: mark@xxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')