Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Tuesday 2006-12-19 at 23:03 +0100, Sandy Drobic wrote:
Having a proper reverse DNs means that: - your provider is on good speaking terms with the provider of address space (or even that he is the address space provider) - your dns name is meant to last for some time.
Interesting... still, in my country it is very difficult or even impossible to get rDNS even from the address space owner. They simply do not offer that service, and the talk persons do not even know what it is (not really technicians).
I simply can't imagine that a company with a/several static ip(s) and good bandwidth will not get a correct reverse dns if they insist on getting one. If that is the case and there is an alternative available the customer WILL change. They definitely won't offer that service to small fry. I asked my current provider (of my private internet connection) if I could get a static ip for additional pay and they told me it is impossible. On the other hand they simply don't have business customers. So it's logical that they won't set up static ips and reverse dns.
An idea.
When asking for the r-name for my current IP (W.X.Y.Z), I get something like this:
Z.Red-W-X-Y-.dynamicIP.rima-tde.net.
(and sometimes "static" something, instead of dynamic, go figure - this is the main provider here, by the way).
Bleah, I see these hostnames very often on my reject report. Let's see what restrictions would make your server fail: Your IP (example): Dec 20 12:27:12 spamkill postfix/smtpd[15448]: NOQUEUE: reject: RCPT from 181.Red-83-59-227.dynamicIP.rima-tde.net[83.59.227.181]: 554 5.7.1 Service unavailable; Client host [83.59.227.181] blocked using dynablock.njabl.org; Dynamic/Residential IP range listed by NJABL dynablock - http://njabl.org/dynablock.html; My server would block you, because that IP is listed as dynamic. Even if the ip would not be blocked, just your hostname alone (the reverse dns name, not the helo) would trigger additional check like checking in bl.spamcop.net, greylisting and sender address verify. Because I did indeed get some desired mails from that address space I can't block rima-tde.net hard.
So, suppose I had a domain name, but instead of pointing it to my static address (if I had one), could I point it to the given reverse name instead? I don't know how that is called in DNS parlance, but I suppose you get the idea.
The rDNS on the "real" name would work, as my real name would not be the one I choosed, but the one my ISP gave me...
:-?
This wouldn't change your IP, and many checks apply ip based blacklists. I have a server on a dynamic ip, so I know very well that the situation might be manageable if you are using the server to learn and only for your own private purposes, that that will fail if more users are depending on the server and they can't react and set a route for a domain that does not take the mail directly. In the end the only solution is to use the relayhost of your provider with all the restrictions that apply to that solution. I decided to invest in a static ip and change provider because more and more servers do not accept mails directly, and the relayserver of my provider is not as reliable as I wish my server to be. So, I will soon be able to enjoy the benefits of a static ip. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org