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.0tests=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 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]
domainsender.com>    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?

Dnk

On 10/1/07, Jake Vickers <[EMAIL PROTECTED]> wrote:
>
> dnk wrote:
> > Hi there, I have a user on one of my toasters that got an email like
> this:
> >
> > -----Original Message-----
> > From:
> > Sent: None
> > Subject:
> >
> >
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> >
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> > X
> >
> >
> >
> > Has anyone seen that before? They are asking me why it happened, and
> > it is not something I am familiar with.
> >
>
> Look at the headers of the message. I've seen messages like this before,
> but I generated them myself (manually logged into SMTP and typed a user
> to send the message to and a message to test SMTP) - I've also generated
> messages like this when I manually inject a message into the queue.
> You'll know more when you see the full headers.
>
>
>

Reply via email to