Bowie Bailey wrote:
> Matt Kettler wrote:
>
>> [EMAIL PROTECTED] wrote:
>>
>>> Philip Prindeville wrote:
>>>
> header L_INCOMPETENT1ALL =~ /\\r\\n/
>
> header L_INCOMPETENT2ALL =~ /\\r\\n\s?$/
>
> header L_INCOMPETENT3ALL =~ /\\
Matt Kettler wrote:
> [EMAIL PROTECTED] wrote:
> > Philip Prindeville wrote:
> > > > header L_INCOMPETENT1ALL =~ /\\r\\n/
> > > >
> > > > header L_INCOMPETENT2ALL =~ /\\r\\n\s?$/
> > > >
> > > > header L_INCOMPETENT3ALL =~ /\\r\\n\s?\n/
> > > Ok, I tried #3 and
Philip Prindeville wrote:
> Matt Kettler wrote:
>
>> Philip Prindeville wrote:
>>
>>
>>> Matt Kettler wrote:
>>>
>>>
>>>
Philip Prindeville wrote:
> Matt Kettler wrote:
>
>
>
>
>> Perhaps you want somethin
Matt Kettler wrote:
>Philip Prindeville wrote:
>
>
>>Matt Kettler wrote:
>>
>>
>>
>>>Philip Prindeville wrote:
>>>
>>>
>>>
>>>
Matt Kettler wrote:
>>>
>>>
>>>
>>>
>Perhaps you want something more like:
>
>header L_INCOMPETENT
[EMAIL PROTECTED] wrote:
> Philip Prindeville wrote:
>>> header L_INCOMPETENT1ALL =~ /\\r\\n/
>>>
>>> header L_INCOMPETENT2ALL =~ /\\r\\n\s?$/
>>>
>>> header L_INCOMPETENT3ALL =~ /\\r\\n\s?\n/
>> Ok, I tried #3 and it worked, as you said... But leaving the \s?
>
Philip Prindeville wrote:
>> header L_INCOMPETENT1ALL =~ /\\r\\n/
>>
>> header L_INCOMPETENT2ALL =~ /\\r\\n\s?$/
>>
>> header L_INCOMPETENT3ALL =~ /\\r\\n\s?\n/
>
> Ok, I tried #3 and it worked, as you said... But leaving the \s?
> didn't.
>
> I'm confused.
Philip Prindeville wrote:
> Matt Kettler wrote:
>
>> Philip Prindeville wrote:
>>
>>
>>> Matt Kettler wrote:
>>>
>>>
>>
>>
Perhaps you want something more like:
header L_INCOMPETENTALL =~ /\\r\\n\s?$/
>> Scratch my last email. $ doesn't work with
Matt Kettler wrote:
>Philip Prindeville wrote:
>
>
>>Matt Kettler wrote:
>>
>>
>
>
>
>>>Perhaps you want something more like:
>>>
>>>header L_INCOMPETENTALL =~ /\\r\\n\s?$/
>>>
>>>
>
>Scratch my last email. $ doesn't work with ALL.
>
>I just tested 3 variants:
>
>header L
Philip Prindeville wrote:
> Matt Kettler wrote:
>> Perhaps you want something more like:
>>
>> header L_INCOMPETENTALL =~ /\\r\\n\s?$/
Scratch my last email. $ doesn't work with ALL.
I just tested 3 variants:
header L_INCOMPETENT1ALL =~ /\\r\\n/
header L_INCOMPETENT2
Philip Prindeville wrote:
> Matt Kettler wrote:
>> Perhaps you want something more like:
>>
>> header L_INCOMPETENTALL =~ /\\r\\n\s?$/
>>
>> The $ forces end-of-line match, and the \s? allows any single whitespace to
>> be
>> inserted before the actual EOL.
>>
>>
>>
>>
>
> I know t
Matt Kettler wrote:
>Philip Prindeville wrote:
>
>
>>Theo Van Dinter wrote:
>>
>>
>>
>>>The malformed content-type header caused this. The MIME part isn't
>>>"text/html", it's "text/htmlcontent-transfer-encoding8bitrn". So the best
>>>that can happen is URLs are parsed out of the text.
>>>
Philip Prindeville wrote:
> Theo Van Dinter wrote:
>
>> The malformed content-type header caused this. The MIME part isn't
>> "text/html", it's "text/htmlcontent-transfer-encoding8bitrn". So the best
>> that can happen is URLs are parsed out of the text.
>>
>>
>
> Ok, we'll here's a new rule:
Philip Prindeville wrote:
>Theo Van Dinter wrote:
>
>
>
>>The malformed content-type header caused this. The MIME part isn't
>>"text/html", it's "text/htmlcontent-transfer-encoding8bitrn". So the best
>>that can happen is URLs are parsed out of the text.
>>
>>
>>
>>
>
>Ok, we'll here's a
Theo Van Dinter wrote:
>The malformed content-type header caused this. The MIME part isn't
>"text/html", it's "text/htmlcontent-transfer-encoding8bitrn". So the best
>that can happen is URLs are parsed out of the text.
>
>
Ok, we'll here's a new rule:
# incompetent spamware programmers...
he
Philip Prindeville wrote:
Doesn't RFC-822 require that the addresses be bracketed? Or is that
only when a comment string is present?
Only when there's a comment.
--
Kelson Vibber
SpeedGate Communications
Philip Prindeville wrote:
> Theo Van Dinter wrote:
>
>>> Well, for a start, normally the X-Spam-* stuff gets inserted at the very
>>>
>>> end of the header block, but what I'm seeing instead is:
>>>
>>>
>> You're running 3.1 which puts them at the top of the headers. It was in the
>> 3.1.0 re
Philip Prindeville wrote:
things would be a little clearer if there was a consistent place that the
X-Spam-*: stuff got inserted at... It seems to move around.
IIRC this is the first time it's moved in the lifetime of the product,
but perhaps I've forgotten another occasion...
--
Kelson Vib
Theo Van Dinter wrote:
>> Well, for a start, normally the X-Spam-* stuff gets inserted at the very
>>
>>end of the header block, but what I'm seeing instead is:
>>
>>
>
>You're running 3.1 which puts them at the top of the headers. It was in the
>3.1.0 release announcement:
>
>- modify header
On Wed, Apr 05, 2006 at 01:46:08PM -0600, Philip Prindeville wrote:
> >What gives you that idea? The debug output clearly shows the received
> >headers
> >being parsed, the mime parser finds the message part (malformed content-type
> >and all), URIs are parsed out of the message, etc.
>
> Well,
Matt Kettler wrote:
Philip Prindeville wrote:
What gives you that idea? The debug output clearly shows the received headers
being parsed, the mime parser finds the message part (malformed content-type
and all), URIs are parsed out of the message, etc.
Well, for a start, normally the X-Spam-
Matt Kettler wrote:
> Erm.. When do you see SA inserting X-Spam-* at the END of the header
> block???
SA doesn't (anymore.) MIMEDefang does, when using action_add_header, which
calls libmilter's smfi_addheader function. Recent versions of MIMEDefang have
action_insert_header, which can be use
Philip Prindeville wrote:
>
>>>
>> What gives you that idea? The debug output clearly shows the received
>> headers
>> being parsed, the mime parser finds the message part (malformed content-type
>> and all), URIs are parsed out of the message, etc.
>>
>>
>
> Well, for a start, normally the X
Philip Prindeville wrote:
> The following message got through and I couldn't figure out why:
>
> ftp://ftp.redfish-solutions.com/pub/paypal4.eml
>
> so I ran:
>
> spamassassing -x -LD
>
> on it and saved the output into:
>
> ftp://ftp.redfish-solutions.com/pub/paypal4.log
>
> what's odd is th
Theo Van Dinter wrote:
>On Wed, Apr 05, 2006 at 01:30:20PM -0600, Philip Prindeville wrote:
>
>
>>The following message got through and I couldn't figure out why:
>>
>>ftp://ftp.redfish-solutions.com/pub/paypal4.eml
>>
>>
>
>The first problem is that the headers are a bit malformed:
>
>MIME-
On Wed, Apr 05, 2006 at 01:30:20PM -0600, Philip Prindeville wrote:
> The following message got through and I couldn't figure out why:
>
> ftp://ftp.redfish-solutions.com/pub/paypal4.eml
The first problem is that the headers are a bit malformed:
MIME-Version: 1.0 Content-Type: text/html\r\n
Con
The following message got through and I couldn't figure out why:
ftp://ftp.redfish-solutions.com/pub/paypal4.eml
so I ran:
spamassassing -x -LD
on it and saved the output into:
ftp://ftp.redfish-solutions.com/pub/paypal4.log
what's odd is that it reads the first line (the Return-Path:) line a
26 matches
Mail list logo
