Menu
▾
▴
fetchmail-users
|
From: Claudio M. <va...@ho...> - 2015-02-10 14:00:59
|
hi, somehow can't get fetchmail to work properly # Configuration created Tue Feb 10 10:18:32 2015 by fetchmailconf 1.52 $Revision: 4636 $set postmaster "ad...@do..."#set nobouncemail#set no spambounce#set properties ""#set daemon 900poll mail.domain.com with proto POP3 localdomains domain.com envelope X-Originally-To user 'user' with password 'pass' to * here options smtphost 192.168.15.150 fetchmail: WARNING: Running as root is discouraged.fetchmail: 6.3.2 querying mail.domain.com (protocol POP3) at Tue Feb 10 10:38:09 2015: poll startedfetchmail: POP3< +OK POP3 server ready <848...@ma...>fetchmail: POP3> CAPAfetchmail: POP3< -ERR bad commandfetchmail: bad commandfetchmail: Repoll immediately on us...@ma...fetchmail: POP3< +OK POP3 server ready <210...@ma...>fetchmail: POP3> USER userfetchmail: POP3< +OKfetchmail: POP3> PASS *fetchmail: POP3< +OK connectedfetchmail: POP3> STATfetchmail: POP3< +OK 1 3255fetchmail: POP3> LASTfetchmail: POP3< -ERR bad commandfetchmail: bad commandfetchmail: POP3> UIDLfetchmail: POP3< +OK listing followsfetchmail: POP3< 1 15021010380695fetchmail: POP3< .1 message for user at mail.domain.com (3255 octets).fetchmail: POP3> LIST 1fetchmail: POP3< -ERR message 1 not foundfetchmail: message 1 not foundfetchmail: POP3> QUITfetchmail: POP3< +OKfetchmail: client/server protocol error while fetching from us...@ma...fetchmail: 6.3.2 querying mail.domain.com (protocol POP3) at Tue Feb 10 10:38:09 2015: poll completedfetchmail: Query status=4 (PROTOCOL)fetchmail: normal termination, status 4Done. |
|
From: Rob M. <rob...@gm...> - 2015-02-10 17:46:32
|
On Tue Feb 10 2015 at 14:02:15 Claudio Mendes <va...@ho...> wrote: > hi, > somehow can't get fetchmail to work properly > # Configuration created Tue Feb 10 10:18:32 2015 by fetchmailconf 1.52 > $Revision: 4636 $set postmaster "ad...@do..."#set nobouncemail#set no > spambounce#set properties ""#set daemon 900poll mail.domain.com with > proto POP3 localdomains domain.com envelope X-Originally-To user > 'user' with password 'pass' to * here options smtphost 192.168.15.150 > > fetchmail: WARNING: Running as root is discouraged.fetchmail: 6.3.2 > querying mail.domain.com (protocol POP3) at Tue Feb 10 10:38:09 2015: > poll startedfetchmail: POP3< +OK POP3 server ready < > 848...@ma...>fetchmail: POP3> CAPAfetchmail: POP3< > -ERR bad commandfetchmail: bad commandfetchmail: Repoll immediately on > us...@ma...fetchmail: POP3< +OK POP3 server ready < > 210...@ma...>fetchmail: POP3> USER > userfetchmail: POP3< +OKfetchmail: POP3> PASS *fetchmail: POP3< +OK > connectedfetchmail: POP3> STATfetchmail: POP3< +OK 1 3255fetchmail: POP3> > LASTfetchmail: POP3< -ERR bad commandfetchmail: bad commandfetchmail: POP3> > UIDLfetchmail: POP3< +OK listing followsfetchmail: POP3< 1 > 15021010380695fetchmail: POP3< .1 message for user at mail.domain.com > (3255 octets).fetchmail: POP3> LIST 1fetchmail: POP3< -ERR message 1 not > foundfetchmail: message 1 not foundfetchmail: POP3> QUITfetchmail: POP3< > +OKfetchmail: client/server protocol error while fetching from > us...@ma...fetchmail: 6.3.2 querying mail.domain.com (protocol > POP3) at Tue Feb 10 10:38:09 2015: poll completedfetchmail: Query status=4 > (PROTOCOL)fetchmail: normal termination, status 4Done. > A few things: 1) Your version of Fetchmail is terribly out of date - please update to the current version (6.3.26 ISTR) 2) The formatting of your email makes it impractical to parse the messages. If you can't correct the formatting in your mail client please use the likes of pastebin. 3) It looks, from what I can parse, that the POP server is not well behaved - it would be good to know technical details about that server to enable folks to work out whether it really is the problem. -- Rob MacGregor |
|
From: Jerry <je...@se...> - 2015-02-10 20:11:35
|
On Tue, 10 Feb 2015 15:00:51 +0100, Claudio Mendes stated: > hi, > somehow can't get fetchmail to work properly > # Configuration created Tue Feb 10 10:18:32 2015 by fetchmailconf 1.52 > $Revision: 4636 $set postmaster "ad...@do..."#set nobouncemail#set no > spambounce#set properties ""#set daemon 900poll mail.domain.com with proto > POP3 localdomains domain.com envelope X-Originally-To user 'user' > with password 'pass' to * here options smtphost 192.168.15.150 > > fetchmail: WARNING: Running as root is discouraged.fetchmail: 6.3.2 > querying mail.domain.com (protocol POP3) at Tue Feb 10 10:38:09 2015: poll > startedfetchmail: POP3< +OK POP3 server ready > <848...@ma...>fetchmail: POP3> CAPAfetchmail: POP3< > -ERR bad commandfetchmail: bad commandfetchmail: Repoll immediately on > us...@ma...fetchmail: POP3< +OK POP3 server ready > <210...@ma...>fetchmail: POP3> USER userfetchmail: > POP3< +OKfetchmail: POP3> PASS *fetchmail: POP3< +OK connectedfetchmail: > POP3> STATfetchmail: POP3< +OK 1 3255fetchmail: POP3> LASTfetchmail: POP3< > POP3> -ERR bad commandfetchmail: bad commandfetchmail: POP3> UIDLfetchmail: > POP3> POP3< +OK listing followsfetchmail: POP3< 1 15021010380695fetchmail: > POP3> POP3< .1 message for user at mail.domain.com (3255 octets).fetchmail: > POP3> POP3> LIST 1fetchmail: POP3< -ERR message 1 not foundfetchmail: > POP3> POP3> message 1 not foundfetchmail: POP3> QUITfetchmail: POP3< > POP3> POP3> +OKfetchmail: client/server protocol error while fetching from > POP3> POP3> us...@ma...fetchmail: 6.3.2 querying mail.domain.com > POP3> POP3> (protocol POP3) at Tue Feb 10 10:38:09 2015: poll > POP3> POP3> completedfetchmail: Query status=4 (PROTOCOL)fetchmail: normal > POP3> POP3> termination, status 4Done. > POP3> POP3> ------------------------------------------------------------------------------ > POP3> POP3> Dive into the World of Parallel Programming. The Go Parallel > POP3> POP3> Website, sponsored by Intel and developed in partnership with > POP3> POP3> Slashdot Media, is your hub for all things parallel software > POP3> POP3> development, from weekly thought leadership blogs to news, > POP3> POP3> videos, case studies, tutorials and more. Take a look and join > POP3> POP3> the conversation now. http://goparallel.sourceforge.net/ > POP3> POP3> _______________________________________________ Fetchmail-users > POP3> POP3> mailing list You are going to have to supply your configuration file if you want anyone to debug this for you. I think that is what you have at the top of this post, but it is so mangled on my screen that I am not even going to begin to spend the time to figure it out. Mungle the "PASSWORDS" but leave the rest intact. Also, DO NOT use HTML. Send it as plain ASCII text. Hotmail has a setting for that if you are using their web interface. Otherwise, set your MUA to use plain text. -- Jerry |
|
From: Matthias A. <mat...@gm...> - 2015-02-10 21:07:07
|
Am 10.02.2015 um 15:00 schrieb Claudio Mendes: > hi, > somehow can't get fetchmail to work properly > # Configuration created Tue Feb 10 10:18:32 2015 by fetchmailconf 1.52 $Revision: 4636 $set postmaster "ad...@do..."#set nobouncemail#set no spambounce#set properties ""#set daemon 900poll mail.domain.com with proto POP3 localdomains domain.com envelope X-Originally-To user 'user' with password 'pass' to * here options smtphost 192.168.15.150 > > fetchmail: WARNING: Running as root is discouraged.fetchmail: 6.3.2 querying mail.domain.com (protocol POP3) at Tue Feb 10 10:38:09 2015: poll startedfetchmail: POP3< +OK POP3 server ready <848...@ma...>fetchmail: POP3> CAPAfetchmail: POP3< -ERR bad commandfetchmail: bad commandfetchmail: Repoll immediately on us...@ma...fetchmail: POP3< +OK POP3 server ready <210...@ma...>fetchmail: POP3> USER userfetchmail: POP3< +OKfetchmail: POP3> PASS *fetchmail: POP3< +OK connectedfetchmail: POP3> STATfetchmail: POP3< +OK 1 3255fetchmail: POP3> LASTfetchmail: POP3< -ERR bad commandfetchmail: bad commandfetchmail: POP3> UIDLfetchmail: POP3< +OK listing followsfetchmail: POP3< 1 15021010380695fetchmail: POP3< .1 message for user at mail.domain.com (3255 octets).fetchmail: POP3> LIST 1fetchmail: POP3< -ERR message 1 not foundfetchmail: message 1 not foundfetchmail: POP3> QUITfetchmail: POP3< +OKfetchmail: client/server protocol error whil e fetching from us...@ma...fetchmail: 6.3.2 querying mail.domain.com (protocol POP3) at Tue Feb 10 10:38:09 2015: poll completedfetchmail: Query status=4 (PROTOCOL)fetchmail: normal termination, status 4Done. Claudio, the server offers a message with number 1 in the UIDL reply, but refuses to list its size when fetchmail asks for it (although it seems to know the mailbox size). While I concur with Jerry's and Rob's assessments, a fetchmail update - while still advised - isn't going to help here because the trouble is on the server's end. Nothing can cope with a server that promises a message and then fails to deliver it. Please reproduce the log with line breaks intact and without reformatting, and forward it to the POP3 server's administrator with a polite request to check into and resolve the issue. The technical reference for how the server should behave is RFC 1939, found for example here: <http://tools.ietf.org/html/rfc1939> Hope that helps. Best, Matthias |
|
From: Claudio M. <va...@ho...> - 2015-02-11 10:43:32
|
if i use EFS instead of fetchmail it works Received: from SRV-EX01.domain.local (192.168.15.150) by SRV-EX01.domain.local (192.168.15.150) with Microsoft SMTP Server (TLS) id 15.0.1044.25 via Mailbox Transport; Mon, 9 Feb 2015 11:59:10 +0100 Received: fromSRV-EX01.domain.local (192.168.15.150) by SRV-EX01.domain.local (192.168.15.150) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Mon, 9 Feb 2015 11:59:10 +0100 Received: from vmsrv (192.168.15.180) by SRV-EX01.domain.local (192.168.15.150) with Microsoft SMTP Server id 15.0.1044.25 via Frontend Transport; Mon, 9 Feb 2015 11:59:10 +0100 Received: from 195.218.8.138 by 195.218.28.28 INC_SMTP_SERVER 2.58; Mon, 09 Feb 2015 11:58:50 +0100 Received: from domain.com (shopping.domain.com [195.218.85.8]) by mailgate.domain.com (Postfix) with SMTP id 7627F9C0055; Mon, 9 Feb 2015 11:58:50 +0100 (CET) Date: Mon, 9 Feb 2015 11:58:50 +0100 Subject: System Notification Message-ID: <20150209115850.0334@hel...@do...> X-Mailer: incsmtp version 2.12 X-Originally-From: <hel...@do...> X-Originally-To: <jhi...@do...> X-Forwarder: Redirected by EFS, http://www.chimeracomputing.com/ To: <tt...@do...> From: <hel...@do...> Return-Path: hel...@do... MIME-Version: 1.0 Content-Type: text/plain X-MS-Exchange-Organization-Network-Message-Id: ad317a54-bc90-461c-82de-08d2126e914d X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0 X-MS-Exchange-Organization-AuthSource: SRV-EX01.domain.local X-MS-Exchange-Organization-AuthAs: Anonymous # Configuration created Fri Jan 9 17:33:10 2015 by fetchmailconf 1.52 $Revision: 4636 $ set postmaster "ad...@do..." #set bouncemail #set no spambounce #set properties "" #set daemon 900 poll mail.domain.com with proto POP3 localdomains domain.com #001 poll 195.219.0.173 with proto POP3 localdomains domain.com #002 poll 195.219.0.195 with proto POP3 localdomains domain.com #003 poll 195.218.28.28 with proto POP3 localdomains domain.com envelope X-Originally-To # user 'domainemail' with password 'pass1234' to * here options smtphost 192.168.16.160 user 'domainemail' with password 'pass1234' to * here options smtphost 192.168.15.150 proxy-srv:~ # fetchmail -v -v fetchmail: WARNING: Running as root is discouraged. fetchmail: 6.3.2 querying mail.domain.com (protocol POP3) at Tue Feb 10 15:17:41 2015: poll started fetchmail: POP3< +OK POP3 server ready <134...@ma...> fetchmail: POP3> CAPA fetchmail: POP3< -ERR bad command fetchmail: bad command fetchmail: Repoll immediately on dom...@ma... fetchmail: POP3< +OK POP3 server ready <589...@ma...> fetchmail: POP3> USER domainemail fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< +OK connected fetchmail: selecting or re-polling default folder fetchmail: POP3> STAT fetchmail: POP3< +OK 4 117964 fetchmail: POP3> LAST fetchmail: POP3< -ERR bad command fetchmail: bad command fetchmail: POP3> UIDL fetchmail: POP3< +OK listing follows fetchmail: POP3< 1 15021015161094 fetchmail: 1 is unseen fetchmail: POP3< 2 15021015171770 fetchmail: 2 is unseen fetchmail: POP3< 3 15021015154640 fetchmail: 3 is unseen fetchmail: POP3< 4 15021015155722 fetchmail: 4 is unseen fetchmail: POP3< . 4 messages for domainemail at mail.domain.com (117964 octets). fetchmail: POP3> LIST 1 fetchmail: POP3< -ERR message 1 not found fetchmail: message 1 not found fetchmail: POP3> QUIT fetchmail: POP3< +OK fetchmail: client/server protocol error while fetching from dom...@ma... fetchmail: 6.3.2 querying mail.domain.com (protocol POP3) at Tue Feb 10 15:17:41 2015: poll completed fetchmail: discarding new UID list fetchmail: Query status=4 (PROTOCOL) fetchmail: Deleting fetchids file. fetchmail: normal termination, status 4 fetchmail: Deleting fetchids file. |
|
From: Martin K. <mk...@gm...> - 2015-02-11 19:03:43
|
Hi Claudio, On Wed, 11 Feb 2015, Claudio Mendes wrote: > if i use EFS instead of fetchmail it works > > # Configuration created Fri Jan 9 17:33:10 2015 by fetchmailconf 1.52 $Revision: 4636 $ > set postmaster "ad...@do..." > #set bouncemail > #set no spambounce > #set properties "" > #set daemon 900 > poll mail.domain.com with proto POP3 localdomains domain.com > #001 poll 195.219.0.173 with proto POP3 localdomains domain.com > #002 poll 195.219.0.195 with proto POP3 localdomains domain.com > #003 poll 195.218.28.28 with proto POP3 localdomains domain.com > envelope X-Originally-To > # user 'domainemail' with password 'pass1234' to * here options smtphost 192.168.16.160 > user 'domainemail' with password 'pass1234' to * here options smtphost 192.168.15.150 > > > > proxy-srv:~ # fetchmail -v -v > fetchmail: WARNING: Running as root is discouraged. > fetchmail: 6.3.2 querying mail.domain.com (protocol POP3) at Tue Feb 10 15:17:41 2015: poll started > fetchmail: POP3< +OK POP3 server ready <134...@ma...> > fetchmail: POP3> CAPA > fetchmail: POP3< -ERR bad command > fetchmail: bad command > fetchmail: Repoll immediately on dom...@ma... > fetchmail: POP3< +OK POP3 server ready <589...@ma...> > fetchmail: POP3> USER domainemail > fetchmail: POP3< +OK > fetchmail: POP3> PASS * > fetchmail: POP3< +OK connected > fetchmail: selecting or re-polling default folder > fetchmail: POP3> STAT > fetchmail: POP3< +OK 4 117964 > fetchmail: POP3> LAST > fetchmail: POP3< -ERR bad command > fetchmail: bad command > fetchmail: POP3> UIDL > fetchmail: POP3< +OK listing follows > fetchmail: POP3< 1 15021015161094 > fetchmail: 1 is unseen > fetchmail: POP3< 2 15021015171770 > fetchmail: 2 is unseen > fetchmail: POP3< 3 15021015154640 > fetchmail: 3 is unseen > fetchmail: POP3< 4 15021015155722 > fetchmail: 4 is unseen > fetchmail: POP3< . > 4 messages for domainemail at mail.domain.com (117964 octets). > fetchmail: POP3> LIST 1 > fetchmail: POP3< -ERR message 1 not found > fetchmail: message 1 not found > fetchmail: POP3> QUIT > fetchmail: POP3< +OK > fetchmail: client/server protocol error while fetching from dom...@ma... > fetchmail: 6.3.2 querying mail.domain.com (protocol POP3) at Tue Feb 10 15:17:41 2015: poll completed > fetchmail: discarding new UID list > fetchmail: Query status=4 (PROTOCOL) > fetchmail: Deleting fetchids file. > fetchmail: normal termination, status 4 > fetchmail: Deleting fetchids file. > you could give the option "fetchall" a try. (If it is OK for your use case.) For me it then worked when I had a pure RFC compliant server, with only the mandatory features available. fetchmail doesn't do unseen/seen processing in this case, but simply fetches everything. Martin |
|
From: Matthias A. <mat...@gm...> - 2015-02-11 21:14:19
|
Am 11.02.2015 um 11:43 schrieb Claudio Mendes: > if i use EFS instead of fetchmail it works Claudio, thank you for providing reformatted logs. My stance remains unchanged. The POP3 server you are fetching from is broken. It offers, through STAT and UIDL, message #1, but refuses to list its size. That is implausible. If the message #1 is deleted, the server is not permitted to list it through UIDL. Complain to the POP3 server's operator. Everybody, please use "example.com" for making up domains if you do not wish to expose the actual name to the public. It is reserved for documentation purposes and can safely be used. Random inventions of yours (such as domain.com) must not be used. It's too prone for abuse. > proxy-srv:~ # fetchmail -v -v > fetchmail: WARNING: Running as root is discouraged. > fetchmail: 6.3.2 querying mail.domain.com (protocol POP3) at Tue Feb 10 15:17:41 2015: poll started > fetchmail: POP3< +OK POP3 server ready <134...@ma...> > fetchmail: POP3> CAPA > fetchmail: POP3< -ERR bad command > fetchmail: bad command OK, fetchmail skips that. > fetchmail: Repoll immediately on dom...@ma... > fetchmail: POP3< +OK POP3 server ready <589...@ma...> > fetchmail: POP3> USER domainemail > fetchmail: POP3< +OK > fetchmail: POP3> PASS * > fetchmail: POP3< +OK connected > fetchmail: selecting or re-polling default folder > fetchmail: POP3> STAT > fetchmail: POP3< +OK 4 117964 > fetchmail: POP3> LAST > fetchmail: POP3< -ERR bad command OK, that is from an older POP3 revision (RFC 1725) and was removed. fetchmail proceeds to UIDL... > fetchmail: bad command > fetchmail: POP3> UIDL > fetchmail: POP3< +OK listing follows > fetchmail: POP3< 1 15021015161094 > fetchmail: 1 is unseen ...the server offers message #1. It is not permitted to list deleted messages (but we didn't delete it). [...] > 4 messages for domainemail at mail.domain.com (117964 octets). > fetchmail: POP3> LIST 1 > fetchmail: POP3< -ERR message 1 not found The server refuse to list the size of the message it offered previously. This doesn't make sense. If you want to experiment, download and build the newest fetchmail 6.x.y release and add --fetchsizelimit 0 to the command line. This causes fetchmail to request a LIST for all messages up front, instead of one by one, and then see what you get and perhaps show the traces. HTH. Best regards, Matthias |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X