Re: avoiding Spam rules when building emails

Giganews Newsgroups
Subject: Re: avoiding Spam rules when building emails
Posted by:  Remy Lebeau (TeamB) (no.spam@no.spam.com)
Date: Thu, 14 Apr 2005

"John Evans" <johneva…@clear-Advantage.co.uk> wrote in message
news:CDA6C0F809C7E240johneva…@clear-Advantage.co.uk...

> 2.35 MIME_BOUND_RKFINDY    Spam tool pattern in MIME boundary (rfkindy)

A lot of spammers use Indy, so anti-spam tools usually flag Indy messages
immediately, even if they aren't really spam.  Nothing you can do about that
one.

> 1.70 MSGID_FROM_MTA_ID      Message-Id for external message added locally

I don't know about that one.

> 1.50 MPART_ALT_DIFF        BODY: HTML and text parts are different

Your plain text needs to match what the HTML would actually look as plain
text.  If you just throw in any plain text you wish, it will probably not
pass through anti-spam tools.

>          memo1.clear;
>          with Tidtext.Create(email.MessageParts, memo1.lines) do
>          begin
>            ContentType := 'text/plain';
>          end;

You cleared the Memo and then immediately added the empty text to the
TIdText.  That will produce an empty text part in the generated email.  That
is probably what is flagging the anti-spam tools the most.

>          memo1.Lines.Add(emailtext.Text);  // this is just copying the
> separately built html into a memo component.
>          with Tidtext.Create(email.MessageParts, memo1.lines) do
>          begin
>            ContentType := 'text/html';
>          end;

Rather than adding the HTML back into the Memo, you could just add it to the
TIdText directly:

    with TIdtext.Create(email.MessageParts, nil) do
    begin
        Body.Text := emailtext.Text
        ContentType := 'text/html';
    end;

Gambit

Replies

In response to

avoiding Spam rules when building emails posted by John Evans on Thu, 14 Apr 2005