Not withstanding Sam's point, I've done this when shutting down a client who's late with the bill - existing DNS with a short TTL and pointing to local host gives INSTANT notification that the site is down, the mail is bouncing etc.
Killing off the DNS or deleting the MX record can still result in delivery by some mail servers (sendmail) and doesn't give an immediate indication of the problem. I have seen people use localhost for delivery in PRIVATE situations where many servers may deliver mail through NFS etc. - not that I agree with the kludge, but that sort of scenario should NEVER be seen on the public side of things unless they screw up. IMHO, blocking them is an excellent idea. m/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sam Varshavchik Sent: Friday, March 28, 2003 2:31 PM To: [EMAIL PROTECTED] Subject: [courier-users] Re: Blocking 'localhost resolving' domains Sam wrote: > This sounds like a pretty clean solution. Are there any other side-effects > from using this setting? Is there any valid reason 127.0.0.1 would show up > in a list of mail servers? Stupidity on the part of the admin. ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
