From: Mail Delivery Subsystem <MAILER-DAEMON@mx0b-0019e102.pphosted.com>
To: <linux-coco@lists.linux.dev>
Subject: Returned mail: see transcript for details
Date: Sat, 27 Aug 2022 21:03:14 GMT [thread overview]
Message-ID: <202208272103.27RL3E6Q013083@mx0b-0019e102.pphosted.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
The original message was received at Sat, 27 Aug 2022 21:03:14 GMT
from m0074417.ppops.net [127.0.0.1]
----- The following addresses had permanent fatal errors -----
<pelcoservice-shanghai@pelco.com>
(reason: 550-5.1.1 The email account that you tried to reach does not exist. Please try)
----- Transcript of session follows -----
... while talking to aspmx.l.google.com.:
>>> DATA
<<< 550-5.1.1 The email account that you tried to reach does not exist. Please try
<<< 550-5.1.1 double-checking the recipient's email address for typos or
<<< 550-5.1.1 unnecessary spaces. Learn more at
<<< 550 5.1.1 https://support.google.com/mail/?p=NoSuchUser y195-20020a814bcc000000b00340c82a1872si1084437ywa.317 - gsmtp
550 5.1.1 <pelcoservice-shanghai@pelco.com>... User unknown
<<< 503 5.5.1 RCPT first. y195-20020a814bcc000000b00340c82a1872si1084437ywa.317 - gsmtp
[-- Attachment #2: Type: message/delivery-status, Size: 468 bytes --]
[-- Attachment #3: Type: message/rfc822, Size: 6231 bytes --]
[-- Attachment #3.1: Type: text/html, Size: 3117 bytes --]
From: "4C9f00e" <linux-coco@lists.linux.dev>
To: "PelcoService-Shanghai" <PelcoService-Shanghai@pelco.com>
Date: Sun, 28 Aug 2022 05:03:14 +0800
Message-ID: <202208280503119295000@lists.linux.dev>
reply other threads:[~2022-08-27 21:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202208272103.27RL3E6Q013083@mx0b-0019e102.pphosted.com \
--to=mailer-daemon@mx0b-0019e102.pphosted.com \
--cc=linux-coco@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).