>
> I agree with Michael that spamdyke is great. Highly recommended.
>
> I'd like to clarify the tcpserver -h option though. This option does do
> an rDNS lookup which is duplicative with spamdyke, but I think it's best
> to do both, as they're used for different purposes. Spamdyke uses rDNS
> for blocking. Tcpserver's -h option simply sets the TCPREMOTEHOST
> variable, which does no blocking of any kind, but does provide more
> complete logging messages. The overhead of the duplicate rDNS lookup is
> negligible (immeasurable I expect), since the lookup is cached. That's
> why I think it's best to have both.
>
> Sam C (spamdyke's author) discusses this (and other things) here:
> http://www.mail-archive.com/[email protected]/msg00842.html
>
Thanks for the clarification Eric. I wasn't that familiar with the -h
option in SpamAssassin, and just assumed that since it was doing rDNS
lookups, it was using them for blocking. And, you're right, the DNS
information should be cached, especially if SpamDyke is used to initially
filter, making the overhead looking it up again in SpamAssassin
insignificant.
Michael J. Colvin
NorCal Internet Services
www.norcalisp.com
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
