Re: [Fetchmail-users] fetchmail -ERR message 1 not found

[Matthias A. <mat...@gm...>]

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