[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Base64 -- Gnus vs. Exchange
From: |
Ted Zlatanov |
Subject: |
Re: Base64 -- Gnus vs. Exchange |
Date: |
Mon, 12 Oct 2009 13:33:19 -0500 |
User-agent: |
Gnus/5.110011 (No Gnus v0.11) Emacs/23.1.50 (gnu/linux) |
On Thu, 17 Sep 2009 07:22:49 -0700 (PDT) Ian Soboroff <isoboroff@gmail.com>
wrote:
IS> Sorry if this is a FAQ, but I couldn't dig up a solution anywhere.
IS> Pointers appreciated.
IS> I have recently had the misfortune to get stuck behind an Exchange
IS> server. Exchange, as we all know, seems to enjoy re-encoding
IS> perfectly reasonable and innocent text sections into base64 which Gnus
IS> then refuses to decode. ("Error while decoding: (error Invalid base64
IS> data)". (Believe me, I wrote some of the software that sends me mail,
IS> and I _know_ it sends it as text/plain! I tried adding a X-Get-Your-
IS> Filthy-Mitts-Off-My-Encoding header, but that didn't help.)
IS> My current solution is that I wrote a Perl script to decode base64,
IS> and then I call it via the menus Article->Washing->Unix pipe, which
IS> unfortunately has no keystroke. The script is pretty dumb:
IS> use MIME::Base64 qw/decode_base64/;
IS> local($/) = undef;
IS> print decode_base64(<STDIN>);
IS> Can someone better at Gnus/Elisp help me to teach Gnus to just do this
IS> right natively? i.e. to decode base64 without extra mousing or
IS> keystrokes, but when i view the message or MIME part?
Would it be possible to:
- provide a sample message
- do `M-x toggle-debug-on-error' and show the stack trace when Base64
decoding fails?
I read Base64 encoded messages every day without issues so this may be a
bug in Gnus or a malformed message.
Thanks
Ted
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: Base64 -- Gnus vs. Exchange,
Ted Zlatanov <=