Hi, Kris wrote: > As best I can recall it runs some trailing bits of what you might > reasonably call "message parsing", and at least the first stages of > running rule checks. I couldn't find a middle ground that only did the > real minimum necessary for extracting the relay IPs and URIs from the > message.
It turned out to be a bit of local config, but mostly not expecting it to take so long to check() a single message. I'm sorry for the trouble; perhaps I was impatient due to not understanding the SA perl API. Do you think there's anything that can be done to further automate the process of inspecting the IP addresses it produces? If I understand your docs correctly, it's an entirely manual process with inserting them into your web cgi and determining whether it should be added to your DNSBL, correct? I'm finding that by the time I can collect the FNs and run the script on them, a few spot-checks show they're already listed in zen. I've taken a handful of IPs that it's produced and added them to a postfix client restriction, which has worked quite well, until I can find the time to implement the local DNSBL. I'd like to be able to enhance the script to run it against a whitelist of IPs or some other way to make this process less manually intensive. For now, I'm just picking a few that have been reported most frequently and checking them manually in my mail logs, and adding them if necessary. Thanks, Alex
