This is my opinion, and like many things, everyone has one.
I'd like to suggest a subtly different approach/guideline:
Any time new functionality is added, leave the new
functionality disabled by default.
I believe, in this case, that means the PhishingScanURLs option
would have
Dennis wrote:
You can rip out a lot of code (well, some code) if you just use the Perl
date method by default and forget the date +%s stuff entirely.
Your mileage may vary.
$ time perl -le print+time
real0m0.002s
$ time date +%s
real0m0.001s
(Those results were surprisingly
Andrew Watkins wrote:
I have been running clamAV 0.91.2 software on our Solaris email server
for a few weeks and all has been well, but I have noticed in the last
few days that clamscan does not end on a specific HTML email.
ClamAV's PhishingScanURLs regex code runs afoul of the Solaris
Paul Griffith wrote:
Does any one have any suggestions for handling spam surges? We had a spam
mail surge and exim was getting connection timeout errors from the clamd
socket, for spamassassin we can increase the number of child processes to
handle more connections.
With postfix, I
It looks like one (or more) of the changes to ClamAV 0.91.2 fixed the
problem I described with 0.91.1.
I can safely re-inject old postfix queue files back into the mail path
on my server(s) and have the messages be delivered normally, rather than
jamming up on clamd.
--Kyle
Amos wrote:
Have to admit that we just experienced this on Solaris 10 x86 (AMD). I
killed and restarted clamd and the backup of incoming mail starting
flowing again. This is with 0.91.1. Build pretty simple:
./configure \
--with-user=amavis \
--with-group=amavis \
