It seems to
be happening when staff are
not in the office when they send the mail. When they are out of office
they connect to email either through webmail or use outlook same as
always but
use an outside ISP. In some cases, they have to use some mail proxy
server as some of the ISPs are blocking access to port 25 on servers
that are
not their own.
X-Declude-Sender:
[EMAIL PROTECTED] [127.0.0.1]
X-Declude-Sender:
[EMAIL PROTECTED] [32.97.166.48]
The first time around
it shows the
local loop address and the second time around the dial-up ISP (att
global) address.
Should I still be getting this if I use Whitelist Auth? I’ve even
whitelisted specific users and still their messages sometimes get
caught.
Shouldn’t whitelist
take care
of incoming and not outgoing? Should I just turn off outgoing tests?
I seem to have
misplaced the
original message, but here are the headers of another message that
follows the
same rules. It wasn’t scanned twice, but it doesn’t show as
whitelisted either.
Received:
from DTRAYOWCRO001.pngxnet.com
[209.87.233.98] by ute-sei.org with ESMTP
(SMTPD32-8.15) id A4071060152; Tue,
07 Jun 2005 08:33:11 -0400
Received:
from UTENP01 ([10.255.255.142])
by
DTRAYOWCRO001.pngxnet.com (8.12.4/8.12.4) with ESMTP id j57CfnGK023801
for
<[EMAIL PROTECTED]>; Tue, 7 Jun 2005 08:41:53 -0400
From: "Betty
Bannon"
<[EMAIL PROTECTED]>
To:
<[EMAIL PROTECTED]>
Subject: FW:
FW: utelocals distribution
list
Date: Tue, 7
Jun 2005 08:41:36 -0400
Message-ID:
<[EMAIL PROTECTED]>
MIME-Version:
1.0
Content-Type:
text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding:
quoted-printable
X-Priority:
3 (Normal)
X-MSMail-Priority:
Normal
X-Mailer:
Microsoft Outlook, Build
10.0.6626
Importance:
Normal
X-MimeOLE:
Produced By Microsoft MimeOLE
V6.00.2900.2180
X-Declude-Sender:
[EMAIL PROTECTED]
[209.87.233.98]
X-Declude-Spoolname:
D94070106015219BF.SMD
X-Declude-Note:
Scanned by Declude 2.0.6
(http://www.declude.com/x-note.htm) for spam.
X-Declude-Scan:
Score [-5] at 08:33:13 on
07 Jun 2005
X-Declude-Tests:
None
X-Country-Chain:
CANADA->destination
X-RCPT-TO:
<[EMAIL PROTECTED]>
Status: U
X-UIDL:
418092265
-----Original
Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On
Behalf Of Matt
Sent: June 7, 2005
10:42 AM
To:
[email protected]
Subject: Re:
[Declude.JunkMail]
X-RBL-Warning // Whitelisted but not
Susan
Duncan wrote:
That still
doesn’t
explain why someone who is whitelisted still has some of their email
caught.
That's
not the issue,
they aren't actually both happening at the same time. It's being
double
scanned, and it is only being whitelisted when it is being sent, but
not when
it is received (over one minute later according to your logs). The
full
headers should have showed the complete path that the E-mail took and
it would
be easier to diagnose if they were shared (the Received lines). I'm
thinking that maybe this E-mail was sent from your server to an address
on
another server that was actually forwarded back to her address on your
server. That's the only way that I can think of that would generate
two
different spool file names, and cause it to be scanned twice by Declude
in this
way; adding headers each time.
Matt
--
=====================================================
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=====================================================
