ddaas a écrit : > Hi, thanks. > One more question: I have virtual hosting on my server. This means > that the reverse dns of the server ip is ns1.mydomain.com and the EHLO > hostname is mail.maindomain.com > Could this be a problem? I mean the server tries to reverse the ip and > it doesn't get what's in EHLO. >
There is no requirement that the reverse dns be the helo name. but - the reverse dns should resolve back to the client IP. example: $ host 91.121.103.130 130.103.121.91.in-addr.arpa domain name pointer imlil.netoyen.net. $ host imlil.netoyen.net imlil.netoyen.net has address 91.121.103.130 - the helo name should resolve in DNS. ideally, it should resolve to the client IP, although this is rarey checked. (but the helo name may be different that the "reverse dns", since multiple names may resolve to the same IP). if you are on a shared host, then you will have problems. This is because other sites may be sending mail from the same IP, and if they get a bad reputation, the IP is dirty. if you have a "generic reverse dns" (such as mon75-10-82-239-111-12.fbx.proxad.net), you will get problems. This is why you should ask for a custom reverse dns. but you can't get a "custom" rdns on a shared host.
