Fetchmail socket error while fetching from

Модератор: Bizdelnick

poll pop.gmail.com port 995 proto POP3 auth password
user "user@gmail.com" pass "passsw" is "localuser" here sslcertck keep

fetchmail: socket error while fetching from globusmira70@gmail.com@pop.gmail.com
fetchmail: Query status=2 (SOCKET)

fetchmail: timeout after 300 seconds waiting to connect to server gmail.com.
fetchmail: socket error while fetching from globusmira70@gmail.com
fetchmail: Query status=2 (SOCKET)

From: Google <no-reply@accounts.google.com>
To: rtgert
Subject: Вы можете потерять доступ к некоторым сторонним приложениям
Date: Sun, 06 Mar 2022 01:43:04 GMT

[image: Google]
30 мая вы можете потерять доступ к приложениям, использующим небезопасную
технологию входа


ertherh
Чтобы защитить ваш аккаунт, Google больше не будет поддерживать сторонние
приложения или устройства, которые предлагают войти в аккаунт Google только
с помощью имени пользователя и пароля. Вместо этого вам потребуется
выполнять вход с помощью функции Войти с аккаунтом Google
<https://accounts.google.com/AccountChooser?Email=globusmira70@gmail.com&continue=https://support.google.com/accounts/answer/112802?rfn%3D1646530984773%26anexp%3Dnret-fa>
или использовать более защищенные технологии, например OAuth 2.0. Подробнее…
<https://accounts.google.com/AccountChooser?Email=globusmira70@gmail.com&continue=https://support.google.com/accounts/answer/6010255?rfn%3D1646530984773%26anexp%3Dnret-fa>
------------------------------
*Что нужно сделать?*

Доступ к почте Gmail через *почтовый клиент, например Outlook 2016 и более
ранних версий*, недостаточно безопасен. Мы рекомендуем использовать Office
365, Outlook 2019 (и более поздней версии) или другой почтовый клиент,
поддерживающий функцию *Войти с аккаунтом Google*.
Подробнее…
<https://accounts.google.com/AccountChooser?Email=globusmira70@gmail.com&continue=https://support.google.com/accounts/answer/6010255?rfn%3D1646530984773%26anexp%3Dnret-fa>
Это сообщение о важных изменениях в вашем аккаунте и сервисах Google.
© 2022 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA

CentOS

The Community ENTerprise Operating System

fetchmail socket errors, need clarification

fetchmail socket errors, need clarification

Post by Dogbyte » 2013/09/05 19:00:48

ive hit a snag. not sure how to go about fixing this Socket error, ive seen many posts on how to fix it, and it seems there are right ways and wrong ways. Different ways, being called wrong by different people, so im not sure what to think. Ive gone [url=http://www.centos.org/docs/5/html/5.2/Deployment_Guide/s3-email-security-servers.html]here[/url] and tried following the directions on making a self signed cert, but i dont get the prompts to any questions like the instructions claim. So ive stopped there, and want more opinions.

Fetchmail is failing because its unable to get local issuer cert. But im not even positive it means the box im running fetchmail on, but rather the cert from the exchange server, since it says its an unknown org, and server common name. ive edited some stuff out because im not sure whats safe and whats not, dont post this sort of stuff online much.

]$ fetchmail -d0 -vk
fetchmail: 6.3.17 querying exchange.server.org (protocol POP3) at Thu 05 Sep 2013 01:31:48 PM CDT: poll started
Trying to connect to 192.xx.xx.xx/995. connected.
fetchmail: Server certificate:
fetchmail: Unknown Organization
fetchmail: Issuer CommonName: FORESTCA
fetchmail: Unknown Server CommonName
fetchmail: exchange.server.org key fingerprint: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
fetchmail: exchange.server.org fingerprints match.
fetchmail: Server certificate verification error: unable to get local issuer certificate
fetchmail: This means that the root signing certificate (issued for ) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of —sslcertpath and —sslcertfile in the manual page.
139886606989128:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:s3_clnt.c:1068:
fetchmail: SSL connection failed.
fetchmail: socket error while fetching from dropbox@exchange.server.org
fetchmail: 6.3.17 querying exchange.server.org (protocol POP3) at Thu 05 Sep 2013 01:31:53 PM CDT: poll completed
fetchmail: Query status=2 (SOCKET)
fetchmail: normal termination, status 2
[dropbox@WEBHOST

]# rpm -V ca-certificates
[root@WEBHOST

# set username
set postmaster «dropbox»
# set polling time (5 minutes)
set daemon 600

poll exchange.server.org with proto POP3
user ‘dropbox’ there with password ‘mypassword’ is ‘dropbox’ here options ssl
sslproto tls1
sslcertpath /usr/share/ssl/certs
sslfingerprint ‘xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx’
sslcertck

[root@WEBHOST dropbox]# ls /usr/share/ssl/certs -al
total 16
drwxr-xr-x 2 root root 4096 Aug 29 16:36 .
drwxr-xr-x 3 root root 4096 Aug 29 16:21 ..
-rwxr-xr-x 1 root root 3958 Aug 29 16:36 c_rehash
lrwxrwxrwx 1 root root 36 Aug 29 16:36 eea339da.0 -> exchange.server.org.pem
-rw-r—r— 1 root root 2049 Aug 29 16:24 exchange.server.org.pem
-rw-r—r— 1 root root 0 Aug 29 16:22 thawte.pem
[root@WEBHOST dropbox]#

Re: fetchmail socket errors, need clarification

Post by Dogbyte » 2013/09/06 16:37:42

well, i checked the version of fetchmail i had installed, and it looks like the version it pulls from Centos repos is an older version, not that old though. 6.3.17

So now im trying to install the latest fetchmail version 6.3.26 from the source files, the few times ive done this, ive never had a problem, but it seems the package is not installing. as i ./configure, i notice its checking for OpenSSL, which is installed, but it warns that SSL support is dropped because it doesnt see that openssl is installed.

What am i doing wrong? i followed the directions, and did the ./configure —with-ssl command. Then after the make, and make install commands, also with a rpm -qi fetchmail command, the output is this:

[root@WEBHOST fetchmail-6.3.26]# make install
make install-recursive
make[1]: Entering directory `/root/Downloads/fetchmail-6.3.26′
Making install in .
make[2]: Entering directory `/root/Downloads/fetchmail-6.3.26′
make[3]: Entering directory `/root/Downloads/fetchmail-6.3.26′
test -z «/usr/local/bin» || /bin/mkdir -p «/usr/local/bin»
/usr/bin/install -c fetchmail ‘/usr/local/bin’
test -z «/usr/local/bin» || /bin/mkdir -p «/usr/local/bin»
/usr/bin/install -c fetchmailconf ‘/usr/local/bin’
test -z «/usr/local/share/man/man1» || /bin/mkdir -p «/usr/local/share/man/man1»
/usr/bin/install -c -m 644 ‘fetchmail.man’ ‘/usr/local/share/man/man1/fetchmail.1’
/usr/bin/install -c -m 644 ‘fetchmailconf.man’ ‘/usr/local/share/man/man1/fetchmailconf.1’
test -z «/usr/local/lib/python2.6/site-packages» || /bin/mkdir -p «/usr/local/lib/python2.6/site-packages»
/usr/bin/install -c -m 644 fetchmailconf.py ‘/usr/local/lib/python2.6/site-packages’
Byte-compiling python modules.
fetchmailconf.py
Byte-compiling python modules (optimized versions) .
fetchmailconf.py
make[3]: Leaving directory `/root/Downloads/fetchmail-6.3.26′
make[2]: Leaving directory `/root/Downloads/fetchmail-6.3.26′
Making install in po
make[2]: Entering directory `/root/Downloads/fetchmail-6.3.26/po’
/bin/mkdir -p /usr/local/share
installing ca.gmo as /usr/local/share/locale/ca/LC_MESSAGES/fetchmail.mo
installing cs.gmo as /usr/local/share/locale/cs/LC_MESSAGES/fetchmail.mo
installing da.gmo as /usr/local/share/locale/da/LC_MESSAGES/fetchmail.mo
installing de.gmo as /usr/local/share/locale/de/LC_MESSAGES/fetchmail.mo
installing el.gmo as /usr/local/share/locale/el/LC_MESSAGES/fetchmail.mo
installing en_GB.gmo as /usr/local/share/locale/en_GB/LC_MESSAGES/fetchmail.mo
installing eo.gmo as /usr/local/share/locale/eo/LC_MESSAGES/fetchmail.mo
installing es.gmo as /usr/local/share/locale/es/LC_MESSAGES/fetchmail.mo
installing fi.gmo as /usr/local/share/locale/fi/LC_MESSAGES/fetchmail.mo
installing fr.gmo as /usr/local/share/locale/fr/LC_MESSAGES/fetchmail.mo
installing gl.gmo as /usr/local/share/locale/gl/LC_MESSAGES/fetchmail.mo
installing id.gmo as /usr/local/share/locale/id/LC_MESSAGES/fetchmail.mo
installing it.gmo as /usr/local/share/locale/it/LC_MESSAGES/fetchmail.mo
installing ja.gmo as /usr/local/share/locale/ja/LC_MESSAGES/fetchmail.mo
installing nl.gmo as /usr/local/share/locale/nl/LC_MESSAGES/fetchmail.mo
installing pl.gmo as /usr/local/share/locale/pl/LC_MESSAGES/fetchmail.mo
installing pt_BR.gmo as /usr/local/share/locale/pt_BR/LC_MESSAGES/fetchmail.mo
installing ru.gmo as /usr/local/share/locale/ru/LC_MESSAGES/fetchmail.mo
installing sk.gmo as /usr/local/share/locale/sk/LC_MESSAGES/fetchmail.mo
installing sq.gmo as /usr/local/share/locale/sq/LC_MESSAGES/fetchmail.mo
installing sv.gmo as /usr/local/share/locale/sv/LC_MESSAGES/fetchmail.mo
installing tr.gmo as /usr/local/share/locale/tr/LC_MESSAGES/fetchmail.mo
installing vi.gmo as /usr/local/share/locale/vi/LC_MESSAGES/fetchmail.mo
installing zh_CN.gmo as /usr/local/share/locale/zh_CN/LC_MESSAGES/fetchmail.mo
if test «fetchmail» = «gettext-tools»; then
/bin/mkdir -p /usr/local/share/gettext/po;
for file in Makefile.in.in remove-potcdate.sin quot.sed boldquot.sed en@quot.header en@boldquot.header insert-header.sin Rules-quot Makevars.template; do
/usr/bin/install -c -m 644 ./$file
/usr/local/share/gettext/po/$file;
done;
for file in Makevars; do
rm -f /usr/local/share/gettext/po/$file;
done;
else
: ;
fi
make[2]: Leaving directory `/root/Downloads/fetchmail-6.3.26/po’
make[1]: Leaving directory `/root/Downloads/fetchmail-6.3.26′
[root@WEBHOST fetchmail-6.3.26]# rpm -qi fetchmail
package fetchmail is not installed

Re: fetchmail socket errors, need clarification

Post by Dogbyte » 2013/09/06 17:03:04

i see that OPENSUSE has an updated rpm for fetchmail, but i doubt yum will get through it since its not built for Centos. Is there a safe way to get yum to install rpm’s made for other builds, where the dependencies will resolve?

I just want to make sure im using the latest version of fetchmail, especially since it may be socket related as to why fetchmail doesnt see that Openssl is installed during the make install.

Re: fetchmail socket errors, need clarification

Post by TrevorH » 2013/09/06 18:37:19

Whatever your problem is, it’s very unlikely that you will fix it by using a source install. We even have a Wiki page warning of why they are not a good idea — http://wiki.centos.org/PackageManagement/SourceInstalls

Looking at what you have, your exchange.server.org.pem is most likely a self-signed one and you will need a copy of the CA cert that created it and you’ll need to run c_rehash against it.

Re: fetchmail socket errors, need clarification

Post by Dogbyte » 2013/09/06 19:19:18

fetchmail socket errors, need clarification

Post by gerald_clark » 2013/09/06 19:34:50

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

error using fetchmail: Query status=2 (SOCKET)

error using fetchmail: Query status=2 (SOCKET)

Post by Riko » Mon Mar 25, 2013 4:01 pm

I recentely switch to LMDE (from Nadia from Maya from Ubuntu). I use fetchmail in a cronjob to extract certain emails automatically from our corporate mail server using imap with ssl on a regular basis. This setup is working flawlessly since years, however not anymore since I installed LMDE. This is the essential output of fetchmail:

As I said, this was working fine before, is still working fine on a parallel install of Bodhi Linux but not on LMDE. I assume, it has something to do with the system wide ssl or fetchmal config, but so far haven’t found any hint yet what it might be.

Thanks and cheers,
Riko

Re: error using fetchmail: Query status=2 (SOCKET)

Post by Riko » Thu Apr 11, 2013 8:50 am

just my own follow-up in case someone else encounters this problem. After installing different versions of fetchmail and/or openssl I still couldn’t get it to work. I don’t have time (probably nor the expertise) to solve it myself. But, a work around that did it for me is

1) do a local port forwarding via ssh using stunnel to the imap server
2) connect fetchmail to the local host without ssl

That works for me. Since thjis works while fetchmail/ssl doesn’t, I conclude that somehow the interplay of fetchmail and openssl under LMDE screws up the direct connection.

Источник

Fetchmail socket error while fetching from

FreeBSD, 7 пользователей, диалап. По характеру фирмы почты приходит довольно много. Оччень медленно забирается 1 письмо, даже маленькое. Несколько минут. Коннект 56k, на пользовательских машинах инет достаточно быстрый. Параллельно никаких закачек не идет. Что с этим делать?

Второй вопрос: что такое Query status=2?

fetchmail: socket error while fetching from 212.26.128.10
fetchmail: Query status=2 (SOCKET)
fetchmail: sleeping at Mon Aug 30 15:23:57 2004

Не достучалась до почтового сервера?

Рекомендовать в FAQ | Cообщить модератору | Наверх

Индекс форумов | Темы | Пред. тема | След. тема

>FreeBSD, 7 пользователей, диалап. По характеру фирмы почты приходит довольно много. Оччень
>медленно забирается 1 письмо, даже маленькое. Несколько минут. Коннект 56k, на
>пользовательских машинах инет достаточно быстрый. Параллельно никаких закачек не идет. Что
>с этим делать?
>
>Второй вопрос: что такое Query status=2?
>
>fetchmail: socket error while fetching from 212.26.128.10
>fetchmail: Query status=2 (SOCKET)
>fetchmail: sleeping at Mon Aug 30 15:23:57 2004
>
>Не достучалась до почтового сервера?

Да, не может соединиться с хостом 212.26.128.10.
Возможно это проблема с почтовым сервером. Может он сильно занят и поэтому не принимает соединения?

esr/fetchmail/fetchmail-man.html#30
Вот что там сказано про код возврата 2:
An error was encountered when attempting to open a socket to retrieve mail. If you don’t know what a socket is, don’t worry about it — just treat this as an ’unrecoverable error’. This error can also be because a protocol fetchmail wants to use is not listed in /etc/services.

Т.е. предлагается либо забить на эту ошибку, либо проверить описан ли протокол который ты используешь (POP3, IMAP) в файле /etc/services.

Попробуй забрать почту другим почтовым клиентом и посмотри, повторится ли ситуация. Проверь ещё раз конфиг fetchmail.

2. «fetchmail: oчень медленно забирается почта.»

Сообщение от Michael_GMV (ok) on 05-Сен-04, 15:16 (MSK)

Когда не достукивается до сервера, то понятно. Но а когда приконнектился и забирает 30-50 писем в час? Это главная проблема. Просто по характеру фирмы вместе с рассылками писем набирается до 50 в час. Диалап по приказу шефа на ночь отключают и в результате за ночь наваливается до 400 писем, которые аккурат к обеду и вытягиваются. А если попросить провайдера фильтровать падающие в ящик письма на предмет спама, то они отфильтровывают и часть нужных писем. Да, и если бы протокол не был описан в /etc/services, то почта б вообще не забиралась. Так ведь? Источник Adblock detector

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх