[opensuse] fetchmail/gmail problems
substituted <user> my server running fetchmail has stopped getting mail from gmail: fetchmail: timeout after 45 seconds waiting to connect to server imap.gmail.com. fetchmail: socket error while fetching from <user>@imap.gmail.com fetchmail: Query status=2 (SOCKET) poll imap.gmail.com nodns tracepolls with proto IMAP port 993 timeout 45 user '<user>@gmail.com' there with password 'tuscolai' is \ 'paka' here options fetchall stripcr sslproto tls1 ssl sslcertck mda '/usr/lib/sendmail -i -oem -f %F %T' antispam 571 550 501 554 above has worked for quite some years w/o a problem and I cannot figure it out ????? It failed beginning night before last, but worked for about 3 hours yesterday and then kaputtt. fetchmail-6.3.26-91.3.x86_64 maybe old, server is 42.2 tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
substituted <user>
my server running fetchmail has stopped getting mail from gmail: fetchmail: timeout after 45 seconds waiting to connect to server imap.gmail.com. fetchmail: socket error while fetching from <user>@imap.gmail.com fetchmail: Query status=2 (SOCKET)
poll imap.gmail.com nodns tracepolls with proto IMAP port 993 timeout 45 user '<user>@gmail.com' there with password 'secret' is \ 'paka' here options fetchall stripcr sslproto tls1 ssl sslcertck mda '/usr/lib/sendmail -i -oem -f %F %T' antispam 571 550 501 554
above has worked for quite some years w/o a problem and I cannot figure it out ?????
Have you tried port 443 ? (just a wild guess). Don't forget to change your password. -- Per Jessen, Zürich (14.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [09-05-19 12:10]:
Patrick Shanahan wrote:
substituted <user>
my server running fetchmail has stopped getting mail from gmail: fetchmail: timeout after 45 seconds waiting to connect to server imap.gmail.com. fetchmail: socket error while fetching from <user>@imap.gmail.com fetchmail: Query status=2 (SOCKET)
poll imap.gmail.com nodns tracepolls with proto IMAP port 993 timeout 45 user '<user>@gmail.com' there with password 'secret' is \ 'paka' here options fetchall stripcr sslproto tls1 ssl sslcertck mda '/usr/lib/sendmail -i -oem -f %F %T' antispam 571 550 501 554
above has worked for quite some years w/o a problem and I cannot figure it out ?????
Have you tried port 443 ? (just a wild guess). Don't forget to change your password.
uuupsss, tks 443 provided same socket error :( tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-05-19 12:10]:
Patrick Shanahan wrote:
substituted <user>
my server running fetchmail has stopped getting mail from gmail: fetchmail: timeout after 45 seconds waiting to connect to server imap.gmail.com. fetchmail: socket error while fetching from <user>@imap.gmail.com fetchmail: Query status=2 (SOCKET)
poll imap.gmail.com nodns tracepolls with proto IMAP port 993 timeout 45 user '<user>@gmail.com' there with password 'secret' is \ 'paka' here options fetchall stripcr sslproto tls1 ssl sslcertck mda '/usr/lib/sendmail -i -oem -f %F %T' antispam 571 550 501 554
above has worked for quite some years w/o a problem and I cannot figure it out ?????
Have you tried port 443 ? (just a wild guess). Don't forget to change your password.
uuupsss, tks
443 provided same socket error :(
FWIW, 443 doesn't work here either, but I get responses on 993, ipv4 and ipv6. Can you ping imap.gmail.com ? -- Per Jessen, Zürich (13.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [09-05-19 14:31]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-05-19 12:10]:
Patrick Shanahan wrote:
substituted <user>
my server running fetchmail has stopped getting mail from gmail: fetchmail: timeout after 45 seconds waiting to connect to server imap.gmail.com. fetchmail: socket error while fetching from <user>@imap.gmail.com fetchmail: Query status=2 (SOCKET)
poll imap.gmail.com nodns tracepolls with proto IMAP port 993 timeout 45 user '<user>@gmail.com' there with password 'secret' is \ 'paka' here options fetchall stripcr sslproto tls1 ssl sslcertck mda '/usr/lib/sendmail -i -oem -f %F %T' antispam 571 550 501 554
above has worked for quite some years w/o a problem and I cannot figure it out ?????
Have you tried port 443 ? (just a wild guess). Don't forget to change your password.
uuupsss, tks
443 provided same socket error :(
FWIW, 443 doesn't work here either, but I get responses on 993, ipv4 and ipv6. Can you ping imap.gmail.com ?
openssl s_client -connect imap.gmail.com:995 and openssl s_client -connect imap.gmail.com:993 both work but take quit some time, may be the timeout indicated above (45 seconds waiting to connect). ping imap.gmail.com and pop.gmail.com both work w/o delay on a lark, copied certs from up-to-date tw to 42.2 server /usr/share/pki/trust restarted fetchmail but same timeouts/socket err tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [09-05-19 15:28]:
* Per Jessen <per@computer.org> [09-05-19 14:31]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-05-19 12:10]:
Patrick Shanahan wrote:
substituted <user>
my server running fetchmail has stopped getting mail from gmail: fetchmail: timeout after 45 seconds waiting to connect to server imap.gmail.com. fetchmail: socket error while fetching from <user>@imap.gmail.com fetchmail: Query status=2 (SOCKET)
poll imap.gmail.com nodns tracepolls with proto IMAP port 993 timeout 45 user '<user>@gmail.com' there with password 'secret' is \ 'paka' here options fetchall stripcr sslproto tls1 ssl sslcertck mda '/usr/lib/sendmail -i -oem -f %F %T' antispam 571 550 501 554
above has worked for quite some years w/o a problem and I cannot figure it out ?????
Have you tried port 443 ? (just a wild guess). Don't forget to change your password.
uuupsss, tks
443 provided same socket error :(
FWIW, 443 doesn't work here either, but I get responses on 993, ipv4 and ipv6. Can you ping imap.gmail.com ?
openssl s_client -connect imap.gmail.com:995 and openssl s_client -connect imap.gmail.com:993
both work but take quit some time, may be the timeout indicated above (45 seconds waiting to connect).
ping imap.gmail.com and pop.gmail.com both work w/o delay
on a lark, copied certs from up-to-date tw to 42.2 server /usr/share/pki/trust
restarted fetchmail but same timeouts/socket err
removed the "poll" timeout for test -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [09-05-19 15:43]:
* Patrick Shanahan <paka@opensuse.org> [09-05-19 15:28]:
* Per Jessen <per@computer.org> [09-05-19 14:31]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-05-19 12:10]:
Patrick Shanahan wrote:
substituted <user>
my server running fetchmail has stopped getting mail from gmail: fetchmail: timeout after 45 seconds waiting to connect to server imap.gmail.com. fetchmail: socket error while fetching from <user>@imap.gmail.com fetchmail: Query status=2 (SOCKET)
poll imap.gmail.com nodns tracepolls with proto IMAP port 993 timeout 45 user '<user>@gmail.com' there with password 'secret' is \ 'paka' here options fetchall stripcr sslproto tls1 ssl sslcertck mda '/usr/lib/sendmail -i -oem -f %F %T' antispam 571 550 501 554
above has worked for quite some years w/o a problem and I cannot figure it out ?????
Have you tried port 443 ? (just a wild guess). Don't forget to change your password.
uuupsss, tks
443 provided same socket error :(
FWIW, 443 doesn't work here either, but I get responses on 993, ipv4 and ipv6. Can you ping imap.gmail.com ?
openssl s_client -connect imap.gmail.com:995 and openssl s_client -connect imap.gmail.com:993
both work but take quit some time, may be the timeout indicated above (45 seconds waiting to connect).
ping imap.gmail.com and pop.gmail.com both work w/o delay
on a lark, copied certs from up-to-date tw to 42.2 server /usr/share/pki/trust
restarted fetchmail but same timeouts/socket err
removed the "poll" timeout for test
put it back but changed to 360 and connected. will test shorter timeouts and put old certs back, slowly and report results tks for assistance. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [09-05-19 15:58]:
* Patrick Shanahan <paka@opensuse.org> [09-05-19 15:43]:
* Patrick Shanahan <paka@opensuse.org> [09-05-19 15:28]:
* Per Jessen <per@computer.org> [09-05-19 14:31]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-05-19 12:10]:
Patrick Shanahan wrote:
> substituted <user> > > my server running fetchmail has stopped getting mail from gmail: > fetchmail: timeout after 45 seconds waiting to connect to server > imap.gmail.com. fetchmail: socket error while fetching from > <user>@imap.gmail.com fetchmail: Query status=2 (SOCKET) > > > poll imap.gmail.com nodns tracepolls with proto IMAP port 993 > timeout 45 > user '<user>@gmail.com' there with password 'secret' is \ > 'paka' here options fetchall stripcr sslproto tls1 ssl > sslcertck > mda '/usr/lib/sendmail -i -oem -f %F %T' > antispam 571 550 501 554 > > > > above has worked for quite some years w/o a problem > and I cannot figure it out ?????
Have you tried port 443 ? (just a wild guess). Don't forget to change your password.
uuupsss, tks
443 provided same socket error :(
FWIW, 443 doesn't work here either, but I get responses on 993, ipv4 and ipv6. Can you ping imap.gmail.com ?
openssl s_client -connect imap.gmail.com:995 and openssl s_client -connect imap.gmail.com:993
both work but take quit some time, may be the timeout indicated above (45 seconds waiting to connect).
ping imap.gmail.com and pop.gmail.com both work w/o delay
on a lark, copied certs from up-to-date tw to 42.2 server /usr/share/pki/trust
restarted fetchmail but same timeouts/socket err
removed the "poll" timeout for test
put it back but changed to 360 and connected.
will test shorter timeouts and put old certs back, slowly and report results
tks for assistance.
just trying to work my head a little. do I need to reboot server to relieve the sockets problem? ss -l | wc -l provides 275, box has 8g memory -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/09/2019 21.26, Patrick Shanahan wrote:
* Per Jessen <> [09-05-19 14:31]:
Patrick Shanahan wrote:
...
restarted fetchmail but same timeouts/socket err
I just started a fetchmail run against gmail, and it is working perfectly. <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - 6.3.26 querying imap.gmail.com (protocol IMAP) at 2019-09-05T21:27:50 CEST: poll started <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - Trying to connect to 74.125.206.109/993...connected. <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - Server certificate: <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - Issuer Organization: Google Trust Services <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - Issuer CommonName: GTS CA 1O1 <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - Subject CommonName: imap.gmail.com <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - Subject Alternative Name: imap.gmail.com <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - imap.gmail.com key fingerprint: E3:26:B0:59:8B:36:92:96:89:DA:41:F4:FD:1E:3D:94 <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - IMAP< * OK Gimap ready for requests from 83..... m19mb38216074wmc <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - IMAP> A0001 CAPABILITY <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - 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 <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< A0001 OK Thats all she wrote! m19mb38216074wmc <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP> A0002 LOGIN "r....@gmail.com" * <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - 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 <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< A0002 OK r....@gmail.com authenticated (Success) <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP> A0003 SELECT "INBOX" <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< * FLAGS (\Answered \Flagged \Draft \Deleted \Seen $Forwarded $MDNSent $NotPhishing $Phishing $label1 $label3 $label4 Junk NonJunk jerks mio) <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen $Forwarded $MDNSent $NotPhishing $Phishing $label1 $label3 $label4 Junk NonJunk jerks mio \*)] Flags permitted. <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< * OK [UIDVALIDITY 2] UIDs valid. <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< * 1850 EXISTS <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< * 0 RECENT <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< * OK [UIDNEXT 544858] Predicted next UID. <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< * OK [HIGHESTMODSEQ 20315191] <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< A0003 OK [READ-WRITE] INBOX selected. (Success) <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP> A0004 EXPUNGE <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< A0004 OK Success <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - 1850 messages for r....@gmail.com at imap.gmail.com. <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP> A0005 FETCH 1:100 RFC822.SIZE <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< * 1 FETCH (RFC822.SIZE 6940) <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< * 2 FETCH (RFC822.SIZE 6915) <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< * 3 FETCH (RFC822.SIZE 10586) ... My configuration is unchanged since may 2017 at least: poll imap.gmail.com with interval 0 proto imap timeout 50, and tracepolls user r....@gmail.com, with password "....", is cer here, expunge 20, and ssl, and fetchall An hour ago I looked with Thunderdbird and it seemed a bit slow, but it always is. I learned a few days ago about this: <https://support.google.com/accounts/answer/185833> I get it in Spanish, so I can't paste it. Basically, you can get a separate password for each "less secure" application to make google happy. I'm not using it, but I'm considering. When my IP changes, like when using my laptop on tethering, Gmail blocks me and sends a security alert. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [09-05-19 15:58]:
On 05/09/2019 21.26, Patrick Shanahan wrote:
* Per Jessen <> [09-05-19 14:31]:
Patrick Shanahan wrote:
...
restarted fetchmail but same timeouts/socket err
I just started a fetchmail run against gmail, and it is working perfectly.
<2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - 6.3.26 querying imap.gmail.com (protocol IMAP) at 2019-09-05T21:27:50 CEST: poll started <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - Trying to connect to 74.125.206.109/993...connected. <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - Server certificate: <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - Issuer Organization: Google Trust Services <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - Issuer CommonName: GTS CA 1O1 <2.6> 2019-09-05 21:27:50 Telcontar fetchmail 23782 - - Subject CommonName: imap.gmail.com [...] <2.6> 2019-09-05 21:27:51 Telcontar fetchmail 23782 - - IMAP< * 3 FETCH (RFC822.SIZE 10586) ...
My configuration is unchanged since may 2017 at least:
poll imap.gmail.com with interval 0 proto imap timeout 50, and tracepolls user r....@gmail.com, with password "....", is cer here, expunge 20, and ssl, and fetchall
tks, will try your config and report.
An hour ago I looked with Thunderdbird and it seemed a bit slow, but it always is.
I learned a few days ago about this:
<https://support.google.com/accounts/answer/185833>
I get it in Spanish, so I can't paste it. Basically, you can get a separate password for each "less secure" application to make google happy.
I'm not using it, but I'm considering. When my IP changes, like when using my laptop on tethering, Gmail blocks me and sends a security alert.
will consider this when and if I must :) fwiw, increasing my timeout values (45 -> 360 -> 300) provides connection. don't know why the increase on googgles end :(. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/09/2019 22.15, Patrick Shanahan wrote:
* Carlos E. R. <> [09-05-19 15:58]:
...
fwiw, increasing my timeout values (45 -> 360 -> 300) provides connection. don't know why the increase on googgles end :(.
Gmail is slower than any of my other providers, every day. It is slow to connect, and it is slow to transfer me the emails. Which means, that Thunderbird also syncs slowly. Maybe now it is even slower. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [09-05-19 16:56]:
On 05/09/2019 22.15, Patrick Shanahan wrote:
* Carlos E. R. <> [09-05-19 15:58]:
...
fwiw, increasing my timeout values (45 -> 360 -> 300) provides connection. don't know why the increase on googgles end :(.
Gmail is slower than any of my other providers, every day. It is slow to connect, and it is slow to transfer me the emails. Which means, that Thunderbird also syncs slowly.
Maybe now it is even slower.
amen to slower. I used to timeout at 60, now 180 appears to work. but I have other slow sockets on my server. that I don't understand. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/09/2019 23.12, Patrick Shanahan wrote:
* Carlos E. R. <> [09-05-19 16:56]:
On 05/09/2019 22.15, Patrick Shanahan wrote:
* Carlos E. R. <> [09-05-19 15:58]:
...
fwiw, increasing my timeout values (45 -> 360 -> 300) provides connection. don't know why the increase on googgles end :(.
Gmail is slower than any of my other providers, every day. It is slow to connect, and it is slow to transfer me the emails. Which means, that Thunderbird also syncs slowly.
Maybe now it is even slower.
amen to slower. I used to timeout at 60, now 180 appears to work. but I have other slow sockets on my server. that I don't understand.
Can not be related. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Patrick Shanahan <paka@opensuse.org> [09-05-19 16:48]:
* Carlos E. R. <robin.listas@telefonica.net> [09-05-19 15:58]: [...]
My configuration is unchanged since may 2017 at least:
poll imap.gmail.com with interval 0 proto imap timeout 50, and tracepolls user r....@gmail.com, with password "....", is cer here, expunge 20, and ssl, and fetchall
tks, will try your config and report.
An hour ago I looked with Thunderdbird and it seemed a bit slow, but it always is.
I learned a few days ago about this:
<https://support.google.com/accounts/answer/185833>
I get it in Spanish, so I can't paste it. Basically, you can get a separate password for each "less secure" application to make google happy.
I'm not using it, but I'm considering. When my IP changes, like when using my laptop on tethering, Gmail blocks me and sends a security alert.
will consider this when and if I must :)
fwiw, increasing my timeout values (45 -> 360 -> 300) provides connection. don't know why the increase on googgles end :(.
your config works so long as I increase the timeout to 180 which also works for my config. but my server is still quite socket timeout sensitive. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/09/2019 22.53, Patrick Shanahan wrote:
* Patrick Shanahan <> [09-05-19 16:48]:
* Carlos E. R. <> [09-05-19 15:58]:
fwiw, increasing my timeout values (45 -> 360 -> 300) provides connection. don't know why the increase on googgles end :(.
your config works so long as I increase the timeout to 180 which also works for my config.
Well, some improvement.
but my server is still quite socket timeout sensitive.
:-? I don't know about that. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Quoting Carlos E. R. <robin.listas@telefonica.net>: [snip]
I learned a few days ago about this:
<https://support.google.com/accounts/answer/185833>
I get it in Spanish, so I can't paste it. Basically, you can get a separate password for each "less secure" application to make google happy.
I'm not using it, but I'm considering. When my IP changes, like when using my laptop on tethering, Gmail blocks me and sends a security alert.
Google started tightening security a year or two ago on Google Apps e-mail (different from Gmail accounts). My professional organization, IEEE, uses Gmail for their e-mail aliases. Google quit using the usual IMAP/POP sign in protocols and moved to Oauth2. Fetchmail looked at it and decided this requires too much Web browser (HTTP) functionality and that they would not support it. I used Google's API library in Ruby to write a script to fetch Gmail. It worked fine for about a year. Then they wanted me to jump through hoops designed for corporations and apps to prove I was obeying EU privacy laws. No way for an individual running a script to jump through the hoop. Thunderbird handles the Google App style authentication, though I need to restart it several times a week. You may be encountering this paranoia/disease spreading to Gmail accounts. HTH, Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
openssl s_client -connect imap.gmail.com:995 and openssl s_client -connect imap.gmail.com:993
both work but take quit some time, may be the timeout indicated above (45 seconds waiting to connect). ping imap.gmail.com and pop.gmail.com both work w/o delay
I only tried with telnet, got immedate responses. Maybe it is TLS related - otoh, I just tried openssl s_client -connect imap.gmail.com:993 and had immediate response. (on a 15.0 system). Maybe try telnet too, and see if that also hangs ? -- Per Jessen, Zürich (12.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [09-06-19 01:51]:
Patrick Shanahan wrote:
openssl s_client -connect imap.gmail.com:995 and openssl s_client -connect imap.gmail.com:993
both work but take quit some time, may be the timeout indicated above (45 seconds waiting to connect). ping imap.gmail.com and pop.gmail.com both work w/o delay
I only tried with telnet, got immedate responses. Maybe it is TLS related - otoh, I just tried
openssl s_client -connect imap.gmail.com:993
and had immediate response. (on a 15.0 system). Maybe try telnet too, and see if that also hangs ?
wahoo:~ > time telnet imap.gmail.com telnet: connect to address 2607:f8b0:400d:c09::6c: Connection timed out telnet: connect to address 173.194.204.109: Connection timed out telnet: connect to address 173.194.204.108: Connection timed out real 6m21.730s user 0m0.000s sys 0m0.004s wahoo:~ > time openssl s_client -connect imap.gmail.com:993 > openssl.time.txt depth=2 OU = GlobalSign Root CA - R2, O = GlobalSign, CN = GlobalSign verify return:1 depth=1 C = US, O = Google Trust Services, CN = GTS CA 1O1 verify return:1 depth=0 C = US, ST = California, L = Mountain View, O = Google LLC, CN = imap.gmail.com verify return:1 read:errno=0 real 33m3.520s user 0m0.026s sys 0m0.004s openssl.time.txt: CONNECTED(00000003) --- Certificate chain 0 s:/C=US/ST=California/L=Mountain View/O=Google LLC/CN=imap.gmail.com i:/C=US/O=Google Trust Services/CN=GTS CA 1O1 1 s:/C=US/O=Google Trust Services/CN=GTS CA 1O1 i:/OU=GlobalSign Root CA - R2/O=GlobalSign/CN=GlobalSign --- Server certificate -----BEGIN CERTIFICATE----- MI <certificate removed> CDrOfMSLn2dyIzxoRv02wkwhwStH7+kKk= -----END CERTIFICATE----- subject=/C=US/ST=California/L=Mountain View/O=Google LLC/CN=imap.gmail.com issuer=/C=US/O=Google Trust Services/CN=GTS CA 1O1 --- No client certificate CA names sent Peer signing digest: SHA256 Server Temp Key: ECDH, P-256, 256 bits --- SSL handshake has read 3234 bytes and written 419 bytes --- New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256 Server public key is 2048 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : ECDHE-RSA-AES128-GCM-SHA256 Session-ID: 2840B91E33EEA3A3494226A4F8B4CEF5CB0541B5E2DBA5D0CE45A85268C50A0E Session-ID-ctx: Master-Key: 6FB08FD3D6C2E622BD7E754EAE7D3E62EA0C49AFBECC24C02592864E0B7B7BAE011DEE1A33035E005935E66DAB8628AE Key-Arg : None PSK identity: None PSK identity hint: None SRP username: None TLS session ticket lifetime hint: 100800 (seconds) TLS session ticket: 0000 - 00 c1 56 0e a4 82 67 89-b8 98 65 e6 fb a7 c7 f3 ..V...g...e..... 0010 - bd c7 c8 85 09 ed fc 1c-a0 9b d6 20 29 0a bc bc ........... )... 0020 - 66 99 87 28 cf 66 b0 3e-ce 9d 3c a2 ed 09 be 07 f..(.f.>..<..... 0030 - 5e e8 63 38 bf a0 37 91-09 99 3b 94 75 35 3d cf ^.c8..7...;.u5=. 0040 - fc 62 23 55 a1 00 1d 63-d3 93 bf 38 5c 46 83 1d .b#U...c...8\F.. 0050 - f5 ac e7 4c 40 b8 1d 62-81 f8 88 2c f4 e9 38 19 ...L@..b...,..8. 0060 - fb b1 fa 21 fb f0 c1 22-9b 1e bb 73 ca d3 b7 2a ...!..."...s...* 0070 - 39 2b 1b fb dd 7e ad f1-9d ae ca 41 30 0d ea 2a 9+...~.....A0..* 0080 - c0 6a 1c 76 58 33 43 5a-15 0c db e4 f2 14 2b e1 .j.vX3CZ......+. 0090 - 1a fd 87 eb db 6e 76 98-aa c0 23 8a be 1a 1c 86 .....nv...#..... 00a0 - 9e 22 fb 36 36 26 e9 37-73 fd 6d af 9f 04 3b 0c .".66&.7s.m...;. 00b0 - ac 0e 47 56 01 97 4e 4b-a4 e9 6d d4 6f d5 e6 94 ..GV..NK..m.o... 00c0 - 51 7e 25 1d d6 32 a8 6e-a9 c5 ac 14 5a ce 1d 7d Q~%..2.n....Z..} 00d0 - 25 a3 a8 51 b6 %..Q. Start Time: 1567774567 Timeout : 300 (sec) Verify return code: 0 (ok) --- * OK Gimap ready for requests from 108.246.209.12 n23mb55614055qtr maybe it makes sense to someone? again, the delays are not on my other local boxes, only the server and only the last several days. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-06-19 01:51]:
Patrick Shanahan wrote:
openssl s_client -connect imap.gmail.com:995 and openssl s_client -connect imap.gmail.com:993
both work but take quit some time, may be the timeout indicated above (45 seconds waiting to connect). ping imap.gmail.com and pop.gmail.com both work w/o delay
I only tried with telnet, got immedate responses. Maybe it is TLS related - otoh, I just tried
openssl s_client -connect imap.gmail.com:993
and had immediate response. (on a 15.0 system). Maybe try telnet too, and see if that also hangs ?
wahoo:~ > time telnet imap.gmail.com telnet: connect to address 2607:f8b0:400d:c09::6c: Connection timed out telnet: connect to address 173.194.204.109: Connection timed out telnet: connect to address 173.194.204.108: Connection timed out
Sorry, forgot to say you need to specify the port number, 993 or 143. i.e. telnet imap.gmail.com 993 If you get a virtually instant response, your connection is good. It looks to me like SSL is working too. That would seem to leave the problem in the actual fetching of mails. -- Per Jessen, Zürich (14.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [09-06-19 10:21]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-06-19 01:51]:
Patrick Shanahan wrote:
openssl s_client -connect imap.gmail.com:995 and openssl s_client -connect imap.gmail.com:993
both work but take quit some time, may be the timeout indicated above (45 seconds waiting to connect). ping imap.gmail.com and pop.gmail.com both work w/o delay
I only tried with telnet, got immedate responses. Maybe it is TLS related - otoh, I just tried
openssl s_client -connect imap.gmail.com:993
and had immediate response. (on a 15.0 system). Maybe try telnet too, and see if that also hangs ?
wahoo:~ > time telnet imap.gmail.com telnet: connect to address 2607:f8b0:400d:c09::6c: Connection timed out telnet: connect to address 173.194.204.109: Connection timed out telnet: connect to address 173.194.204.108: Connection timed out
Sorry, forgot to say you need to specify the port number, 993 or 143. i.e.
telnet imap.gmail.com 993
If you get a virtually instant response, your connection is good. It looks to me like SSL is working too. That would seem to leave the problem in the actual fetching of mails.
see other recent post, did not get quick response. currently testing with port 993 specified but appears slow. have to go on a job, back and report shortly. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-06-19 10:21]:
Sorry, forgot to say you need to specify the port number, 993 or 143. i.e.
telnet imap.gmail.com 993
If you get a virtually instant response, your connection is good. It looks to me like SSL is working too. That would seem to leave the problem in the actual fetching of mails.
see other recent post, did not get quick response. currently testing with port 993 specified but appears slow.
That sounds like a network issue - not necessarily your side. When I do "telnet imap.gmail.com 993", response is instant. Firewall issue? When you can ping imap.gmail.com and there are no delays, those packets are coming through - somehow there is a problem with tcp. -- Per Jessen, Zürich (13.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [09-06-19 14:13]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-06-19 10:21]:
Sorry, forgot to say you need to specify the port number, 993 or 143. i.e.
telnet imap.gmail.com 993
If you get a virtually instant response, your connection is good. It looks to me like SSL is working too. That would seem to leave the problem in the actual fetching of mails.
see other recent post, did not get quick response. currently testing with port 993 specified but appears slow.
That sounds like a network issue - not necessarily your side. When I do "telnet imap.gmail.com 993", response is instant.
Firewall issue? When you can ping imap.gmail.com and there are no delays, those packets are coming through - somehow there is a problem with tcp.
wahoo:~ > time telnet imap.gmail.com 993 Trying 2607:f8b0:400d:c08::6d... telnet: connect to address 2607:f8b0:400d:c08::6d: Connection timed out Trying 173.194.175.109... Connected to imap.gmail.com. Escape character is '^]'. ^CConnection closed by foreign host. real 2m14.793s user 0m0.003s sys 0m0.001s that makes it look like gmail doesn't like ipv6... and apparently my servier is defaulting to ipv6 first. and delay appears same with SuSEfirewall2 off. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-06-19 14:13]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-06-19 10:21]:
Sorry, forgot to say you need to specify the port number, 993 or 143. i.e.
telnet imap.gmail.com 993
If you get a virtually instant response, your connection is good. It looks to me like SSL is working too. That would seem to leave the problem in the actual fetching of mails.
see other recent post, did not get quick response. currently testing with port 993 specified but appears slow.
That sounds like a network issue - not necessarily your side. When I do "telnet imap.gmail.com 993", response is instant.
Firewall issue? When you can ping imap.gmail.com and there are no delays, those packets are coming through - somehow there is a problem with tcp.
wahoo:~ > time telnet imap.gmail.com 993 Trying 2607:f8b0:400d:c08::6d... telnet: connect to address 2607:f8b0:400d:c08::6d: Connection timed out Trying 173.194.175.109... Connected to imap.gmail.com. Escape character is '^]'. ^CConnection closed by foreign host.
real 2m14.793s user 0m0.003s sys 0m0.001s
that makes it look like gmail doesn't like ipv6... and apparently my servier is defaulting to ipv6 first.
Do you have ipv6 locally? If you do, but you have no uplink, that could explain the situation. You could perhaps amend your 'poll' with something to restrict to ipv4 only. -- Per Jessen, Zürich (12.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [09-06-19 15:04]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-06-19 14:13]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-06-19 10:21]:
Sorry, forgot to say you need to specify the port number, 993 or 143. i.e.
telnet imap.gmail.com 993
If you get a virtually instant response, your connection is good. It looks to me like SSL is working too. That would seem to leave the problem in the actual fetching of mails.
see other recent post, did not get quick response. currently testing with port 993 specified but appears slow.
That sounds like a network issue - not necessarily your side. When I do "telnet imap.gmail.com 993", response is instant.
Firewall issue? When you can ping imap.gmail.com and there are no delays, those packets are coming through - somehow there is a problem with tcp.
wahoo:~ > time telnet imap.gmail.com 993 Trying 2607:f8b0:400d:c08::6d... telnet: connect to address 2607:f8b0:400d:c08::6d: Connection timed out Trying 173.194.175.109... Connected to imap.gmail.com. Escape character is '^]'. ^CConnection closed by foreign host.
real 2m14.793s user 0m0.003s sys 0m0.001s
that makes it look like gmail doesn't like ipv6... and apparently my servier is defaulting to ipv6 first.
Do you have ipv6 locally? If you do, but you have no uplink, that could explain the situation.
You could perhaps amend your 'poll' with something to restrict to ipv4 only.
researching fetchmail appears ipv6 not available ??? and substituting the ipv4 ###.###.###.### for imap.gmail.com only works a couple of times then Server CommonName mismatch: imap.gmail.com != 173.194.175.108 may have to change to getmail ??? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/09/2019 21.11, Patrick Shanahan wrote:
* Per Jessen <> [09-06-19 15:04]:
Patrick Shanahan wrote:
wahoo:~ > time telnet imap.gmail.com 993 Trying 2607:f8b0:400d:c08::6d... telnet: connect to address 2607:f8b0:400d:c08::6d: Connection timed out Trying 173.194.175.109... Connected to imap.gmail.com. Escape character is '^]'. ^CConnection closed by foreign host.
real 2m14.793s user 0m0.003s sys 0m0.001s
that makes it look like gmail doesn't like ipv6... and apparently my servier is defaulting to ipv6 first.
Do you have ipv6 locally? If you do, but you have no uplink, that could explain the situation.
You could perhaps amend your 'poll' with something to restrict to ipv4 only.
researching fetchmail appears ipv6 not available ??? and substituting the ipv4 ###.###.###.### for imap.gmail.com only works a couple of times then Server CommonName mismatch: imap.gmail.com != 173.194.175.108
may have to change to getmail ???
You can use gai.conf to select preference to IPv4. #precedence ::1/128 50 #precedence ::/0 40 #precedence 2002::/16 30 #precedence ::/96 20 #precedence ::ffff:0:0/96 10 # # For sites which prefer IPv4 connections change the last line to # precedence ::ffff:0:0/96 100 #CER <http://www.fetchmail.info/> What fetchmail does: Fetchmail is a full-featured, robust, well-documented remote-mail retrieval and forwarding utility intended to be used over on-demand TCP/IP links (such as SLIP or PPP connections). It supports every remote-mail protocol now in use on the Internet: POP2, POP3, RPOP, APOP, KPOP, all flavors of IMAP, ETRN, and ODMR. It can even support *IPv6* and IPSEC. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [09-06-19 16:02]:
On 06/09/2019 21.11, Patrick Shanahan wrote:
* Per Jessen <> [09-06-19 15:04]:
Patrick Shanahan wrote:
wahoo:~ > time telnet imap.gmail.com 993 Trying 2607:f8b0:400d:c08::6d... telnet: connect to address 2607:f8b0:400d:c08::6d: Connection timed out Trying 173.194.175.109... Connected to imap.gmail.com. Escape character is '^]'. ^CConnection closed by foreign host.
real 2m14.793s user 0m0.003s sys 0m0.001s
that makes it look like gmail doesn't like ipv6... and apparently my servier is defaulting to ipv6 first.
Do you have ipv6 locally? If you do, but you have no uplink, that could explain the situation.
You could perhaps amend your 'poll' with something to restrict to ipv4 only.
researching fetchmail appears ipv6 not available ??? and substituting the ipv4 ###.###.###.### for imap.gmail.com only works a couple of times then Server CommonName mismatch: imap.gmail.com != 173.194.175.108
may have to change to getmail ???
You can use gai.conf to select preference to IPv4.
#precedence ::1/128 50 #precedence ::/0 40 #precedence 2002::/16 30 #precedence ::/96 20 #precedence ::ffff:0:0/96 10 # # For sites which prefer IPv4 connections change the last line to # precedence ::ffff:0:0/96 100 #CER
and uncommenting that last precedence line provides the fetchmail service I experienced before the last several days. but do I want to keep this precedence? does that do the same as turning off ipv6? not sure I really understand what this does. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/09/2019 22.16, Patrick Shanahan wrote:
* Carlos E. R. <> [09-06-19 16:02]:
On 06/09/2019 21.11, Patrick Shanahan wrote:
* Per Jessen <> [09-06-19 15:04]:
Patrick Shanahan wrote:
You can use gai.conf to select preference to IPv4.
#precedence ::1/128 50 #precedence ::/0 40 #precedence 2002::/16 30 #precedence ::/96 20 #precedence ::ffff:0:0/96 10 # # For sites which prefer IPv4 connections change the last line to # precedence ::ffff:0:0/96 100 #CER
and uncommenting that last precedence line provides the fetchmail service I experienced before the last several days.
but do I want to keep this precedence? does that do the same as turning off ipv6?
not sure I really understand what this does.
That applications will choose IPv4 when both are available. If no IPv4 address, then they will use IPv6. For all applications. Sigh. IPv6 is not ready yet.
tks,
Welcome :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [09-06-19 18:14]:
On 06/09/2019 22.16, Patrick Shanahan wrote:
* Carlos E. R. <> [09-06-19 16:02]:
On 06/09/2019 21.11, Patrick Shanahan wrote:
* Per Jessen <> [09-06-19 15:04]:
Patrick Shanahan wrote:
You can use gai.conf to select preference to IPv4.
#precedence ::1/128 50 #precedence ::/0 40 #precedence 2002::/16 30 #precedence ::/96 20 #precedence ::ffff:0:0/96 10 # # For sites which prefer IPv4 connections change the last line to # precedence ::ffff:0:0/96 100 #CER
and uncommenting that last precedence line provides the fetchmail service I experienced before the last several days.
but do I want to keep this precedence? does that do the same as turning off ipv6?
not sure I really understand what this does.
That applications will choose IPv4 when both are available. If no IPv4 address, then they will use IPv6. For all applications.
possibly solved resterted server network, "systemctl restart network" reduced timeout parameters in .fetchmailrc fetchmail works as before w/o the delays and timeouts returned /etc/gai.conf to it's default restarted server network again restarted fetchmail with all timeouts set to 45 seconds mail system is working normally openssl s_client -connect imap.gmail.com:995 -showcerts is nearly instantaneous apparently there was a network problem, but I know not why. tks everyone for the help and persistance. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
possibly solved resterted server network, "systemctl restart network"
reduced timeout parameters in .fetchmailrc fetchmail works as before w/o the delays and timeouts
returned /etc/gai.conf to it's default restarted server network again restarted fetchmail with all timeouts set to 45 seconds
mail system is working normally
openssl s_client -connect imap.gmail.com:995 -showcerts is nearly instantaneous
apparently there was a network problem, but I know not why.
For the IPv6-sceptics - this is an excellent example of a transparent migration to IPv6 ... in 2015. It's not black magic, it just works. -- Per Jessen, Zürich (14.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/09/2019 09.39, Per Jessen wrote:
Patrick Shanahan wrote:
possibly solved resterted server network, "systemctl restart network"
reduced timeout parameters in .fetchmailrc fetchmail works as before w/o the delays and timeouts
returned /etc/gai.conf to it's default restarted server network again restarted fetchmail with all timeouts set to 45 seconds
mail system is working normally
openssl s_client -connect imap.gmail.com:995 -showcerts is nearly instantaneous
apparently there was a network problem, but I know not why.
For the IPv6-sceptics - this is an excellent example of a transparent migration to IPv6 ... in 2015. It's not black magic, it just works.
Well, it is the second time I see a very similar problem, where IPv6 stopped to work and required a reboot. The other instance a reboot of the router, IIRC. Not sure who he was. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 09/07/2019 12:39 AM, Per Jessen wrote:
Patrick Shanahan wrote:
possibly solved resterted server network, "systemctl restart network"
reduced timeout parameters in .fetchmailrc fetchmail works as before w/o the delays and timeouts
returned /etc/gai.conf to it's default restarted server network again restarted fetchmail with all timeouts set to 45 seconds
mail system is working normally
openssl s_client -connect imap.gmail.com:995 -showcerts is nearly instantaneous
apparently there was a network problem, but I know not why. For the IPv6-sceptics - this is an excellent example of a transparent migration to IPv6 ... in 2015. It's not black magic, it just works.
:-D Except for when it doesn't work... Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/09/2019 14:56, Per Jessen wrote:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-06-19 14:13]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-06-19 10:21]:
Sorry, forgot to say you need to specify the port number, 993 or 143. i.e.
telnet imap.gmail.com 993
If you get a virtually instant response, your connection is good. It looks to me like SSL is working too. That would seem to leave the problem in the actual fetching of mails.
see other recent post, did not get quick response. currently testing with port 993 specified but appears slow.
That sounds like a network issue - not necessarily your side. When I do "telnet imap.gmail.com 993", response is instant.
Firewall issue? When you can ping imap.gmail.com and there are no delays, those packets are coming through - somehow there is a problem with tcp.
wahoo:~ > time telnet imap.gmail.com 993 Trying 2607:f8b0:400d:c08::6d... telnet: connect to address 2607:f8b0:400d:c08::6d: Connection timed out Trying 173.194.175.109... Connected to imap.gmail.com. Escape character is '^]'. ^CConnection closed by foreign host.
real 2m14.793s user 0m0.003s sys 0m0.001s
that makes it look like gmail doesn't like ipv6... and apparently my servier is defaulting to ipv6 first.
Do you have ipv6 locally? If you do, but you have no uplink, that could explain the situation.
You could perhaps amend your 'poll' with something to restrict to ipv4 only.
This goes back 4 years ... https://lists.opensuse.org/opensuse/2015-07/msg00739.html -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/09/2019 00.21, Anton Aylward wrote:
On 06/09/2019 14:56, Per Jessen wrote:
Patrick Shanahan wrote:
wahoo:~ > time telnet imap.gmail.com 993 Trying 2607:f8b0:400d:c08::6d... telnet: connect to address 2607:f8b0:400d:c08::6d: Connection timed out Trying 173.194.175.109... Connected to imap.gmail.com. Escape character is '^]'. ^CConnection closed by foreign host.
real 2m14.793s user 0m0.003s sys 0m0.001s
that makes it look like gmail doesn't like ipv6... and apparently my servier is defaulting to ipv6 first.
Do you have ipv6 locally? If you do, but you have no uplink, that could explain the situation.
You could perhaps amend your 'poll' with something to restrict to ipv4 only.
This goes back 4 years ... https://lists.opensuse.org/opensuse/2015-07/msg00739.html
Yes, it is the same problem. Unfortunately that solution disables upstream DNS search; it is rather a test. Since then we found another solution. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 07/09/2019 00.21, Anton Aylward wrote:
On 06/09/2019 14:56, Per Jessen wrote:
Patrick Shanahan wrote:
wahoo:~ > time telnet imap.gmail.com 993 Trying 2607:f8b0:400d:c08::6d... telnet: connect to address 2607:f8b0:400d:c08::6d: Connection timed out Trying 173.194.175.109... Connected to imap.gmail.com. Escape character is '^]'. ^CConnection closed by foreign host.
real 2m14.793s user 0m0.003s sys 0m0.001s
that makes it look like gmail doesn't like ipv6... and apparently my servier is defaulting to ipv6 first.
Do you have ipv6 locally? If you do, but you have no uplink, that could explain the situation.
You could perhaps amend your 'poll' with something to restrict to ipv4 only.
This goes back 4 years ... https://lists.opensuse.org/opensuse/2015-07/msg00739.html
Yes, it is the same problem.
Interesting. So Patrick has had IPv6 for years. Patrick, unless something changed in your environment before fetchmail started failing, you have most likely been retrieving your mail over IPv6 for quite some time. Good stuff! -- Per Jessen, Zürich (14.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [09-06-19 12:56]:
* Per Jessen <per@computer.org> [09-06-19 10:21]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-06-19 01:51]:
Patrick Shanahan wrote:
openssl s_client -connect imap.gmail.com:995 and openssl s_client -connect imap.gmail.com:993
both work but take quit some time, may be the timeout indicated above (45 seconds waiting to connect). ping imap.gmail.com and pop.gmail.com both work w/o delay
I only tried with telnet, got immedate responses. Maybe it is TLS related - otoh, I just tried
openssl s_client -connect imap.gmail.com:993
and had immediate response. (on a 15.0 system). Maybe try telnet too, and see if that also hangs ?
wahoo:~ > time telnet imap.gmail.com telnet: connect to address 2607:f8b0:400d:c09::6c: Connection timed out telnet: connect to address 173.194.204.109: Connection timed out telnet: connect to address 173.194.204.108: Connection timed out
Sorry, forgot to say you need to specify the port number, 993 or 143. i.e.
telnet imap.gmail.com 993
If you get a virtually instant response, your connection is good. It looks to me like SSL is working too. That would seem to leave the problem in the actual fetching of mails.
see other recent post, did not get quick response. currently testing with port 993 specified but appears slow. have to go on a job, back and report shortly.
pinging imap.gmail.com appears normal/almost instantaneous, ~50 ms substituting an ipv4 address for imap.gmail.com returns normal timeout openssl s_client -connect 209.85.201.108:993 -showcerts appears instantenous looks like the problem is gmail chocking on ipv6 which my server appears to present first/default. substituting the ipv4 address for imap.gmail.com makes fetchmail work as before. google has a problem, I believe? fwiw: pop3.live.com (access to old hotmail accounts) has same problem. but substituting ipv4 addr does not solve -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
looks like the problem is gmail chocking on ipv6 which my server appears to present first/default. substituting the ipv4 address for imap.gmail.com makes fetchmail work as before. google has a problem, I believe?
Hmm, I think it's on your side - imap.gmail.com does have an ipv6 address, but your system should not be trying it when it has no IPv6 connectivity. On the system where you run fetchmail, could you show us output from: ip addr ip route show ip -6 route show -- Per Jessen, Zürich (12.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [09-06-19 15:05]:
Patrick Shanahan wrote:
looks like the problem is gmail chocking on ipv6 which my server appears to present first/default. substituting the ipv4 address for imap.gmail.com makes fetchmail work as before. google has a problem, I believe?
Hmm, I think it's on your side - imap.gmail.com does have an ipv6 address, but your system should not be trying it when it has no IPv6 connectivity.
On the system where you run fetchmail, could you show us output from:
ip addr ip route show ip -6 route show
ip addr: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 78:e3:b5:ad:f1:2f brd ff:ff:ff:ff:ff:ff inet 192.168.1.3/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 2600:1702:1031:3f91:9c18:980c:30e6:1d80/64 scope global temporary dynamic valid_lft 544938sec preferred_lft 25938sec inet6 2600:1702:1031:3f90:d163:5440:8c25:63e2/64 scope global temporary dynamic valid_lft 3309sec preferred_lft 298sec inet6 2600:1702:1031:3f91:d163:5440:8c25:63e2/64 scope global temporary deprecated dynamic valid_lft 459141sec preferred_lft 0sec inet6 2600:1702:1031:3f90:e4c2:d431:6f9e:4042/64 scope global temporary deprecated dynamic valid_lft 3309sec preferred_lft 0sec inet6 2600:1702:1031:3f91:e4c2:d431:6f9e:4042/64 scope global temporary deprecated dynamic valid_lft 373344sec preferred_lft 0sec inet6 2600:1702:1031:3f91:7ae3:b5ff:fead:f12f/64 scope global mngtmpaddr dynamic valid_lft 2360544sec preferred_lft 373344sec inet6 2600:1702:1031:3f90:7da1:479a:1b69:e73c/64 scope global temporary deprecated dynamic valid_lft 3309sec preferred_lft 0sec inet6 2600:1702:1031:3f90:137:537:d238:3ea8/64 scope global temporary deprecated dynamic valid_lft 3309sec preferred_lft 0sec inet6 2600:1702:1031:3f90:798b:91ad:8874:a225/64 scope global temporary deprecated dynamic valid_lft 3309sec preferred_lft 0sec inet6 2600:1702:1031:3f90:24f0:3292:6ccc:6c0a/64 scope global temporary deprecated dynamic valid_lft 3309sec preferred_lft 0sec inet6 2600:1702:1031:3f90:c9fd:4b77:497:b9aa/64 scope global temporary deprecated dynamic valid_lft 3309sec preferred_lft 0sec inet6 2600:1702:1031:3f90:7ae3:b5ff:fead:f12f/64 scope global mngtmpaddr dynamic valid_lft 3309sec preferred_lft 3309sec inet6 fe80::7ae3:b5ff:fead:f12f/64 scope link valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 74:de:2b:df:0e:c9 brd ff:ff:ff:ff:ff:ff ip route show: default via 192.168.1.254 dev eth0 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.3 ip -6 route show: 2600:1702:1031:3f90::/64 dev eth0 proto kernel metric 256 expires 3287sec pref medium 2600:1702:1031:3f91::/64 dev eth0 proto kernel metric 256 expires 2360523sec pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium default via fe80::de7f:a4ff:fe21:cd8d dev eth0 proto ra metric 1024 expires 1487sec hoplimit 64 pref medium tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
On the system where you run fetchmail, could you show us output from:
ip addr ip route show ip -6 route show
ip addr: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 78:e3:b5:ad:f1:2f brd ff:ff:ff:ff:ff:ff inet 192.168.1.3/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 2600:1702:1031:3f91:9c18:980c:30e6:1d80/64 scope global temporary dynamic valid_lft 544938sec preferred_lft 25938sec
Perfect! You have IPv6 on your local network.
ip -6 route show: 2600:1702:1031:3f90::/64 dev eth0 proto kernel metric 256 expires 3287sec pref medium 2600:1702:1031:3f91::/64 dev eth0 proto kernel metric 256 expires 2360523sec pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium default via fe80::de7f:a4ff:fe21:cd8d dev eth0 proto ra metric 1024 expires 1487sec hoplimit 64 pref medium
The latter, default ipv6 route, is your uplink router, so in principle it ought to work. From here, accessing imap.gmail.com over ipv6 does work, but clearly yours does not. What does 'ping6 imap.gmail.com' say? I'm hoping it will say destination unreachable. I suspect a routing issue. I think you have two options - a) force your system(s) to only use ipv4 b) try to solve the uplink ipv6 issue -- Per Jessen, Zürich (13.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [09-07-19 03:31]:
Patrick Shanahan wrote:
On the system where you run fetchmail, could you show us output from:
ip addr ip route show ip -6 route show
ip addr: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 78:e3:b5:ad:f1:2f brd ff:ff:ff:ff:ff:ff inet 192.168.1.3/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 2600:1702:1031:3f91:9c18:980c:30e6:1d80/64 scope global temporary dynamic valid_lft 544938sec preferred_lft 25938sec
Perfect! You have IPv6 on your local network.
ip -6 route show: 2600:1702:1031:3f90::/64 dev eth0 proto kernel metric 256 expires 3287sec pref medium 2600:1702:1031:3f91::/64 dev eth0 proto kernel metric 256 expires 2360523sec pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium default via fe80::de7f:a4ff:fe21:cd8d dev eth0 proto ra metric 1024 expires 1487sec hoplimit 64 pref medium
The latter, default ipv6 route, is your uplink router, so in principle it ought to work. From here, accessing imap.gmail.com over ipv6 does work, but clearly yours does not.
What does 'ping6 imap.gmail.com' say? I'm hoping it will say destination unreachable. I suspect a routing issue.
I think you have two options -
a) force your system(s) to only use ipv4 b) try to solve the uplink ipv6 issue
fortunately or unfortunately depending on ones position, restarting network on the server appears to have solved the problem. "a" worked for a short time before I restarted the network and now ping6s times are respectable. wahoo:~ > ping6 imap.gmail.com PING imap.gmail.com(qn-in-x6d.1e100.net) 56 data bytes 64 bytes from qn-in-x6d.1e100.net: icmp_seq=1 ttl=44 time=50.5 ms 64 bytes from qn-in-x6d.1e100.net: icmp_seq=2 ttl=44 time=50.5 ms I cannot say with *any* certainty what was actually wrong, only that resetting the network appears to have solved the mail problem. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/09/2019 13.59, Patrick Shanahan wrote:
* Per Jessen <> [09-07-19 03:31]:
Patrick Shanahan wrote:
...
I think you have two options -
a) force your system(s) to only use ipv4 b) try to solve the uplink ipv6 issue
fortunately or unfortunately depending on ones position, restarting network on the server appears to have solved the problem. "a" worked for a short time before I restarted the network and now ping6s times are respectable. wahoo:~ > ping6 imap.gmail.com PING imap.gmail.com(qn-in-x6d.1e100.net) 56 data bytes 64 bytes from qn-in-x6d.1e100.net: icmp_seq=1 ttl=44 time=50.5 ms 64 bytes from qn-in-x6d.1e100.net: icmp_seq=2 ttl=44 time=50.5 ms
I cannot say with *any* certainty what was actually wrong, only that resetting the network appears to have solved the mail problem.
You had a similar problem last month: [opensuse] something with IPV6 causing Tumbleweed connection problems? IPv6 connectivity to yahoo was lost. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [09-07-19 14:14]:
On 07/09/2019 13.59, Patrick Shanahan wrote:
* Per Jessen <> [09-07-19 03:31]:
Patrick Shanahan wrote:
...
I think you have two options -
a) force your system(s) to only use ipv4 b) try to solve the uplink ipv6 issue
fortunately or unfortunately depending on ones position, restarting network on the server appears to have solved the problem. "a" worked for a short time before I restarted the network and now ping6s times are respectable. wahoo:~ > ping6 imap.gmail.com PING imap.gmail.com(qn-in-x6d.1e100.net) 56 data bytes 64 bytes from qn-in-x6d.1e100.net: icmp_seq=1 ttl=44 time=50.5 ms 64 bytes from qn-in-x6d.1e100.net: icmp_seq=2 ttl=44 time=50.5 ms
I cannot say with *any* certainty what was actually wrong, only that resetting the network appears to have solved the mail problem.
You had a similar problem last month:
[opensuse] something with IPV6 causing Tumbleweed connection problems?
IPv6 connectivity to yahoo was lost.
I guess I did, but that was all local machines and this instance *only* affected my server but is the same router. and restarting network on the server would not correct the router. ??? fwiw: I complained to at&t and they are sending a tech to look at my lines and modem/router, Wednesday next. guess my connectivity is not important to at&t. and I will change providers shortly, back to cable. my experiences with at&t are not good or even average ... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/09/2019 20.30, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [09-07-19 14:14]:
On 07/09/2019 13.59, Patrick Shanahan wrote:
* Per Jessen <> [09-07-19 03:31]:
Patrick Shanahan wrote:
...
I think you have two options -
a) force your system(s) to only use ipv4 b) try to solve the uplink ipv6 issue
fortunately or unfortunately depending on ones position, restarting network on the server appears to have solved the problem. "a" worked for a short time before I restarted the network and now ping6s times are respectable. wahoo:~ > ping6 imap.gmail.com PING imap.gmail.com(qn-in-x6d.1e100.net) 56 data bytes 64 bytes from qn-in-x6d.1e100.net: icmp_seq=1 ttl=44 time=50.5 ms 64 bytes from qn-in-x6d.1e100.net: icmp_seq=2 ttl=44 time=50.5 ms
I cannot say with *any* certainty what was actually wrong, only that resetting the network appears to have solved the mail problem.
You had a similar problem last month:
[opensuse] something with IPV6 causing Tumbleweed connection problems?
IPv6 connectivity to yahoo was lost.
I guess I did, but that was all local machines and this instance *only* affected my server but is the same router. and restarting network on the server would not correct the router. ???
Problem is, at least me I don't have an exact idea of why it failed in both cases, for IPv6 only.
fwiw: I complained to at&t and they are sending a tech to look at my lines and modem/router, Wednesday next. guess my connectivity is not important to at&t. and I will change providers shortly, back to cable. my experiences with at&t are not good or even average ...
:-( I have been lucky so far with Telefonica, which was more or less founded by ITT, so which I tend to confuse with AT&T. People here post similar complains as you do about Ma Bell and look a likes :-p That said, I get much better service by entering my issues on Telefonica web forum than by using the phone. Service is slower, but the people seem to know their stuff and not be talking heads. And I don't have to fight the entry robot. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [09-07-19 14:49]:
On 07/09/2019 20.30, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [09-07-19 14:14]:
On 07/09/2019 13.59, Patrick Shanahan wrote:
* Per Jessen <> [09-07-19 03:31]:
Patrick Shanahan wrote:
...
I think you have two options -
a) force your system(s) to only use ipv4 b) try to solve the uplink ipv6 issue
fortunately or unfortunately depending on ones position, restarting network on the server appears to have solved the problem. "a" worked for a short time before I restarted the network and now ping6s times are respectable. wahoo:~ > ping6 imap.gmail.com PING imap.gmail.com(qn-in-x6d.1e100.net) 56 data bytes 64 bytes from qn-in-x6d.1e100.net: icmp_seq=1 ttl=44 time=50.5 ms 64 bytes from qn-in-x6d.1e100.net: icmp_seq=2 ttl=44 time=50.5 ms
I cannot say with *any* certainty what was actually wrong, only that resetting the network appears to have solved the mail problem.
You had a similar problem last month:
[opensuse] something with IPV6 causing Tumbleweed connection problems?
IPv6 connectivity to yahoo was lost.
I guess I did, but that was all local machines and this instance *only* affected my server but is the same router. and restarting network on the server would not correct the router. ???
Problem is, at least me I don't have an exact idea of why it failed in both cases, for IPv6 only.
fwiw: I complained to at&t and they are sending a tech to look at my lines and modem/router, Wednesday next. guess my connectivity is not important to at&t. and I will change providers shortly, back to cable. my experiences with at&t are not good or even average ...
:-(
I have been lucky so far with Telefonica, which was more or less founded by ITT, so which I tend to confuse with AT&T. People here post similar complains as you do about Ma Bell and look a likes :-p
That said, I get much better service by entering my issues on Telefonica web forum than by using the phone. Service is slower, but the people seem to know their stuff and not be talking heads.
And I don't have to fight the entry robot.
will advise result of ?tech? visit and whatever repairs/replacements. hopefully the ?tech? will know more than I do. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/09/2019 09:43, Patrick Shanahan wrote:
again, the delays are not on my other local boxes, only the server and only the last several days.
That makes me suspicious that the server doesn't have a certain library, or possibly a different implementation of a library. I can't pin it down as to a specific, just a feeling that, if it were my machine, I try to figure out how to investigate, comparing what's in the RPM datatbases and such. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Anton Aylward <opensuse@antonaylward.com> [09-06-19 11:16]:
On 06/09/2019 09:43, Patrick Shanahan wrote:
again, the delays are not on my other local boxes, only the server and only the last several days.
That makes me suspicious that the server doesn't have a certain library, or possibly a different implementation of a library. I can't pin it down as to a specific, just a feeling that, if it were my machine, I try to figure out how to investigate, comparing what's in the RPM datatbases and such.
that would *really* be odd as the server has worked properly/acceptably for >4 years w/o a similar problem until the last several days and has had virtually no updates for over a year. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/09/2019 18.42, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [09-06-19 11:16]:
On 06/09/2019 09:43, Patrick Shanahan wrote:
again, the delays are not on my other local boxes, only the server and only the last several days.
Weird.
That makes me suspicious that the server doesn't have a certain library, or possibly a different implementation of a library. I can't pin it down as to a specific, just a feeling that, if it were my machine, I try to figure out how to investigate, comparing what's in the RPM datatbases and such.
that would *really* be odd as the server has worked properly/acceptably for >4 years w/o a similar problem until the last several days and has had virtually no updates for over a year.
Not a tumbleweed machine? What firewall? When was last reboot? -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [09-06-19 14:49]:
On 06/09/2019 18.42, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [09-06-19 11:16]:
On 06/09/2019 09:43, Patrick Shanahan wrote:
again, the delays are not on my other local boxes, only the server and only the last several days.
Weird.
That makes me suspicious that the server doesn't have a certain library, or possibly a different implementation of a library. I can't pin it down as to a specific, just a feeling that, if it were my machine, I try to figure out how to investigate, comparing what's in the RPM datatbases and such.
that would *really* be odd as the server has worked properly/acceptably for >4 years w/o a similar problem until the last several days and has had virtually no updates for over a year.
Not a tumbleweed machine?
Leap 42.2
What firewall?
SuSEfirewall2
When was last reboot?
wahoo:~ > uptime 14:58pm up 16 days 21:01, 10 users, load average: 0.28, 0.23, 0.19 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/09/2019 20.59, Patrick Shanahan wrote:
* Carlos E. R. <> [09-06-19 14:49]:
On 06/09/2019 18.42, Patrick Shanahan wrote:
* Anton Aylward <> [09-06-19 11:16]:
On 06/09/2019 09:43, Patrick Shanahan wrote:
again, the delays are not on my other local boxes, only the server and only the last several days.
Weird.
That makes me suspicious that the server doesn't have a certain library, or possibly a different implementation of a library. I can't pin it down as to a specific, just a feeling that, if it were my machine, I try to figure out how to investigate, comparing what's in the RPM datatbases and such.
that would *really* be odd as the server has worked properly/acceptably for >4 years w/o a similar problem until the last several days and has had virtually no updates for over a year.
Not a tumbleweed machine?
Leap 42.2
What firewall?
SuSEfirewall2
When was last reboot?
wahoo:~ > uptime 14:58pm up 16 days 21:01, 10 users, load average: 0.28, 0.23, 0.19
I thought that a reboot might be in order, but it seems that your IPv6 connectivity is not good. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 05/09/2019 10:34, Patrick Shanahan wrote:
It failed beginning night before last, but worked for about 3 hours yesterday and then kaputtt.
Pouring over my logs in detail I see a burst of name resolution problems that then cleared up promptly followed by connections that responded "Resource unavailable" for that time period. I suspect Gmail had a outage or "unannounced maintenance" issue. My access to imap.gmail.com though fetchmail is now working. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Anton Aylward <opensuse@antonaylward.com> [09-05-19 12:16]:
On 05/09/2019 10:34, Patrick Shanahan wrote:
It failed beginning night before last, but worked for about 3 hours yesterday and then kaputtt.
Pouring over my logs in detail I see a burst of name resolution problems that then cleared up promptly followed by connections that responded "Resource unavailable" for that time period.
I suspect Gmail had a outage or "unannounced maintenance" issue.
My access to imap.gmail.com though fetchmail is now working.
I have no suck luck :( tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/09/2019 12:32, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [09-05-19 12:16]:
On 05/09/2019 10:34, Patrick Shanahan wrote:
It failed beginning night before last, but worked for about 3 hours yesterday and then kaputtt.
Pouring over my logs in detail I see a burst of name resolution problems that then cleared up promptly followed by connections that responded "Resource unavailable" for that time period.
I suspect Gmail had a outage or "unannounced maintenance" issue.
My access to imap.gmail.com though fetchmail is now working.
I have no suck luck :(
You may recall that last month I asked about GMail+fetchmail. You gave me a hint to the configure, but what made the difference was going into my GMail web page and altering the specific security to allow foreign applications. I suppose the 'hint' I should have seen was that my thunderbird ->imap setting used OAuth not cleartext :-) I'm using: poll imap.gmail.com nodns tracepolls with proto IMAP port 993 timeout 45 auth any user antonexxxxx@gmail.com there with password "YYYYYYYYYY" is "anton" here options fetchall stripcr sslproto tls1 ssl sslcertck mda "/usr/bin/procmail -f %F -d %T"; but even that didn't work until is tweaked the GMail security settings, as I mentioned. It seems the "auth any" tells it to try GSSAPI first. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Anton Aylward <opensuse@antonaylward.com> [09-05-19 23:14]:
On 05/09/2019 12:32, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [09-05-19 12:16]:
On 05/09/2019 10:34, Patrick Shanahan wrote:
It failed beginning night before last, but worked for about 3 hours yesterday and then kaputtt.
Pouring over my logs in detail I see a burst of name resolution problems that then cleared up promptly followed by connections that responded "Resource unavailable" for that time period.
I suspect Gmail had a outage or "unannounced maintenance" issue.
My access to imap.gmail.com though fetchmail is now working.
I have no suck luck :(
You may recall that last month I asked about GMail+fetchmail. You gave me a hint to the configure, but what made the difference was going into my GMail web page and altering the specific security to allow foreign applications.
I suppose the 'hint' I should have seen was that my thunderbird ->imap setting used OAuth not cleartext :-)
I'm using:
poll imap.gmail.com nodns tracepolls with proto IMAP port 993 timeout 45 auth any user antonexxxxx@gmail.com there with password "YYYYYYYYYY" is "anton" here options fetchall stripcr sslproto tls1 ssl sslcertck mda "/usr/bin/procmail -f %F -d %T";
but even that didn't work until is tweaked the GMail security settings, as I mentioned.
It seems the "auth any" tells it to try GSSAPI first.
will try "auth any" and see if it helps reduce the excessive timeout allotment. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/09/2019 23:24, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [09-05-19 23:14]:
It seems the "auth any" tells it to try GSSAPI first.
will try "auth any" and see if it helps reduce the excessive timeout allotment.
Per's email is a few hours later that your, reporting reasonable access time. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Anton Aylward <opensuse@antonaylward.com> [09-06-19 07:14]:
On 05/09/2019 23:24, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [09-05-19 23:14]:
It seems the "auth any" tells it to try GSSAPI first.
will try "auth any" and see if it helps reduce the excessive timeout allotment.
Per's email is a few hours later that your, reporting reasonable access time.
"auth any" does not improve the timeout :( fwiw: problem appears to *only* be on my server machine. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Anton Aylward -
Carlos E. R. -
Jeffrey L. Taylor -
Lew Wolfgang -
Patrick Shanahan -
Per Jessen