Article View: pl.comp.mail
Article #69368TBird i IMAP o2 - problem
From: pueblo
Date: Thu, 28 May 2020 11:57
Date: Thu, 28 May 2020 11:57
4 lines
1068 bytes
1068 bytes
Zna ktoś łatawe rozwiązenie ciągłego komunikatu: Serwer pocztowy konta @o2.pl odpowiedział fetch failed (marker:tutaj jakiś ciąg znaków) Można używać poczty, ale z problemami.
Technical Details
Message-ID:
<5ecfa724$0$518$65785112@news.neostrada.pl>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed.pionier.net.pl!news.samoylyk.net!aioe.org!peer02.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!newsfeed.neostrada.pl!unt-exc-01.news.neostrada.pl!unt-spo-a-01.news.neostrada.pl!news.neostrada.pl.POSTED!not-for-mailShow Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed.pionier.net.pl!news.samoylyk.net!aioe.org!peer02.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!newsfeed.neostrada.pl!unt-exc-01.news.neostrada.pl!unt-spo-a-01.news.neostrada.pl!news.neostrada.pl.POSTED!not-for-mail Newsgroups: pl.comp.mail Subject: TBird i IMAP o2 - problem From: pueblo <nomail@nomail.pl> User-Agent: Xnews/2009.05.01 Mime-proxy/2.3.c.1 (Win32) Mime-Version: 1.0 Date: 28 May 2020 11:57:24 GMT Lines: 4 Message-ID: <5ecfa724$0$518$65785112@news.neostrada.pl> Organization: Telekomunikacja Polska NNTP-Posting-Host: 88.156.133.83 X-Trace: 1590667044 unt-rea-b-01.news.neostrada.pl 518 88.156.133.83:59471 X-Complaints-To: abuse@news.neostrada.pl X-Received-Bytes: 852 X-Received-Body-CRC: 528808990 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit