Re: Timing out while trying to connect to gmail. Config?

On Mon, Feb 25, 2019 at 10:51 PM Charles Cazabon
<[email protected]> wrote:
>
> Mauricio Tavares <[email protected]> wrote:
> > [mailsucker@mailbox ~]$ nc -tv imap.gmail.com 993
> > Ncat: Version 7.50 ( https://nmap.org/ncat )
> > Ncat: Connected to 173.194.207.109:993.
>
> Okay, so you have low-level TCP connectivity.  It's failing and timing out
> higher up the stack.
>
> > getmail version 5.6
> > Copyright (C) 1998-2012 Charles Cazabon.  Licensed under the GNU GPL version 2.
> > SimpleIMAPSSLRetriever:[email protected]@imap.gmail.com:993:
>
> That's a bit old.  I wonder if this is related to the recent SNI stuff.  Can
> you please try with the current getmail version (5.13, which has a couple of
> changes specifically for Gmail when your TLS library is OpenSSL 1.1.1 or
> later)?
>
      That is the version that is being provided as a package through
the EPEL redhat repository. But, as I see your point, I will get
http://pyropus.ca/software/getmail/old-versions/getmail-5.13.tar.gz
instead as shown later on this email.

> Also, what version of Python are you running getmail with?
>
      Running Python 2.7.5

> > read_all and not delete -- all messages will be retrieved each time
> > getmail is run
>
> Where is that "getmail is run" message coming from?  Did you add it in trying
> to debug this?
>
      I have no clue. Other than telling it to fetch only 2K emails,
the rc file I am running is still the same one from the first post.
The only debugging I did was passing -vvv as a runtime argument, but
that seem to have no control of those messages. When I ran version
5.13 I got the same messages.

[mailsucker@mailbox ~]$ getmail --getmaildir ~/mail/mailrc -r
~/mail/mailrc/getmailrc.gmail.raubvogel
getmail version 5.13
Copyright (C) 1998-2019 Charles Cazabon.  Licensed under the GNU GPL version 2.
SimpleIMAPSSLRetriever:[email protected]@imap.gmail.com:993:
read_all and not delete -- all messages will be retrieved each time
getmail is run
SimpleIMAPSSLRetriever:[email protected]@imap.gmail.com:993:
getmailrc.gmail.raubvogel: socket error (('The read operation timed out',))
  0 messages (0 bytes) retrieved, 0 skipped
[mailsucker@mailbox ~]$


Also, note I am running this inside a docker container, which I blew
last night. All it does is

1. Grab and install the program (script is doing a more elegant version of)

curl -O http://pyropus.ca/software/getmail/old-versions/getmail-5.13.tar.gz
tar xzvf getmail-5.13.tar.gz
cd getmail-5.13
python setup.py install

2. Create mailsucking account.
3. NFS mount ~mailsucker/mail and create any directories inside it as needed.
4. Upload the rc files and the script to feed said rc files to getmail
without bothering me. Script calls each file the same way I have been
manually calling, i.e.

getmail --getmaildir ~/mail/mailrc -r ~/mail/mailrc/getmailrc.gmail.raubvogel

That is it. Any fiddling I did before is gone because of the nature of
the setup. Extra messages, during runtime? I have no idea how they got
there.

I looked at my log file -- I let it run overnight -- and it showed
that sometimes it grabbed some email and sometimes it times out:

[...]
2019-02-26 11:32:58 msg   1998/928923 (17773 bytes) msgid 2/103919
from <[email protected]> delivered to Maildir
/home/mailsucker/mail/gmail/raubvogel/
2019-02-26 11:32:59 msg   1999/928923 (19792 bytes) msgid 2/103931
from <[email protected]> delivered to Maildir
/home/mailsucker/mail/gmail/raubvogel/
2019-02-26 11:32:59 msg   2000/928923 (2938 bytes) msgid 2/103957 from
<[email protected]> delivered to Maildir
/home/mailsucker/mail/gmail/raubvogel/
2019-02-26 11:56:31 socket error (('The read operation timed out',))
2019-02-26 13:30:05 socket error (('The read operation timed out',))
2019-02-26 14:56:30 socket error (('The read operation timed out',))


> Charles
>
> --
> -----------------------------------------------------------------------
> Charles Cazabon
> GPL'ed software available at:               http://pyropus.ca/software/
> -----------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>