[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Nmh-workers] content-transfer-encoding: base64
From: |
Anders Eriksson |
Subject: |
[Nmh-workers] content-transfer-encoding: base64 |
Date: |
Sat, 08 Mar 2008 11:31:22 +0100 |
Hi,
I regularly get traffic form a bugzilla in the following form:
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: base64
<other headers>
aHR0cDovL2J1Z3MuZnJlZWRlc2t0b3Aub3JnL3Nob3dfYnVnLmNnaT9pZD0xNDY4NwoKCk1hcnRp
bi3DiXJpYyBSYWNpbmUgPHEtZnVua0Bpa2kuZmk+IGNoYW5nZWQ6CgogICAgICAgICAgIFdoYXQg
ICAgfFJlbW92ZWQgICAgICAgICAgICAgICAgICAgICB8QWRkZWQKLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LQogICAgICAgICAgQ29tcG9uZW50fERyaXZlci9BTUQgICAgICAgICAgICAgICAgICB8RHJpdmVy
L3JhZGVvbmhkCgoKCgotLSAKQ29uZmlndXJlIGJ1Z21haWw6IGh0dHA6Ly9idWdzLmZyZWVkZXNr
dG9wLm9yZy91c2VycHJlZnMuY2dpP3RhYj1lbWFpbAotLS0tLS0tIFlvdSBhcmUgcmVjZWl2aW5n
IHRoaXMgbWFpbCBiZWNhdXNlOiAtLS0tLS0tCllvdSBhcmUgdGhlIFFBIGNvbnRhY3QgZm9yIHRo
ZSBidWcuCllvdSBhcmUgdGhlIGFzc2lnbmVlIGZvciB0aGUgYnVnLgpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwp4b3JnLXRlYW0gbWFpbGluZyBsaXN0Cnhv
cmctdGVhbUBsaXN0cy54Lm9yZwpodHRwOi8vbGlzdHMueC5vcmcvbWFpbG1hbi9saXN0aW5mby94
b3JnLXRlYW0K
--
To unsubscribe, e-mail: address@hidden
For additional commands, e-mail: address@hidden
show erros out with:
(Message lists/radeonhd:646)
mhshow: invalid BASE64 encoding -- continuing
(content text/plain in message 646)
mhshow: invalid BASE64 encoding -- continuing
(content text/plain in message 646)
mhshow: invalid BASE64 encoding -- continuing
(content text/plain in message 646)
mhshow: invalid BASE64 encoding -- continuing
(content text/plain in message 646)
mhshow: invalid BASE64 encoding -- continuing
(content text/plain in message 646)
mhshow: invalid BASE64 encoding -- continuing
(content text/plain in message 646)
mhshow: invalid BASE64 encoding -- continuing
(content text/plain in message 646)
mhshow: invalid BASE64 encoding -- continuing
(content text/plain in message 646)
mhshow: invalid BASE64 encoding -- continuing
(content text/plain in message 646)
mhshow: invalid BASE64 encoding -- continuing
(content text/plain in message 646)
mhshow: invalid BASE64 encoding -- continuing
(content text/plain in message 646)
mhshow: invalid BASE64 encoding -- continuing
(content text/plain in message 646)
mhshow: invalid BASE64 encoding
(content text/plain in message 646)
Seems familiar? Is cte:base64 legal, or is nmh missing something? Judging from
the bugzilla list, others can read the messages fine.
/Anders
- [Nmh-workers] content-transfer-encoding: base64,
Anders Eriksson <=