Re: [fetchmail-users] SMTP connect error with fetchmail under Cygwin

[Kyle Contreras-B. <kyl...@gm...>]

On 5/13/07, Jason Tishler <ja...@ti...> wrote:
>
> 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:
>
> <snip>
>

I've put that into my rc file now, but I'm still getting socket errors at
the same point, at the 14MB e-mail.

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.
>

I'm happy to post it - it's rather large, so here's a snippet. Let me know
if more (or a specific segment) would be helpful.

2007-05-13 20:59:25 Start queue run: pid=1596
2007-05-13 20:59:25 End queue run: pid=1596
2007-05-13 21:14:26 Start queue run: pid=1640
2007-05-13 21:14:26 End queue run: pid=1640
2007-05-13 21:29:26 Start queue run: pid=1660
2007-05-13 21:29:26 End queue run: pid=1660
2007-05-13 21:44:27 Start queue run: pid=1720
2007-05-13 21:44:27 End queue run: pid=1720
2007-05-13 21:59:28 Start queue run: pid=1064
2007-05-13 21:59:28 End queue run: pid=1064
2007-05-13 22:14:47 Start queue run: pid=1208
2007-05-13 22:14:48 End queue run: pid=1208
2007-05-13 22:30:06 Start queue run: pid=1660
2007-05-13 22:30:06 End queue run: pid=1660
2007-05-13 22:45:06 Start queue run: pid=1460
2007-05-13 22:45:06 End queue run: pid=1460
2007-05-13 23:00:06 Start queue run: pid=1208
2007-05-13 23:00:06 End queue run: pid=1208
2007-05-13 23:15:07 Start queue run: pid=1208
2007-05-13 23:15:07 End queue run: pid=1208
2007-05-13 23:30:07 Start queue run: pid=1440
2007-05-13 23:30:07 End queue run: pid=1440
2007-05-13 23:45:07 Start queue run: pid=868
2007-05-13 23:45:07 End queue run: pid=868

Farther back than this, there's some entries such as this one:

2007-05-12 14:35:22 SMTP connection from localhost (<hostname>) [127.0.0.1]
lost while reading message data

Again, thanks for all the help in figuring this out.
Kyle