Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010612115414.B298@BOEKHOFF_M>; from "malcolm.boekhoff" on Tue, Jun 12,
2001 at 11:54:14AM
On Tue, Jun 12, 2001 at 11:54:14AM +0100, malcolm.boekhoff wrote:
> On 2001-05-07 06:24:18, Duke Normandin wrote:
>
> I have the same problem, I have Cygwin translating CRLF to CR before
> Mutt encoding starts (so that at the other end the unencoded file hasn't
> got any CR's in it).
>
> My solution at the moment is to use uuencode to 7-bit ascify the binary
> tar file, but beware the same CRLF translation takes place on stdin, but
> not on pipes, so use this:
>
> cat zipfile | uuencode zipFileNamePutInUueHeader
>
> and send the ".uue" file as "text/plain".
>
> I have discovered that OE can decode the uuencoded file correctly at the
> other end.
>
> Probably, "uuencode zipfile zipFileNamePutInUueHeader" works as well because then
> uuencode is opening the file as binary.
Thanks for that information and solution. The problem I was having was
with the recipients OE settings or something, and not my Cygwin/Mutt
configuration. However it's very possible that I still have a problem
with this matter and don't know it -- as I don't send too many zipfiles.
--
-duke
Calgary, Alberta, Canada
