It looks like the sender address [EMAIL PROTECTED] was ignored in a
regex. Because the report lines should not contain the senders address.
Aug-20-08 17:49:02 [Bayesian] 202.124.241.22
[EMAIL PROTECTED] [spam found] (Bayesian) [Nett
Partner Offer HP helps cut your costs plus you can win 3500
Thank you for the additional information. I had most of the logging
options turned off, however I went ahead and unchecked all logging
options, and selected silent mode. I'll keep a close eye on it today to
see if it does any better. At this point in time, it is taking ASSP
about 6 seconds to
I tried completely turning logging off and it does not appear to be
helping the situation. :( I'm seeing upwards of 9 seconds+ response time
before ASSP provides the 220.
I'm going to leave logging off and immediately start working on moving
to a mySQL backend with hopes that it will help.
I'm not able to start ASSP with the mySQL information programmed in to
it.. Any ideas?
[EMAIL PROTECTED] assp]# perl assp.pl
create table whitelist (pkeyvarbinary(254) primary key,pvalue
varbinary(255),pfrozen tinyint not null)
create table redlist (pkeyvarbinary(254) primary
Try setting the PATH so, that ImageMagick convert.exe is found before
Windows convert.exe in ...\system32 !
If you start cmd.exe and type convert - version ImageMagic
convert.exe should start!
That would be convert -version without the extra space (or the
quotes). In case that wasn't
Hello All,
During the run of the install.cmd file I get the following error in a dialog
box:
The ordinal 3654 could not be located in the dynamic link library
LIBEAY32.dll.
Everything else seems to install fine. The end result says everything
installs except Mail::DKIM::Verifier.
I have went
ERROR in description: not supported insite ASSP !!!
Probably should be: (not supported inside ASSP !!!) or (not supported by
ASSP !!!)
Daniel Du Vall
P.S thanks for the addition of this I set it to day and will see how it
works.
Version 2, 5.10.
This morning I got a phishing spam email. The headers had no mention
of ASSP, so I was puzzled as to how this could be.
Looking at the log I could only find:
Aug-22-08 09:22:29 [Worker_2] Info: got STARTTLS request from
62.213.74.114
Looking at the postfix logs:
Aug 22
No, this is not a bug! After a TLS connection is astablished the
comunication between the peers is encrypted (in your case with cipher
DHE-RSA-AES256-SHA) and we are unable to parse the transmitted data in
ASSP! If you get SPAM via TLS just set 'DoNotTLS' to on. This will remove
the STARTTLS
