linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: postmaster@intel.com
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Delivery Status Notification (Failure)
Date: Wed, 12 May 2004 02:46:19 -0700	[thread overview]
Message-ID: <gtZKpjE5a0009ef3a@fmsmsx332.amr.corp.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 146 bytes --]

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

       mike.stephens@intel.com




[-- Attachment #2: Type: message/delivery-status, Size: 220 bytes --]

[-- Attachment #3: Type: message/rfc822, Size: 2201 bytes --]

[-- Attachment #3.1.1: Type: text/plain, Size: 497 bytes --]


Protected Mail System Test.



===========================================================================
WARNING:In accordance with Intel's security policy this email
has been modified.

The file attachment data.rtf                                                                           .scr is a restricted file type and has been removed from
 the following message: Re: Extended Mail.  If you require this file, please contact the sender
 and arrange an alternate means of receiving it.



             reply	other threads:[~2004-05-12  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12  9:46 postmaster [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-12 12:56 Delivery Status Notification (Failure) postmaster
2004-04-27 14:35 postmaster
2004-04-08  4:10 postmaster
2004-03-29 10:33 postmaster
2004-03-15 19:16 postmaster
2003-09-01 21:31 postmaster
2003-08-27 22:58 postmaster

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=gtZKpjE5a0009ef3a@fmsmsx332.amr.corp.intel.com \
    --to=postmaster@intel.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).