date:20120424

[Assp-test] Antwort: Re: Antwort: V2 spamdb problems?

2012-04-24 Thread Thomas Eckardt

Scott,

build 12116 should solve the problem anyway. I had a look in to the zip - 
thank you . Exactly like I assumed - all of the mails contain one or more 
wrong MIME encodings like 

Subject: mi...@interspancanada.comä¼ä¸šè®²åº§ è¯šé‚€æ‚¨çš„å…‰ä¸´

Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: 7bit
.
å›½/ç²¾/è‹±/åŸ¹

These wrong encodings together with a too weak EmailDomain regex and the 
resulting 'not allowed' call to 'Digest::MD5' with unicode characters >255 
(wide) caused the problem.

Thomas

Von:Scott MacLean 
An: ASSP development mailing list 
Datum:  24.04.2012 21:04
Betreff:Re: [Assp-test] Antwort:  V2 spamdb problems?

Hi Thomas,

I did as you suggested. Each time the rebuild failed, I took the last 
file written to the rebuilddebug.txt file, and moved it from the spam 
directory to another directory. Then I restarted the rebuild.

I did this four times, and after removing the fourth file, the 
rebuild got past processing the spam files...but then failed while 
processing notspam. I repeated the process, removing the notspam 
files that were causing the rebuild failure until the process 
completed successfully.

I had a look through all of the files causing the problems - and I 
really don't see any common features between them all - no common 
IPs, senders, subjects or content.

Interestingly enough, some of the files that were causing the failure 
were almost two weeks old - and it's only been the last few days that 
the rebuild has started to fail. These files were not causing the 
failure previously. More importantly - well after I had gotten the 
process to complete the spam rebuild, and was working on identifying 
the bad messages in notspam, it suddenly started failing in the spam 
rebuild again. The message in the spam rebuild it suddenly started 
failing on was three days old. This message had passed with no 
problem on the previous eight rebuilddb attempts, and suddenly caused 
it to fail. Obviously something changed, and the only thing I can 
think of that changed is the contents of spamdb. So I suspect it's a 
combination of the content of the emails, along with data that is 
stored in the spamdb database that is causing the problem.

I've sent you copies of the emails that were causing the problems, 
along with the spamdb export of my system.

At 10:25 AM 4/24/2012, Thomas Eckardt wrote:

>Scott,
>
>create a file 'rebuilddebug.txt' in the assp root folder. You can do that
>using the GUI - at the bottom of the rebuild section - store an empty
>file!
>Once this file exists, start the rebuild. If that crashes - look in to
>that debug file - it will show the name of the message file, that was 
last
>accessed at the last line. The rebuild processes the files by the
>time/date - starting with the youngest. It could be possible that the 
file
>name of the bad file was still not written to the debug output !!!
>Move that file away - zip it - send it to me.
>
>Analyze the file for sender , IP, subject, content  - try to 
indentify
>(possibly  block) similar mails (preHeaderRe) - ot at least use
>noCollecting and/or noCollectRe to prevent assp from collecting such
>mails.
>Remove all similar files from the corpus - restart the rebuild - possibly
>repeat that procedure.
>
>DO NOT analyze this file with the ASSP analyzers - this will crash the
>MainThread - the assp process!
>
>Meanwhile I'll try to find a way to prevent the error 'Wide character in
>subroutine entry at sub main::BayesWordClean line 9.'
>
> >so it is definitely based on the content of the email
>100% right !
>
>Thomas
>
>
>
>Von:Scott MacLean 
>An: ASSP development mailing list 
>Datum:  24.04.2012 14:47
>Betreff:[Assp-test] V2 spamdb problems?
>
>
>
>I'm running the latest V2 release (12115), against an MSSQL server.
>
>On my old mail server, I had many problems with people sending to the
>EmailSpam address. They would forward a spam email to that address,
>and sometimes it would go through, other times it would hang during
>send, taking out one of the ASSP workers in the process. Eventually
>all of the workers would be killed off by this problem, and a
>watchdog process would reset ASSP to get it back.
>
>Once I rebuilt the mail server on a newer, bigger, faster server,
>this problem went away. However...it has now returned, and it is
>happening exactly the same way. It has something to do with the
>spamdb table, because I recall that truncating that table on my old
>server would fix the problem, at least until it filled the table up
>again. I don't know if it was due to the size of the table, or some
>errant entries in the table that ASSP was not handling properly.
>
>I do know that if an email causes the problem, that email will ALWAYS
>cause the problem -  and emails that don't cause the problem, NEVER
>cause the problem - so it is definitely based on the content of the 
email.
>
>In addition, at the same time this problem has resurfaced, my

[Assp-test] fixes in assp 2.1.2 build 12116

2012-04-24 Thread Thomas Eckardt

Hi all,

fixed in assp 2.1.2 build 12116:

- on some systems the rebuild spamdb failed with a 'wide character' error 
in sub 'BayesWordClean'
- the analyze report send failed in some cases
- recursive definitions of include files in report files leads in to assp 
restarts
- in the 'address action' GUI dialog some strings were wrong parsed for 
domain names

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!
***


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

[Assp-test] Antwort: Re: Antwort: V2 spamdb problems?

2012-04-24 Thread Thomas Eckardt

Hi Scott,

only for me to know - I assume that you run perl 5.14.x - because only 
perl 5.14.x could run in to the 'wide character' error - I'm right?

Thomas

Von:Scott MacLean 
An: ASSP development mailing list 
Datum:  24.04.2012 21:04
Betreff:Re: [Assp-test] Antwort:  V2 spamdb problems?

Hi Thomas,

I did as you suggested. Each time the rebuild failed, I took the last 
file written to the rebuilddebug.txt file, and moved it from the spam 
directory to another directory. Then I restarted the rebuild.

I did this four times, and after removing the fourth file, the 
rebuild got past processing the spam files...but then failed while 
processing notspam. I repeated the process, removing the notspam 
files that were causing the rebuild failure until the process 
completed successfully.

I had a look through all of the files causing the problems - and I 
really don't see any common features between them all - no common 
IPs, senders, subjects or content.

Interestingly enough, some of the files that were causing the failure 
were almost two weeks old - and it's only been the last few days that 
the rebuild has started to fail. These files were not causing the 
failure previously. More importantly - well after I had gotten the 
process to complete the spam rebuild, and was working on identifying 
the bad messages in notspam, it suddenly started failing in the spam 
rebuild again. The message in the spam rebuild it suddenly started 
failing on was three days old. This message had passed with no 
problem on the previous eight rebuilddb attempts, and suddenly caused 
it to fail. Obviously something changed, and the only thing I can 
think of that changed is the contents of spamdb. So I suspect it's a 
combination of the content of the emails, along with data that is 
stored in the spamdb database that is causing the problem.

I've sent you copies of the emails that were causing the problems, 
along with the spamdb export of my system.

At 10:25 AM 4/24/2012, Thomas Eckardt wrote:

>Scott,
>
>create a file 'rebuilddebug.txt' in the assp root folder. You can do that
>using the GUI - at the bottom of the rebuild section - store an empty
>file!
>Once this file exists, start the rebuild. If that crashes - look in to
>that debug file - it will show the name of the message file, that was 
last
>accessed at the last line. The rebuild processes the files by the
>time/date - starting with the youngest. It could be possible that the 
file
>name of the bad file was still not written to the debug output !!!
>Move that file away - zip it - send it to me.
>
>Analyze the file for sender , IP, subject, content  - try to 
indentify
>(possibly  block) similar mails (preHeaderRe) - ot at least use
>noCollecting and/or noCollectRe to prevent assp from collecting such
>mails.
>Remove all similar files from the corpus - restart the rebuild - possibly
>repeat that procedure.
>
>DO NOT analyze this file with the ASSP analyzers - this will crash the
>MainThread - the assp process!
>
>Meanwhile I'll try to find a way to prevent the error 'Wide character in
>subroutine entry at sub main::BayesWordClean line 9.'
>
> >so it is definitely based on the content of the email
>100% right !
>
>Thomas
>
>
>
>Von:Scott MacLean 
>An: ASSP development mailing list 
>Datum:  24.04.2012 14:47
>Betreff:[Assp-test] V2 spamdb problems?
>
>
>
>I'm running the latest V2 release (12115), against an MSSQL server.
>
>On my old mail server, I had many problems with people sending to the
>EmailSpam address. They would forward a spam email to that address,
>and sometimes it would go through, other times it would hang during
>send, taking out one of the ASSP workers in the process. Eventually
>all of the workers would be killed off by this problem, and a
>watchdog process would reset ASSP to get it back.
>
>Once I rebuilt the mail server on a newer, bigger, faster server,
>this problem went away. However...it has now returned, and it is
>happening exactly the same way. It has something to do with the
>spamdb table, because I recall that truncating that table on my old
>server would fix the problem, at least until it filled the table up
>again. I don't know if it was due to the size of the table, or some
>errant entries in the table that ASSP was not handling properly.
>
>I do know that if an email causes the problem, that email will ALWAYS
>cause the problem -  and emails that don't cause the problem, NEVER
>cause the problem - so it is definitely based on the content of the 
email.
>
>In addition, at the same time this problem has resurfaced, my
>rebuildspamdb has started to fail EVERY time, while processing the
>spam directory:
>
>Apr-24-12 06:16:10 D:/ASSP/spam
>Apr-24-12 06:16:10 File Count:   14,552
>Apr-24-12 06:16:10 Processing... spam with 14552 files
>Apr-24-12 06:16:26 ignore files older than Mar-24-12 06:16:10 in folder
>spam
>
>That is the last entry that is in my rebuildrun.txt file,
>consistently, every

Re: [Assp-test] Antwort: V2 spamdb problems?

2012-04-24 Thread Scott MacLean

Hi Thomas,

I did as you suggested. Each time the rebuild failed, I took the last 
file written to the rebuilddebug.txt file, and moved it from the spam 
directory to another directory. Then I restarted the rebuild.

I did this four times, and after removing the fourth file, the 
rebuild got past processing the spam files...but then failed while 
processing notspam. I repeated the process, removing the notspam 
files that were causing the rebuild failure until the process 
completed successfully.

I had a look through all of the files causing the problems - and I 
really don't see any common features between them all - no common 
IPs, senders, subjects or content.

Interestingly enough, some of the files that were causing the failure 
were almost two weeks old - and it's only been the last few days that 
the rebuild has started to fail. These files were not causing the 
failure previously. More importantly - well after I had gotten the 
process to complete the spam rebuild, and was working on identifying 
the bad messages in notspam, it suddenly started failing in the spam 
rebuild again. The message in the spam rebuild it suddenly started 
failing on was three days old. This message had passed with no 
problem on the previous eight rebuilddb attempts, and suddenly caused 
it to fail. Obviously something changed, and the only thing I can 
think of that changed is the contents of spamdb. So I suspect it's a 
combination of the content of the emails, along with data that is 
stored in the spamdb database that is causing the problem.

I've sent you copies of the emails that were causing the problems, 
along with the spamdb export of my system.

At 10:25 AM 4/24/2012, Thomas Eckardt wrote:

>Scott,
>
>create a file 'rebuilddebug.txt' in the assp root folder. You can do that
>using the GUI - at the bottom of the rebuild section - store an empty
>file!
>Once this file exists, start the rebuild. If that crashes - look in to
>that debug file - it will show the name of the message file, that was last
>accessed at the last line. The rebuild processes the files by the
>time/date - starting with the youngest. It could be possible that the file
>name of the bad file was still not written to the debug output !!!
>Move that file away - zip it - send it to me.
>
>Analyze the file for sender , IP, subject, content  - try to indentify
>(possibly  block) similar mails (preHeaderRe) - ot at least use
>noCollecting and/or noCollectRe to prevent assp from collecting such
>mails.
>Remove all similar files from the corpus - restart the rebuild - possibly
>repeat that procedure.
>
>DO NOT analyze this file with the ASSP analyzers - this will crash the
>MainThread - the assp process!
>
>Meanwhile I'll try to find a way to prevent the error 'Wide character in
>subroutine entry at sub main::BayesWordClean line 9.'
>
> >so it is definitely based on the content of the email
>100% right !
>
>Thomas
>
>
>
>Von:Scott MacLean 
>An: ASSP development mailing list 
>Datum:  24.04.2012 14:47
>Betreff:[Assp-test] V2 spamdb problems?
>
>
>
>I'm running the latest V2 release (12115), against an MSSQL server.
>
>On my old mail server, I had many problems with people sending to the
>EmailSpam address. They would forward a spam email to that address,
>and sometimes it would go through, other times it would hang during
>send, taking out one of the ASSP workers in the process. Eventually
>all of the workers would be killed off by this problem, and a
>watchdog process would reset ASSP to get it back.
>
>Once I rebuilt the mail server on a newer, bigger, faster server,
>this problem went away. However...it has now returned, and it is
>happening exactly the same way. It has something to do with the
>spamdb table, because I recall that truncating that table on my old
>server would fix the problem, at least until it filled the table up
>again. I don't know if it was due to the size of the table, or some
>errant entries in the table that ASSP was not handling properly.
>
>I do know that if an email causes the problem, that email will ALWAYS
>cause the problem -  and emails that don't cause the problem, NEVER
>cause the problem - so it is definitely based on the content of the email.
>
>In addition, at the same time this problem has resurfaced, my
>rebuildspamdb has started to fail EVERY time, while processing the
>spam directory:
>
>Apr-24-12 06:16:10 D:/ASSP/spam
>Apr-24-12 06:16:10 File Count:   14,552
>Apr-24-12 06:16:10 Processing... spam with 14552 files
>Apr-24-12 06:16:26 ignore files older than Mar-24-12 06:16:10 in folder
>spam
>
>That is the last entry that is in my rebuildrun.txt file,
>consistently, every day.
>
>The ASSP log, however, yields a bit better clue:
>
>Apr-24-12 06:16:10 [Worker_10001] D:/ASSP/spam
>Apr-24-12 06:16:10 [Worker_10001] File Count:14,552
>Apr-24-12 06:16:10 [Worker_10001] Processing... spam with 14552 files
>Apr-24-12 06:16:26 [Worker_10001] Ignore files older than Mar-24-12
>06:16

[Assp-test] Antwort: Re: Antwort: Database question

2012-04-24 Thread Thomas Eckardt

Tim,

there is nothing unclear in the docu (GUI)  - one assp is a master - ALL 
others that are using the same DB (shared or replicated 'even to the 
arctis':) ) are slaves.
Only the master is doing the DB maintenance - and only the master should 
do the rebuild. Also sharing the corpus folders is optimal.

Replicating a DB is better than sharing a DB, because of the SPOF (Single 
Point Of Failure). How ever sharing more simple to configure.

Thomas




Von:Tim Jacob 
An: ASSP development mailing list 
Datum:  24.04.2012 17:35
Betreff:Re: [Assp-test] Antwort:  Database question



Do both Email1 and Email2 get configured as slaves if MySQL is on a 
totally different server?


On 04/24/2012 11:01 AM, Thomas Eckardt wrote:
>> what happens if Email1 goes down?
> Email2 will have problems - will detect that mysql is down - will switch
> to the last backup files, using file based hashes - and will possibly
> crash if the databases are too large.
>
> I recommend to use a separate mysql server.
>
> Thomas
>
>
>
> Von:Tim Jacob
> An: ASSP development mailing list
> Datum:  24.04.2012 12:50
> Betreff:[Assp-test] Database question
>
>
>
> I have 2 email servers, each running ASSP v2.1.2(10109) on Linux.
>
> If I set up a database - probably MySQL - on Email1, and point Email2 to
> it, what happens if Email1 goes down?
> Does that mean that Email2 will continue operating on some kind of 
cache?
> Or does it mean that Email2 will stop functioning properly until Email1
> is back up?
> Or some other variation?
>
> Many thanks
> Tim
>
>
> 
--
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. 
Discussions
> will include endpoint security, mobile security and the latest in 
malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> 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!
> ***
>
>
>
>
> 
--
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. 
Discussions
> will include endpoint security, mobile security and the latest in 
malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> ___
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test

-- 
# Jolly Farmer: Tim Jacob
# Email: tja...@jollyfarmer.com 
# Website: www.jollyfarmer.com 
# Phone: 506-325-3850 

# 56 Crabbe Rd | Northampton, NB E7N 1R6

"Integrity, Quality, & Reliable Service Since 1967"

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
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!
***


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourcef

Re: [Assp-test] Antwort: Database question

2012-04-24 Thread Tim Jacob

Do both Email1 and Email2 get configured as slaves if MySQL is on a 
totally different server?


On 04/24/2012 11:01 AM, Thomas Eckardt wrote:
>> what happens if Email1 goes down?
> Email2 will have problems - will detect that mysql is down - will switch
> to the last backup files, using file based hashes - and will possibly
> crash if the databases are too large.
>
> I recommend to use a separate mysql server.
>
> Thomas
>
>
>
> Von:Tim Jacob
> An: ASSP development mailing list
> Datum:  24.04.2012 12:50
> Betreff:[Assp-test] Database question
>
>
>
> I have 2 email servers, each running ASSP v2.1.2(10109) on Linux.
>
> If I set up a database - probably MySQL - on Email1, and point Email2 to
> it, what happens if Email1 goes down?
> Does that mean that Email2 will continue operating on some kind of cache?
> Or does it mean that Email2 will stop functioning properly until Email1
> is back up?
> Or some other variation?
>
> Many thanks
> Tim
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> 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!
> ***
>
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> ___
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test

-- 
# Jolly Farmer: Tim Jacob
# Email: tja...@jollyfarmer.com 
# Website: www.jollyfarmer.com 
# Phone: 506-325-3850 

# 56 Crabbe Rd | Northampton, NB E7N 1R6

"Integrity, Quality, & Reliable Service Since 1967"

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

[Assp-test] Antwort: V2 spamdb problems?

2012-04-24 Thread Thomas Eckardt

Scott,

create a file 'rebuilddebug.txt' in the assp root folder. You can do that 
using the GUI - at the bottom of the rebuild section - store an empty 
file!
Once this file exists, start the rebuild. If that crashes - look in to 
that debug file - it will show the name of the message file, that was last 
accessed at the last line. The rebuild processes the files by the 
time/date - starting with the youngest. It could be possible that the file 
name of the bad file was still not written to the debug output !!!
Move that file away - zip it - send it to me.

Analyze the file for sender , IP, subject, content  - try to indentify 
(possibly  block) similar mails (preHeaderRe) - ot at least use 
noCollecting and/or noCollectRe to prevent assp from collecting such 
mails.
Remove all similar files from the corpus - restart the rebuild - possibly 
repeat that procedure.

DO NOT analyze this file with the ASSP analyzers - this will crash the 
MainThread - the assp process!

Meanwhile I'll try to find a way to prevent the error 'Wide character in 
subroutine entry at sub main::BayesWordClean line 9.'

>so it is definitely based on the content of the email
100% right !

Thomas



Von:Scott MacLean 
An: ASSP development mailing list 
Datum:  24.04.2012 14:47
Betreff:[Assp-test] V2 spamdb problems?



I'm running the latest V2 release (12115), against an MSSQL server.

On my old mail server, I had many problems with people sending to the 
EmailSpam address. They would forward a spam email to that address, 
and sometimes it would go through, other times it would hang during 
send, taking out one of the ASSP workers in the process. Eventually 
all of the workers would be killed off by this problem, and a 
watchdog process would reset ASSP to get it back.

Once I rebuilt the mail server on a newer, bigger, faster server, 
this problem went away. However...it has now returned, and it is 
happening exactly the same way. It has something to do with the 
spamdb table, because I recall that truncating that table on my old 
server would fix the problem, at least until it filled the table up 
again. I don't know if it was due to the size of the table, or some 
errant entries in the table that ASSP was not handling properly.

I do know that if an email causes the problem, that email will ALWAYS 
cause the problem -  and emails that don't cause the problem, NEVER 
cause the problem - so it is definitely based on the content of the email.

In addition, at the same time this problem has resurfaced, my 
rebuildspamdb has started to fail EVERY time, while processing the 
spam directory:

Apr-24-12 06:16:10 D:/ASSP/spam
Apr-24-12 06:16:10 File Count:   14,552
Apr-24-12 06:16:10 Processing... spam with 14552 files
Apr-24-12 06:16:26 ignore files older than Mar-24-12 06:16:10 in folder 
spam

That is the last entry that is in my rebuildrun.txt file, 
consistently, every day.

The ASSP log, however, yields a bit better clue:

Apr-24-12 06:16:10 [Worker_10001] D:/ASSP/spam
Apr-24-12 06:16:10 [Worker_10001] File Count:14,552
Apr-24-12 06:16:10 [Worker_10001] Processing... spam with 14552 files
Apr-24-12 06:16:26 [Worker_10001] Ignore files older than Mar-24-12 
06:16:10 in folder spam
Apr-24-12 06:18:10 [Worker_10001] Error: rebuildspamdb failed - Wide 
character in subroutine entry at sub main::BayesWordClean line 9.

Any idea what I should be looking for? Are these problems related, or 
is it just a coincidence that both started failing at the same time?



--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
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!
***


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Assp-test mailing list
Assp-test@lists.sourceforge.net

[Assp-test] Antwort: Database question

2012-04-24 Thread Thomas Eckardt

>what happens if Email1 goes down?

Email2 will have problems - will detect that mysql is down - will switch 
to the last backup files, using file based hashes - and will possibly 
crash if the databases are too large.

I recommend to use a separate mysql server.

Thomas



Von:Tim Jacob 
An: ASSP development mailing list 
Datum:  24.04.2012 12:50
Betreff:[Assp-test] Database question



I have 2 email servers, each running ASSP v2.1.2(10109) on Linux.

If I set up a database - probably MySQL - on Email1, and point Email2 to 
it, what happens if Email1 goes down?
Does that mean that Email2 will continue operating on some kind of cache?
Or does it mean that Email2 will stop functioning properly until Email1 
is back up?
Or some other variation?

Many thanks
Tim


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
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!
***


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

[Assp-test] V2 spamdb problems?

2012-04-24 Thread Scott MacLean

I'm running the latest V2 release (12115), against an MSSQL server.

On my old mail server, I had many problems with people sending to the 
EmailSpam address. They would forward a spam email to that address, 
and sometimes it would go through, other times it would hang during 
send, taking out one of the ASSP workers in the process. Eventually 
all of the workers would be killed off by this problem, and a 
watchdog process would reset ASSP to get it back.

Once I rebuilt the mail server on a newer, bigger, faster server, 
this problem went away. However...it has now returned, and it is 
happening exactly the same way. It has something to do with the 
spamdb table, because I recall that truncating that table on my old 
server would fix the problem, at least until it filled the table up 
again. I don't know if it was due to the size of the table, or some 
errant entries in the table that ASSP was not handling properly.

I do know that if an email causes the problem, that email will ALWAYS 
cause the problem -  and emails that don't cause the problem, NEVER 
cause the problem - so it is definitely based on the content of the email.

In addition, at the same time this problem has resurfaced, my 
rebuildspamdb has started to fail EVERY time, while processing the 
spam directory:

Apr-24-12 06:16:10 D:/ASSP/spam
Apr-24-12 06:16:10 File Count:  14,552
Apr-24-12 06:16:10 Processing... spam with 14552 files
Apr-24-12 06:16:26 ignore files older than Mar-24-12 06:16:10 in folder spam

That is the last entry that is in my rebuildrun.txt file, 
consistently, every day.

The ASSP log, however, yields a bit better clue:

Apr-24-12 06:16:10 [Worker_10001] D:/ASSP/spam
Apr-24-12 06:16:10 [Worker_10001] File Count:   14,552
Apr-24-12 06:16:10 [Worker_10001] Processing... spam with 14552 files
Apr-24-12 06:16:26 [Worker_10001] Ignore files older than Mar-24-12 
06:16:10 in folder spam
Apr-24-12 06:18:10 [Worker_10001] Error: rebuildspamdb failed - Wide 
character in subroutine entry at sub main::BayesWordClean line 9.

Any idea what I should be looking for? Are these problems related, or 
is it just a coincidence that both started failing at the same time?



--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

[Assp-test] Database question

2012-04-24 Thread Tim Jacob

I have 2 email servers, each running ASSP v2.1.2(10109) on Linux.

If I set up a database - probably MySQL - on Email1, and point Email2 to 
it, what happens if Email1 goes down?
Does that mean that Email2 will continue operating on some kind of cache?
Or does it mean that Email2 will stop functioning properly until Email1 
is back up?
Or some other variation?

Many thanks
Tim


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

[Assp-test] small bug in build 12115

2012-04-24 Thread Thomas Eckardt

Hi all,

just saw a small bug in 12115.

To prevent assp from running in to this code part, make sure you use a 
file 'reports/analyzereport.txt' based on the latest version (includes a 
MIME header).

http://assp.cvs.sourceforge.net/viewvc/assp/assp2/reports/analyzereport.txt?view=log

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!
***


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

[Assp-test] Antwort: Re: Antwort: V2 spamdb problems?

[Assp-test] fixes in assp 2.1.2 build 12116

[Assp-test] Antwort: Re: Antwort: V2 spamdb problems?

Re: [Assp-test] Antwort: V2 spamdb problems?

[Assp-test] Antwort: Re: Antwort: Database question

Re: [Assp-test] Antwort: Database question

[Assp-test] Antwort: V2 spamdb problems?

[Assp-test] Antwort: Database question

[Assp-test] V2 spamdb problems?

[Assp-test] Database question

[Assp-test] small bug in build 12115

11 matches

Site Navigation

Mail list logo

Footer information