Bug 167515 - mail-filter/spamassassin-3.1.8 error in sa-learn
Bug#: 167515 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: minor Priority: P2
Resolution: FIXED Assigned To: perl@gentoo.org Reported By: art-gt@broomstick.com
Component: Applications
URL: 
Summary: mail-filter/spamassassin-3.1.8 error in sa-learn
Keywords:  
Status Whiteboard: 
Opened: 2007-02-18 19:27 0000
Description:   Opened: 2007-02-18 19:27 0000 
piping an email to sa-learn --spam now returns:
archive-iterator: invalid (undef) format in target list, 2 at
/usr/lib/perl5/ven
dor_perl/5.8.8/Mail/SpamAssassin/ArchiveIterator.pm line 724, <STDIN> line 1.

Worked fine yesterday with 3.1.3

Reproducible: Always

Steps to Reproduce:
cat singlemail | sa-learn --spam
(or "[|] [CTRL-W] sa-learn --spam" in pine)

Actual Results:  
archive-iterator: invalid (undef) format in target list, 2 at
/usr/lib/perl5/ven
dor_perl/5.8.8/Mail/SpamAssassin/ArchiveIterator.pm line 724, <STDIN> line 1.
Learned tokens from 1 message(s) (1 message(s) examined)


Expected Results:  
Learned tokens from 1 message(s) (1 message(s) examined)

------- Comment #1 From Arthur Hagen 2007-02-18 20:53:51 0000 ------- 
Testing further shows that this is a problem with the autodetect.  If
specifying - (for stdin), it works.  If relying on autodetecting the input
stream, it no longer does.

------- Comment #2 From bugzilla@schoenhaber.de 2007-02-19 11:14:51 0000 ------- 
I see the same message from sa-learn since upgrading SpamAssassin from 3.1.3 to
3.1.8.
Arthur's workaround of explicitly adding "-" to sa-learn's command line helps
in my case too.

------- Comment #3 From Adam Piątyszek 2007-02-20 07:31:44 0000 ------- 
This problem is already reported to upstream and the patch is ready:
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5336

/ediap

------- Comment #4 From Christian Hartmann 2007-02-25 12:39:09 0000 ------- 
Fixed in 3.1.8-r1.

------- Comment #5 From Michael Cummings (RETIRED) 2007-04-15 11:54:21 0000 ------- 
*** Bug 127459 has been marked as a duplicate of this bug. ***