This feature would not alter any whitelist files. It would only save
the IP addresses in memory long enough to process the message. The next
incoming message would have to look up the IP addresses again.
-- Sam Clippinger
Sergio Minini {NETKEY} wrote:
> What would happen when the DynDNS changes? Would the IP still remain in the
> whiteiplist?
> If automatic de-listing is not possible, it would be useful to add a comment
> (like: # mail.example.org DynDNS) to the IP listing, to make manual editing
> easier.
>
> Just a thought.
> Thanks- Sergio
>
>
>
>> -----Original Message-----
>>
>> 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
>>
>
> _______________________________________________
> spamdyke-users mailing list
> spamdyke-users@spamdyke.org
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>
_______________________________________________
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
