Date: Fri, 1 Feb 2008 17:31:24 +0100 From: Mel <fbsd.questions@rachie.is-a-geek.net> To: freebsd-questions@freebsd.org Cc: zszalbot@gmail.com, perryh@pluto.rain.com, Peter Boosten <peter@boosten.org> Subject: Re: cron to attach a gz file Message-ID: <200802011731.25322.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: <47A2CEB2.2000705@boosten.org> References: <94136a2c0801310049k22d7a890kac8a2482ac49333c@mail.gmail.com> <47a2c295.zZbt1U/oWvbDh508%perryh@pluto.rain.com> <47A2CEB2.2000705@boosten.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 01 February 2008 08:48:02 Peter Boosten wrote: > perryh@pluto.rain.com wrote: > >>> I know I can use > >>> > >>> mail -s "logfile " < /var/log/httpd_access.log > >>> > >>> in cron to email the content of a log file to a particular email > >>> address but how do I make that log file a binary attachment (*.gz)? > >> > >> gzip -c /var/log/httpd_access.log | uuencode httpd_access.log.gz | mail > >> -s "logfile" someone@somewhere > > > > If you want an actual MIME attachment, see /usr/ports/mail/nail Nice tip, thanks for that. > From a modern mail reader point of view there is not much difference > between a MIME or a uuencoded attachment. But there is between an uuencoded /body/ and an attachment. At the risk of this degrading into a mail useragent battle: kmail didn't give an option to uudecode the body. -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200802011731.25322.fbsd.questions>