Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Content-Transfer-Encoding: BASE64

4 views
Skip to first unread message

dann.f...@gmail.com

unread,
Jun 15, 2006, 4:02:02 PM6/15/06
to
When I receive a message that is encoded as follows:

Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: BASE64

All I see is the raw BASE64. If (IMAP4) the message is opened with
Outlook, or Squirrelmail it reders correctly.

TIA

Dann Farquhar

Mike Cowperthwaite

unread,
Jun 15, 2006, 5:09:32 PM6/15/06
to

Those few headers aren't sufficient to determine what the problem is.
Maybe the Base64 encoding isn't quite up to spec. Maybe there's some
other header (Content-Disposition?) that could affect this.

Ron K.

unread,
Jun 16, 2006, 11:51:00 AM6/16/06
to
T-bird Leader Mike Cowperthwaite radioed the tower On 6/15/2006 5:09 PM:

When a codec encodes a binary for transfer over mail or news they insert a
ID code that says which encoding was used. Could you reply with the codes
that are inserted at the head of the data for BASE-64, UUENCODE, ETC. I
see the OP's issue at least weekly on a NNTP server and suspect it is a
flaw in the news poster, but can not ID the coding method. Any clues to
spotting a cause will be appreciated so TB can be improved.

--
Ron K.
Don't be a fonted, it's just type casting.

0 new messages