Re: [fetchmail-users] message was not the expected length errors

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

Frederik <fr...@gm...> writes:

> fetchmail: SMTP< 354 Enter message, ending with "." on a line by itself
> #**********************************.****************fetchmail: message
> use...@po...:1 was not the expected length (4803 actual != 4693
> expected) fetchmail: SMTP>. (EOM)
> fetchmail: terminated with signal 2

These "not the expected length" messages are hints that the upstream
server is broken and is misreporting the actual message size.

Many POP3 server software packages are broken like this, for instance
some Exchange versions, qmail-pop3d and the one your server uses,
fetchmail just reports them and continues.  This "not the expected
length" message does not cause fetchmail to fail.

fetchmail aborts because someone or something is sending signal 2
(SIGINT, ^C), and it's not fetchmail, which has no code to raise
SIGINT.

Stop that something from sending fetchmail signals like SIGINT. Check
your scripts that run fetchmail, the shells that you run this script
from, and perhaps check if fetchmail is somehow part of a process group
with rampant programs. plugin, plugout are also possible candidates.

Details about your setup, such as fetchmail configuration and how you
start fetchmail, may help in tracking down the problem.

-- 
Matthias Andree