https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5986
--- Comment #1 from Mark Martinec <[EMAIL PROTECTED]> 2008-09-25 05:32:55 PST
---
I know what "Modification of a read-only value attempted" indicates,
although I can't see any aliasing going on around that code section
(loop variables, @_ arguments, $_ and the like are common suspects).
I tried to simulate the problem by feeding all kinds of real and aliased
arguments to a standalone parse_content_type, but can not reproduce
the failure. Needless to say, running amavisd myself too, there is
no such error message in my logs of the recent months.
Just to make sure, is the indicated Util.pm line 852 in your file
the same as in the 3.2.5 distribution:
$ct =~ s/^\s+//; # strip leading whitespace
and the subroutine starts by (excluding comments):
sub parse_content_type {
my $ct = $_[-1] || 'text/plain; charset=us-ascii';
Is the problem reproducible by feeding the same message again
through a content filter? Is the problem reproducible by
feeding the same message to a command line spamassassin:
su vscan -c 'spamassassin -t -D <x.msg'
Can you please attach a sample message (possibly sanitized) to this PR.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
