...
> so, in contrast to 28,800 possible messages in the day, an unencumbered
> spammer could deliver between 147744 and 4060800 pieces of spam. yes,
> 28,000 messages is a lot but it's one helluva lot less than 150,000.
...
I think you'll find that most spammers are not limited by the fatness
...
> So let's
> say it's closer to 8 billion pieces of spam per day.
...
> we are still looking at
> somewhere between 30,000 and 100,000 additional machines necessary for
> spammers to be able to deliver their wares.
Total. For 8 billion pieces of spam. That's nothing.
You said it yoursel
> I am using qmail+vpopmail+maildrop to Maildirs. Like I said it does not
> happen often but I have seen it occasionally. Here are some of the headers
> from the broken message:
You should give us all headers, if possible
> X-INTM-Message-Id:
> sp-lists.com>
> X-Spam-Status: No, hits=-4.5 req
> Why not write your own wrapper front end? That's what we do (it's only a
> few lines of code - see perl.com for an example wrapper). Our wrapper
> simply returns 100 if it's spam, the first line of output being the
> score, the second being the short form of stuff to add to the headers,
> an
> >The \d's there are unnecessary, as \w includes digits. That means a
> >character class is not needed, so the regex simplifies to
> >
> > rawbody UNIQUE_BODY_ID/^(?:(?:\w{7,}-)+)\w{7,}$/
> >
> >Greg
>
> This strikes me as a bad rule. It matches any hyphenated English phrase
>
> I can't speak for Craig, but I'm sure a patch to implement adding spam
> reports by MIME-mangling would be considered.
Depending on what Rick manages to get done, maybe I'll look into doing
this over the weekend.
> Everyone pretty much agrees that SpamAssassin does one thing, and does
> it wel
> Have you gotten any response to your email (attached below for
> reference) ? I'm interested in BOTH options.
No, and I've been too busy to get around to implementing anything yet.
I'm a bit surprised nobody answered that (given the traffic on this
list).. what do people think of the idea?
-
I'd like to make two changes to how SpamAssassin behaves:
1) If a message is spam, it should not be modified, but instead be
replaced by a multipart/mixed message where the first part is
a text/plain containing the SpamAssassin report and the second
part is a message/rfc822 containing t
