Wolfgang Zeikat wrote:
Hello again,
On 07/12/07 16:22, Dallas Engelken wrote:
Wolfgang Zeikat wrote:
I noticed that some of the latest pdf spam mails do not contain a
filename in the mime headers, could that be a reason for the above
behaviour?
Possibly, but seeing that line 300 is just a dbg() line itself, you
can either comment it out, or change it to something that will not
through a warn.
# dbg("pdfinfo: found part, type=$type file=$name cte=$cte");
dbg("pdfinfo: found part, type=".($type ? $type : '')."
file=".($name ? $name : '')." cte=".($cte ? $cte : '')."");
Thanks, that fixed those. Lately, I see a lot of:
Jul 17 14:27:10 spamlock2 spamd[9786]: Use of uninitialized value in
concatenation (.) or string at /etc/mail/spamassassin/PDFInfo.pm line
272, <GEN25171> line 1579.
Jul 17 14:27:10 spamlock2 spamd[9786]: Use of uninitialized value in
hash element at /etc/mail/spamassassin/PDFInfo.pm line 283, <GEN25171>
line 1579.
Line 272 is (after the earlier changes):
dbg("pdfinfo: MD5 results for ".($name ? $name : '')." - md5=$md5
fuzzy1=$fuzzy_md5 fuzzy2=$tags_md5");
Line 283 is:
$pms->{pdfinfo}->{fuzzy_md5}->{$tags_md5} = 1;
I'd say $tags_md5 is undef then.... which is odd because if it made it
that far, then the message has a pdf in it.... and all pdfs have tag
structures.
Got samples that make that warn appear?
--
Dallas Engelken
[EMAIL PROTECTED]
http://uribl.com
