nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: linux-net@vger.kernel.org
To: linux-nvdimm@lists.01.org
Subject: Report
Date: Tue, 12 Dec 2017 11:23:16 +0800	[thread overview]
Message-ID: <20171212031840.0B426221EA0C0@ml01.01.org> (raw)

This Message was undeliverable due to the following reason:

Your message was not delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message was not delivered within 8 days:
Host 63.117.221.157 is not responding.

The following recipients did not receive this message:
<linux-nvdimm@lists.01.org>

Please reply to postmaster@vger.kernel.org
if you feel this message to be in error.



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

             reply	other threads:[~2017-12-12  3:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12  3:23 linux-net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-08-31 10:33 Report Returned mail
2018-08-31 10:33 Report Returned mail
2018-05-24  3:03 report Automatic Email Delivery Software
2018-05-24  3:03 report Automatic Email Delivery Software
2018-03-23  3:41 Report Mail Delivery Subsystem
2018-03-23  3:41 Report Mail Delivery Subsystem
2018-03-05  3:32 report The Post Office
2018-03-05  3:32 report The Post Office
2017-12-12  3:23 Report linux-net-u79uwXL29TY76Z2rM5mHXA
2017-08-21  3:12 report Automatic Email Delivery Software
2017-08-21  3:12 report Automatic Email Delivery Software
2016-08-30  6:05 report Post Office

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=20171212031840.0B426221EA0C0@ml01.01.org \
    --to=linux-net@vger.kernel.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).