> -----Message d'origine----- > De : /dev/null [mailto:[EMAIL PROTECTED] > Envoy=E9 : mardi 19 avril 2005 12:00 > =C0 : xmail@xmailserver.org > Objet : [xmail] Re: AW: Re: AW: Bind sending IP ? >=20 >=20 > Greetings, > Actually the only way to get around the AOL thing (and=20 > others) is to be > able to *authorativly* answer for the IP to NAME matching. In=20 > other words; > having a Name Service (Domain Name System) running that can answer = the > querries from AOL and anyone else trying to filter spam from=20 > their mail > servers/ Customers. This is the only way to get past the problem you > originally mentioned you were having. Your "routing"=20
Correct > situation stems from > the GW (gateway) IP. That is the lowest IP (1 in this case)=20 > *must* be your > gateway in almost any situation. It is more of the way networking is > designed than an "OS" situation. It is all calculated=20 > mathematically. Net > Blocks are created in such a way that you have "NET" and=20 > "BCAST" numbers > and you will almost always need to use your Lowest number=20 > "NET" as your > gateway. Because the Network Protocol is designed to=20 > communicate in this > fashon, so looks there for that type of information. Hope that helps. False Networks Numbers assignements don't fix the ip to use on the gateway. I personnaly use a ip in the 'middle' of our ip block and this is = correct. I too use another 'middle' ip for my smtp server. I just have to create a good PTR entry for it to pass aol and other = rdns checks ... Use of the first or last ip available in a block (except broadcasts) is = just a 'convention'. Francis - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
