From: Jason T. <ja...@ti...> - 2007-05-14 02:42:17
|
Kyle, On Sat, May 12, 2007 at 11:03:18PM +0100, Rob MacGregor wrote: > On 5/12/07, Kyle Contreras-Barbour <kyl...@gm...> wrote: > > 6.3.8 and 3.22, respectively, according to setup.exe). > > > > I did indeed need to get exim running, it seems (thanks!) - I ran > > exim-config to get the daemon going and when I ran fetchmail, > > instead of giving "connection to localhost failed" it happily > > connected. However, it's still having certificate verification > > errors (I don't know if that's a big issue or not) and terminating > > with a socket error. This is what it's showing at the end: > > Not a big deal. Agreed, I get the same error messages when I fetch from gmail too. > > It's been getting stuck at the same message, which appears to be > > fairly large (14003782 octets), so I'm starting to wonder if there > > isn't some issue there. Before it hits that message, it's giving > > this: > > > > [snip] > > It could be a problem related to your exim config (14 MB is pretty > large for an email). The contents of the exim log would be useful to > further diagnose, though from the snippet above it doesn't appear to > be a fetchmail problem. You don't need to use exim or another MTA, if you are only interested in local mail delivery. If so, then you may want to model your fetchmail configuration after mine which delivers via procmail: poll "pop.gmail.com" protocol pop3 username "${USER}@gmail.com" password "${PASSWORD}" fetchall ssl nokeep mda "/usr/bin/procmail -d %T" where ${USER} and ${PASSWORD} are as appropriate. 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 |