From: Mail Delivery System <Mailer-Daemon@hosts.co.uk>
To: newlib@sourceware.org
Subject: Mail delivery failed: returning message to sender
Date: Tue, 14 Nov 2023 04:42:29 +0000 [thread overview]
Message-ID: <E1r2lFt-0005JY-Kw@fwd0.hosts.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
ae9101ee@gmail.com
(generated from cls@lubutu.com)
host gmail-smtp-in.l.google.com [142.250.13.27]
SMTP error from remote mail server after end of data:
550-5.7.1 [85.233.160.22] Messages missing a valid Message-ID header are not
550-5.7.1 accepted. Please visit
550-5.7.1 https://support.google.com/mail/?p=RfcMessageNonCompliant and review
550 5.7.1 RFC 5322 specifications for more information. q10-20020a05600c46ca00b00404fbefcea7si4154548wmo.20 - gsmtp
[-- Attachment #2: Type: message/delivery-status, Size: 482 bytes --]
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: Type: text/rfc822-headers, Size: 587 bytes --]
Return-path: <newlib@sourceware.org>
Received: from [120.245.22.69] (helo=lubutu.com)
by fwd0.hosts.co.uk with esmtp (Exim 4.95)
(envelope-from <newlib@sourceware.org>)
id 1r2lFs-0005Gs-Ea
for cls@lubutu.com;
Tue, 14 Nov 2023 04:42:29 +0000
From: newlib@sourceware.org
To: cls@lubutu.com
Subject: Re: Encrypted Mail
Date: Tue, 14 Nov 2023 12:42:07 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 3
X-MSMail-Priority: Normal
X-Exim-DSN-Information: Due to administrative limits only headers are returned
next reply other threads:[~2023-11-14 4:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 4:42 Mail Delivery System [this message]
2024-04-08 0:04 Mail Delivery System
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=E1r2lFt-0005JY-Kw@fwd0.hosts.co.uk \
--to=mailer-daemon@hosts.co.uk \
--cc=newlib@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).