treating "broken" base64 parts

treating "broken" base64 parts

[Vladimir Volovich]

Hi,

i often receive messages from mailing lists which have the following
form:

From: someone
Subject: test
To: someone
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: base64
OtherHeaders: ...

5MzRINrB1NLB18vJINDSxcTMwcfBwCDPwtPVxMnU2CDgzsnLz8QgySDFx88gy8nSyczMyd7F
08vVwCDewdPU2CDOwSDQ0sXEzcXUDQrQ0snHz8TOz9PUySDLIM7B28XN1SDExczVLiDuwSDN
...
yc/OLCDF08zJIM7FIMnNxcXUxQ0K1MHLz9fPx88uDQpodHRwOi8vY2hzbGF2Lmh5cGVybWFy
dC5uZXQNCg0K4czFy9PFyg0KDQoNCg==

-------------------------------------------------------------------------------
-=COOL-LIST=- Project // Mail Lists service on something.com

I.e., the text is a 1-part messages with CTE=base64, but mailing list
software adds a trailer lines. Gnus does not display these messages
correctly, i.e. what i see is the undecoded base64 text. I wonder,
could gnus automagically treat such messages?

Best,
v.

Re: treating "broken" base64 parts

[Vladimir Volovich]

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

"VV" == Vladimir Volovich writes:

 VV> i often receive messages from mailing lists which have the
 VV> following form:
[...]
 VV> From: someone Subject: test To: someone Content-Type: text/plain;
 VV> charset=koi8-r Content-Transfer-Encoding: base64 OtherHeaders:
 VV> ...

 VV> 5MzRINrB1NLB18vJINDSxcTMwcfBwCDPwtPVxMnU2CDgzsnLz8QgySDFx88gy8nSyczMyd7F
 VV> 08vVwCDewdPU2CDOwSDQ0sXEzcXUDQrQ0snHz8TOz9PUySDLIM7B28XN1SDExczVLiDuwSDN
 VV> ...
 VV> yc/OLCDF08zJIM7FIMnNxcXUxQ0K1MHLz9fPx88uDQpodHRwOi8vY2hzbGF2Lmh5cGVybWFy
 VV> dC5uZXQNCg0K4czFy9PFyg0KDQoNCg==

 VV> -------------------------------------------------------------------------------
 VV> -=COOL-LIST=- Project // Mail Lists service on something.com

 VV> I.e., the text is a 1-part messages with CTE=base64, but mailing
 VV> list software adds a trailer lines. Gnus does not display these
 VV> messages correctly, i.e. what i see is the undecoded base64
 VV> text. I wonder, could gnus automagically treat such messages?

well, here is a patch which solves this problem for me:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: mm-bodies.el.diff --]
[-- Type: text/x-patch, Size: 602 bytes --]

--- mm-bodies.el.orig	Tue Jan 11 23:51:31 2000
+++ mm-bodies.el	Tue Jan 11 23:52:28 2000
@@ -154,8 +154,12 @@
 				  ;; Some mailers insert whitespace
 				  ;; junk at the end which
 				  ;; base64-decode-region dislikes.
+				  ;; Also remove possible junk which could
+				  ;; have been added by mailing list software.
 				  (save-excursion
-				    (goto-char (point-max))
+				    (goto-char (point-min))
+				    (re-search-forward "^[\t ]*$")
+				    (delete-region (point) (point-max))
 				    (skip-chars-backward "\n\t ")
 				    (delete-region (point) (point-max))
 				    (point))))

[-- Attachment #3: Type: text/plain, Size: 320 bytes --]


could someone with CVS rw access apply this if you find it correct?

BTW, i just noticed that the Lines: header generated by gnus is
incorrect. So the old bug with Lines: header is still there. :-(
Could someone please fix it? (calculate Lines: NOT for MML message,
but for a MIME message)

	Best regards, -- Vladimir.