I'm very sorry it's taken so long to get back to you on this; I've been buried at work and haven't had any time to investigate.
It definitely sounds like you've hit a bug. spamdyke does save the addresses of all the recipients in order to print them all out in a loop, but only when the header blacklist feature is enabled. It does this because the recipient names have already gone by before the message header is sent, so it must save the recipient addresses to print either "ALLOWED" or "DENIED" once the header is finished. But it should only do this once and I'm not seeing a way to trigger that code more than once, though it certainly looks like that's what's happening. So let me start with all the standard questions: what OS and version are you on? What version of spamdyke are you using? Could you please post your configuration file(s) (or send them to me directly)? Would you mind turning on spamdyke's full logging feature (the "full-log-dir" option) and capturing one of these sessions? Needless to say this behavior isn't by design and it's not happening on any of the servers I manage (and I use the header-blacklist feature on every one). After spending a little while testing and tracking through the code I can't reproduce this problem, so I suspect it's a combination of environment and a specific configuration you're using. I'd love to track this down and fix it! -- Sam Clippinger On May 22, 2013, at 7:40 AM, Teodor Milkov wrote: > Hello, > > I did a quick search in the mailing list about this issue, but didn't > find anything related, so here I go: > > When an email with multiple RCPT TO is sent in single SMTP session, it > seems all previous recipients are logged at each new RCPT TO command. > See attached spamdyke.txt log for details (I've replaced original > sender/recipient names for privacy reasons). > > Basically if there's incoming mail from one sender to 3 recipients in > single smtp session I see something like: > > ALLOWED from: sender to recipient-1 > ALLOWED from: sender to recipient-1 > ALLOWED from: sender to recipient-2 > ALLOWED from: sender to recipient-1 > ALLOWED from: sender to recipient-2 > ALLOWED from: sender to recipient-3 > > Which in some extreme cases where session had 9000 recipients led to > multi GB log file. > > Glancing quickly through sources I didn't find how this works, but I'll > look again later this week when I have more time. > > > -- > Teodor Milkov | System Administrator | ICDSoft Ltd. > <spamdyke.txt>_______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
