Date: Fri, 30 Jan 2004 16:21:25 -0500 From: Christopher Nehren <apeiron@comcast.net> To: FreeBSD Questions List <questions@freebsd.org> Subject: fetchmail chopping off messages > 77 kB Message-ID: <20040130212125.GA80095@prophecy.dyndns.org>
next in thread | raw e-mail | index | archive | help
--0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm currently using fetchmail to retrieve my email from my ISP. It works wonderfully, especially in combination with procmail and SpamAssassin -- except for one little problem that I'd like to verify is a bug here before sending a possibly spurious bug report. It seems that fetchmail truncates all messages to around 77 kB or so. It sees the message as more than 77 kB (for example, one such message comes up as 975525 octets.). It just can't deal with it. Here's what my .fetchmailrc looks=20 like: =3D=3D cut here =3D=3D set daemon 600 set syslog poll my.mail.server proto pop3 pass 'pass' ssl limit 0 fetchsizelimit 0 =3D=3D cut here=3D I've tried cutting procmail + SpamAssassin out of the process, and it still truncates the message, this time sending to /var/mail/apeiron rather than where I've told procmail to send it. I've tried manually retrieving the email with mutt, saving it on disk, and viewing it with Evolution versus having procmail fetch it, then viewing it with Evolution. The former works, the latter doesn't. I'm running fetchmail as /usr/local/bin/fetchmail -v -v from cron with the @reboot qualifier. I've RTFM'd and looked around for anything that would cause such an arbitrary limit, and can't find anything. It seems rather odd that such a limit would be arbitrarily imposed on messages, and I'm hesitant to label it as a bug being that fetchmail is so widely used.=20 --=20 I abhor a system designed for the "user", if that word is a coded pejorative meaning "stupid and unsophisticated". -- Ken Thompson - Please CC me in all replies, even if I'm on the relevant list(s). --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAGsrVk/lo7zvzJioRAnY3AJ4seF4S7cu3ZxIaJ6pkt4wjohjC1gCgtr0O /CjfkC7ooGGqaRx+5UZsIvQ= =jogn -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040130212125.GA80095>