That's what I was looking for (I think). I should be able to script something together with that. I'll post it here if/when I get it done. Not really a high priority at the moment. ;)
Sam Clippinger wrote: > That's not a bad idea, I'll add that to the ever-growing list. :) > > With the current version (assuming you're comfortable at the command > line), you can set the TCPREMOTEIP environment variable to the remote IP > and run spamdyke manually to see what it says. Something like this: > $ export TCPREMOTEIP=11.22.33.44 > $ spamdyke -f /etc/spamdyke.conf /var/qmail/bin/qmail-smtpd /bin/true > > -- Sam Clippinger > > Eric Shubert wrote: >> Christoph Kuhle (Expat Email Ltd) wrote: >> >>> Separately, I do notice a small but sufficiently significant number of >>> genuine emails which get rejected with no reverse DNS. Should we be happy >>> to put email addresses on the white list, or is that dangerous with Spammers >>> being able to get through if they purport to be that address? Up to now, we >>> have just passed on the maillog entry on so that they can check it out with >>> their own hosting company. >>> >> This is what I do, whitelist and notify the sending server's admin. >> >> It'd be nice if there was a spamdyke tool that would allow one to easily >> re-check an IP address to see if their server has subsequently been >> fixed, as an aid in keeping the whitelist clean. Sort of a "if a certain >> IP address were to send an email to my server, would spamdyke reject >> it?" tool. What do you think, Sam? >> >> -- -Eric 'shubes' _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
