From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Send mail problem
Date: Thu, 04 Aug 2016 09:15:04 -0700 [thread overview]
Message-ID: <8760rgfr3r.fsf@mushroom.localdomain> (raw)
In-Reply-To: <alpine.LRH.2.00.1608040940270.2277@euclid.colorado.edu> (Lawrence Baggett's message of "Thu, 4 Aug 2016 09:44:48 -0600 (MDT)")
Lawrence Baggett <Lawrence.Baggett@Colorado.EDU> writes:
> 501-5.5.4 HELO/EHLO argument "lawrence.baggett@gmail.com" invalid, closing
> 501-5.5.4 connection.
> 501 5.5.4 https://support.google.com/mail/?p=helo a65sm1827857itd.18
Hi,
Yes, this is apparently due to a change Google made a few months back.
I fixed it in git a while ago, but I'm guessing that you're not running
from git.
-- Chris
prev parent reply other threads:[~2016-08-04 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 15:44 Lawrence Baggett
2016-08-04 16:15 ` Chris Brannon [this message]
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=8760rgfr3r.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=edbrowse-dev@lists.the-brannons.com \
/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).