Re: Using tin to access fido(7) nntp geteways
Anton Shepelev <[email protected]> Fri, 11 May 2012 03:22:30 +0400
| Newsgroups | gmane.network.tin.user |
|---|---|
| Message-ID | <[email protected]> |
Urs Jan=CE=B2en: > I can reporduice the problem with: >=20 > chao% echo $LC_CTYPE > en_US.utf8 > chao% cat ~/.tin/attributes > scope=3Dru.*,relcom.*,fido7.*,medlux.* > mime_forward=3DON > mm_network_charset=3DKOI8-R > undeclared_charset=3DKOI8-R > post_8bit_header=3DON > post_mime_encoding=3D8bit >=20 > local charset differs from the undeclared_charset > and post_8bit_header is on, the cached overview > data is written out raw in the local charset > (utf8) and when reread undeclared_charset is as- > sumed as no mime headers are found -> garbage. Many thanks for investigating, Urs. This is my con- figuration, indeed. > something like the following should solve the > problem (you have to purge the cached overview da- > ta first!). I'll try it and let you know. --=20 () ascii ribbon campaign - against html e-mail=20 /\ www.asciiribbon.org - against proprietary attachments=