-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Someone sent me an email which **appears* to be base64 encoded?


here's the first few lines:

- --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)
Content-type: text/plain; charset=utf-8
Content-language:
Content-transfer-encoding: base64

U29tZSBSZWFsbHkgR3JlYXQgTW9tZW50cyBvZiBSYWRpbyB0aG lzIHdlZWsuIFdlIGhlYXJkIGZy
b20gaW5zaWRlIEJ1cm1hIGEgUXVlYmVjZXIncyBmaXJzdCBoYW 5kIGFjY291bnQuIFdlIGxhdWdo
ZWQgb3ZlciB0aGUgVm9nZWwgZmFtaWx5J3Mgc3RpbGwgZHVyaW 5nIFByb2hpYml0aW9uIGFuZCB3



It ends with :


- --Boundary_(ID_Ta8U5Dd8tk/FeCjCVPGiyw)--

- --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)--


Base64 doesn't know what to do with this file.

anyone?



- --

Change the world one loan at a time - visit Kiva.org to find out how





-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIJN7snQV1aTcQlJsRAuw2AJ9BLzbAHEPociYV5OFap9 5LyE1/hgCfRGMc
Ip99jPMd6d5mQNBmZqpVtDA=
=ukvf
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, May 09, 2008 at 07:31:52PM -0400, Frank McCormick wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> Someone sent me an email which **appears* to be base64 encoded?
>
>
> here's the first few lines:
>
> - --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)
> Content-type: text/plain; charset=utf-8
> Content-language:
> Content-transfer-encoding: base64
>
> U29tZSBSZWFsbHkgR3JlYXQgTW9tZW50cyBvZiBSYWRpbyB0aG lzIHdlZWsuIFdlIGhlYXJkIGZy
> b20gaW5zaWRlIEJ1cm1hIGEgUXVlYmVjZXIncyBmaXJzdCBoYW 5kIGFjY291bnQuIFdlIGxhdWdo
> ZWQgb3ZlciB0aGUgVm9nZWwgZmFtaWx5J3Mgc3RpbGwgZHVyaW 5nIFByb2hpYml0aW9uIGFuZCB3
>
>
>
> It ends with :
>
>
> - --Boundary_(ID_Ta8U5Dd8tk/FeCjCVPGiyw)--
>
> - --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)--
>
>
> Base64 doesn't know what to do with this file.
>From what I recall, you but the stuff in a seperate file, say
base64.txt and then use uudecode on it.
-K
--
| .''`. == Debian GNU/Linux == | my web site: |
| : :' : The Universal |mysite.verizon.net/kevin.mark/|
| `. `' Operating System | go to counter.li.org and |
| `- http://www.debian.org/ | be counted! #238656 |
| my keyserver: subkeys.pgp.net | my NPO: cfsg.org |
|join the new debian-community.org to Debian! |
|_______ Unless I ask to be CCd, assume I am subscribed _______|


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 09 May 2008 19:46:04 -0400
Kevin Mark <kevin.mark@verizon.net> wrote:

> On Fri, May 09, 2008 at 07:31:52PM -0400, Frank McCormick wrote:
> >
> > Someone sent me an email which **appears* to be base64 encoded?
> >
> >
> > here's the first few lines:
> >
> > - --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)
> > Content-type: text/plain; charset=utf-8
> > Content-language:
> > Content-transfer-encoding: base64

> >From what I recall, you but the stuff in a seperate file, say
> base64.txt and then use uudecode on it.


Nope, afraid not. uudecode expects a begin and an end in the file.
Seems like it's some other system...anybody ??




- --
Frank McCormick debian@videotron.ca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIJPFznQV1aTcQlJsRAgc9AKCOVo1yp7E+vZXPlauPWV BBVLNVvwCggVoy
EerQ8emAM62LRkbI7i0Za9Q=
=l8U5
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri May 9 2008 04:31:52 pm Frank McCormick wrote:
> Someone sent me an email which **appears* to be base64 encoded?
>
>
> here's the first few lines:
>
> --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)
> Content-type: text/plain; charset=utf-8
> Content-language:
> Content-transfer-encoding: base64
>
> U29tZSBSZWFsbHkgR3JlYXQgTW9tZW50cyBvZiBSYWRpbyB0aG lzIHdlZWsuIFdlIGhlYXJkIGZ
>y
> b20gaW5zaWRlIEJ1cm1hIGEgUXVlYmVjZXIncyBmaXJzdCBoYW 5kIGFjY291bnQuIFdlIGxhdWd
>o
> ZWQgb3ZlciB0aGUgVm9nZWwgZmFtaWx5J3Mgc3RpbGwgZHVyaW 5nIFByb2hpYml0aW9uIGFuZCB
>3
>
>
>
> It ends with :
>
>
> --Boundary_(ID_Ta8U5Dd8tk/FeCjCVPGiyw)--
>
> --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)--
>
>
> Base64 doesn't know what to do with this file.
>
> anyone?

I used to do this manually quite some time ago. IIRC I used mpack/munpack but
I'm not certain of that now but you could try that and see.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, 09 May 2008 18:35:49 -0700
Alan Ianson <alianson@shaw.ca> wrote:

> On Fri May 9 2008 04:31:52 pm Frank McCormick wrote:
> > Someone sent me an email which **appears* to be base64 encoded?
> >
> >
> > here's the first few lines:
> >
> > --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)
> > Content-type: text/plain; charset=utf-8
> > Content-language:
> > Content-transfer-encoding: base64
> >
> > U29tZSBSZWFsbHkgR3JlYXQgTW9tZW50cyBvZiBSYWRpbyB0aG lzIHdlZWsuIFdlIGhlYXJkIGZ
>
> I used to do this manually quite some time ago. IIRC I used
> mpack/munpack but I'm not certain of that now but you could try that and
> see.


Nope. munpack says nothing to decode. This mail came from a Groupwise
mail server. Normally this person does not send out
encoded mail ..I am beginning to wonder whether she did something to it by
accident.



--
Frank McCormick debian@videotron.ca


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/09/08 18:31, Frank McCormick wrote:
>
>
> Someone sent me an email which **appears* to be base64 encoded?
>
>
> here's the first few lines:
>
> --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)
> Content-type: text/plain; charset=utf-8
> Content-language:
> Content-transfer-encoding: base64
>
> U29tZSBSZWFsbHkgR3JlYXQgTW9tZW50cyBvZiBSYWRpbyB0aG lzIHdlZWsuIFdlIGhlYXJkIGZy
> b20gaW5zaWRlIEJ1cm1hIGEgUXVlYmVjZXIncyBmaXJzdCBoYW 5kIGFjY291bnQuIFdlIGxhdWdo
> ZWQgb3ZlciB0aGUgVm9nZWwgZmFtaWx5J3Mgc3RpbGwgZHVyaW 5nIFByb2hpYml0aW9uIGFuZCB3
>
>
>
> It ends with :
>
>
> --Boundary_(ID_Ta8U5Dd8tk/FeCjCVPGiyw)--
>
> --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)--
>
>
> Base64 doesn't know what to do with this file.
>
> anyone?

This is gmail stupidity. It's how Google sends html-enabled mail.
The only solution is to ask the sender to enable plain-text.

- --
Ron Johnson, Jr.
Jefferson LA USA

We want... a Shrubbery!!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIJQsXS9HxQb37XmcRAlunAJ9SMKTQJwofwl390Adf2j FiYCTZygCcDxAl
TT2U2oNRvSg8lH3KYwkU7ds=
=uaOm
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On 05/09/2008 06:31 PM, Frank McCormick wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> Someone sent me an email which **appears* to be base64 encoded?
>
>
> here's the first few lines:
>
> - --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)
> Content-type: text/plain; charset=utf-8
> Content-language:
> Content-transfer-encoding: base64
>
> U29tZSBSZWFsbHkgR3JlYXQgTW9tZW50cyBvZiBSYWRpbyB0aG lzIHdlZWsuIFdlIGhlYXJkIGZy
> b20gaW5zaWRlIEJ1cm1hIGEgUXVlYmVjZXIncyBmaXJzdCBoYW 5kIGFjY291bnQuIFdlIGxhdWdo
> ZWQgb3ZlciB0aGUgVm9nZWwgZmFtaWx5J3Mgc3RpbGwgZHVyaW 5nIFByb2hpYml0aW9uIGFuZCB3
>
>
>
> It ends with :
>
>
> - --Boundary_(ID_Ta8U5Dd8tk/FeCjCVPGiyw)--
>

Huh?

That's not the right boundary. Below is the right boundary.

> - --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)--
>
>
> Base64 doesn't know what to do with this file.
>

Of course not. Base64 expects each message part to have a beginning and
an end, and message parts cannot (AFAIK) be interleaved.

> anyone?
>

I suspect that whatever software created the message is broken. Delete
the spurious message boundary line and decode using munpack or another
Base64 decoder. Since that is a private message to you, I won't ask you
to send it to me, but I am curious...



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Frank McCormick wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> Someone sent me an email which **appears* to be base64 encoded?
>
>
> here's the first few lines:
>
> - --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)
> Content-type: text/plain; charset=utf-8
> Content-language:
> Content-transfer-encoding: base64
>
> U29tZSBSZWFsbHkgR3JlYXQgTW9tZW50cyBvZiBSYWRpbyB0aG lzIHdlZWsuIFdlIGhlYXJkIGZy
> b20gaW5zaWRlIEJ1cm1hIGEgUXVlYmVjZXIncyBmaXJzdCBoYW 5kIGFjY291bnQuIFdlIGxhdWdo
> ZWQgb3ZlciB0aGUgVm9nZWwgZmFtaWx5J3Mgc3RpbGwgZHVyaW 5nIFByb2hpYml0aW9uIGFuZCB3
>
>
>
> It ends with :
>
>
> - --Boundary_(ID_Ta8U5Dd8tk/FeCjCVPGiyw)--
>
> - --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)--
>
>
> Base64 doesn't know what to do with this file.
>
> anyone?
>
>

Prepend the line "begin-base64 644 -" to your encoded text. Append the
line "====" and pipe it through `uudecode'


--
Raj Kiran Grandhi
--
Politics is for the moment. An equation is for eternity.
-- Albert Einstein


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Raj Kiran Grandhi wrote:
> Frank McCormick wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>>
>> Someone sent me an email which **appears* to be base64 encoded?
>>
>>
>> here's the first few lines:
>>
>> - --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)
>> Content-type: text/plain; charset=utf-8
>> Content-language:
>> Content-transfer-encoding: base64
>>
>> U29tZSBSZWFsbHkgR3JlYXQgTW9tZW50cyBvZiBSYWRpbyB0aG lzIHdlZWsuIFdlIGhlYXJkIGZy
>>
>> b20gaW5zaWRlIEJ1cm1hIGEgUXVlYmVjZXIncyBmaXJzdCBoYW 5kIGFjY291bnQuIFdlIGxhdWdo
>>
>> ZWQgb3ZlciB0aGUgVm9nZWwgZmFtaWx5J3Mgc3RpbGwgZHVyaW 5nIFByb2hpYml0aW9uIGFuZCB3
>>
>>
>>
>>
>> It ends with :
>>
>>
>> - --Boundary_(ID_Ta8U5Dd8tk/FeCjCVPGiyw)--
>>
>> - --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)--
>>
>>
>> Base64 doesn't know what to do with this file.
>>
>> anyone?
>>
>>
>
> Prepend the line "begin-base64 644 -" to your encoded text. Append the
> line "====" and pipe it through `uudecode'
>
>
That also did it. Came out like the message imported into Thunderbird
came out. T'bird must automatically uudecode stuff.


Thanks

Cheers

Frank

--




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mumia W.. wrote:
| On 05/09/2008 06:31 PM, Frank McCormick wrote:
|> -----BEGIN PGP SIGNED MESSAGE-----
|> Hash: SHA1
|>
|>
|>
|> Someone sent me an email which **appears* to be base64 encoded?
|>
|>
|> here's the first few lines:
|>
|> - --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)
|> Content-type: text/plain; charset=utf-8
|> Content-language:
|> Content-transfer-encoding: base64
|>
|>
U29tZSBSZWFsbHkgR3JlYXQgTW9tZW50cyBvZiBSYWRpbyB0aG lzIHdlZWsuIFdlIGhlYXJkIGZy

|>
|>
b20gaW5zaWRlIEJ1cm1hIGEgUXVlYmVjZXIncyBmaXJzdCBoYW 5kIGFjY291bnQuIFdlIGxhdWdo

|>
|>
ZWQgb3ZlciB0aGUgVm9nZWwgZmFtaWx5J3Mgc3RpbGwgZHVyaW 5nIFByb2hpYml0aW9uIGFuZCB3

|>
|>
|>
|>
|> It ends with :
|>
|>
|> - --Boundary_(ID_Ta8U5Dd8tk/FeCjCVPGiyw)--
|>
|
| Huh?
|
| That's not the right boundary. Below is the right boundary.
|
|> - --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)--
|>
|>
|> Base64 doesn't know what to do with this file.
|>
|
| Of course not. Base64 expects each message part to have a beginning and
| an end, and message parts cannot (AFAIK) be interleaved.
|
|> anyone?
|>
|
| I suspect that whatever software created the message is broken. Delete
| the spurious message boundary line and decode using munpack or another
| Base64 decoder. Since that is a private message to you, I won't ask you
| to send it to me, but I am curious...
|
|
|


~ I'll try it when i get a chance.. but as I told Ron Johnson when I
exported it from Sylpheed and imported it into Thunderbird it all became
clear! I have no idea what went on. But I''ll try your method.

Frank

- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIJYuNnQV1aTcQlJsRAm5BAJ4982E/TO9cGtY+TX1iVVTFShwhNgCeJE4j
rvP3BEUgguorLLqQw8TEi3E=
=/GmT
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/10/08 06:54, debian@videotron.ca wrote:
> Raj Kiran Grandhi wrote:
[snip]
>>
>> Prepend the line "begin-base64 644 -" to your encoded text. Append the
>> line "====" and pipe it through `uudecode'
>>
>>
> That also did it. Came out like the message imported into Thunderbird
> came out. T'bird must automatically uudecode stuff.

Since Tbird inline-displays uuencoded & base64 attachments, I'm sure
that's the case.

- --
Ron Johnson, Jr.
Jefferson LA USA

We want... a Shrubbery!!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIJaVSS9HxQb37XmcRAqJgAJ9MOP6pWiuBdbR6tnxTQa lsK3nm1wCeMIbs
s3mN+GvXOIMq8Vfd6hRmuqk=
=Vu4h
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org