At 05:05 AM 5/1/01 -0700, you wrote: >At 7:15 PM -0700 4/26/01, Joe Wagner imposed structure on a stream of >electrons, yielding: >>For some reason, no doubt the full moon plus a cut and paste I used in >>two lines: >> >>domain1.com = domain1.com.smtp >>*.domain1.com = *.domain1.com.smtp > >Do you have any other idea why you added the second line? Do you really >get mail aimed at [EMAIL PROTECTED] addresses where you don't know what ><foo> might be? Actually, the other reason is that I've done that a couple times in the past when I've been a secondary (but not primary) for some other domains. Since I am not necessarily notified when they add subdomains, I though that was the correct syntax to handle whatever would come down the pike. >Note that this makes mail3 a usable backup MX for any host anywhere under >the domain1.com zone. If you don't control that zone absolutely (i.e. >someone else runs DNS for sub.domain1.com) you are enabling stuff you >might not like. I don't think this is a security (relay) hazard though, right? Or do I open myself up to ! addressing or other such subtleties. >The following is a guess based on empirical analysis, not on knowledge of >how exactly the router works internally... >[...] Hmm, interesting thought. >You can probably test this theory by turning up logging on mail3 to "all >info" and taking the other boxes offline. Mail something and watch what >exactly the router is doing. I'll have to try this when our SDSL finally gets back on line and I'd have some extra IP's to throw temp servers on. Thanks, Joe ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
