> On Thu, 19 Aug 2004, Kristian Davies wrote:
>
> >
> >
> > >updating sa2.63 to 2.64 (perl 5.8.3 solaris 5.9 sparc):
> > >installed Mail-SpamAssassin-SpamCopURI-0.22 and copied
> > >rules/spamcop_uri.cf into /etc/mail/spamassassin
> >
> > >'make test' says:
> >
> > [...]
> >
> >
> >
> > >Failed to
> Hmm. I disagree. For three of the machines, I _know_ there is no
> port 80 blocking.
>
> > It might be useful if you could show us which tests are failing,
> > but I assume it's the same redirection-handling ones that other
> > people have mentioned.
>
> Yup. Same set:
>
> t/blacklist.
BTW, imap access to Public folders works also. They are addressed like
"Public Folders/spam" for example.
Combine Mail::IMAPClient and Mail::SpamAssassin mix well and learn away.
-steve halligan
http://www.333tech.com
http://sguil.sf.net
> Interesting suggestion. I haven't thought of that.
>
>
> > Received: from mta5.fibertel.com.ar ([24.232.0.159]:43916 "EHLO
> > mail.fibertel.com.ar" whoson: "-unregistered-") by
> dedos.pert.com.ar
> > with ESMTP id ; Mon, 29 Mar 2004 18:26:46 -0300
>
> ick! We don't have support for this Received-header format
> in our code,
> that's th
> How does this cope with say a list of names. There are many
> reasons for
> sending out lists of names and I think the rule above would consider
> them spam ?
>
> Ron
What are the chances that a list of names would not include any
punctuation?
Also, as another replier suggested, and as was m
>
> In general a good idea, but note that it is NOT just looking
> for lower case
> letters. \w matches [a-zA-Z_], so you're actually matching
> uppercase too. And
> you might find it faster to use non-matching parens. Also,
> there's no reason
> to do the {6,}, since if it'll match 6 even
> Hi all!
>
> Since a while I am getting a ton of messages like this:
>
>
>
> Until now I've been unable to find good way to tag them. But I noticed
> that what they all have in common is the complete absence of
> two-chars
> long words and a very few three-chars long word (if compared with
