[Bug 7454] New: unknown encoding type 'utf-8' in Node.pm

[bu...@bugzilla.spamassassin.org]

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7454

            Bug ID: 7454
           Summary: unknown encoding type 'utf-8' in Node.pm
           Product: Spamassassin
           Version: 3.4 SVN branch
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Libraries
          Assignee: dev@spamassassin.apache.org
          Reporter: kmcgrail@apache.org
  Target Milestone: Undefined

Off-list: I compiled and installed the spamassassin-3.4.2 from svn last night
and are now receiving the following:

May 18 05:39:39 mail02 amavis[11059]: (11059-08) _WARN: rules: failed
to run LOC_OLEMACRO_ZIP_PW test, skipping:\n\t(message: unknown
encoding type 'ISO-8859-1' in RFC2047 header at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Message/Node.pm line
779.\n)
May 18 06:20:19 mail03 amavis[28035]: (28035-05) _WARN: rules: failed
to run LOC_OLEMACRO test, skipping:\n\t(message: unknown encoding type
'UTF-8' in RFC2047 header at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Message/Node.pm line
779.\n)

The LOC_OLEMACRO are local rules that attempt to check whether an
email contains a Word doc.

How can I troubleshoot this? Line 779 is in the __decode_header
function in Node.pm.

KAM has samples.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7454] unknown encoding type 'utf-8' in Node.pm

[bu...@bugzilla.spamassassin.org]

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7454

Kevin A. McGrail <km...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
                 CC|                            |kmcgrail@apache.org
             Status|NEW                         |RESOLVED

--- Comment #1 from Kevin A. McGrail <km...@apache.org> ---
We believe this is resolved now in trunk and 3.4.  Will have to wait for 3.4.2
to identify for sure.

-- 
You are receiving this mail because:
You are the assignee for the bug.