Re: fetchmail timeout

[Andrei POPESCU]

On Lu, 06 apr 20, 10:33:36, Pierre Frenkiel wrote:
> On Mon, 6 Apr 2020, Andrei POPESCU wrote:
> 
> > Long term you might need a hold or pin for that (my preference would be
> > a pin).
> 
>hi Andrei,
>I felt that the description of the pinning process is rather
>confusing, either in the apt-get man or the aptitude man.
>Can you tell me what whould be the exact command to pin getmail?

The relevant documentation is in apt_preferences(5). Pins are configured 
via /etc/apt/preferences or (my preference, no pun intended), files in 
/etc/apt/preferences.d/.

The manpage is quite complex and difficult to understand. Fortunately it 
has good examples for common uses.

I would argue that its understanding should be a prerequisite for 
complex setups like mixing releases[1] or pinning important parts of the 
system (python, not getmail).

[1] I wouldn't count stable+backports or unstable+experimental as these 
are supported by apt out-of-the box.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: fetchmail timeout

[Pierre Frenkiel]

On Mon, 6 Apr 2020, Andrei POPESCU wrote:


Long term you might need a hold or pin for that (my preference would be
a pin).


   hi Andrei,
   I felt that the description of the pinning process is rather
   confusing, either in the apt-get man or the aptitude man.
   Can you tell me what whould be the exact command to pin getmail?

best regards,
--
Pierre Frenkiel

Re: fetchmail timeout

[Andrei POPESCU]

On Du, 05 apr 20, 19:21:31, Pierre Frenkiel wrote:
> On Sun, 5 Apr 2020, Pierre Frenkiel wrote:
> 
> > let them remove getmail if thay are not able to support it.
> > As I'm perfectly happy with the present Debian version,
> > I'll just keep it, disabling my upgrade process, until getmail support
> > reappears.
> > 
>   actually, I was too drastic: as "apt-get upgrade" gives all actions
>   that would be taken(upgraded, removed and new packages)
>   it's easy to cancel the upgrade if it wants to remove getmail

Long term you might need a hold or pin for that (my preference would be 
a pin).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: fetchmail timeout

[mick crane]

On 2020-04-04 21:46, Andrei POPESCU wrote:

On Sb, 04 apr 20, 19:30:05, Pierre Frenkiel wrote:

On Sat, 4 Apr 2020, Andrei POPESCU wrote:

> You have to keep also a Python 2 interpreter for it.

  same question: why would it disapear ?


Because it's not supported upstream anymore.

https://legacy.python.org/dev/peps/pep-0373/

Debian is actively working on removing it and as far as I recall the
developers hope to complete this in time for the bullseye release.

https://wiki.debian.org/Python/2Removal

issue seems to be is getmail a security risk with python 2 ? developer 
says no, then it is if having python2 on your computer a security risk ?

If I understand it.
I'm certain they make it so it works

mick



--
Key ID4BFEBB31

Re: fetchmail timeout

[Pierre Frenkiel]

On Sun, 5 Apr 2020, Pierre Frenkiel wrote:


let them remove getmail if thay are not able to support it.
As I'm perfectly happy with the present Debian version,
I'll just keep it, disabling my upgrade process, until getmail support
reappears.


  actually, I was too drastic: as "apt-get upgrade" gives all actions
  that would be taken(upgraded, removed and new packages)
  it's easy to cancel the upgrade if it wants to remove getmail

best regards,
--
Pierre Frenkiel

Re: fetchmail timeout

[Pierre Frenkiel]

On Sun, 5 Apr 2020, songbird wrote:


Celejar wrote:
...

https://marc.info/?l=getmail=157365887605305=2



 let them remove getmail if thay are not able to support it.
 As I'm perfectly happy with the present Debian version,
 I'll just keep it, disabling my upgrade process, until getmail support
 reappears.

best regards,
--
Pierre Frenkiel

Re: fetchmail timeout

[songbird]

Celejar wrote:
...
> https://marc.info/?l=getmail=157365887605305=2

  well that didn't happen and as soon as anyone
expressed any interest in carrying patches Osamu
pretty much just said take over the package because
he wasn't interested in it any more.  and then the
topic dropped because nobody wanted to pick it up.

  the original author of the package made some 
noises about how much work it would take to make
all the changes and someone else just did it.

  if the link i posted in this thread is correct and
the person did convert it to python3 there was no 
comment by anyone or the original author.  so to me 
it looks like they aren't that interested or it would 
have been merged and kept up (even if in another
branch).

  i grabbed it myself just in case it actually does 
keep working after python2 goes away.  my initial
test of it was that it worked, but i dunno if that
test was correct.

  i've also investigated other packages but they are
not drop in replacements so that means more work i
don't have time for at the moment.


  songbird

Re: fetchmail timeout

[Celejar]

On Sat, 4 Apr 2020 06:34:41 -0400
songbird  wrote:

> Pierre Frenkiel wrote:
> >>>> I have the following problem with fetchmail:
> >>>> fetchmail: timeout after 300 seconds waiting for server
> >>>> imap.gmail.com.
> >
> >hi,
> >the fix I found was to abandon fetchmail. I'm using now getmail, which
> >works perfectly
> >
> > best regards,
> 
>   yes, but don't get too complacent as eventually
> getmail goes away if nobody ports it to python3.

Upstream is potentially interested in moving to python3, but
it's not clear when / if this will happen. Discussion:

https://marc.info/?l=getmail=157365887605305=2

Celejar

Re: fetchmail timeout

[Andrei POPESCU]

On Sb, 04 apr 20, 19:30:05, Pierre Frenkiel wrote:
> On Sat, 4 Apr 2020, Andrei POPESCU wrote:
> 
> > You have to keep also a Python 2 interpreter for it.
> 
>   same question: why would it disapear ?

Because it's not supported upstream anymore.

https://legacy.python.org/dev/peps/pep-0373/

Debian is actively working on removing it and as far as I recall the 
developers hope to complete this in time for the bullseye release.

https://wiki.debian.org/Python/2Removal

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: fetchmail timeout

[songbird]

songbird wrote:
...
>   in my nosing around i've found this:
>
>   https://gitlab.com/dkg/getmail/commits/python3

  i meant that to be:

https://gitlab.com/dkg/getmail


  songbird

Re: fetchmail timeout

[songbird]

Pierre Frenkiel wrote:
> On Sat, 4 Apr 2020, Andrei POPESCU wrote:
>
>> You have to keep also a Python 2 interpreter for it.
>
>same question: why would it disapear ?
>
> best regards,

  because eventually it stops being packaged or kept up
and gets left behind long enough that nobody cares to do
any work on it.


  in my nosing around i've found this:

  https://gitlab.com/dkg/getmail/commits/python3

  can anyone verify this is an only python3 version?  i'm not
a python wizard to be able to know.

  i did grab it and try it out and it works for me.


  songbird

Re: fetchmail timeout

[Pierre Frenkiel]

On Sat, 4 Apr 2020, Andrei POPESCU wrote:


You have to keep also a Python 2 interpreter for it.


  same question: why would it disapear ?

best regards,
--
Pierre Frenkiel

Re: fetchmail timeout

[Andrei POPESCU]

On Sb, 04 apr 20, 12:44:38, Pierre Frenkiel wrote:
> On Sat, 4 Apr 2020, songbird wrote:
> 
> >  yes, but don't get too complacent as eventually
> > getmail goes away if nobody ports it to python3.
> > 
>thank you for the advice, but I imagine it will not disappear from my disk,
>even if it is no more supported.

You have to keep also a Python 2 interpreter for it.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: fetchmail timeout

[Pierre Frenkiel]

On Sat, 4 Apr 2020, songbird wrote:


 yes, but don't get too complacent as eventually
getmail goes away if nobody ports it to python3.


   thank you for the advice, but I imagine it will not disappear from my disk,
   even if it is no more supported.

best regards,
--
Pierre Frenkiel

Re: fetchmail timeout

[songbird]

Pierre Frenkiel wrote:
>>>> I have the following problem with fetchmail:
>>>> fetchmail: timeout after 300 seconds waiting for server
>>>> imap.gmail.com.
>
>hi,
>the fix I found was to abandon fetchmail. I'm using now getmail, which
>works perfectly
>
> best regards,

  yes, but don't get too complacent as eventually
getmail goes away if nobody ports it to python3.


  songbird

Re: fetchmail timeout

[Pierre Frenkiel]

I have the following problem with fetchmail:
fetchmail: timeout after 300 seconds waiting for server
imap.gmail.com.


  hi,
  the fix I found was to abandon fetchmail. I'm using now getmail, which
  works perfectly

best regards,
--
Pierre Frenkiel

Re: fetchmail timeout

[Cindy Sue Causey]

On 3/29/20, to...@tuxteam.de  wrote:
> On Sat, Mar 28, 2020 at 06:35:04PM +0100, Pierre Frenkiel wrote:
>> hi,
>> I have the following problem with fetchmail:
>>     fetchmail: timeout after 300 seconds waiting for server
>> imap.gmail.com.
>> here is my .fetchmailrc
>
> If I followed correctly, you're trying to access gmail at
> the "traditional" imap port (that's 143). There is nobody
> there answering the calls. Try imaps (i.e. 993), either through
> fetchmail's option "-P 993" or "--service imaps".
>
> Perhaps you'll have to play with options --ssl (and possibly
> with --sslproto, although that's improbable). See manpage.
>
> And, oh, I agree with the others. Try to avoid Google as
> your mail provider.


Poking my nose in again. I CC'd on this one because (I think I
remember) there being that request. I'm WAY behind on everything so
just now found this that had bounced back in response:

+
FROM: postmas...@outlook.comSun, Mar 29, 2020
at 3:08 PM
TO: ButterflyBytes

Delivery has failed to these recipients or groups:

***@**

Your message wasn't delivered. Despite repeated attempts to deliver
your message, the recipient's email system refused to accept a
connection from your email system.
+

Message went on to say I should try a phone, yada, grin. To the OP who
started this, maybe playing around with multiple email addresses is
throwing a kink in things?

OR NOT.

Decided it should be mentioned since this was just found.

Please be safe out there, everyone

PS As an afterthought, my Gmail has been just a tiny bit "hinky"
today. Takes several refreshes for pages to load after they
*timeout* in Firefox ESR browser. Seemed also worth noting. :)

Cindy.
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with a fresh refresh of birdseed *

Re: fetchmail timeout (fwd)

[mick crane]

On 2020-03-29 13:24, Reco wrote:


On Sun, Mar 29, 2020 at 01:46:12PM +0200, Pierre Frenkiel wrote:

Mike fetchmail, getmail gives a Time Out


OP
did you select "allow non-standard email client" or whatever it is at 
gmail ?

use SimpleIMAPSSLReciever ?

[retriever]
type=SimpleIMAPSSLRetriever
server = imap.gmail.com
username = 
password = X
[destination]
type = MDA_external
path = /usr/lib/dovecot/deliver
[options]
verbose = 0
delete = true
message_log = ~/.getmail/log

mick
--
Key ID4BFEBB31

Re: fetchmail timeout (fwd)

[Reco]

Please CC the list. And please refrain from top posting.

On Sun, Mar 29, 2020 at 01:46:12PM +0200, Pierre Frenkiel wrote:
> Mike fetchmail, getmail gives a Time Out


Two options left.

> >1) Try using POP3 instead of IMAP.
> >
> >3) Make a forward to your gmx mailbox from gmail.

Reco

Re: fetchmail timeout (fwd)

[Reco]

Hi.

On Sun, Mar 29, 2020 at 10:06:19AM +0200, Pierre Frenkiel wrote:
> as requested, here is the output of fetchmail -v

So, login's good:

> fetchmail: IMAP> A0002 LOGIN "pierre.frenkiel" *
> fetchmail: IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID 
> XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE ENABLE MOVE CONDSTORE 
> ESEARCH UTF8=ACCEPT LIST-EXTENDED LIST-STATUS LITERAL- SPECIAL-USE 
> APPENDLIMIT=35651584
> fetchmail: IMAP< A0002 OK pierre.frenk...@gmail.com authenticated (Success)

Mail sizes fetched:

...
> fetchmail: IMAP< * 100 FETCH (RFC822.SIZE 12783)
> fetchmail: IMAP< A0005 OK Success
> fetchmail: IMAP> A0006 FETCH 1 RFC822.HEADER

And here lies an anomaly - then requested mail headers:

> fetchmail: IMAP< * 1 FETCH (RFC822.HEADER {3040}
> fetchmail: reading message pierre.frenk...@imap.gmail.com:1 of 211 (3040 
> header octets) (log message incomplete)
> fetchmail: IMAP< )
> fetchmail: IMAP< A0006 OK Success

Gmail returned exactly zero rows (there should've been headers before
"IMAP< )").
Whichever is broken is broken on their side, not yours.


> fetchmail: IMAP> A0007 FETCH 1 BODY.PEEK[TEXT]
> fetchmail: IMAP< A0007 NO System Error (Failure)

No surprise it bailed on attempt to retrieve mail body.


I see three options here:

1) Try using POP3 instead of IMAP.

2) Replace fetchmail with getmail.

3) Make a forward to your gmx mailbox from gmail.

Reco

Re: fetchmail timeout (fwd)

[Kamil Jońca]

Pierre Frenkiel  writes:

> as requested, here is the output of fetchmail -v
> you can see at the end "reading message ...", but I can't find it
>
>  please reply pierre.frenk...@gmx.com
>
[...]
> fetchmail: IMAP> A0004 EXPUNGE
> fetchmail: IMAP< A0004 OK Success
> fetchmail: 211 messages for pierre.frenkiel at imap.gmail.com.
> fetchmail: IMAP> A0005 FETCH 1:100 RFC822.SIZE
[...]
> fetchmail: IMAP< A0005 OK Success
> fetchmail: IMAP> A0006 FETCH 1 RFC822.HEADER
> fetchmail: IMAP< * 1 FETCH (RFC822.HEADER {3040}
> fetchmail: reading message pierre.frenk...@imap.gmail.com:1 of 211 (3040 
> header octets) (log message incomplete)
> fetchmail: IMAP< )
> fetchmail: IMAP< A0006 OK Success
> fetchmail: IMAP> A0007 FETCH 1 BODY.PEEK[TEXT]
> fetchmail: IMAP< A0007 NO System Error (Failure)
> best regards,

Can you use imap with another client? (mutt/thunderbird). It seems, that
gmail let you to logi, get message list, but then is timeout at first
message body. I'd ask gmail help now.


KJ
-- 
http://wolnelektury.pl/wesprzyj/teraz/

Re: fetchmail timeout

[tomas]

On Sat, Mar 28, 2020 at 06:35:04PM +0100, Pierre Frenkiel wrote:
> hi,
> I have the following problem with fetchmail:
> fetchmail: timeout after 300 seconds waiting for server imap.gmail.com.
> here is my .fetchmailrc

If I followed correctly, you're trying to access gmail at
the "traditional" imap port (that's 143). There is nobody
there answering the calls. Try imaps (i.e. 993), either through
fetchmail's option "-P 993" or "--service imaps".

Perhaps you'll have to play with options --ssl (and possibly
with --sslproto, although that's improbable). See manpage.

And, oh, I agree with the others. Try to avoid Google as
your mail provider.

HTH
-- tomás


signature.asc
Description: Digital signature

Re: fetchmail timeout (fwd)

[mick crane]

On 2020-03-29 09:06, Pierre Frenkiel wrote:

as requested, here is the output of fetchmail -v
you can see at the end "reading message ...", but I can't find it


with gmail you have to select "allow non-conforming clients" or 
something.
I had problems with fetchmail and gmail ( forget what exactly) so 
started using getmail.


mick
--
Key ID4BFEBB31

fetchmail timeout (fwd)

[Pierre Frenkiel]

as requested, here is the output of fetchmail -v
you can see at the end "reading message ...", but I can't find it

 please reply pierre.frenk...@gmx.com

fetchmail: starting fetchmail 6.4.0.beta4 daemon
fetchmail: 6.4.0.beta4 querying imap.gmail.com (protocol IMAP) at Sun 29 Mar 
2020 10:00:12 AM CEST: poll started
fetchmail: Trying to connect to 2a00:1450:400c:c0b::6c/993...connected.
fetchmail: Loaded OpenSSL library 0x1010104f newer than headers 0x1010101f, 
trying to continue.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Google Trust Services
fetchmail: Issuer CommonName: GTS CA 1O1
fetchmail: Subject CommonName: imap.gmail.com
fetchmail: Subject Alternative Name: imap.gmail.com
fetchmail: imap.gmail.com key fingerprint: 
D0:AE:2E:A9:43:15:E0:72:00:5A:E2:C7:79:92:80:14
fetchmail: SSL/TLS: using protocol TLSv1.3, cipher TLS_AES_256_GCM_SHA384, 
256/256 secret/processed bits
fetchmail: IMAP< * OK Gimap ready for requests from 
2a01:e0a:509:99b0:2e4d:54ff:fed0:5806 o6mb110676674wrm
fetchmail: IMAP> A0001 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST 
CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN 
AUTH=OAUTHBEARER AUTH=XOAUTH
fetchmail: IMAP< A0001 OK Thats all she wrote! o6mb110676674wrm
fetchmail: IMAP> A0002 LOGIN "pierre.frenkiel" *
fetchmail: IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST 
CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE ENABLE MOVE CONDSTORE ESEARCH 
UTF8=ACCEPT LIST-EXTENDED LIST-STATUS LITERAL- SPECIAL-USE APPENDLIMIT=35651584
fetchmail: IMAP< A0002 OK pierre.frenk...@gmail.com authenticated (Success)
fetchmail: IMAP> A0003 SELECT "INBOX"
fetchmail: IMAP< * FLAGS (\Answered \Flagged \Draft \Deleted \Seen $NotPhishing 
$Phishing)
fetchmail: IMAP< * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen 
$NotPhishing $Phishing \*)] Flags permitted.
fetchmail: IMAP< * OK [UIDVALIDITY 4] UIDs valid.
fetchmail: IMAP< * 211 EXISTS
fetchmail: IMAP< * 0 RECENT
fetchmail: IMAP< * OK [UIDNEXT 488592] Predicted next UID.
fetchmail: IMAP< * OK [HIGHESTMODSEQ 52495552]
fetchmail: IMAP< A0003 OK [READ-WRITE] INBOX selected. (Success)
fetchmail: IMAP> A0004 EXPUNGE
fetchmail: IMAP< A0004 OK Success
fetchmail: 211 messages for pierre.frenkiel at imap.gmail.com.
fetchmail: IMAP> A0005 FETCH 1:100 RFC822.SIZE
fetchmail: IMAP< * 1 FETCH (RFC822.SIZE 9545047)
fetchmail: IMAP< * 2 FETCH (RFC822.SIZE 6800)
fetchmail: IMAP< * 3 FETCH (RFC822.SIZE 13965)
fetchmail: IMAP< * 4 FETCH (RFC822.SIZE 7577)
fetchmail: IMAP< * 5 FETCH (RFC822.SIZE 12323)
fetchmail: IMAP< * 6 FETCH (RFC822.SIZE 14943)
fetchmail: IMAP< * 7 FETCH (RFC822.SIZE 6373)
fetchmail: IMAP< * 8 FETCH (RFC822.SIZE 14261)
fetchmail: IMAP< * 9 FETCH (RFC822.SIZE 11218)
fetchmail: IMAP< * 10 FETCH (RFC822.SIZE 296892)
fetchmail: IMAP< * 11 FETCH (RFC822.SIZE 20328)
fetchmail: IMAP< * 12 FETCH (RFC822.SIZE 27847)
fetchmail: IMAP< * 13 FETCH (RFC822.SIZE 6944)
fetchmail: IMAP< * 14 FETCH (RFC822.SIZE 5512)
fetchmail: IMAP< * 15 FETCH (RFC822.SIZE 11460)
fetchmail: IMAP< * 16 FETCH (RFC822.SIZE 5507)
fetchmail: IMAP< * 17 FETCH (RFC822.SIZE 5313)
fetchmail: IMAP< * 18 FETCH (RFC822.SIZE 5998)
fetchmail: IMAP< * 19 FETCH (RFC822.SIZE 5411)
fetchmail: IMAP< * 20 FETCH (RFC822.SIZE 9284)
fetchmail: IMAP< * 21 FETCH (RFC822.SIZE 6828)
fetchmail: IMAP< * 22 FETCH (RFC822.SIZE 7484)
fetchmail: IMAP< * 23 FETCH (RFC822.SIZE 7)
fetchmail: IMAP< * 24 FETCH (RFC822.SIZE 7840)
fetchmail: IMAP< * 25 FETCH (RFC822.SIZE 9752)
fetchmail: IMAP< * 26 FETCH (RFC822.SIZE 5953)
fetchmail: IMAP< * 27 FETCH (RFC822.SIZE 8173)
fetchmail: IMAP< * 28 FETCH (RFC822.SIZE 6939)
fetchmail: IMAP< * 29 FETCH (RFC822.SIZE 20121)
fetchmail: IMAP< * 30 FETCH (RFC822.SIZE 18251)
fetchmail: IMAP< * 31 FETCH (RFC822.SIZE 4450)
fetchmail: IMAP< * 32 FETCH (RFC822.SIZE 11674)
fetchmail: IMAP< * 33 FETCH (RFC822.SIZE 53030)
fetchmail: IMAP< * 34 FETCH (RFC822.SIZE 9242)
fetchmail: IMAP< * 35 FETCH (RFC822.SIZE 25132)
fetchmail: IMAP< * 36 FETCH (RFC822.SIZE 17722)
fetchmail: IMAP< * 37 FETCH (RFC822.SIZE 9960)
fetchmail: IMAP< * 38 FETCH (RFC822.SIZE 20088)
fetchmail: IMAP< * 39 FETCH (RFC822.SIZE 9417)
fetchmail: IMAP< * 40 FETCH (RFC822.SIZE 7609)
fetchmail: IMAP< * 41 FETCH (RFC822.SIZE 13259)
fetchmail: IMAP< * 42 FETCH (RFC822.SIZE 6554)
fetchmail: IMAP< * 43 FETCH (RFC822.SIZE 6749)
fetchmail: IMAP< * 44 FETCH (RFC822.SIZE 17092)
fetchmail: IMAP< * 45 FETCH (RFC822.SIZE 8476)
fetchmail: IMAP< * 46 FETCH (RFC822.SIZE 20436)
fetchmail: IMAP< * 47 FETCH (RFC822.SIZE 48444)
fetchmail: IMAP< * 48 FETCH (RFC822.SIZE 6982)
fetchmail: IMAP< * 49 FETCH (RFC822.SIZE 7849)
fetchmail: IMAP< * 50 FETCH (RFC822.SIZE 7336)
fetchmail: IMAP< * 51 FETCH (RFC822.SIZE 6322)
fetchmail: IMAP< * 52 FETCH (RFC822.SIZE 11556)
fetchmail: IMAP< * 53 FETCH (RFC822.SIZE 10822)
fetchmail: IMAP< * 54 FETCH (RFC822.SIZE 9561)
fetchmail: IMAP< * 55 FETCH (RFC822.SIZE 33494)
fetchmail: 

Re: fetchmail timeout

[황병희]

Pierre Frenkiel  writes:

> poll imap.gmail.com with proto IMAP auth password

It is just side comments. There is alternative software. The name is
getmail[*]. The getmail supports Gmail's label. It is available to
downloading messages from each Gmail's label. Personaly i use getmail
with Gnus. Always i'm happy with getmail + Gnus ^^^

[*] http://pyropus.ca/software/getmail/

Sincerely, Byung-Hee

-- 
^고맙습니다 _白衣從軍_ 감사합니다_^))//

[OT] COVID-19 (Was: Re: fetchmail timeout)

[황병희]

Cindy Sue Causey  writes:

> ..
> While checking trending one more time to see if there were any current
> references, a new trending topic is that Twitter direct messages are
> taking a hit right now. It all seems an understandable, predictable
> social networking side effect in light of our World's current health
> situation. Lots of folks turning to the Internet to stay in touch
> while physically isolated from each other.
>
> Cindy... Hoping everyone is safe and well.

Cindy! I hope you always stay health and happy^^^

Sincerely, Byung-Hee from South Korea

-- 
^고맙습니다 _白衣從軍_ 감사합니다_^))//

Re: fetchmail timeout

[Cindy Sue Causey]

On 3/28/20, Pierre Frenkiel  wrote:
> hi,
> I have the following problem with fetchmail:
>  fetchmail: timeout after 300 seconds waiting for server
> imap.gmail.com.
>  here is my .fetchmailrc


Poking my nose in to say that Gmail AND Youtube were down in last
couple days. I only know this because it was a "trending" topic so it
was an at least somewhat notable outage. My usage wasn't affected. It
was one of those times that location may or may not have played an
immediate effect.

While checking trending one more time to see if there were any current
references, a new trending topic is that Twitter direct messages are
taking a hit right now. It all seems an understandable, predictable
social networking side effect in light of our World's current health
situation. Lots of folks turning to the Internet to stay in touch
while physically isolated from each other.

Cindy... Hoping everyone is safe and well.
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* (still) runs with birdseed *

Re: fetchmail timeout

[Reco]

Hi.

On Sat, Mar 28, 2020 at 06:35:04PM +0100, Pierre Frenkiel wrote:
> hi,
> I have the following problem with fetchmail:
> fetchmail: timeout after 300 seconds waiting for server imap.gmail.com.
> here is my .fetchmailrc

fetchmail -v

Reco

Re: fetchmail timeout

[Henning Follmann]

On Sat, Mar 28, 2020 at 06:35:04PM +0100, Pierre Frenkiel wrote:
> hi,
> I have the following problem with fetchmail:
> fetchmail: timeout after 300 seconds waiting for server imap.gmail.com.
> here is my .fetchmailrc
> 
> 
> set logfile "/data/home/frenkiel/log/fetchmail"
> set pidfile "/data/home/frenkiel/.fetchmail.pid"
> set postmaster "frenkiel"
> set nobouncemail
> set no spambounce
> set properties ""
> set daemon 15
> set invisible
> poll imap.gmail.com with proto IMAP auth password
>  interface enp0s31f6/192.168.1.12/255.255.255.255
>  user 'pierre.frenkiel' there is 'frenkiel' here options fetchall stripcr 
> ssl
> 
>  the password is set in .netrc
> 
> 
>  please reply pierre.frenk...@gmx.com
> 


Google mail is broken. Consider a decent mail provider instead.

However. Did this ever work? Or are you just trying to set this up?
If you are just setting this up, did you authorize for "less secure"
access to that account?
This is Googles spin to make everyones life miserable.

-H

-- 
Henning Follmann   | hfollm...@itcfollmann.com

fetchmail timeout

[Pierre Frenkiel]

hi,
I have the following problem with fetchmail:
fetchmail: timeout after 300 seconds waiting for server imap.gmail.com.
here is my .fetchmailrc


set logfile "/data/home/frenkiel/log/fetchmail"
set pidfile "/data/home/frenkiel/.fetchmail.pid"
set postmaster "frenkiel"
set nobouncemail
set no spambounce
set properties ""
set daemon 15
set invisible
poll imap.gmail.com with proto IMAP auth password
 interface enp0s31f6/192.168.1.12/255.255.255.255
 user 'pierre.frenkiel' there is 'frenkiel' here options fetchall stripcr 
ssl

 the password is set in .netrc


 please reply pierre.frenk...@gmx.com

best regards,
--
Pierre Frenkiel