So far, it doesn't seem to introduce any expected behavior.
As to seeing if it does what it's supposed to do, that will take some
time. I've never experienced total quarantine loss, just reports of
lost email when retraining 2 more more messages from the history tab.
Seems to not be easily rep
On 07.01.2013 22:23, Tom Hendrikx wrote:
> On 07-01-13 20:34, Tod A. Sandman wrote:
>>> Did the patch you submitted get merged in the official dspam.cgi?
>>>
>> I never received a reply, so I assume not.
>>
> Hi
Hello,
> It's not that we are ungrateful, just the fact that there are not many
> deve
On 07-01-13 20:34, Tod A. Sandman wrote:
>> Did the patch you submitted get merged in the official dspam.cgi?
>>
>
> I never received a reply, so I assume not.
>
Hi
It's not that we are ungrateful, just the fact that there are not many
developers actively working on DSPAM. Another problem is th
> Did the patch you submitted get merged in the official dspam.cgi?
>
I never received a reply, so I assume not.
Tod Sandman
Sr. Systems Administrator
Middleware Development & Integration
Rice University
Voice: 713.348.5816
--
Did the patch you submitted get merged in the official dspam.cgi?
-Troy
On 12/10/2012 3:37 PM, Tod A. Sandman wrote:
> And here's the patch.
>
>
> Tod Sandman
> Sr. Systems Administrator
> Middleware Development & Integration
> Rice University
>
---
And here's the patch.
Tod Sandman
Sr. Systems Administrator
Middleware Development & Integration
Rice University
--- configure.pl.orig 2012-10-08 01:37:12.0 -0500
+++ configure.pl2012-12-03 08:29:14.611409303 -0600
@@ -34,6 +34,10 @@
$CONFIG{'WEB_ROOT'}= ""; # URL locatio
We are currently upgrading from dspam-3.6.8 to dspam-3.10.2.
Long ago we had functional issues with the web ui, especially regarding the
delivery of false positives, and we made changes to prevent false positives (or
whole quarantines) from disappearing, no matter how rarely.
I am now figuring
