From: "Mail Delivery Subsystem" <noreply-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: Message could not be delivered
Date: Mon, 26 Mar 2018 10:46:24 +0800 [thread overview]
Message-ID: <20180326024011.C7DFE224CCC14@ml01.01.org> (raw)
The original message was received at Mon, 26 Mar 2018 10:46:24 +0800
from lists.01.org [65.54.123.48]
----- The following addresses had permanent fatal errors -----
<linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
----- Transcript of session follows -----
while talking to lists.01.org.:
>>> MAIL From:"Mail Delivery Subsystem" <noreply-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
<<< 501 "Mail Delivery Subsystem" <noreply-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>... Refused
next reply other threads:[~2018-03-26 2:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 2:46 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-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-12-09 4:47 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=20180326024011.C7DFE224CCC14@ml01.01.org \
--to=noreply-hn68rpc1hr1g9huczpvpmw@public.gmane.org \
--cc=linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.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).