On 2014-10-16 Ángel González <angel@...54...> wrote: > fr33domlover wrote: > > I'm simply running mpop from a cron job with a regular config file, > > actually. But clearly it stops due to timeout (or I stop it manually), and > > next time the "downloading message X or Y" starts where it stopped last > > time, not with 1 - maybe the previously downloaded ones are found and used? > > *That* makes sense. mpop tries hard not to duplicate messages. That it > continues where it left is fine. > The odd thing was that from your old email, it seemed like delivery of > the first messages didn't happen until after the second fetch. > > > (There's still the issue of timeouts that shouldn't be happening, > though) Yeah, I'm getting TLS timeout for my main POP account, which uses many mailing lists and therefore gets a lot of mail (I check once in 30 minutes). But nothing unusual - 80 new messages shouldn't be critically big, I hope. I'm getting this in stderr: mpop: cannot read from TLS connection: the operation timed out mpop: error during mail retrieval When it starts, it just keeps repeating it on every run, so unless I intervene manually, it will never fetch the messages. For now I'm switching to a client-side solution (with a 24/7 running IMAP client), but I'll try soon to debug it with gdb and/or look at more detailed logs. Is debian's mpop 1.0.27 stable? Maybe I should try a more recent version? -- fr33
Attachment:
signature.asc
Description: PGP signature