I've gotten the latest release and there is a bug with the stats not counting
correctly. I have changed DelayIP to 40 in the IP Blocking section to greylist
anything in the penalty box with a score over 40. This is working just fine
however when looking at the stats this is not accounted for
The penaltyboxextreme setting (DoPenaltyExtremeSMTP) is not overriding the
DelayIP setting from the IP Blocking section. For example my PenaltyExtreme is
set to 175, and DelayIP is set to 40, yet in the logs when a sender whose PB
Box value is 185 gets delayed instead of denied by PB Extreme.
ASSP development mailing list assp-test@lists.sourceforge.net
schreibt:
This is working just fine however when looking at the stats this is
not accounted for as part of the Messages Processed total nor is it
reflected in the message statistics.
It is reflected. Where it belongs:
SMTP Connection
ASSP development mailing list assp-test@lists.sourceforge.net
schreibt:
The penaltyboxextreme setting (DoPenaltyExtremeSMTP) is not
overriding the DelayIP setting from the IP Blocking section.
That is not a bug. It is working as designed. Delaying on IPs is a
very early activity, based ONLY on
Sounds like one of the latest code changes probably
reintroduced an old bug; users are complaining about
HTML emails being badly mangled; had a look at
some of those and it sounds like the content-type
header is missing and the header got badly wrapped
did anyone experience the same issue with the
If we have DNSBL set to block, if SenderBase identifies a whitelisted org,
would a match in DNSBL be overridden?
--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power
Hi
I've received 1150 of these errors in the past 12 hours.
Worker_3: Not a SCALAR reference at assp.pl line 20526
The block reports came ok, I've had no issue with those.
But I saw one block report from someone which didn't look like the block
report I receive and we are both using the same
Worker_3: Not a SCALAR reference at assp.pl line 20526
Grepped the logs to find any Not a SCALAR and the grep
found nothing at all; as for the rebuild, it's running fine so I tend
to suspect that the issue may be somewhat local to your
setup... which means that you may start by trying to run
Hi,
I don't think this is a local issue. I get the same amount and type of errors,
like dale. Downgrading to 3.1.0.1 for example does not generate these errors.
However it would be great if you could post your Perl module versions, maybe
you are right and is it related to one of the modules
Hi,
I don't think this is a local issue. I get the same amount and type of
errors, like dale. Downgrading to 3.1.0.1 for example does not
generate these errors.
Pascal, don't take it as a personal issue, please, I'm just trying
to be of help; I'm running the latest v2 (.05) and checking the
Worker_3: Not a SCALAR reference at assp.pl line 20526
Grepped the logs to find any Not a SCALAR and the grep
found nothing at all; as for the rebuild, it's running fine so I tend
to suspect that the issue may be somewhat local to your
setup... which means that you may start by trying to
Hi,
I don't think this is a local issue. I get the same amount and type of
errors, like dale. Downgrading to 3.1.0.1 for example does not
generate these errors.
Pascal, don't take it as a personal issue, please, I'm just trying
to be of help; I'm running the latest v2 (.05) and checking
Newer: DB_File: 1.82 instead of you: 1.817
Older: Digest::MD5: 2.39 instead of you: 2.51
Older: Email::MIME::Modifier: 1.905 instead of you: 1.906
Older: Email::Valid: 0.182 instead of you: 0.184
Newer: File::Scan::ClamAV: 1.91 instead of you: 1.8
Older: LWP::Simple: 5.827 instead of you: 5.835
GrayHat Peter,
What are the Perl versions you are using ?
PerlIO::Scalar is part of the Perl distro afaics!
Regards,
Pascal
Op 9 jun 2011, om 16:14 heeft Peter W Bowey het volgende geschreven:
Hi,
I don't think this is a local issue. I get the same amount and type of
errors, like
Newer: DB_File: 1.82 instead of you: 1.817
Older: Digest::MD5: 2.39 instead of you: 2.51
[...]
Just ran a ppm upgrade --install ; I'll be monitoring
logs for messages like the one you are seeing...
till now... none
ASSP_Razor 1.06 / 1.06 (You 1.07 + recommended 1.07)
Yes, sorry, I've
Hi
Here's what I'm running on a Centos VPS (Yes, a vps) :)
Perl Version: 5.010001
ASSP Version: 2.0.2(3.1.05)
Authen::SASL 2.15 / 2.1401
BerkeleyDB 0.42 / 0.42
BerkeleyDB_DBEngine 5.0 / 4.5
Compress::Zlib 2.027 / 2.008
Convert::Scalar 1.04 / 1.04
Afaics it is related to DoDomainCheck, i disabled it right now to see if this
is getting rid of all the messages.
Keep you posted!
Op 9 jun 2011, om 16:27 heeft GrayHat het volgende geschreven:
Newer: DB_File: 1.82 instead of you: 1.817
Older: Digest::MD5: 2.39 instead of you: 2.51
[...]
What are the Perl versions you are using ?
ActivePerl 5.10 in my case; if you want the full details
from perl -v or perl -V just holler
--
EditLive Enterprise is the world's most technically advanced content
GrayHat Peter,
What are the Perl versions you are using ?
Answer:
ASSP version 2.0.2(3.1.05) (Perl 5.012003) (on linux)
Peter
--
EditLive Enterprise is the world's most technically advanced content
authoring
On 2011-06-09 10:44 AM, Peter W Bowey wrote:
(Perl 5.012003)
Ta-da...
--
Best regards,
Charles
--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track
GrayHat Peter,
What are the Perl versions you are using ?
Though Linux perl -v reports this:
This is perl 5, version 12, subversion 3 (v5.12.3) built for
x86_64-linux-thread-multi
The previous email response was what ASSP reports in the log..
Peter
Though Linux perl -v reports this:
This is perl 5, version 12, subversion 3 (v5.12.3) built for
x86_64-linux-thread-multi
This is perl, v5.10.1 built for MSWin32-x86-multi-thread
(with 4 registered patches, see perl -V for more detail)
:)
Well turning off dodomaincheck got rid of all the
error messages so it is related, are you guys
using this ?
in my case, I have (from assp.cfg)
DoDomainCheck:=3
--
EditLive Enterprise is the world's most
Well turning off dodomaincheck got rid of all the
error messages so it is related, are you guys
using this ?
in my case, I have (from assp.cfg)
DoDomainCheck:=3
In my case I also have; DoDomainCheck:=3
Listed as found in; assp.cfg
Peter
Hi
Here's what I'm running on a Centos VPS (Yes, a vps) :)
Perl Version: 5.010001
ASSP Version: 2.0.2(3.1.05)
Authen::SASL 2.15 / 2.1401
BerkeleyDB 0.42 / 0.42
BerkeleyDB_DBEngine 5.0 / 4.5
Compress::Zlib 2.027 / 2.008
Convert::Scalar 1.04 / 1.04
Well turning off dodomaincheck got rid of all the error messages so it is
related, are you guys using this ?
Mvg,
Pascal Dreissen
Op 9 jun. 2011 om 16:52 heeft GrayHat gray...@gmx.net het volgende
geschreven:
Though Linux perl -v reports this:
This is perl 5, version 12, subversion 3
On 2011-06-09 10:44 AM, Peter W Bowey wrote:
(Perl 5.012003)
Maybe you missed my first pointer...
Unless I'm mistaken, perl 5.12 is not supported, so maybe this is your
problem?
--
Best regards,
Charles
--
EditLive
27 matches
Mail list logo
