On Thu, 23 Sep 2004, Joe Smith wrote:
*This message was transferred with a trial version of CommuniGate(tm) Pro*
I'm using SpamAssassin 3.0 when I use whitelist_from_rcvd with domain names that reverse to only one possible domain it works just as it should. When the domain name is one that has multiple possibilities that it can reverse dns to then it doesn't work unless it happens to pick the domain name listed in my whitelist_rcvd_to entry. For example, if I create an entry for whitelist_from_rcvd [EMAIL PROTECTED] domain1.com but the server hosting domain1.com also hosts domain2.com, anotherdomain.com and anotherdomain.net, I have problems. Say the server that hosted email for the domain I wanted to whitelist had an ip of 123.123.123.1 and I did dig -x 123.123.123.1, it would give me all the various domains that that address is configured for.
I think this is what's going on anyway. I looked at the output from spamassassin -D -t < problem then I notice that the rdns= is for one of the other domains hosted on the server and not the domain I would like to whitelist. When I examine the same output from a message that is working, the rdns= is the domain name that I specified in the whitelist_from_rcvd entry. Do I need to specify the IP address of the server using multiple dns entries to get whitelist_from_rcvd to work or should this not be an issue and I need to look at other reasons why this particular domain is causing problems.
Let me try to understand what you are saying.
You are saying that a server has multiple PTR records for a given ip, and that *that* is causing the problem --
So if 1.2.3.4 had PTR records for domainone.com. and domaintwo.com. and domainthree.com., and you had written a filter to whitelist domainone.com's email, but you found it didn't always work?
The person running 1.2.3.4 has NO CLUE what they are doing. 1.2.3.4 should RDNS to whatever the "hostname" value of that machine is. This should be the same as the HELO the machine uses when talking out to the outside world.
Assigning multiple addresses (A or PTR -- for the sake of this discussion there's no difference) to things makes them into a round-robin type thing. The possible answers will be handed out in cyclic order (at least, the first time they are queried), and then they are cached as long as the TTL value for the record -- which I've seen some caches override.
--
"Happy, Sad, Happy, Sad, Happy, Sad, Happy, Intruiged! I've never been so in touch with my emotions!"
-AndrAIa as Hexadecimal, Reboot Episode 3.2.3
--------Dan Mahoney-------- Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org ---------------------------
