> On 4 Dec 2003 07:40:04 -0800, [email]vangelobin.tum.de[/email] (murph) wrote:
> >Sebastian Jaenicke <sjaenicktechfak.uni-bielefeld.de> wrote in message news:<slrnbsq2q7.8ko.sjaenickazathoth.jaenicke.or g>...
> >> * murph <vangelobin.tum.de> wrote:
> >> [..]
> >> > But the problem is that spamassassin performs all the tests and not
> >> > only that specified in the user_prefs file .Is it a standart procedure
> >> > by SpamAssassin.
> >> SpamAssassin always uses all available tests (except non-local checks
> >> like e.g. DNS blacklists, which can be disabled separately). If you
> >> don't want to use some specific tests, you can adjust their scores
> >> in your ~/.spamassassin/user_prefs file to 0.
> >> See the SpamAssassin home page for further doentation.
> >> - Sebastian
> >thank you for the help
> >now everything looks OK
> >i have some more questions
> >1) Why the spamer use invisible fonts in HTML
> So you can't see the words when you open the message.
> >i thought that is from the generator of the email, something like the
> >ID of the email .But i saw a spam mail and the words were not without
> >sense ?
> Many spamkiller programs compare the email in question to a known database of
> spam emails, and grade the sample email according to if it matches or not.
> Spammers know this, and try to make their spam email different enough from the
> known spam so as to not be caught by this comparison technique. They do this by
> adding random words, phrases, or character sequences to the email, in order to
> change the contents enough to fail the comparison. Since these words would
> intefere with the human reader's ability to comprehend the email, spammers try
> to hide them from view by imbedding them as html comments, or as invalid html
> tags, or as invisible text within the body of the email.
> >2) I want to add some new tests to Spamassassin
> >Is it possible and how can i do it ?
> >Should i change the /usr/share/spamassassin/ files ?
> It is possible. See 'perldoc Mail::SpamAssassin::Conf' for details on the
> configuration file options, and make your own tests up as a seperate file in
> /usr/share/spamassassin. You also want to read the spamassassin(1) manpage; it
> gives some hints about naming and placement of your local grading file within
> the spamassassin file hierarchy.