Anti-Spam SMTP Proxy Server

SF has removed the small attachment - here is the script:

#!/usr/local/bin/perl

 use strict;
 use IO::Socket;

 my $nachricht;
 my $file="maillog.txt";
 my $azeilen=0;
 my $i=0;
 my @zeilen;
 my $a;
 my $port;
 my $sl;

open F, "<assp.cfg" or die "unable to find assp.cfg";
@zeilen=<F>;
close F;

foreach $a (@zeilen) {
  ($sl,$port) = split("=",$a) if ($a =~ /sysLogPort/);
}

die "sysLogPort in assp.cfg not found" if (!$port);

if (open F, "<$file") {
  @zeilen=<F>;
  close F;
  $azeilen=@zeilen;
  $i = $azeilen - 60;
  $i = 0 if ($i < 0);
  for ($a=$i;$a<$azeilen;$a++) {
   print @zeilen[$a];
  }
}

 my $socket = IO::Socket::INET->new(
   Proto => "udp",
   LocalPort => $port,
   ReuseAddr => 1,
 )
 or die "problem: $!";

 while ($socket->recv($nachricht, 1024)) {
   chomp($nachricht);
   my $m=localtime();
   $m=~s/^... (...) +(\d+) (\S+) ..(..)/$1-$2-$4 $3/;
   $nachricht =~ s/^\<.*\]\: //;
   print "$m $nachricht\n";
 }




Thomas

DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

RC01.02 is acting strange on quit:

mbppdreissen:~ pdreissen$ telnet cp.domain.nl 25
Trying xx.xxx.xx.xxx...
Connected to cp.domain.nl.
Escape character is '^]'.
220 lnxmail01.domain.nl ESMTP
helo pc1.domain.nl
250 lnxmail01.domain.nl
mail from: pascal@...
250 ok
rcpt to: pascal@...
250 ok
data
354 go ahead
Subject: Test

test
test
.
250 ok 1241112665 qp 26725
quit
221 lnxmail01.domain.nl

554 5.7.1 Misbehaved SMTP session (EarlyTalker)
421 <nospam4us01.domain.nl> closing transmission channel
Connection closed by foreign host.
mbppdreissen:~ pdreissen$



Op 30 apr 2009, om 17:35 heeft Thomas Eckardt/eck het volgende  
geschreven:

>> Thomas, was there not an option
>> to change the method that ASSP used to write to log files?
>
> No.
>
>> I logged in and ran a "tail" app on the log file,
>
> very bad idea on windows. Better use syslog. If you do not have a  
> syslog
> server take the following script assp_monitor.pl - it is functioning  
> like
> a syslog server.
> It looks in to assp.cfg searching for the syslog-Port, reading the  
> last 60
> lines in maillog.txt and print them to screen and starts a UDP- 
> listener.
> Start it inside the assp directory.
>
>
>
> Thomas
>
>
>
>
>
> Scott MacLean <assp@...>
> 30.04.2009 17:06
> Bitte antworten an
> ASSP development mailing list <assp-test@...>
>
>
> An
> ASSP development mailing list <assp-test@...>
> Kopie
>
> Thema
> Re: [Assp-test] Antwort: Re:  Something has gone very wrong, RC22+?
>
>
>
>
>
>
> While looking at my logs, I have a feeling I might have stumbled upon
> a cause. I don't know this for certain, but it certainly makes sense
> more than anything else I can come up with.
>
> When I got the original call that the mail server was not behaving
> properly, I logged in and ran a "tail" app on the log file, so I
> could watch what was happening, and identify when it had locked up.
> This has never affected anything before. However, as the logfile grew
> in size, the lockups became more and more frequent. Near the end of
> the day, when the logfile was 170+ megabytes, ASSP would lockup
> within seconds after it was started.
>
> The logfile did not roll at midnight, I assume because ASSP was
> locked up at the time it should have rolled it. I noticed this and
> rolled it myself manually, well after midnight. Shortly thereafter,
> ASSP suddenly became stable again - well, for the most part - it was
> more stable, shall we say. It was near 1 am, and I didn't connect the
> two. I gave up, logged out (which shut down the tail app) and ASSP
> ran without a hitch for the most part for the rest of the night.
>
> I wonder if the large log, along with the tail app accessing the
> file, is causing some sort of file contention with ASSP doing its log
> writing, which causes it to lock up? Thomas, was there not an option
> to change the method that ASSP used to write to log files?
>
> At 09:33 AM 4/30/2009, Thomas Eckardt/eck wrote:
>
>> Scott,
>>
>> I was looking in to the log I've got from you (last night / this  
>> morning)
>> - there was no possible reason to find. But one thing is realy hard -
> your
>> system got on startup up to 15 (or even more) connections within 1  
>> second
>> - this results in a dayly rate of 1.3 million connections per day.  
>> I dont
>> believe that ASSP can do that. And I do not know anyone, who can
> reproduce
>> this.
>>
>> Thomas
>>
>>
>>
>>
>> Scott MacLean <assp@...>
>> 30.04.2009 14:36
>> Bitte antworten an
>> ASSP development mailing list <assp-test@...>
>>
>>
>> An
>> ASSP development mailing list <assp-test@...>
>> Kopie
>>
>> Thema
>> Re: [Assp-test] Something has gone very wrong, RC22+?
>>
>>
>>
>>
>>
>>
>> Well my system has inexplicably become stable once more. It was
>> locking up every 30-45 seconds until 12:56 am, then it ran until 1:08
>> am, then until 3:09 am, and has been up since then with no problems -
>> that's 5 1/2 hours now.
>>
>> I'm just shaking my head at this point.
>>
>> At 02:39 AM 4/30/2009, Victor wrote:
>>
>>> Hi!
>>>
>>>> ASSP locking up every few minutes.
>>>> have no idea why.
>>>
>>> Please, see by Process Monitor ( it's include FileMon functionality
>>> ), what last file has read by perl.exe ( i.e. ASSP)
>>> And try temporary remove/rename this file.
>>>
>>> Best regards, Victor Miasnikov
>>> SysAdmin System Technologies
>>>
>>> P.S.   At me last versions of ASSP v2.X  work very well:
>>>
>>> ASSP v2.0.1(RC 0.0.25) 15 hours 50 mins since restart  ( and run at
> this
>> time)
>>>
>>> ASSP v2.0.1(RC 0.0.13) 5 days 23 hours 46 mins 54 secs since restart
>>>
>>>
>>> Thanks Thomas Eckardt
>> ------------------------------------------------------------------------------
>> Register Now & Save for Velocity, the Web Performance & Operations
>> Conference from O'Reilly Media. Velocity features a full day of
>> expert-led, hands-on workshops and two days of sessions from industry
>> leaders in dedicated Performance & Operations tracks. Use code  
>> vel09scf
>> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
>> _______________________________________________
>> Assp-test mailing list
>> Assp-test@...
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>
>>
>>
>>
>> DISCLAIMER:
>> *******************************************************
>> This email and any files transmitted with it may be confidential,  
>> legally
>> privileged and protected in law and are intended solely for the use  
>> of
> the
>>
>> individual to whom it is addressed.
>> This email was multiple times scanned for viruses. There should be no
>> known virus in this email!
>> *******************************************************
>>
>> ------------------------------------------------------------------------------
>> Register Now & Save for Velocity, the Web Performance & Operations
>> Conference from O'Reilly Media. Velocity features a full day of
>> expert-led, hands-on workshops and two days of sessions from industry
>> leaders in dedicated Performance & Operations tracks. Use code  
>> vel09scf
>> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
>> _______________________________________________
>> Assp-test mailing list
>> Assp-test@...
>> https://lists.sourceforge.net/lists/listinfo/assp-test
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code  
> vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
>
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential,  
> legally
> privileged and protected in law and are intended solely for the use  
> of the
>
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> *******************************************************
>
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code  
> vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf_______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test

Met vriendelijke groet / Best regards,

Pascal Dreissen

Virus
Inside
Switch
To
Apple

>421 <nospam4us01.domain.nl> closing transmission channel

This is fixed in 2.0.1_RC0.1.04

Thomas




Pascal Dreissen <pascal@...> 
30.04.2009 19:37
Bitte antworten an
ASSP development mailing list <assp-test@...>


An
ASSP development mailing list <assp-test@...>
Kopie

Thema
Re: [Assp-test] Antwort: Re: Antwort: Re: Something has gone very wrong, 
RC22+?






RC01.02 is acting strange on quit:

mbppdreissen:~ pdreissen$ telnet cp.domain.nl 25
Trying xx.xxx.xx.xxx...
Connected to cp.domain.nl.
Escape character is '^]'.
220 lnxmail01.domain.nl ESMTP
helo pc1.domain.nl
250 lnxmail01.domain.nl
mail from: pascal@...
250 ok
rcpt to: pascal@...
250 ok
data
354 go ahead
Subject: Test

test
test
.
250 ok 1241112665 qp 26725
quit
221 lnxmail01.domain.nl

554 5.7.1 Misbehaved SMTP session (EarlyTalker)
421 <nospam4us01.domain.nl> closing transmission channel
Connection closed by foreign host.
mbppdreissen:~ pdreissen$



Op 30 apr 2009, om 17:35 heeft Thomas Eckardt/eck het volgende 
geschreven:

>> Thomas, was there not an option
>> to change the method that ASSP used to write to log files?
>
> No.
>
>> I logged in and ran a "tail" app on the log file,
>
> very bad idea on windows. Better use syslog. If you do not have a 
> syslog
> server take the following script assp_monitor.pl - it is functioning 
> like
> a syslog server.
> It looks in to assp.cfg searching for the syslog-Port, reading the 
> last 60
> lines in maillog.txt and print them to screen and starts a UDP- 
> listener.
> Start it inside the assp directory.
>
>
>
> Thomas
>
>
>
>
>
> Scott MacLean <assp@...>
> 30.04.2009 17:06
> Bitte antworten an
> ASSP development mailing list <assp-test@...>
>
>
> An
> ASSP development mailing list <assp-test@...>
> Kopie
>
> Thema
> Re: [Assp-test] Antwort: Re:  Something has gone very wrong, RC22+?
>
>
>
>
>
>
> While looking at my logs, I have a feeling I might have stumbled upon
> a cause. I don't know this for certain, but it certainly makes sense
> more than anything else I can come up with.
>
> When I got the original call that the mail server was not behaving
> properly, I logged in and ran a "tail" app on the log file, so I
> could watch what was happening, and identify when it had locked up.
> This has never affected anything before. However, as the logfile grew
> in size, the lockups became more and more frequent. Near the end of
> the day, when the logfile was 170+ megabytes, ASSP would lockup
> within seconds after it was started.
>
> The logfile did not roll at midnight, I assume because ASSP was
> locked up at the time it should have rolled it. I noticed this and
> rolled it myself manually, well after midnight. Shortly thereafter,
> ASSP suddenly became stable again - well, for the most part - it was
> more stable, shall we say. It was near 1 am, and I didn't connect the
> two. I gave up, logged out (which shut down the tail app) and ASSP
> ran without a hitch for the most part for the rest of the night.
>
> I wonder if the large log, along with the tail app accessing the
> file, is causing some sort of file contention with ASSP doing its log
> writing, which causes it to lock up? Thomas, was there not an option
> to change the method that ASSP used to write to log files?
>
> At 09:33 AM 4/30/2009, Thomas Eckardt/eck wrote:
>
>> Scott,
>>
>> I was looking in to the log I've got from you (last night / this 
>> morning)
>> - there was no possible reason to find. But one thing is realy hard -
> your
>> system got on startup up to 15 (or even more) connections within 1 
>> second
>> - this results in a dayly rate of 1.3 million connections per day. 
>> I dont
>> believe that ASSP can do that. And I do not know anyone, who can
> reproduce
>> this.
>>
>> Thomas
>>
>>
>>
>>
>> Scott MacLean <assp@...>
>> 30.04.2009 14:36
>> Bitte antworten an
>> ASSP development mailing list <assp-test@...>
>>
>>
>> An
>> ASSP development mailing list <assp-test@...>
>> Kopie
>>
>> Thema
>> Re: [Assp-test] Something has gone very wrong, RC22+?
>>
>>
>>
>>
>>
>>
>> Well my system has inexplicably become stable once more. It was
>> locking up every 30-45 seconds until 12:56 am, then it ran until 1:08
>> am, then until 3:09 am, and has been up since then with no problems -
>> that's 5 1/2 hours now.
>>
>> I'm just shaking my head at this point.
>>
>> At 02:39 AM 4/30/2009, Victor wrote:
>>
>>> Hi!
>>>
>>>> ASSP locking up every few minutes.
>>>> have no idea why.
>>>
>>> Please, see by Process Monitor ( it's include FileMon functionality
>>> ), what last file has read by perl.exe ( i.e. ASSP)
>>> And try temporary remove/rename this file.
>>>
>>> Best regards, Victor Miasnikov
>>> SysAdmin System Technologies
>>>
>>> P.S.   At me last versions of ASSP v2.X  work very well:
>>>
>>> ASSP v2.0.1(RC 0.0.25) 15 hours 50 mins since restart  ( and run at
> this
>> time)
>>>
>>> ASSP v2.0.1(RC 0.0.13) 5 days 23 hours 46 mins 54 secs since restart
>>>
>>>
>>> Thanks Thomas Eckardt
>> 
------------------------------------------------------------------------------
>> Register Now & Save for Velocity, the Web Performance & Operations
>> Conference from O'Reilly Media. Velocity features a full day of
>> expert-led, hands-on workshops and two days of sessions from industry
>> leaders in dedicated Performance & Operations tracks. Use code 
>> vel09scf
>> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
>> _______________________________________________
>> Assp-test mailing list
>> Assp-test@...
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>
>>
>>
>>
>> DISCLAIMER:
>> *******************************************************
>> This email and any files transmitted with it may be confidential, 
>> legally
>> privileged and protected in law and are intended solely for the use 
>> of
> the
>>
>> individual to whom it is addressed.
>> This email was multiple times scanned for viruses. There should be no
>> known virus in this email!
>> *******************************************************
>>
>> 
------------------------------------------------------------------------------
>> Register Now & Save for Velocity, the Web Performance & Operations
>> Conference from O'Reilly Media. Velocity features a full day of
>> expert-led, hands-on workshops and two days of sessions from industry
>> leaders in dedicated Performance & Operations tracks. Use code 
>> vel09scf
>> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
>> _______________________________________________
>> Assp-test mailing list
>> Assp-test@...
>> https://lists.sourceforge.net/lists/listinfo/assp-test
> 
------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code 
> vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
>
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential, 
> legally
> privileged and protected in law and are intended solely for the use 
> of the
>
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> *******************************************************
>
> 
------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code 
> vel09scf
> and Save an extra 15% before 5/3. 
http://p.sf.net/sfu/velocityconf_______________________________________________

> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test

Met vriendelijke groet / Best regards,

Pascal Dreissen

Virus
Inside
Switch
To
Apple






------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Assp-test mailing list
Assp-test@...
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

Nor for me.

After upgrading to 1.5.1.2(1.1.12) it has started again!

pr-30-09 11:56:59 PenaltyBox: cleaning BlackBox finished; IP's before=165, deleted=75
Apr-30-09 11:56:59 Error: orderedtie is unable to delete c:/assp/pb/pbdb.black.db - Permission
                   denied



Peter

Peter Ingham wrote:
> Yesterday I ran 1.5.1.2(1.1.09) (with antivirus resident shield not checking 
> c:\assp) which checked for file permissions on startup, no problems found.
> 
> No problems with BlackBox and Whitebox, but others failed:
> 




Well it can't be the virus scanning, at least not in my case. I'm not 
running any.


------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Assp-test mailing list
Assp-test@...
https://lists.sourceforge.net/lists/listinfo/assp-test



Disclaimer: The information in this e-mail is confidential and may be legally privileged. Its contents including any file attachments are intended for the above named addressee(s) only. If you are not (or suspect that you are not) the correct recipient please contact us immediately on 01423 322706, ask for the sender and then delete the e-mail from your computer system and destroy any hard copies you have made.  You must not otherwise use, forward it or copy it or act upon its contents. Please note that we cannot guarantee that this message or any attachment is virus free nor that it has not been intercepted or amended. Internet communications are not secure and therefore A-One Feed Supplements Ltd does not accept legal responsibility for the contents of this message and / or attachments. 
Any views or opinions presented are solely those of the author and do not necessarily represent those of A-One Feed Supplements Ltd unless otherwise specifically stated.

A-One Feed Supplements Ltd. 
Registered Office: North Hill, Dishforth Airfield,THIRSK, North  Yorkshire.  YO7 3DH

Registered in England No. 120 7930   VAT No. GB 171 8557 42

Hill, Brett wrote:
> 
> Just an FYI.  Everything appears to be working like it's supposed to.
> 

I think a possible reason why there aren't more people complaining about
this is that it is hard to notice unless you are specifically researching a
problem.  For two years of running ASSP I never really manually checked the
size of the Penalty box, and turned off Penalty logging altogether.

First of all, thanks for everyone already working on this. There is always
the fear when you "Google" something that you are the only one in the world
with the problem.  I appreciate everyones groundwork on this already.

I had a valid MTA-IP get placed in the penaltybox.  Whitelisting the domain
(whiteListDomains) and marking the IP address as no-pentalitybox (noPB)
never removed the associated IP address.  This is when I noticed the cleanup
file "pbdb.black.db.tmp" never replaced the active "pbdb.black.db".  I was
only able to remove the offending IP address by wiping out the entire PB
directory and letting it rebuild itself from scratch. 

>From there the whole "never cleaning up" restarts from the beginning:
Apr-30-09 01:33:48 Cleaning up penalty records ...
Apr-30-09 01:33:49 PenaltyBox: cleaning BlackBox finished; IP's before=429,
deleted=157
Apr-30-09 01:33:49 PenaltyBox: cleaning WhiteBox finished; IP's before=35,
deleted=0
Apr-30-09 01:33:49 PBTrap: cleaning finished; before=47, deleted=0
Apr-30-09 04:33:48 Cleaning up penalty records ...
Apr-30-09 04:33:49 PenaltyBox: cleaning BlackBox finished; IP's before=546,
deleted=200
Apr-30-09 04:33:49 PenaltyBox: cleaning WhiteBox finished; IP's before=42,
deleted=0
Apr-30-09 04:33:49 PBTrap: cleaning finished; before=50, deleted=0
Apr-30-09 07:33:49 Cleaning up penalty records ...
Apr-30-09 07:33:50 PenaltyBox: cleaning BlackBox finished; IP's before=673,
deleted=248
Apr-30-09 07:33:50 PenaltyBox: cleaning WhiteBox finished; IP's before=47,
deleted=0
Apr-30-09 07:33:50 PBTrap: cleaning finished; before=55, deleted=0
...and so on...

My Setup:
ASSP 1.5.1.1(1.0.04)
Windows 2003 Server - Fully Patched
ActiveState Perl 5.8.9
No Antivirus
Permissions granted to everyone on all ASSP sub directories (yup it sucks)
MaintenanceLog set to Verbose
Ran ASSP since 1.2.6 (2 Years with no problems) - Same box
Upgraded ASSP two weeks ago (when problems began)

One thing I noticed is that I am not receiving a lock-file error in my log
files.  Is this verbose logging error exclusive to those running 1.5.1.2?   


-- 
View this message in context: http://www.nabble.com/About-the-penaltybox-cleanup-tp23212830p23322173.html
Sent from the assp-test mailing list archive at Nabble.com.

on linux too , resend now works (even if I receive the resend after 
about 5 minutes).
> I'll keep an eye on it.
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations 
> Conference from O'Reilly Media. Velocity features a full day of 
> expert-led, hands-on workshops and two days of sessions from industry 
> leaders in dedicated Performance & Operations tracks. Use code vel09scf 
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>

for me it simply does not resend , the error is not created at all
I tested also (1.2.01) .

Graziano
> ASSP development mailing list <assp-test@...>
> schreibt:
>   
>> I continued to have resend issues with 1.5.1.2 with all kinds of
>> resend errors showing up in the log. 
>>     
>
>
> Please send me the "all kinds of errors"
>
>
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations 
> Conference from O'Reilly Media. Velocity features a full day of 
> expert-led, hands-on workshops and two days of sessions from industry 
> leaders in dedicated Performance & Operations tracks. Use code vel09scf 
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>

I do not think this is a permissions problem, since the file is newly created and thus inherites all permissions from the folder in which it resides. If there would be a problem, the other files in there would have the same problem.

Another reason could be too long path/filenames. However, in your case, where you installed to C:\ASSP, this should neither be the reason for your problems.

I did not follow all of this thread, but did you ever check if this file is simply being kept open by another process/user?
Not only virus scanners keep files open, but also backup software shadow copy, other logged on users, external applications etc.

Henning Hildebrand
RIBE IT

>>> Paul Houlbrooke <duke16@...> 30.04.2009 16:21 >>>
OS: Windows 2003, NTFS
User Account : Administrator
Service : SYSTEM

No Group Policies
No new events are generated in the Event Log at the time of the error in 
ASSP
Only 1 account, Administrator (which is under the Administrators group)
The SYSTEM account is not apart of the Administrators group

I can't login as SYSTEM. But the SYSTEM account has the same privileges 
to the assp folder that the Administrator account has, and I can delete, 
create, etc with that account.

I really don't think this is a problem with my permissions. All the 
other files in the pb folder are fine, only the pbdb.black.db file 
generates the error. I'm assuming all the other files are getting the 
same treatment as the pbdblack.db file.

Thomas Eckardt/eck wrote:
> 
> Hi Paul,
> 
> it is a realy long thread - so let us start again.
> 
> first some info for me:
> 
> OS: W2K / W2K3 / XP
> filesystem: NTFS
> useraccount that has done the install of ASSP (owner of the files):  ?
> useraccount that is used to run ASSP (runuser):  ?
> 
> Are there any GroupPolicies that could prevent users /admins to delete 
> files in the assp dir?:
> Could you see any entries in the SecurityEventLog related to the user 
> that is running assp?:
> 
> are both accounts local Adminstators? at least the user that is running 
> assp (runuser) should be local Administrator or the System account:
> 
> - logon as the user (runuser), go to ....assp/pb, open a cmd prompt, try 
> to create (no copy of existing - use >copy con filename - end with ^Z), 
> rename and delete a file   -  is this possible ?
> - yes : so you should have no problem - stop here and forget it
> - no : check (set) the permission of the created file - click on 
> advanced to show all permissions (post this if you not sure)
> - if you have installed assp on the systemdrive - make a backup (of your 
> choice) of your system drive (incl. Systemstate) - create the recovery 
> disks (you should already have them) , hope that you'll never need them. 
> It could be possible, that any filesystem backup will fail, if some 
> security hives in MFT are destroyed. So only an image-backup will realy 
> help.
> - if all permissions are like expected (everyone - full , is not a right 
> setting), run >chkdsk drive: /F   - answer with yes to all questions (if 
> some) and restart the system if required
> - chkdsk should now run on startup - part 3 of the chkdsk is the check 
> of the security hives in the filesystem (MFT) - are there any errors 
> reported?
> 
> Try again to copy, rename and delete (as runuser) - now it should be 
> successfull.
> 
> - check and set all Permissions for all files inside ASSP to right 
> values,  and start assp in console mode
> - set some (or all) cleaning intervals (cleanPBInterval....) in GUI to 
> low values to force the flush in orderedtie
> 
> The error should be gone.
> 
> Thomas
> 
> 
> 
> *Paul Houlbrooke <duke16@...>*
> 
> 30.04.2009 14:24
> Bitte antworten an
> ASSP development mailing list <assp-test@...>
> 
> 
> 	
> An
> 	ASSP development mailing list <assp-test@...>
> Kopie
> 	
> Thema
> 	Re: [Assp-test] About the penaltybox cleanup
> 
> 
> 	
> 
> 
> 
> 
> 
> Peter Ingham wrote:
>  > Yesterday I ran 1.5.1.2(1.1.09) (with antivirus resident shield not 
> checking
>  > c:\assp) which checked for file permissions on startup, no problems 
> found.
>  >
>  > No problems with BlackBox and Whitebox, but others failed:
>  >
>  > "Apr-29-09 06:25:50 PenaltyBox: cleaning BlackBox finished; IP's 
> before=113,
>  > deleted=18
>  > Apr-29-09 06:25:50 PenaltyBox: cleaning WhiteBox finished; IP's 
> before=361,
>  > deleted=1
>  >
>  > Apr-29-09 07:25:48 Error: orderedtie is unable to delete
>  > c:/assp/pb/pbdb.uribl.db - Permission denied
>  > Apr-29-09 07:25:48 Error: orderedtie is unable to rename
>  > c:/assp/pb/pbdb.uribl.db.tmp to c:/assp/pb/pbdb.uribl.db - Permission
>  > denied"
>  >
>  > Stopped ASSP and deleted all files in "pb" that had a problem, restarted
>  > ASSP.
>  >
>  > All cache files showed no errors from orderedtie for the rest of the day.
>  >
>  > Thanks for all help.
>  >
>  > Peter Ingham
>  >
> 
> 
> 
> Well it can't be the virus scanning, at least not in my case. I'm not
> running any.
> 
> 
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf 
> _______________________________________________
> Assp-test mailing list
> Assp-test@... 
> https://lists.sourceforge.net/lists/listinfo/assp-test 
> 
> 
> 
> 
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential, 
> legally privileged and protected in law and are intended solely for the 
> use of the
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no 
> known virus in this email!
> *******************************************************
> 


------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf 
_______________________________________________
Assp-test mailing list
Assp-test@... 
https://lists.sourceforge.net/lists/listinfo/assp-test

This is, I can delete the file just fine manually. So, I don't think any 
other processes (besides ASSP), are accessing the file.

Henning Hildebrand wrote:
> I do not think this is a permissions problem, since the file is newly created and thus inherites all permissions from the folder in which it resides. If there would be a problem, the other files in there would have the same problem.
> 
> Another reason could be too long path/filenames. However, in your case, where you installed to C:\ASSP, this should neither be the reason for your problems.
> 
> I did not follow all of this thread, but did you ever check if this file is simply being kept open by another process/user?
> Not only virus scanners keep files open, but also backup software shadow copy, other logged on users, external applications etc.
> 
> Henning Hildebrand
> RIBE IT
> 
>>>> Paul Houlbrooke <duke16@...> 30.04.2009 16:21 >>>

> Reverted back to 1.0.07 and the permission denied errors are gone.

not gone, they just are NOT logged, but there are STILL there :P

> I do not think this is a permissions problem, since the file is
> newly created and thus inherites all permissions from the folder
> in which it resides. If there would be a problem, the other files in
> there would have the same problem.

I suspect the same, and imVVHo it's ASSP itself (or some perl
code inside one of the modules used by ASSP) which is keeping
the file "in use"

> Another reason could be too long path/filenames.

not my case, the path is "c:/assp/pb" so there's no problem for
that, also, if paths were the cause then the code shouldn't be able
to create the "tmp" files :)

> I did not follow all of this thread, but did you ever check if this
file
> is simply being kept open by another process/user?

ASSP seems to be the only process keeping it open

> Not only virus scanners keep files open, but also backup software

nothing in my case, no AV scanner, backup or shadow copy and
the permissions are fully ok, so, again, I tend to suspect that the
issue
may be either sitting inside ASSP or inside one of the file I/O modules
used; I suspect (not sure btw, just shooting in the dark) that
"buffering"
may play a role here; let's say ASSP closes a handle; the "close"
call immediately returns, but the underlying perl runtime starts
flushing
the file... at the same time ASSP tries to delete the file... and such
an
operation fails... maybe I'm wrong, again, it's just an idea

Also... another /strange/ thing I noticed is that, while the "tmp" files
are left in place due to those errors, if I stop and then restart ASSP
they disappear

ASSP development mailing list <assp-test@...>
schreibt:
>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:

We put the error messages in. Before that, same happened without
logging.

ASSP development mailing list <assp-test@...>
schreibt:
>I do not think this is a permissions problem, since the file is newly
>created and thus inherites all permissions from the folder in which
>it resides. If there would be a problem, the other files in there
>would have the same problem.

But all files in that folder (PB) have the problem.

> Also... another /strange/ thing I noticed is that, while the "tmp"
files
> are left in place due to those errors, if I stop and then restart ASSP
> they disappear

just in case, they seem to be wiped when assp stops, so I think
that it may definitely be ASSP which is keeping those files opened

I'm running Windows 2003 Server with Perl 5.10 and ASSP 1.5.1.2(1.1.10).
I'm not experiencing these penaltybox file problems (nor have I
experienced them in the past).  Just an FYI.  Everything appears to be
working like it's supposed to.

Kind Regards,
Brett