Re: Duplicate Mime-version error with 1.7.5
Matt Anton <[email protected]>
| Newsgroups | gmane.network.tin.user |
|---|---|
| Organization | ~/ |
| Message-ID | <[email protected]> |
On 29 Jun 2004 11:22:26 GMT Urs JanÃen <[email protected]> wrote: > the extra mime-headers might come from tin itself via tin/attributes. > ~/.tin doesn't check if the user 'hand'-supplies > mime-headers; this is some kind of bug we should fix somehow. the big > pÃŒroblem here is what we should do if there are some hand-supplied > mime headers. overwrite them? don't add our mime-headers? overwriting > has the disadvantage that we might break nested mime-structures. no > replacing them might lead to bogus mime articles (hand supplied > header says CTE=quoted-printable, but body is in 8bit, etc.pp.) Ok, i should drink more tea as i had some mime-headers in my ~/.tin/headers I've added them while tin didn't put ifself mime-version, content-transfer-encoding and content-type headers in an old version (you adviced me to declare those in either the attributes or headers file). > currently post_8bit_header=ON (not recommended) will never add any > mime-headers and can be used if one likes to compose (multipart) mime > articles by hand. post_8bit_header=OFF (recommended) will add > mime-headers whenever they are needed. unfortunately we do not check > for any usersupplied headers here. IMHO we should overwrite them - if > the uer really likes to hand-compose mime-articles he could/should > use post_8bit_header=ON. Indeed. -- Mettons la pantoufle dans la FAQ avant l'UDP. -+- GS in <http://www.le-gnu.net> : LA FAQ c'est le pied -+-