From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: FOR KEVIN HILMAN: Fwd: Mail delivery failed: returning message to sender
Date: Thu, 26 Jun 2014 16:21:38 +0100 [thread overview]
Message-ID: <20140626152138.GV32514@n2100.arm.linux.org.uk> (raw)
Kevin,
can you please get a different email provider. gmail is becoming
increasingly painful to send email to, and as gmail provides very
little help when this occurs, it's impossible to work around.
----- Forwarded message from Mail Delivery System <Mailer-Daemon@arm.linux.org.uk> -----
Date: Thu, 26 Jun 2014 16:19:07 +0100
From: Mail Delivery System <Mailer-Daemon@arm.linux.org.uk>
To: linux at arm.linux.org.uk
Subject: Mail delivery failed: returning message to sender
Delivery-date: Thu, 26 Jun 2014 16:19:11 +0100
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:
khilman at linaro.org
SMTP error from remote mail server after end of data:
host aspmx.l.google.com [2a00:1450:400c:c00::1a]:
550-5.7.1 [2001:4d48:ad52:3201:214:fdff:fe10:1be6 12] Our system has
550-5.7.1 detected that this message is likely unsolicited mail. To reduce the
550-5.7.1 amount of spam sent to Gmail, this message has been blocked. Please
550-5.7.1 visit
550-5.7.1 http://support.google.com/mail/bin/answer.py?hl=en&answer=188131 for
550 5.7.1 more information. r10si28737564wiz.104 - gsmtp
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next reply other threads:[~2014-06-26 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 15:21 Russell King - ARM Linux [this message]
2014-08-06 0:28 ` FOR KEVIN HILMAN: Fwd: Mail delivery failed: returning message to sender Kevin Hilman
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=20140626152138.GV32514@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).