-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rob,
Sorry about that! I'm running on Linux 2.4.19, modified debian.
I've since done some futzing around and I found out that the two
e-mails after the extremely large one had periods on a blank line. I
think that was causing the actual SIGPIPE..
Now, that big e-mail still remained after I deleted the munged
e-mails. Even while calling -l 0, I think that fetchmail was passing
an error 13 back (which in the documentation shows it as being an
over-limit attachment). Is there something in the code that makes it
so a single e-mail read cannot be bigger than X size, no matter what
the user puts in --limit?
Pete
<snip>
I've also noticed that the problem happens after the second e-mail
in the inbox is gotten. What makes this weird is that the first
e-mail is never received, which makes me think that this big e-mail
is the
culprit.
Ok, the logs say you're running 6.1.1, but on what OS?
I've certainly downloaded 20 MB+ emails using fetchmail so I'd be
surprised
if that's the problem. However anybody emailing stuff that large
should IMO
be using some other method of file transfer!
fetchmail: SIGPIPE thrown from an MDA or a stream socket error
Take a look at the log from your mail server, it looks like something
downstream (your mail server of the delivery agent) had problems.
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBPbl2BbzldGJZqFN6EQKhSgCg/gQpdNxVnpbBe1d+phWvksSqcVUAoKro
JojceKxC/bad0oUgqTCr4jyw
=qzgS
-----END PGP SIGNATURE-----