From: Roger.Ling@mitac-mkl.com.cn
To: <linux-kernel@vger.kernel.org>
Subject: Mail delivery failure
Date: Wed, 30 Apr 2003 17:19:52 +0800 [thread overview]
Message-ID: <S261886AbTD3JIP/20030430090815Z+920@vger.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
****** Message from InterScan E-Mail VirusWall NT ******
Sent >>> RCPT TO: <Roger.Ling@mitac.com.cn>
Received <<< 550 <Roger.Ling@mitac.com.cn>, Recipient unknown
Could not deliver mail to this user.
***************** End of message ***************
[-- Attachment #2: Type: message/rfc822, Size: 1488 bytes --]
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2.1.1: Type: text/plain; charset="gb2312", Size: 167 bytes --]
ÕâÊÇÓʼþ»ØÖ´£¬ÊÕ¼þÈË:
"AdminMKL [À¥ß_ϵ½y¹ÜÀíT]" <AdminMKL@mic.com.tw> ÓÚ 2003-4-30 17:07
´Ë»ØÖ´±íÃ÷¸ÃÓʼþÒѾÏÔʾÔÚÊÕ¼þÈ˵ļÆËã»úÉÏÁË£¬ÏÔʾʱ¼ä: 2003-4-30 17:09
[-- Attachment #2.1.2: Type: message/disposition-notification, Size: 187 bytes --]
next reply other threads:[~2003-04-30 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 9:19 Roger.Ling [this message]
2003-04-30 9:56 Mail delivery failure Roger.Ling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=S261886AbTD3JIP/20030430090815Z+920@vger.kernel.org \
--to=roger.ling@mitac-mkl.com.cn \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).