> So... to report the original spam to razor, I have to unmunge this whole
> mess. Sigh...
>
> Miles
There are often reasons to not report spam to razor. This might just be one
of those situations.
--
Duncan Findlay
___
Spamassassin-talk mailing li
Dan,
On Tue, 9 Apr 2002, Daniel Liston wrote:
> Here is another idea, and requires monitoring, but is easier than
> trying to unmunge a majordomo bounce to a spammer;
>
> /etc/aliases
> majordomo: "|/usr/lib/majordomo/wrapper majordomo",filename
>
> Filename is actually an archive of all message
Here is another idea, and requires monitoring, but is easier than
trying to unmunge a majordomo bounce to a spammer;
/etc/aliases
majordomo: "|/usr/lib/majordomo/wrapper majordomo",filename
Filename is actually an archive of all messages sent to the
majordomo address.
Dan Liston
Miles Fidelman
Theo,
On Tue, 9 Apr 2002, Theo Van Dinter wrote:
> majordomo doesn't actually change anything. the bounce is essentially a new message
>with the old
> message as the body. so you could do something like this:
>
> perl -nle 'next if (1../^\s*$/) or /^>From /; print;' < bounce > fresh
>
> > So.
On Tue, Apr 09, 2002 at 01:55:26PM -0400, Miles Fidelman wrote:
> - strip off both the spamassassin markup (easy - pipe through spamassassin
> -d), AND...
or tell SA to not filter majordomo bounce mails
> - remove the stuff that majordomo changes (headers, BOUNCE info, etc.)
majordomo doesn't a
To any of you gurus who understand both majordomo and spamassassin:
I run several small email lists that people try to spam every once in a
while. The general result is that:
- 1. majordomo bounces the spam, because it doesn't come from a list
member
- 2. spamassassin catches the bounce message
