Yes, the assp code the source of the Perl core and all used modules are much
larger than the source of any Windows kernel.
I was talking about ASSP code, not the Perl core or any standard CPAN modules.
Do you know the source code, the internals, problems, bugs etc. of the Perl
core and all
Fritz, if you don't see it, or you don't know it, or you ignore it - it
doesn't mean that it is not happen!
Don't you find this a chaos? The developer of V1 and the developer of V2 have
different opinions on the code of V1???
Thomas does not recommend running ASSP V1 on Perl below 5.10,
I use ASSP V1 1.9.3.9(1.0.00) on Perl 5.8. without seeing problems.
So, Thomas, please tell me what is wrong with that config and what could
happen. I run this in a production environment. Tell me exactly were are the
conflicts. I have no compile error and therefore my maxim is never touch a
Because you are not able to test older versions I switched to 1.9.2.7 (0.0.00)
to see if whiteRe is working and immediately the best feature ever of ASSP
() which is messagetraps does not work anymore.
Jan-25-12 09:31:59 id-32748-4 [SpoofedSender] 182.185.106.31
Yes it is set! OK, now I see the reason why traps don't work in this case. This
is a pre check.
Thanks for the hint!
Now I try to go back to the current version an see if the whiteRe problem is
gone.
-Ursprüngliche Nachricht-
Von: Fritz Borgstedt [mailto:f...@iworld.de]
Gesendet:
The following mail fragment is considered SPAM because of the URIBL match, but
the message body contains an whiteRe expression which is not processed. The
whole message should therefore be considered white! Assp-Version is
1.9.1.2(0.0.00).
X-Assp-URIBL failed: 'clsmail.de'(black.uribl.com )
What does that mean? Is V1 for home users or students??
I monitor the assp-test list for a long time now. There are definitely more
problems with V2 than with V1. We have a rather small user group and V2,
multithreaded and more resource hungry, is overkill for our mail system. On the
other
Like Brett I would like to know, why there are so many postings on the list
without subject line. Is there a bug in one of the newest releases of ASSP
V1/V2? I'm running on 1.7.5.5(0.0.02). The last postings of Fritz, Thomas and
some other people on the ASSP list have been without subject line.
I missed that version, but it appears to be working like it's supposed to in
newer versions. I'm running 1.7.1.3(0.0.21).
Thanks, I give it a try and installed 1.7.1.3(0.0.22). Quickly running over the
code I don't see a difference regarding that problem, but we will see when this
mail
OK, the processing logic has changed in (0.0.22) and the mail is now handled
correct as was done before (whiteListedDomains/noProcessingDomains are
processed first and if not hit than whiteSenderBase)
Mar-26-10 09:10:06 id-91006-21009 216.34.181.88
assp-test-boun...@lists.sourceforge.net
In ASSP 1.7.1.3(0.0.05) White Org (whiteSenderBase) mail creates a file without
name and only the configured extension in notspam folder (f.e. notspam/.eml)
and the existing .eml-file is permanently overriden.
maillogExt=.eml
DoOrgWhiting=whiting
\bsourceforge\.net in whiteorg.txt
My current assp version is 1.7.1.0(RC 0.3.09)
The whitelisted domain is ignored (envelope from differs from From:-Header)
and delaying is done.
NotGreedyWhitelist is OFF!
Mar-04-10 02:10:33 id-65033-15421 85.114.141.202
anonym...@srv01.lin.level-h.de to: u...@mydomain.com recipient delayed:
I have not checked the code handling delaying, so I was not aware when exactly
it is done.
Thanks
-Ursprüngliche Nachricht-
Von: Fritz Borgstedt [mailto:f...@iworld.de]
Gesendet: Donnerstag, 4. März 2010 12:50
An: ASSP development mailing list
Betreff: Re: [Assp-test] Whitelist check
Thank you for changing your mind,
but there was a small error introduced after changing back.
In the two code lines
} elsif (!$this-{relayok} ( ($spamaddresses
!$this-{nocollect}
matchSL( $u$h,
OK, I installed 1.7.1.0(RC0.0.1) and traps don't work anymore. I made a telnet
smtp session (sender z...@zdata.de) over the internet and tried to send to
in...@ak-funktechnik.de which is in the PBTrapCache and despite that I got the
following log
Feb-24-10 17:02:23 LDAP Results
I cannot understand why this is reported as BombSrcipt spam, because
@klein-klein-verlag.de is a whitelisted domain and therefore should not be
checked against Regex/Bombs
NotGreedyWhitelist, bombReWL, bombReNP, bombReLocal are all OFF!
bombReISPIP is ON but the sender ip 85.114.141.202 is not
I can do that. But before I install 1.7.0.0 I would like to know whether the
PBTrapCache feature has been removed as you planned it for 1.7.1
I use this heavily and I don't want it to go away.
tk
-Ursprüngliche Nachricht-
Von: Fritz Borgstedt [mailto:f...@iworld.de]
Gesendet:
Just tried to install 1.6.5.3 and I could not telnet to the smtp port anymore =
smtp connection lost. Switched back to 1.6.5.0(1.0.02) and everything is OK.
tk
-Ursprüngliche Nachricht-
Von: Fritz Borgstedt [mailto:f...@iworld.de]
Gesendet: Donnerstag, 11. Februar 2010 04:46
An: ASSP
I'm running 1.6.1.4(0.0.06) now and relaying works again, or this mail would
not habe been delivered.
Thanks Fritz!
Thilo
-Ursprüngliche Nachricht-
Von: Fritz Borgstedt [mailto:f...@iworld.de]
Gesendet: Donnerstag, 10. Dezember 2009 20:34
An: ASSP development mailing list
Betreff: Re:
Since the relay code has been changed in 1.6.1.4 my assp proxy (192.168.0.xxx,
assp.mydomain.de) immediately drops the connection to my relayhost
(192.168.0.yyy), which is used for outbound mail. My configuration has not been
changed! See excerpt from smtp log below.
192.168.0.xxx,
Is deny.txt meant as replacement for denyalways.txt (or perhaps as include file
in denyalways.txt???)? Where do these ips come from?
Thilo
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
Just my opinion, it does not make sense to use EmailAdminReportsTo in case
RebuildNotify is empty. For my part I only want to receive internal
warning/info messages but not this report. It is unlucky to combine this.
tk
Then I just wonder why 207.46.22.98 is not there
May-12-09 14:05:24 id-29923-10050 207.46.22.98 cnfrm...@microsoft.com to:
m...@mydomain.com
recipient delayed: m...@mydomain.com
PBWhiteBox:
206.165.243.1351240384982 1240384982 2
207.46.248.401219239376 1240410488 2
Delaying is the fist step in the process, I see it it as unwise to do a dsn -
based query in this early step.
Yes, if I think that over, you are right, because of performance reasons.
Albeit that check would help from loosing not repeated messages. Delaying is a
good thing, so I don't want to
I'm currently running the latest ASSP V1 (1.5.1.2(3.1.02))
I have set EnableDelaying to on and DoOrgWhiting to whiting.
Despite the sender IPs domain/organization is in whiteSenderBase, it will be
delayed. Is that wanted? There is no option similar to DelayWL for whitelisted
sender/domains to
Just a very small cosmetic issue in 3.0.02 INET6 support is not logged anymore.
} else {
$CommentIOSocketINET6 = IPv6 support not available;
$CanUseIOSocketINET6 = 0;
}
mlog( 0, $CommentIOSocketSSL );
mlog( 0, $CommentIOSocketINET6 ); = missing
tk
Ups, my code suggestion
was wrong because the unary operator ! has a higher binding, sorry!
sub pbTrapAdd {
return if !$DoPenaltyMakeTraps !$UseTrapToCollect;
return if $DoPenaltyMakeTraps == 3;
in 1.5.1.2 (2.1.01) is now correct
Sorry again
But the list still is
Just as said multi times before, I'm not a PERL programmer (and hopefully I'm
not wrong) but
['DoPenaltyMakeTraps','Do Heavy Used Invalid Addresses as PenaltyBox Trap
Addresses','0:disabled|1:make traps and use them|2:just make traps|2:use these
traps',\listbox,2,'(.*)',undef,
in combination
Just went from 1.5.1.2 (1.1.09) to 1.5.1.2 (1.2.0) and got SMTP local
configuration error message. I have IO::Socket::INET6 2.55 installed, so INET6
support was not available in the past and therefore made no problems at all.
With 1.2.0 I got 451 4.7.1 Local configuration error, please try
The bug, that came back, was not related to this new feature.
I know that the bug is not related to the email notification feature and yes,
knowbody is perfect. I just commented on that because of Fritzs posting to
1.5.1.2(1.1.11) info notification error:
Because there is a bug. You may load
The last really stable version for me was 1.5.1.2(1.0.07). As I switched to
1.5.1.2(1.1.03) or 1.5.1.2(1.1.05) (can't blame one of them exactly because I
updated them within a short period) I too get:
Apr-29-09 15:32:37 Error: orderedtie is unable to delete
d:/assp/pb/pbdb.black.db -
Thank you for information,
I planed to install 0.95.1 today, but alerted from your warning I will leave my
hands off this. As I mentioned in my last post, I did a manual upgrade to
File::Scan::ClamAV 1.91 last week but still use clamd 0.94. This seems to work,
at least until today. As you are
Thank you!
I finally could install 1.91 with your help!! :)
ASSP now says: File::Scan::ClamAV module version 1.91 installed and available
I will watch what 1.91 does for a couple of days before I upgrade ClamAV to
95.1
The only thing what makes me nervous is that nmake test gives the
How did you install it on win32? I downloaded it from your given link, unpacked
the whole stuff using winzip, and tried to do
nmake makefile.pl
from the download directory which gives
Cannot find clamd in /bin (or a number of other places)
- are you sure clamav in installed?
clamd.exe is
Could someone please confirm that this new port works with File::Scan::ClamAV
1.8
There already has been a discussion on this list at the end of march which
clearly showed that the library of File::Scan::ClamAV has problems with 0.95.
I just want to be sure before I change my production
I found this in the newly added code of sub BlockReportBody in 1.13:
this-{mailfrom}) if $ReportLog;
Ê Ê Ê Ê Ê Ê Ê Ê Ê Ê mlog( 0,warning: at least one line 'us...@domain=to' must
be in body for an admin request) if $ReportLog;
Ê Ê Ê Ê Ê Ê Ê Ê Ê Ê my ($numdays) = $sub =~ /^\s*(\d+)\s*/;
Ê Ê Ê
I'm using Version 1.8 of File::Scan::ClamAV on Win32. Now I am alerted from
your post. The trouchelle repository only offers this version. My freshclam log
urges me to update to 0.95. Does anyone have problems with 0.95 of ClamAV on
Windows and the 1.8 Perl package of File::Scan::ClamAV or is
Trying to run 2.5.1.1 (0.00.0) with Perl 5.008009 gives
Global symbol $filesize requires explicit package name at rebuildspamdb.pl
line 1110.
BEGIN not safe after errors--compilation aborted at rebuildspamdb.pl line 1203.
2.5.1.0 (0.01.0) is ok.
tk
The same here with 1.5.1(1.05).
Mar-24-09 11:05:58 LDAP Results
((|((objectCategory=person)(objectClass=user))(objectClass=
publicFolder))(proxyAddresses=SMTP:iamjustsendingthisle...@ak-funktechnik.de)):
0 :
Mar-24-09 11:05:58 id-89157-23365
The *real* question is: did you understand what the DoPenaltyMakeTraps does
? Apparently, ad least judging
from your question, you didn't and you didn't even read the help text...
I know what it does, and it was not a real question. It was meant rhetorical.
Sorry if that was not clear. You
Fritz Borgstedt wrote:
I cannnot see that from the log. I only see, that the trap is not working
(which is fixed meanwhile).
Traps are looked up before addresscheck.
RTFM:Lies das verdammte Manual
Just installed 1.5.1.0(1.07), problem gone, traps a working again.
You are right, the logs only
Sorry, I'm not a Perl expert, but if $maillogExt is blank
if (/(.*)($base\/($spamlog\/[^\n]+$maillogExt))/) {
my $text = $1;
$text = logWrap( $text, $indent );
.
next;
}
and the following if clauses seem to be false, resulting in none wraped log
lines.
I checked this by setting
Since I've installed ASSP 1.3.5(20.5) Mail::SPF throws EOptionRequired Exception
Apr-7-08 15:17:09 [scoring] (Message-ID suspicious: '')
Apr-7-08 15:17:09 SPF2OK: Missing required 'identity' option (EOptionRequired)
at C:/Perl/site/lib/Mail/SPF/Request.pm line 257.
Can someone else confirm
43 matches
Mail list logo
