On Friday, July 1, 2016 at 2:16:24 PM UTC-7, Ian Lance Taylor wrote: > > I suggest that if EHLO returns a non-nil error and HELO returns an > EOF, then the hello method should return the EHLO error. > > That said, does this case actually happen in the real world? > > YES this happens! And it is really annoying that the standard library STILL eats and discards the real error. For me this happens when connecting to smtp-relay.gmail.com:25 or smtp-relay.gmail.com:587
The first error from EHLO is "421 4.7.0 Try again later, closing connection. (EHLO) v128sm135072ywf.1 - gsmtp" The second error from HELO is "EOF" which makes sense because the server told us it was "closing connection" So all a client sees is EOF with no further diagnostic information. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/f304a93a-4b30-4f34-bd92-219d7558560d%40googlegroups.com.
