The buffer used by stuff_warning() is too small to handle messages like
the following:
The attempt to get authorization failed. Since we have already
succeeded in getting authorization for this connection, this is
probably another failure mode (such as busy server) that fetchmail
cannot distinguish because the server didn't send a useful error
message.
However, if you HAVE changed your account details since starting the
fetchmail daemon, you need to stop the daemon, change your
configuration of fetchmail, and then restart the daemon.
The fetchmail daemon will continue running and attempt to connect at
each cycle. No future notifications will be sent until service is
restored.
So, I get emails like the first attachment when the failure mode
corresponding to the above occurs.
The second attachment is one way to fix this problem.
Thanks,
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
--- Begin Message ---
Fetchmail could not get mail from user(_at_)mailserver(_dot_)
The attempt to get authorization failed.
Since we have already succeeded in getting authorization for this
connection, this is probably another failure mode (such as busy server)
that fetchmail cannot distinguish because the server didn't send a useful
error message.
However, if you HAVE changed your account details since starting the
fetchmail daemon, you need to stop the daemon, change your configuration
of fetchmail, and then restart the daemon.
The fetchmail daemon will continue running and attempt t àý"