On 1999-03-09 21:12:55 -0600, Josh Hildebrand wrote:
The times when I get just the first word of the filename saved is
when I do a '| uudecode' (without -o and the filename).
This is obviously a problem with the version of uudecode you are
using.
Sorry for the confusion, but I still see
Yep.. that's what I would have written for an external script.. Can you
tell me how to call that script from, say, capital-S, in the 'view
attachment' menu of mutt? I haven't bound keys before.
On Tue, Mar 09, 1999 at 12:18:44PM -0500, rfi from Rich Roth wrote:
On Tue, Mar 09, 1999 at
On Wed, Mar 10, 1999 at 08:29:58AM +0100, Thomas Roessler wrote:
On 1999-03-09 21:12:55 -0600, Josh Hildebrand wrote:
The times when I get just the first word of the filename saved is
when I do a '| uudecode' (without -o and the filename).
This is obviously a problem with the version of
On 1999-03-10 08:56:18 -0500, rfi from Rich Roth wrote:
Probably - but couldn't this be fixed with a mailcap entry that uses the -o
option. Or does mutt not use mailcap for uudecode ?
no. 0.95 supports uuencode out of the box, just like base64 or
anything else. (With the exception that we
Josh Hildebrand [EMAIL PROTECTED] wrote:
I will bounce you a message in a few seconds..
I received the message, and Mutt 0.95.1 did properly save and decode the
message, as I expected, with proper filename handling.
Upgrade at your earliest convenience, and you will be happy. :)
I did
On Tue, Mar 09, 1999 at 12:19:31 -0500, Rob Reid wrote:
send-hook tea@astro "my_hdr Subject: Tea and cookies in the Astrolounge at 3:30"
send-hook !tea@astro "unmy_hdr Subject"
Everything works except the subject line, which shows up on the _n_e_x_t
message I write, even if it isn't to
The attached perl script handles removing of the tnef attachment##
it's worked for me. (might want to test with a large assortment of message to
make sure that you're not loosing the attachments.)
##
## Remove the ms-tnef attachments
##
:0
* B ?? ^Content-Type: \/(application/ms-tnef)$
{
