On Mon, 1 Apr 2019 at 20:04, Noel Jones wrote:
>
> On 4/1/2019 2:01 PM, John Beranek wrote:
> > On Mon, 1 Apr 2019 at 19:55, John Beranek wrote:
> >>
> >> On Mon, 1 Apr 2019 at 19:47, John Beranek wrote:
> >>>
> >>> Apologies
On Mon, 1 Apr 2019 at 19:55, John Beranek wrote:
>
> On Mon, 1 Apr 2019 at 19:47, John Beranek wrote:
> >
> > Apologies for resurrecting a somewhat old thread, but presumably the
> > smtp_reply_filter fix won't work if smtp.gmail.com is now responding like:
>
> By the
On Mon, 1 Apr 2019 at 19:47, John Beranek wrote:
>
> Apologies for resurrecting a somewhat old thread, but presumably the
> smtp_reply_filter fix won't work if smtp.gmail.com is now responding like:
By the way, I found this thread as I started having the same issue. I
found that
Apologies for resurrecting a somewhat old thread, but presumably the
smtp_reply_filter fix won't work if smtp.gmail.com is now responding like:
$ telnet smtp.gmail.com 587
Trying 108.177.15.108...
Connected to smtp.gmail.com.
Escape character is '^]'.
220 smtp.gmail.com ESMTP b134sm26404242wmd.26
