Thai VI

champum เขียน:รบกวนด้วยนะค่ะ

soytee เขียน:Please sent to me sir.
[email protected]
Thank you.

"Thomson Security" <[email protected]> Add to Address Book
Subject: Undeliverable mail, invalid characters in header
To: [email protected]
Date: Mon, 25 Apr 2005 15:00:04 +0000 (GMT)


INVALID HEADER (INVALID CHARACTERS OR SPACE GAP)

Non-encoded 8-bit data (char A7 hex) in message header 'Subject':
Subject: Fwd: \247\272\264\330\305 12\273\325 \272\303\324\311\321...

This nondelivery report was generated by the amavisd-new program
at host indyvss2. Our internal reference code for your message
is 26529-01-88.


WHAT IS AN INVALID CHARACTER IN MAIL HEADER?

The RFC 2822 standard specifies rules for forming internet messages.
It does not allow the use of characters with codes above 127 to be
used
directly (non-encoded) in mail header (it also prohibits NUL and bare
CR).

If characters (e.g. with diacritics) from ISO Latin or other
alphabets
need to be included in the header, these characters need to be
properly
encoded according to RFC 2047. This encoding is often done
transparently
by mail reader (MUA), but if automatic encoding is not available
(e.g.
by some older MUA) it is the user's responsibility to avoid the use
of such characters in mail header, or to encode them manually.
Typically
the offending header fields in this category are 'Subject',
'Organization',
and comment fields in e-mail addresses of the 'From', 'To' and 'Cc'.

Sometimes such invalid header fields are inserted automatically
by some MUA, MTA, content checker, or other mail handling service.
If this is the case, that service needs to be fixed or properly
configured.
Typically the offending header fields in this category are 'Date',
'Received', 'X-Mailer', 'X-Priority', 'X-Scanned', etc.

If you don't know how to fix or avoid the problem, please report it
to _your_ postmaster or system manager.


Return-Path: <[email protected]>
Your message <[email protected]> could
not be delivered to:


Message/delivery-status

Reporting-MTA: dns; indyvss2
Received-From-MTA: smtp; indyvss2.am.thmulti.com ([127.0.0.1])
Arrival-Date: Mon, 25 Apr 2005 15:00:00 +0000 (GMT)

Final-Recipient: rfc822; [email protected]
Action: delivered
Status: 2.6.0
Remote-MTA: dns; 127.0.0.1
Diagnostic-Code: smtp; 250 Ok: queued as EF2B537F92
Last-Attempt-Date: Mon, 25 Apr 2005 15:00:04 +0000 (GMT)

Text Attachment [ Download File | Save to Yahoo! Briefcase ]

Received: from dmzraw4.extranet.tce.com (dmzraw.extranet.tce.com
[157.254.234.139])
by indyvss2.am.thmulti.com (Postfix) with ESMTP id 068D037F8E
for <[email protected]>; Mon, 25 Apr 2005 15:00:00
+0000 (GMT)
Received: from web53702.mail.yahoo.com (web53702.mail.yahoo.com
[206.190.37.23])
by dmzraw4.extranet.tce.com (Postfix) with SMTP id EA02B946
for <[email protected]>; Mon, 25 Apr 2005 14:59:49
+0000 (GMT)
Received: (qmail 83585 invoked by uid 60001); 25 Apr 2005 14:59:47
-0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=yahoo.com;

b=mfZFr7ftCx5/B5kfspLy2/n8gcW0PxVY1TqiCh/yboUNUS/2ElTWDvBh8VXT7zW3QbEOm9nzDDJmywEv5HfdVFfW/yWSFllVCDiANVDQsMNjXADrqnPKARV1NJHTQbfi1tF7sVEWA83Sdan+sSgk/h3jmPx+kp/en5nPI4hexpM=
;
Message-ID: <[email protected]>
Received: from [203.188.18.188] by web53702.mail.yahoo.com via HTTP;
Mon, 25 Apr 2005 07:59:43 PDT
Date: Mon, 25 Apr 2005 07:59:43 -0700 (PDT)
From: KANCHIT PAISAN <[email protected]>
Subject: Fwd: งบดุล 12ปี บริษัทใน SET eps12year.zip ราคาปิด 25/4/05
To: [email protected], [email protected]
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-690529308-1114441183=:81079"