From: Ed W. <ew...@ew...> - 2006-03-02 03:41:20
|
On Wed, Mar 01, 2006 at 08:58:52PM -0500, Peter N. Spotts wrote: > After reading the FAQ, I'm hip to fetchmail's "neutrality" on whether an > incoming email has an attachment or not. So I'm hoping for some guidance > on where to look for the source of a recurring problem of randomly lost > or "damaged" pdf attachments. Typically (though not always), the pdfs > that come through unscathed are one-page, sent one per email. The lost > or damaged attachments tend to be larger pdf files and emails with > multiple attachments. > > When I noticed the damaged attachments, I set up my clients for POP3 to > pull the mail directly from the ISP. Then I had the senders resend the > email. All the attachments arrived cleanly from ISP straight into email > client. So although my ISP is Comcast (I noted the Comcast caveats on > the FAQ page), Comcast does not seem to be the problem either. And I've > deactivated clamav, thinking it might not like the attachments for some > reason. But the attachments still come in damaged via the fetchmail et > al route. > > So, if Comcast isn't the problem and fetchmail doesn't give a hoot if an > email bears an attachment or not, where else should I look? But Comcast *is* the problem. I have this in my .fetchmailrc and it works fine, with attachments. poll mail.comcast.net proto POP3 user 'ewilts' password 'noneofyourbusiness!' fetchall Without the "fetchall", any attachments over 70k were mangled. -- Ed Wilts, Mounds View, MN, USA mailto:ew...@ew... |