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:54:50AM -0600, Josh Hildebrand wrote:
Certainly there is either a way to tell mutt to handle the spaces properly,
or to create a macro that grabs the file name with
| head -1 | cut -d ' ' -f 3-
and then runs uudecode -o on it.. I'm not sure how to do that in
Josh Hildebrand [EMAIL PROTECTED] wrote:
Unfortunately, when Notes people send out file attachments, the current
supported Notes-SMTP gateway UUencodes them. That's no problem for mutt;
except for when the file names contain spaces, the first line of the
UUencode text is something like
David, I believe I see what you are saying; however, your suspicion appears
to be wrong, in this case.
See below.
In the message header I find:
Mime-Version: 1.0
Content-type: multipart/mixed;
Boundary="0__=d0vLICMyvygZsBD1fr4XOLmIvfbHtJCvKXjkj9BXMq2hXsDwSZvltNEJ"
Content-Disposition:
Josh Hildebrand [EMAIL PROTECTED] wrote:
David, I believe I see what you are saying; however, your suspicion
appears to be wrong, in this case.
This is not just a suspicion. I actually tested this out using Mutt
0.95.1. You appear to be using Mutt 0.93.2. Is there a difference in
how these
David,
I will bounce you a message in a few seconds..
I did state the problem incorrectly.. it appears that when I "save" the
attachement, it saves it as the proper name.. but it doesn't UUdecode it.
The times when I get just the first word of the filename saved is when I do
a '| uudecode'
10 matches
Mail list logo
