George Georgalis wrote:
> grep -r REPORT /etc/spamassassin/ /usr/share/spamassassin/
> returned nothing that wasn't attached to other characters.
Hmm.. what about greping /etc/resolv.conf?
Better yet, let's look at the code surrounding line 233 of INET.pm
head -n 235 /usr/share/perl/5.6.1/IO/Socket/INET.pm line |tail -n 5
That will at least help us narrow in on what parameter is text instead of
numeric, which might help us figure out what the problem is.
>
> but this is interesting,
>
> # grep -r REPORT /usr/share/perl5 /usr/share/perl /usr/local/lib/perl/5.6.1/
> /usr/share/perl5/Net/FTP.pm:=head1 REPORTING BUGS
> /usr/share/perl5/HTML/TreeBuilder.pm:=head1 BUG REPORTS
> /usr/share/perl5/Mail/SpamAssassin/Conf.pm:
> $self->{headers_spam}->{"Report"} = "_REPORT_";
> /usr/share/perl5/Mail/SpamAssassin/Conf.pm: _REPORT_ terse report of
> tests hit (for header reports)
> /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm: REPORT => sub {
> /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm: return "\n"
> . ($self->{tag_data}->{REPORT} || "");
> /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm:
> $self->{tag_data}->{REPORT} .= sprintf ("* %s %s %s%s\n%s",
That doesn't look at all interesting to me. None of that code has anything to do
with the network code, so none of that should ever approach INET.pm. That's all
stuff related to the markup of the message.
>Looks like a bug in my version.
> # spamassassin -V
> SpamAssassin version 3.0.4
> running on Perl version 5.6.1
Highly unlikely to be a bug in your version. a LOT of people run SA 3.0.4 on
perl 5.6.1, and that particular message is very new to me.
