Are you using spamdyke? I received several reports of this behavior
with remote servers running Microsoft Windows. The latest version
(3.0.1) fixes this problem.
-- Sam Clippinger
dnk wrote:
The only "x's" I put in was over the one IP address. Other than that, it
is as is sent.
dnk
On 10/2/07, *Jake Vickers* < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
wrote:
dnk wrote:
ok, I got access to one of the emails with the original headers,
and it had:
*Return-Path:* < [EMAIL PROTECTED]
<https://smtp.polymetmining.com/webmail/src/compose.php?send_to=JSwanson%40veitusa.com>>
*Delivered-To:* [EMAIL PROTECTED]
<https://smtp.polymetmining.com/webmail/src/compose.php?send_to=jtieberg%40polymetmining.com>
*Received:* (qmail 31841 invoked by uid 89); 2 Oct 2007 13:44:32 -0000
*Received:* by simscan 1.3.1 ppid: 31799, pid: 31803, t: 61.3814s
scanners: attach: 1.3.1 clamav: 0.90.1-exp/m:42/d:2691 spam:
3.1.8
*X-Spam-Checker-Version:* SpamAssassin 3.1.8 (2007-02-13) on
smtp.domainreceiver.com
*X-Spam-Level:* ****
*X-Spam-Status:* No, score=4.2 required=5.0
tests=MISSING_HB_SEP,MISSING_HEADERS,
MISSING_SUBJECT,TO_CC_NONE,UPPERCASE_25_50 autolearn=no
version=3.1.8
*Received:* from unknown (HELO veit?fs5.domainsender.com)
(xxx.xxx.xxx.xxx)
by smtp.domainreceiver.com <http://smtp.domainreceiver.com>
with SMTP; 2 Oct 2007 13:43:30 -0000
*Received-SPF:* none (smtp.domainreceiver.com: domain at
domainsender.com does not designate permitted sender hosts)
XXXXXXXXXX Produced By Microsoft Exchange
V6.0.6603.0*XXXXXXXXXXXXXX urn:*content-classes:message
XXXXXXXXXXXXX 1.0 XXXXXXXXXXXXX text/plain; charset="utf-8"
XXXXXXXXXXXXXXXXXXXXXXXXXX base64 XXXXXXXX Veit mtng*XXXXX
Mon, 1 Oct 2007 09:*16:23 -0500
XXXXXXXXXXX
<[EMAIL PROTECTED]> XXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXX
Veit mtng XXXXXXXXXXXXX
AcgENaV7YEgjAZ7UScyuPxY9DEidIQ== XXXXX "Sender Name" <sender@
<https://smtp.polymetmining.com/webmail/src/compose.php?send_to=JSwanson%40veitusa.com>
domainsender.com
<https://smtp.polymetmining.com/webmail/src/compose.php?send_to=JSwanson%40veitusa.com>>
XXX
< receiver@
<https://smtp.polymetmining.com/webmail/src/compose.php?send_to=jtieberg%40polymetmining.com>
domainreceiver
<https://smtp.polymetmining.com/webmail/src/compose.php?send_to=jtieberg%40polymetmining.com>.com
<https://smtp.polymetmining.com/webmail/src/compose.php?send_to=jtieberg%40polymetmining.com>
>
But I am not sure why I am getting it. Would this be due to my
server or theirs?
Looks like their Exchange machine is sending out junk to me, at
least from what I can see in the header. Did it send you the XXXX in
the headers, or did you put those in?
But if you looks at the spam rules, it is missing all kinds of
header info, so I would assume the message was missing or garbled
anyway.
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
