From: Benjamin LaHaise <bcrl@kvack.org>
To: linux-mm@kvack.org
Subject: @google.com, @googlemail.com, @gmail.com bounces
Date: Wed, 26 Jan 2011 15:46:07 -0500 [thread overview]
Message-ID: <20110126204607.GG8066@kvack.org> (raw)
Hi folks,
Just to let people know, Google appears to be dropping emails that users
of the domains in $SUBJ sent out. Typical bounce messages are as follows:
Final-Recipient: rfc822; XXX@gmail.com
Original-Recipient: rfc822; linux-mm-outgoing
Action: failed
Status: 5.7.1
Remote-MTA: dns; gmail-smtp-in.l.google.com
Diagnostic-Code: smtp; 550 5.7.1 Unauthenticated email is not accepted from
this domain. u12si37691121ibe.45
If someone at Google can get this investigated, it would be beneficial as
that currently accounts for about 50% of the mailing list subscribers users
of these domains are not reaching.
-ben
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2011-01-26 20:46 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=20110126204607.GG8066@kvack.org \
--to=bcrl@kvack.org \
--cc=linux-mm@kvack.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).