Hi,
these headers trigger the FORGED_MUA_OUTLOOK check on 2.64 and 3.1.0:

X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)
X-Spam-Level: *
X-Spam-Status: No, score=1.6 required=5.0 tests=BAYES_00,FORGED_MUA_OUTLOOK,
        FORGED_RCVD_HELO autolearn=no version=3.1.0
Received: from xx.yy.yu (user-broadband-wireless-2.4GHz-1.xx.yy.yu [1.2.3.4])
        by zz.yy.it (Postfix) with ESMTP id 90F881A3A14
        for <[EMAIL PROTECTED]>; Mon, 23 Jan 2006 07:52:38 +0100 (CET)
Received: from galerija2 ([192.168.13.195])
        by xx.yy.yu (kg.org.yu [192.168.13.5])
        (MDaemon.PRO.v6.8.5.R)
        with ESMTP id 1-md50000000001.tmp
        for <[EMAIL PROTECTED]>; Mon, 23 Jan 2006 07:52:57 +0100
Message-ID: <[EMAIL PROTECTED]>
From: "International" <[EMAIL PROTECTED]>
To: "L R" <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Subject: Read: ok subject line
Date: Mon, 23 Jan 2006 07:52:56 +0100
MIME-Version: 1.0
Content-Type: multipart/report;
        report-type=disposition-notification;
        boundary="----=_NextPart_000_0006_01C61FF2.05C6A910"
X-Mailer: Microsoft Outlook Express 5.50.4952.2800
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4952.2800
X-MDRemoteIP: 192.168.13.195
X-Return-Path: [EMAIL PROTECTED]
X-MDaemon-Deliver-To: [EMAIL PROTECTED]

What is wrong with these? This should be a Return Receipt sent by OE through a MDaemon SMTP server (whose behavior is to me unknown). Does it change Message-ID?!

TIA,
Paolo

Reply via email to