Hi Martin,
You certainly did not miss anythingbut I did! Being new to spamassassin,
I was only familiar with spamassassin command. which was awfully slow for a
large number of emails. But now that I used spamc, I'm getting 5+ messages
per second.
Thank you much for the advise. I have practica
On Fri, 2012-12-28 at 16:51 -0800, Sean Tout wrote:
> Hi John,
>
> Thank you much for the help. I have been trying to avoid executing
> spamassassin shell commands from perl since it takes a significant amount of
> time~=12 seconds for each email. I have tried the below script, which works
> but o
Hi John,
Thank you much for the help. I have been trying to avoid executing
spamassassin shell commands from perl since it takes a significant amount of
time~=12 seconds for each email. I have tried the below script, which works
but of course not in a favorable especially for processing 20,000+ em
On Fri, 28 Dec 2012, Sean Tout wrote:
Hi John,
Per your response below, here is what I did to confirm it's not a content
problem.
open (RFILE, $reportfile_name);
while(!$folder_reader->end_of_file())
{
$email = $folder_reader->read_next_email();
chomp($email);
$mail = $spamtest->parse
Hi John,
Per your response below, here is what I did to confirm it's not a content
problem.
open (RFILE, $reportfile_name);
while(!$folder_reader->end_of_file())
{
$email = $folder_reader->read_next_email();
chomp($email);
$mail = $spamtest->parse($email);
$status = $spamtest->c
On Fri, 28 Dec 2012, Sean Tout wrote:
Hi John,
I wrote every email read to an output file. The output file is identical to
the input file I'm reading the emails from according to diff!
The concern is the format of the single mail object being sent to
SpamAssassin for scanning. Having the ver
Hi John,
I wrote every email read to an output file. The output file is identical to
the input file I'm reading the emails from according to diff!
Regards,
-Sean.
--
View this message in context:
http://spamassassin.1065346.n5.nabble.com/Spamassassin-not-parsing-email-messages-tp102770p102
On Fri, 28 Dec 2012, Sean Tout wrote:
That's most likely the case. But I'm not sure what's going in there and how
to get rid of it. I tried with and without chomp() but got the same results.
below is a snippet with chomp, which I applied before parsing the email with
spamassassin.
my $spamtest
Hi Dave,
That's most likely the case. But I'm not sure what's going in there and how
to get rid of it. I tried with and without chomp() but got the same results.
below is a snippet with chomp, which I applied before parsing the email with
spamassassin.
my $spamtest = Mail::SpamAssassin->new();
That implies that what ever mechanism you're using in the original process
is adding a blank line (or bare 'nl' or 'cr') to the beginning of the
message that you're then handing to SA.
Idiot question, are you doing (or not) a "chomp" in the initial read
process?
On Fri, 28 Dec 2012, Sean Tout
Hi Henrik & Jeff,
One more input that might shed more light. I copied one of the emails from
the above 3 emails into its own file and ran spamassassin from the command
line in test mode against it and it worked fine. the command is
spamassassin --test-mode < /spamemails/singleemail.spam
where si
Hi Jeff,
You are correct. it's clear Spamassassin is unable to parse the email. so
there is something in the email that's causing SpamAssassin to not parse the
email, which I'm trying to find out what it is and why!
I have tried multiple sources of emails, many of which are from known spam
corpus
On Fri, 28 Dec 2012, John ffitch wrote:
On Fri, 28 Dec 2012, Niamh Holding wrote:
Friday, December 28, 2012, 9:47:58 AM, you wrote:
jf> SpamAssassin version 3.2.5
That's ancient!
Sorry -- there is also 3.3.2 in /usr/local/bin
Having two different versions installed can potentially lea
From: Sean Tout
Date: Fri, 28 Dec 2012 01:10:02 -0800 (PST)
Hi Henrik,
Thank you much for the prompt response and points. I ran the Perl script
with the code you pasted below, but still got the same report scores for all
emails! by the way, when I also tried to print cont
Hi,
Please add me to the Contributors Group with the wiki username jez.
--
Best regards,
Jeremy Morton (Jez)
On Fri, 28 Dec 2012, Niamh Holding wrote:
Hello john,
Friday, December 28, 2012, 9:47:58 AM, you wrote:
jf> As far as I am away I am running the latest
jf> release
jf> SpamAssassin version 3.2.5
That's ancient!
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) here
Sorry -- there
Hello john,
Friday, December 28, 2012, 9:47:58 AM, you wrote:
jf> As far as I am away I am running the latest
jf> release
jf> SpamAssassin version 3.2.5
That's ancient!
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) here
--
Best regards,
Niamhmailto:ni..
On Friday December 28 2012 10:47:58 john ffitch wrote:
> Not sure I understand. As far as I am away I am running the latest
> release
> SpamAssassin version 3.2.5
> running on Perl version 5.10.1
>
> If it matters, Debian i486, installed from CPAN
>
> Kevin> What version of Net::DNS are you u
> "Kevin" == Kevin A McGrail writes:
Kevin> On 12/18/2012 5:32 PM, john ffitch wrote:
>> I am seeing a number of these
>>
>> Dec 18 22:21:55 snout spamd[12744]: Odd number of elements in hash
>> assignment at /usr/local/lib/perl/5.10.1/Net/DNS/RR.pm line 496.
>> Dec 18 22:21:55 snout
Hi Henrik,
Thank you much for the prompt response and points. I ran the Perl script
with the code you pasted below, but still got the same report scores for all
emails! by the way, when I also tried to print contents of the emails using
$status->get_content_preview(), I got [...] I'm unable to pri
On Fri, Dec 28, 2012 at 12:45:03AM -0800, Sean Tout wrote:
> Hello,
>
> I wrote a short Perl program that reads email from an existing mbox
> formatted file, passes each individual email to Spamassassin for parse and
> score, then prints a report for each email. The strange thing is that I keep
>
21 matches
Mail list logo
