Re: Masscheck error

[Justin Mason <jm...@jmason.org>]

Daryl C. W. O'Shea writes:
> Doc Schneider wrote:
> >>> Doc Schneider wrote:
> 
> >>>> plugin: eval failed: length of 
> >>>> asp|a=368yblkt8m8p9n9kmp9gz*b=8y9n8n9jn39*rg=*t=1108*fnc=1*cname=mybindi 
> >>>> is larger than 63 octets; see RFC1035
> >>>> section 2.3.1 at 
> >>>> /usr/lib/perl5/site_perl/5.8.6/i686-linux/Net/DNS/Question.pm line 199
> 
> > I'll try to dig it out. Should have the offset in one of the log files, 
> > right? Once I get the message(s) I'll open a bug report. Of course it is 
> > caused by some spammer who was trying to be tricky. 8*)
> 
> You'll probably have to go greping for the string, or a part of it, to 
> find the message.  The error won't be in your mass-check logs so you 
> won't be able to tell from the logs what message caused the error.

by the way, these are all harmless in terms of their effects;
they cause a die(), but this is/should be trapped by the calling
code in SpamAssassin.

--j.

Re: Masscheck error

[Doc Schneider <ma...@maddoc.net>]

Justin Mason wrote:
> Daryl C. W. O'Shea writes:
>> Doc Schneider wrote:
>>>>> Doc Schneider wrote:
>>>>>> plugin: eval failed: length of 
>>>>>> asp|a=368yblkt8m8p9n9kmp9gz*b=8y9n8n9jn39*rg=*t=1108*fnc=1*cname=mybindi 
>>>>>> is larger than 63 octets; see RFC1035
>>>>>> section 2.3.1 at 
>>>>>> /usr/lib/perl5/site_perl/5.8.6/i686-linux/Net/DNS/Question.pm line 199
>>> I'll try to dig it out. Should have the offset in one of the log files, 
>>> right? Once I get the message(s) I'll open a bug report. Of course it is 
>>> caused by some spammer who was trying to be tricky. 8*)
>> You'll probably have to go greping for the string, or a part of it, to 
>> find the message.  The error won't be in your mass-check logs so you 
>> won't be able to tell from the logs what message caused the error.
> 
> by the way, these are all harmless in terms of their effects;
> they cause a die(), but this is/should be trapped by the calling
> code in SpamAssassin.
> 
> --j.

I'll sure do a grep for part of this in my spam to find the message(s) 
triggering this.

Not quite sure which plugin: eval failed. Or am I just having one of 
those days this weekend? So far I've seen a half dozen of these... I 
also had to restart my masscheck last night as I had to move the spam 
from my active spam catcher directory to one that has only 6 months or 
so (which I had all prepped) then used the wrong spam:mbox: on. [THUD] 
And didn't notice it til my caughtspam rotated at midnight.

I'm of the theory that it is just a whacked up weekend for me.

-- 

  -Doc

  Penguins: Do it on the ice.
    9:20am  up 14 days, 18:18, 15 users,  load average: 4.27, 2.59, 1.99

  SARE HQ  http://www.rulesemporium.com/