Got it fixed! For some reason I had 'rdns-whitelist-file=/home/vpopmail' with no path to the file. The file did exist, so I simply needed to edit spamdyke.conf. No more errors.
Thanks again for the great work! -- Ben Sam Clippinger wrote: > I wrote a check into all of spamdyke's file reading functions to stop > reading after 65536 lines. The purpose is two-fold: first, if there's a > bug in the parser that could lead to an infinite loop, the function will > bail out and log an error. Second, if there's a typo in the > configuration or on the command line and an incorrect filename is given > (e.g. /dev/random), spamdyke won't read forever. > > In this case, I think the latter is more likely. Check your config file > -- are you specifying "/home/vpopmail" for an option that expects a > filename? If not, the error message isn't showing the entire filename > for some reason and should be fixed. > > If you have any files are legitimately more than 65536 lines long, they > should be broken into several smaller files and the configuration option > should be given multiple times. spamdyke will read more than 65536 > lines total, it just won't do it from a single file. Of course, if you > have that much content in a white/blacklist file, you really should be > using the directory structure instead. Reading large files for every > SMTP connection is very slow. > > A few weeks ago, I realized none of the documentation mentions this > limit and I intend to fix that when I make my changes for the upcoming > version. > > -- Sam Clippinger > > Ben Mills wrote: >> I often see this error in my spamdyke log. I'm using 3.1.6 but I've seen >> this same error with the other versions. Spamdyke is doing its job quite >> well, so it hasn't been a concern to me. >> >> ERROR: ignoring file content past line 65536: /home/vpopmail >> >> Any ideas as to why I'm seeing this? _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
