[Spambayes] Domain name contains the word "spam".

[Bill Hely]

This probably needs to be targeted to Tony Meyer.

Tony?

TIA
 - Bill H.


> -----Original Message-----
> From: spambayes-bounces at python.org
> [mailto:spambayes-bounces at python.org] On Behalf Of Bill Hely
> Sent: Tuesday, March 14, 2006 12:38 PM
> To: spambayes at python.org
> Subject: Re: [Spambayes] Domain name contains the word "spam".
>
>
>
> Thanks very much for your help guys.
>
> Clarification: I am not using Outlook Express. I am writing
about
> it - well, SpamBayes actually - so changing clients (always my
> own first recommendation) is not an option for this exercise.
> Anyway, I am using Outlook Express as the example for all
clients
> that can't use the Outlook plug-in, as there would have to be
> more Outlook Express out there than all the rest put together.
> It's a case of satisfy the majority first.
>
> Skip: "spam," in the TO line doesn't work. What's actually
placed
> in the TO line is "spam;" and you can't filter on the
semi-colon.
>
> The best I have been able to come up with so far is to have a
> filter with two conditions: "spam" in the TO line AND "spam,"
in
> the Subject. The comma helps a little (thanks Skip, I missed
> that) but is obviously not rigidly exclusive.
>
> Tony: I see what you mean about the bug in 1.0.4 - I tried
every
> which-way to get it to work, but it seems that you just cannot
> change the displayed values that are annotated to the TO or
> Subject lines. Any edits to the "notate_to:" lines results in
no
> annotation at all. Since Outlook Express' filters can't read
the
> X-Spambayes-Classification value in the eMail header, this
> doesn't seem to be solvable at the moment.
>
> So the important question for me now is: How far off is the
> release of 1.1.x, complete with an installer executable? I'm
> reluctant to look into the CVS alternative, as I think it
> complicates matters too much for my target audience.
>
> For my own information, to go the CVS route, would I have to
> install Python and download the 12 files at:
> http://cvs.sourceforge.net/viewcvs.py/spambayes/spambayes/ then
> run setup.py, or is it more complex than that? Sorry, never
> encountered Python before SpamBayes.
>
> BTW, is there any documentation available on the legal entries
> for bayescustomize.ini? My INI file did not contain some of the
> entries that Skip showed. If no documentation, what does
> "include_evidence: True" do?
>
> Many thanks for your help.
>
>  - Bill H.
>
> > -----Original Message-----
> > From: Tony Meyer [mailto:tameyer at ihug.co.nz]
> > Sent: Tuesday, March 14, 2006 6:15 AM
> > To: skip at pobox.com
> > Cc: bill.hely at helyholdings.com; spambayes at python.org
> > Subject: Re: [Spambayes] Domain name contains the word
"spam".
> >
> >
> > [Bill Hely]
> > >> I own a domain with "spam" in the domain name so, because
of
> the
> > >> way the proxy brands eMail, the Outlook Express rules trap
> all
> > >> messages to that domain as spam.
> > >>
> > >> I tried changing the [Headers]notate_to: item in
> > >> bayescustomize.ini to something more unique, but that
didn't
> work.
> >
> > The string that is added is the value in [Headers]
> > header_spam_string.  It will get added iff [Headers]
notate_to
>
> > contains that string.
> >
> > IIRC 1.0.4 has a bug with this that means you'll find it hard
> to set
> > both.  This is fixed in CVS, so if 1.0.4 doesn't have the
fix,
> you
> > might have to move to that.  CVS also has a better notate_to
> system
> > (see below), so that could also solve your problem.
> >
> > >> The Outlook Express how-to document suggests there is a
> > >> work-around, so...
> > >>
> > >> What is it please?
> >
> > Don't use Outlook Express <0.5 wink>.
> >
> > [Skip]
> > > I'm not a Windows nor an Outlook Express user, so take this
> with a
> > > grain of
> > > salt...  You might try annotating the subject instead of
> > the to field
> > > (option: notate_subject).
> >
> > That would certainly work.  The catch then is if you have
other
> mail
> > whose subject that starts with "spam,".  (Note that you
should
>
> > include the comma in the rule, to avoid catching just
"spam").
> >
> > > Finally, make sure that Outlook Express's filter rule is
> properly
> > > restrictive.  It should be filtering on "spam,", not just
> > "spam".  You
> > > shouldn't see "spam," in a domain name.
> >
> > Note that in 1.1 the 'notate to' system has changed somewhat,
> > so that
> > it adds header_spam_string at spambayes.invalid.  This both
makes
> it
> > easier to catch without false positives, and doesn't break
the
> rules
> > of the To: header.  IIRC Outlook Express considers the comma
in
> the
> > To header a recipient delimiter, so "spam" (no comma) will be
a
>
> > recipient, and I'm not sure if you can filter to include the
> > comma or
> > not.
> >
> > =Tony.Meyer

--
We take security very seriously.
All outgoing mail is scanned and
certified Virus Free before transmission.

Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.2.3/281 - Release Date:
14/03/2006