[Assp-test] Graylisting issues

Hi there; just stumbled upon what I see as a bug and a source of issues; here's what I noticed Sometimes, under certain conditions ASSP emits both a reject message (message score over limit), that is a 550 ... *followed* by another SMTP tempfail 451 retry later which comes from the graylisting;

[Assp-test] [MessageLimit][lowlimit]

Would it be possible to convert [MessageLimit][lowlimit] into something the end user would understand like Possible Spam ? -- Try before you buy = See our experts in action! The most comprehensive online learning

[Assp-test] How to avoid multiple duplicates in corpus

I was reading a document describing the so called Locality Sensitive Hashing http://www.stanford.edu/class/cs345a/slides/05-LSH.pdf http://en.wikipedia.org/wiki/Locality-sensitive_hashing and, while going through it, I started thinking at the ASSP spam and notspam corpus; as it was discussed

Re: [Assp-test] How to avoid multiple duplicates in corpus

http://en.wikipedia.org/wiki/Locality-sensitive_hashing corpus, now, the above may represent a solution, in such a case, the rebuild may just skip messages if they're repeated too often, so allowing to keep the corpus balanced also say that the email was recognized as spam (or ham,

[Assp-test] error: Worker_1 accept to client failed IO::Socket::INET=GLOB(0x59aa6494) (timeout: 2 s) : Bad file descriptor

Hello, I got messages like this: error: Worker_1 accept to client failed IO::Socket::INET=GLOB(0x59aa6494) (timeout: 2 s) : Bad file descriptor some times a day. I thought it was connected to some performance issues on the old server, but after upgrading to a new system, I still get these

[Assp-test] Antwort: How to avoid multiple duplicates in corpus

The rebuild ignores equal messages in 'spam' and 'notspam' for years now. Similar mails are 100% deteted by HMM as long as some of them where detected or one was reported at a earlyer time . And it is impossible that similar (even thousands) mails are able to compromize the corpusnorm. And the

[Assp-test] Antwort: [MessageLimit][lowlimit]

Where is an enduser able to see this ? [MessageLimit][lowlimit] Thomas Von:Bob Berryman b...@sanlogan.com An: 'ASSP development mailing list' assp-test@lists.sourceforge.net Datum: 05.03.2012 10:27 Betreff:[Assp-test] [MessageLimit][lowlimit] Would it be possible to

[Assp-test] Rebuild spamdb failing

My spamdb rebuild is failing, logging the following - where it shows [null] it is actually inserting null characters into the log. Any idea where it might be picking up these null values from? Mar-05-12 03:34:42 [Worker_10001] Error: rebuildspamdb failed - Database select statement failed:

[Assp-test] ASSP terminating

Now that I am running a brand new install of ASSP on a new server, I'm seeing the exact same problem I had before on my old server: ASSP just quits, randomly, with nothing logged as to the reason, and no common events logged prior to the termination. I had always hoped it was a memory or load

[Assp-test] Antwort: Graylisting issues

The second reply is sent to be nice. ASSP uses the 'DelayError' to do this - which is not 100% RFC conform. I'll change this to '421 closing transmission' - which is 100% RFC conform. At least this reply has nothing to do if or where a message is stored in the corpus. Thomas Von:Grayhat

[Assp-test] Antwort: error: Worker_1 accept to client failed IO::Socket::INET=GLOB(0x59aa6494) (timeout: 2 s) : Bad file descriptor

This could be happen, if the peer has closed the connection before the connection was accepted by assp. In this case the OS file handle is already gone. The timeline would be: 1) peer sends TCP connect 2) ASSP MainThread gets the connection and queues it to the transfer queue for any worker 3)

[Assp-test] Antwort: Rebuild spamdb failing

I don't think that ASSP generates a query for a [null] key - but who knows? I'll include a small check to prevent this. Thomas Von:Scott MacLean a...@hollsco.com An: ASSP development mailing list assp-test@lists.sourceforge.net Datum: 05.03.2012 22:44 Betreff:[Assp-test]