nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Mail Delivery Subsystem" <postmaster@lists.01.org>
To: linux-nvdimm@lists.01.org
Subject: Message could not be delivered
Date: Sat, 9 Dec 2017 12:47:22 +0800	[thread overview]
Message-ID: <20171209044246.378DD2214E32E@ml01.01.org> (raw)

The original message was included as attachment

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

             reply	other threads:[~2017-12-09  4:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-09  4:47 Mail Delivery Subsystem [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-03  2:14 Message could not be delivered Automatic Email Delivery Software
2019-09-03  2:14 Automatic Email Delivery Software
2019-04-26  3:38 Automatic Email Delivery Software
2019-04-25  3:46 Bounced mail
2019-04-18  4:01 Returned mail
2019-04-04 11:26 MESSAGE COULD NOT BE DELIVERED michael-k-KJX8L1YACloTKYOLMXNBRxrm3jAUxWOA
2018-05-11  6:55 Automatic Email Delivery Software
2018-04-26  3:06 Message could not be delivered Mail Administrator
2018-04-26  3:06 Mail Administrator
2018-03-26  3:53 Post Office
2018-03-26  2:46 Mail Delivery Subsystem
2018-03-26  2:46 Mail Delivery Subsystem
2018-03-08  3:27 The Post Office
2018-03-08  3:27 The Post Office
2018-02-07 13:08 MESSAGE COULD NOT BE DELIVERED MAILER-DAEMON
2018-02-07 13:08 MAILER-DAEMON
2017-12-09  4:47 Message could not be delivered Mail Delivery Subsystem
2017-04-19 14:46 buildinfo
2017-04-19 14:46 buildinfo-s4a7dU60G1rB75U6l8LB6Q
2017-04-04  4:41 Bounced mail
2017-04-04  4:41 Bounced mail
2016-09-07  6:49 Mail Administrator
2016-09-07  6:49 Mail Administrator

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=20171209044246.378DD2214E32E@ml01.01.org \
    --to=postmaster@lists.01.org \
    --cc=linux-nvdimm@lists.01.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).