Thank you Sam! I'm downloading version 4.0.2 now and will install forthwith!
I ended up making a cron job to delete those nested _none directories each night, which was working out. This of course is better. ~ Bob Alanis Sam Clippinger wrote: > Definitely a bug in 4.0.1. Definitely due to a boneheaded mistake. > > In 4.0.1, I added some code to specially handle the case of converting a > graylist file named "_none" from the 3.x graylist directory structure to > the 4.0 directory structure. It works like this: > Check for the existence of > graylistdir/recipientdomain/recipientusername/_none > If found, rename it to > graylistdir/recipientdomain/recipientusername/___none > Create a new directory named > graylistdir/recipientdomain/recipientusername/_none > Move and rename ___none to > graylistdir/recipientdomain/recipientusername/_none/_none > The bug is in the first step. It never checks to see if "_none" is a > file or a directory. Renaming and moving works on both types of > entries, so you will eventually end up with a very deep directory > structure (the maximum depth is determined by the filesystem). > > Unfortunately, adding "[EMAIL PROTECTED]" to your sender blacklist won't > work; that entry will only block that literal address, not blank > senders. spamdyke only substitutes "_none" for a blank sender address > while the graylist filter is running. spamdyke doesn't currently > provide a way to blacklist empty senders. > > I've fixed this bug in the code and I'm running the test scripts now. > As soon as they finish successfully (they typically take about 90 > minutes to run), I'll release version 4.0.2. > > -- Sam Clippinger > > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
