You understood it correctly. The main problem is that it would produce a huge additional amount of dns queries. A periodically generated ip whitelist is still better than putting it into spamdyke.
Regards Zoltan Sam Clippinger wrote: > This wouldn't be a right-hand whitelist exactly -- spamdyke already > supports RHSWLs by checking the rDNS name against the list. > > Supporting DynDNS would require an extra step. It would function like > an IP whitelist, except the IP addresses would be found by querying a > list of FQDNs. For example, if this feature was used to whitelist > "mail.example.dyndns.com", spamdyke would perform a DNS A record for > "mail.example.dyndns.com". If that IP address was 11.22.33.44, spamdyke > would add 11.22.33.44 to its IP whitelist. From that point on, spamdyke > would behave as it does now. > > At least, that's my understanding of how DynDNS needs to be supported. > It would increase the number of DNS queries, so it would have to be used > sparingly. > > -- Sam Clippinger > > Eric Shubert wrote: >> Are you simply talking about a right-hand whitelist? >> >> That could be useful in some situations. For instance, I recently came >> across a mailer who was being rejected due to DENIED_RDNS_RESOLVE, so I >> whitelisted the IP (instead of turning off that check). I would rather >> whitelist the domain name though, in case they change their server's IP >> address (which I figure is a fair chance of happening given that it's >> presently not quite correct). >> >> I don't think this should apply to relays (non-local mail) though. >> >> Am I missing something here? >> >> Sam Clippinger wrote: >> >>> SMTP AUTH is definitely the best option, if you can configure postfix to >>> perform it for outbound email. >>> >>> I don't use DynDNS myself -- what would be required to support it? >>> Would spamdyke need to find the IP address(es) of a (list of) DynDNS >>> name(s), then add those IP address(es) to the whitelist? If that's all >>> it would take, I don't think that would be very hard. >>> >>> -- Sam Clippinger >>> >>> Christian Aust wrote: >>> >>>> Hi all, >>>> >>>> I'm using the latest release of spamdyke, and it's working great - >>>> thanks a lot. >>>> >>>> Now I'd like to have my home server relay it's mail through the main >>>> mail system. Spamdyke blocks the connecton with DENIED_IP_IN_CC_RDNS, >>>> because the home system certainly connects using a non-static IP which >>>> happens to have the ip in it's RDNS name. spamdyke is working >>>> perfectly and is doing what it has been told. >>>> >>>> But how could I allow my satellite server to actually send mail >>>> through this relay? If I could instruct spamdyke to check the IP >>>> against some given dyndns name (and allow if the IPs match) it would >>>> be all right, but AFAIK spamdyke doesn't offer such option. Or, does it? >>>> >>>> Any other ideas? BTW: I'm running postfix on the satellite and >>>> (obviously) qmail on the main server. Best regards, >>>> >>>> Christian >>>> > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
