On Mon, 2014-09-01 at 07:59 -0700, Jonathan Ryshpan wrote:
> On Mon, 2014-09-01 at 10:25 -0400, Marc Hurst wrote:
> > On 09/01/2014 04:41 AM, Pete Biggs wrote:
> > > ...
> > > Evolution is reporting an error because the Yahoo servers are giving an
> > > error. This isn't an Evolution problem as such - except in that when an
> > > error occurs, Evolution assumes it's an authentication problem and
> > > immediately prompts for a password. (The difference with something like
> > > Thunderbird is that it retries with the same password and it usually
> > > works the second time - hence it looks like everything is OK with
> > > another MUI.)
>
> > Would it be difficult to change Evo to "retry with the same password,"
> > like Thunderbird?
> >
> > It seems like a very useful strategy.
>
> I suspect that this is exactly what fetchmail is doing, and this is why
> fetchmail appears to be working OK. I can change the verbosity level in
> fetchmail's log and look it over.
Yup. Fetchmail just sleeps however long the ...rc file requires and
tries again. There appears to be a limit to how long fetchmail will
wait for an appropriate reply from a server. From the man page:
The timeout option allows you to set a server-nonresponse
timeout in seconds. If a mailserver does not send a greeting
message or respond to commands for the given number of seconds,
fetchmail will drop the connection to it. ... If a given
connection receives too many timeouts in succession,
fetchmail will consider it wedged and stop retrying. The
calling user will be notified by email if this happens.
This might be a good way for evolution to handle the problem.
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
