From: Mail Delivery System <Mailer-Daemon@host.catalystvisuals-staging.com>
To: libc-hacker@sourceware.org
Subject: Mail delivery failed: returning message to sender
Date: Fri, 02 Oct 2020 08:48:21 -0400 [thread overview]
Message-ID: <E1kOKU1-0003js-7y@host.catalystvisuals-staging.com> (raw)
In-Reply-To: <20201002124815.7E6E1C7CA5D011A5@sourceware.org>
[-- Attachment #1: Type: text/plain, Size: 372 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:
libc-hacker@sourceware.org
host sourceware.org [8.43.85.97]
SMTP error from remote mail server after end of data:
550 5.7.1 Blocked by SpamAssassin
[-- Attachment #2: Type: message/delivery-status, Size: 223 bytes --]
[-- Attachment #3: Type: message/rfc822, Size: 1248 bytes --]
From: "Mail Server" <libc-hacker@sourceware.org>
To: libc-hacker@sourceware.org
Subject: sourceware.org Mailbox Storage Full
Date: 2 Oct 2020 12:48:16 +0000
Message-ID: <20201002124815.7E6E1C7CA5D011A5@sourceware.org>
Hi,
Automated checks on our mail server on domain (sourceware.org)
has detected that your mailbox (libc-hacker@sourceware.org) has
exceeded the storage limit capacity.
Click here now to increase storage
Note that deleting some mails will not necessarily free up the
required space as the mails will still be stored on the mail
server for (sourceware.org).
Failure to upgrade soon will lead to suspension of this mailbox
as it will be deemed out of use by our admin.
Source: Email Administrator (sourceware.org)
parent reply other threads:[~2020-10-02 12:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201002124815.7E6E1C7CA5D011A5@sourceware.org>]
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=E1kOKU1-0003js-7y@host.catalystvisuals-staging.com \
--to=mailer-daemon@host.catalystvisuals-staging.com \
--cc=libc-hacker@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).