procmail
[Top] [All Lists]

counting "Content-Transfer-Encoding:"

1999-12-16 23:35:57
On 17 December 1999, Marc Lev <Mlev(_at_)yahoo(_dot_)com> wrote:
[...]
Date: Fri, 17 Dec 1999 01:54:05 +0100 (MET)
From: Marc Lev <Mlev(_at_)yahoo(_dot_)com>
To: <procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de>
Message-Id: <419(_dot_)436510(_dot_)82438715Mlev(_at_)yahoo(_dot_)com>
Subject: This little ad will change your life.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"4kqun.A.c_E.-mYW4"@campino>
Resent-From: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
X-Mailing-List: <procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de> 
archive/latest/22844
X-Loop: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
Precedence: list
Resent-Sender: procmail-request(_at_)informatik(_dot_)rwth-aachen(_dot_)de
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
[...]

    Given the content of the spam I've been receiving lately, I was
considering using something like this:

    :0:
    * ^Content-Transfer-Encoding: 7bit$Content-Transfer-Encoding: 7bit$
    spam

    Then I found out the (apparently valid) followup to the above
message matches the same recipe:

On 16 December 1999, Bill Gray <wjgray(_at_)cup(_dot_)hp(_dot_)com> wrote:
[...]
Reply-To: <wjgray(_at_)cup(_dot_)hp(_dot_)com>
From: "Bill Gray" <wjgray(_at_)cup(_dot_)hp(_dot_)com>
To: "Marc Lev" <Mlev(_at_)yahoo(_dot_)com>, 
<procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de>
Subject: RE: This little ad will change your life.
Date: Thu, 16 Dec 1999 18:03:13 -0800
Message-ID: <000001bf4832$e0067ef0$b2894b0f(_at_)cup(_dot_)hp(_dot_)com>
MIME-Version: 1.0
Content-Type: text/plain;
      charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
Importance: Normal
In-Reply-To: <419(_dot_)436510(_dot_)82438715Mlev(_at_)yahoo(_dot_)com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"0PfSf.A.CkF.wnZW4"@campino>
Resent-From: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
X-Mailing-List: <procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de> 
archive/latest/22845
X-Loop: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
Precedence: list
Resent-Sender: procmail-request(_at_)informatik(_dot_)rwth-aachen(_dot_)de
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
[...]

    So my question is: how safe is the above recipe?  Does MS LookOut!
add two "Content-Transfer-Encoding:"s these days?  Other comments?

    Regards,

    Liviu Daia

-- 
Dr. Liviu Daia               e-mail:   Liviu(_dot_)Daia(_at_)imar(_dot_)ro
Institute of Mathematics     web page: http://www.imar.ro/~daia
of the Romanian Academy      PGP key:  http://www.imar.ro/~daia/daia.asc

<Prev in Thread] Current Thread [Next in Thread>