First, I apologize for being so silent lately. I haven't been able to devote much time to spamdyke over the last month or two.
Based on the discussion a few months back, the revised TODO list currently stands thus: DKIM/SPF Limited support for examining message headers so some headers could be logged (e.g. Subject). Rewriting/adding headers when filters failed instead of rejecting the message entirely. Replacing/adding recipients unconditionally (e.g. monitoring employee email or redirecting addresses) or when filters failed (e.g. sending all spam to a specific mailbox). Full logging conditionality, based on IP or rDNS. Full database support, especially for the graylist filter, to make life simpler for administrators of large sites. Automatic whitelisting to allow replies from recipients of outbound email. Daemon proxy mode to replace tcpserver and make spamdyke usable by non-qmail sites. Windows Service mode to make spamdyke usable by Exchange administrators. Tarpit mode to trap botnet spammers the way LaBrea used to trap Code Red attackers. Should the full logging be moved up? Current status: the code for recipient validation is complete. I haven't finished testing it yet, so I can't truthfully say it works under all circumstances. I've still got a ton of test scripts to write to exercise the new code. I _am_ working on it, but as my time has diminished, progress has slowed. -- Sam Clippinger Eric Shubert wrote: > I see in the TODO.txt file, for version N+1 a request to limit full > logging by IP or rDNS name. I'd like to see this given a high priority. > > In addition, I'd like to be able to limit by sender domain. Maybe simply > match the right-hand-most portion of the sender's address? (which could > be simply domain or entire address) > > (FWIW) > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
