Re: 3.0.5 rescoring

On Mittwoch, 30. November 2005 19:53 Warren Togami wrote: Documenting calling a script is the easy part.  Making sure that all reporters are following the rules of spam sorting, that is not easy. What about an IMAP server, where each reporter gets an account on, and can drop her SPAM to? Like

[Bug 4714] New: Vpopmail handling of aliases fails

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4714 Summary: Vpopmail handling of aliases fails Product: Spamassassin Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3

[Bug 4714] Vpopmail handling of aliases fails

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4714 --- Additional Comments From [EMAIL PROTECTED] 2005-12-01 16:46 --- Created an attachment (id=3285) -- (http://issues.apache.org/SpamAssassin/attachment.cgi?id=3285action=view) Log excerpt showing the problem Sorry to paste

Re: 3.0.5 rescoring

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Monnerie writes: On Dienstag, 22. November 2005 06:44 Theo Van Dinter wrote: So basically Justin is 34%, I'm 31%, and everyone else combined is 35%. I could send you my hand sorted SPAM, if you like. It's only ~3000 SPAMs, but maybe

Re: 3.0.5 rescoring

I'd expect that the 700k message corpus will be more prone to errors than the 2M message corpus. It still might be good enough. I'm not convinced that rescoring (as opposed to putting in new rules) will do much for 3.0.5's accuracy. If people really want to go to the trouble of running the

Re: 3.0.5 rescoring

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Henry Stern writes: I'd expect that the 700k message corpus will be more prone to errors than the 2M message corpus. It still might be good enough. I'm not convinced that rescoring (as opposed to putting in new rules) will do much for 3.0.5's

[Bug 3787] HTML email 'malformed UTF-8 character' warnings from SA

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3787 --- Additional Comments From [EMAIL PROTECTED] 2005-12-02 00:17 --- Unable to reproduce with current SVN plus 70_sare_obfu.cf. ./spamassassin -V SpamAssassin version 3.2.0-r322462 running on Perl version 5.8.6 Tried with

[Bug 3787] HTML email 'malformed UTF-8 character' warnings from SA

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3787 --- Additional Comments From [EMAIL PROTECTED] 2005-12-02 00:24 --- john, r322462? i can reproduce at will with (at least) r349275 and later ... seems Dallas may be able to as well, but I'm sure he can chime in for himself

[Bug 3787] HTML email 'malformed UTF-8 character' warnings from SA

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3787 --- Additional Comments From [EMAIL PROTECTED] 2005-12-02 00:35 --- It's r351501. --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.

[Bug 4476] prefork: sysread(8) failed after 300 secs (no children responding)

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4476 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED]

[Bug 3787] HTML email 'malformed UTF-8 character' warnings from SA

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3787 --- Additional Comments From [EMAIL PROTECTED] 2005-12-02 01:26 --- agh, my mistake. sorry ... i *still* get occassionally confused by the co'd revision, and that which spamassassin -v reports :-/ --- You are receiving

[Bug 4649] Outlook Express mails sent to Yahoo groups gets blocked when received

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4649 --- Additional Comments From [EMAIL PROTECTED] 2005-12-02 03:44 --- Created an attachment (id=3286) -- (http://issues.apache.org/SpamAssassin/attachment.cgi?id=3286action=view) Full email message that triggers the

SA 3.0.5 SPF error when building

I grabbed the tarball for 3.0.5 and when I do 'make test' it gets one error having to do with SPF. I've got the latest Net::DNS and Net::SPF::Query Perl 5.8.6 Here's the dump from the make test. [EMAIL PROTECTED] Mail-SpamAssassin-3.0.5]# make test PERL_DL_NONLAZY=1 /usr/bin/perl

Re: SA 3.0.5 SPF error when building

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doc Schneider writes: I grabbed the tarball for 3.0.5 and when I do 'make test' it gets one error having to do with SPF. I've got the latest Net::DNS and Net::SPF::Query Perl 5.8.6 Yeah, I've been seeing similar in make test here, too; I

Re: SA 3.0.5 SPF error when building

Justin Mason wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doc Schneider writes: I grabbed the tarball for 3.0.5 and when I do 'make test' it gets one error having to do with SPF. I've got the latest Net::DNS and Net::SPF::Query Perl 5.8.6 Yeah, I've been seeing similar in make

Re: SA 3.0.5 SPF error when building

On 01/12/2005 10:43 PM, Justin Mason wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doc Schneider writes: I grabbed the tarball for 3.0.5 and when I do 'make test' it gets one error having to do with SPF. I've got the latest Net::DNS and Net::SPF::Query Perl 5.8.6 Yeah, I've been

[Bug 4590] prefork: syswrite(6) failed

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4590 [EMAIL PROTECTED] changed: What|Removed |Added CC||dev@spamassassin.apache.org

[Bug 4649] Outlook Express mails sent to Yahoo groups gets blocked when received

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4649 --- Additional Comments From [EMAIL PROTECTED] 2005-12-02 05:42 --- Rick comfirmed that he's only had FP reports about mail sent via Yahoo! Groups. Looking at Bob's samples... the first two are clearly not sent by Outlook

[Bug 4476] prefork: sysread(8) failed after 300 secs (no children responding)

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4476 --- Additional Comments From [EMAIL PROTECTED] 2005-12-02 06:28 --- note: if you're seeing something like this from other spamd processes around the same time: Nov 20 00:07:36 cyan spamd[15882]: prefork: syswrite(7) failed,

[Bug 4476] prefork: sysread(8) failed after 300 secs (no children responding)

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4476 --- Additional Comments From [EMAIL PROTECTED] 2005-12-02 06:50 --- Not in my case. I've only seen a single failure (at line 501) for each (suddenly defunct) child and then nothing: Nov 12 10:26:08 cyan spamd[21524]: