From: postmaster@optibase.com
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Delivery Status Notification (Failure)
Date: Tue, 2 Sep 2003 00:31:28 +0300 [thread overview]
Message-ID: <lSgpzOcAr000077d0@ltde2k.optibase.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 143 bytes --]
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed.
csh@viewgraphics.com
[-- Attachment #2: Type: message/delivery-status, Size: 203 bytes --]
[-- Attachment #3: Type: message/rfc822, Size: 1715 bytes --]
[-- Attachment #3.1.1: Type: text/plain, Size: 33 bytes --]
See the attached file for details
[-- Attachment #3.1.2: Type: text/plain, Size: 109 bytes --]
We have removed document_9446.pif from this email because it is not part of Optibase content security policy.
[-- Attachment #3.1.3: Type: text/plain, Size: 109 bytes --]
We have removed document_9446.pif from this email because it is not part of Optibase content security policy.
next reply other threads:[~2003-09-01 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 21:31 postmaster [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-12 12:56 Delivery Status Notification (Failure) postmaster
2004-05-12 9:46 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-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=lSgpzOcAr000077d0@ltde2k.optibase.com \
--to=postmaster@optibase.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).