[MlMt] Gmail source is unavailable

Adam Liter adam.liter at gmail.com
Mon May 9 22:20:35 EDT 2016


Hmm, doing openssl s_client -connect imap.gmail.com:imaps seems to work
just fine.

I did also try your suggestion of explicitly specifying port 993, and that
seems to fix the problem. I'm not sure why I now need to specify it since
I've never had to do so in the past.

Thanks for the suggestion!

-Adam

On Mon, May 9, 2016 at 10:15 PM, Steven M. Bellovin <smb at cs.columbia.edu>
wrote:

> If you're doing 'telnet imap.gmail.com imap' you're trying for the
> unencrypted IMAP port. I don't think Google supports that. Asking
> for 993 or the imaps protocol gets the encrypted version -- but you
> can't comprehensibly talk to that port via telnet. Try
> openssl s_client -connect imap.gmail.com:imaps
> instead.
> For your underlying problem, you may want to go to "Edit IMAP Account"
> and explicitly specify port 993. You shouldn't have to, but...
> On 9 May 2016, at 21:55, Adam Liter wrote:
>
> Sorry for sending a couple of emails in a row, but it seems that this is
> actually the behavior that I'm seeing:
>
> $ telnet imap.gmail.com 993
> Trying 2607:f8b0:4001:c08::6c...
> Connected to gmail-imap.l.google.com.
> Escape character is '^]'.
> Connection closed by foreign host.
>
> So, unlike I said in the previous email, telnet imap.gmail.com 993 does
> not seem to be working either.
>
> Running telnet imap.gmail.com imap still just seems to hang and never
> gets to a point where a foreign host can close the connection.
>
> Thanks.
>
> -Adam Liter
>
>
> On Mon, May 9, 2016 at 9:44 PM, Adam Liter <adam.liter at gmail.com> wrote:
>
>> Actually, it seems that telnet imap.gmail.com 993 actually works for me
>> to connect, whereas telnet imap.gmail.com imap just hangs. So perhaps
>> the port forwarding on my laptop has somehow been messed up for just Gmail?
>>
>> I don't know much about this, so I'd appreciate any suggestions.
>>
>> Thanks again!
>>
>> -Adam Liter
>>
>> On Mon, May 9, 2016 at 9:41 PM, Adam Liter <adam.liter at gmail.com> wrote:
>>
>>> Hmm, interesting. With telnet imap.gmail.com imap everything just seems
>>> to hang, but when I try, for example, telnet mail.riseup.net imap
>>> everything seems to work fine.
>>>
>>> Thanks for this initial suggestion for help with debugging. Do you have
>>> any further idea what the problem might be?
>>>
>>> -Adam Liter
>>>
>>> On Mon, May 9, 2016 at 9:34 PM, Gary Hull <YH82d7dfU at yandex.com> wrote:
>>>
>>>> On 10 May 2016, at 4:10, Adam Liter wrote:
>>>>
>>>> Since getting home and since connecting to a few other networks, I have
>>>>> continued to be unable to get MailMate to access Gmail via IMAP. It
>>>>> continually says that it is unavailable.
>>>>>
>>>>
>>>> You can use telnet via a terminal window or telnet app to test IMAP.
>>>> For instance:
>>>>
>>>> https://technet.microsoft.com/en-us/library/dd789687(v=exchg.80).aspx
>>>>
>>>> That will at least eliminate one possibility.
>>>> _______________________________________________
>>>> mailmate mailing list
>>>> mailmate at lists.freron.com
>>>> https://lists.freron.com/listinfo/mailmate
>>>>
>>>
>>>
>>
> _______________________________________________
> mailmate mailing list
> mailmate at lists.freron.com
> https://lists.freron.com/listinfo/mailmate
>
> --Steve Bellovin, https://www.cs.columbia.edu/~smb
>
> _______________________________________________
> mailmate mailing list
> mailmate at lists.freron.com
> https://lists.freron.com/listinfo/mailmate
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freron.com/pipermail/mailmate/attachments/20160509/fc2cd578/attachment-0001.html>


More information about the mailmate mailing list