Re: Always sending us-ascii
Hi On Sunday 1 March 2009 at 6:35:44 PM, in mid:448171083.20090301103...@pobox.com, Bill McQuillan wrote: I have noticed that the TBUDL list server makes several changes to each message that it forwards: Adding the List-Id, etc. header fields Adding the Current version... to the bottom of text/plain messages Adding a new Current version... part to multipart/mixed messages I also notice that the Content-Type and Content-Transfer-Encoding header fields are placed with the List-* fields in the header and not with the Mime-Version field where most clients place them. Looking at the headers/kludges, there is a huge difference between the message received directly and the one received via the list server. I don't see that posting the two for comparison would serve a purpose but I can later if anybody asks. This leads me to believe that the list server builds a new message and then after deleting the existing Content-* fields recreates them by scanning the message for non-ascii characters and setting the the Content-Type field to us-ascii if that will suffice. I shall include a couple of pound signs. IIRC, that is not a us-ascii character. Here goes: ££. Wonder if it will still use us-ascii? There is some justification for this in the Email RFCs where it shows a preference for the simplest level necessary when encoding a message. Clearly, TB! doesn't share that preference - so it sends using the character set you tell it to use. (-; In a separate pet peeve of mine, it seems that this much processing of each message would make it straightforward for the list server to determine whether a cut mark already exists and insert one just before the footer if necessary. This could reduce the fish traffic on this list considerably! end peeve :-) Some of the messages (for example mid:160674186.20090213171...@optusnet.com.au) show the list footer in a separate tab. Would that also prevent them being quoted in the event that the poster missed out his cut mark and the replier failed to trim? -- Best regards, MFPA An idealist is a person who helps other people to be prosperous Using The Bat! v4.0.38 on Windows XP 5.1 Build 2600 Current version is 4.1.11 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: Always sending us-ascii
Hi On Monday 2 March 2009 at 2:38:16 PM, in mid:392566194.20090302143...@my_localhost, MFPA wrote: Hi On Sunday 1 March 2009 at 6:35:44 PM, in mid:448171083.20090301103...@pobox.com, Bill McQuillan wrote: [...] This leads me to believe that the list server builds a new message and then after deleting the existing Content-* fields recreates them by scanning the message for non-ascii characters and setting the the Content-Type field to us-ascii if that will suffice. I shall include a couple of pound signs. IIRC, that is not a us-ascii character. Here goes: ££. Wonder if it will still use us-ascii? No: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8BIT So it looks like you may have explained it. (-: I notice 8BIT (capitals) for that one, whereas 7bit does not get capitalised when charset is us-ascii. -- Best regards, MFPA If you can't convince them, confuse them. Using The Bat! v4.0.38 on Windows XP 5.1 Build 2600 Current version is 4.1.11 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: Always sending us-ascii
On Mon, 2009-03-02, MFPA wrote: On Monday 2 March 2009 at 2:38:16 PM, in mid:392566194.20090302143...@my_localhost, MFPA wrote: On Sunday 1 March 2009 at 6:35:44 PM, in mid:448171083.20090301103...@pobox.com, Bill McQuillan wrote: [...] This leads me to believe that the list server builds a new message and then after deleting the existing Content-* fields recreates them by scanning the message for non-ascii characters and setting the the Content-Type field to us-ascii if that will suffice. I shall include a couple of pound signs. IIRC, that is not a us-ascii character. Here goes: ££. Wonder if it will still use us-ascii? No: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8BIT So it looks like you may have explained it. (-: I notice 8BIT (capitals) for that one, whereas 7bit does not get capitalised when charset is us-ascii. Just to add to the confusion, your first message with 2 pound signs arrived at my computer with: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable and the pound signs looked good. However, your second message (which you received with iso-8859-15 and 8BIT) arrived at my computer with: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 and the pound signs still looked good. I haven't a clue what *this* message will look like! :-) Clearly more than one modifying server has been processing our mail! Unfortunately, so called MIME downgrading is not usually mentioned in the trace header fields, so we are probably out of luck in tracking down the culprits. Ain't email fun? -- Bill McQuillan bill.mcquil...@pobox.com Using The Bat! 2.11 on Windows XP 5.1 build 2600-Service Pack 2 Current version is 4.1.11 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: Always sending us-ascii
On Monday, March 2, 2009, 11:13:37 AM, Bill McQuillan wrote: I haven't a clue what *this* message will look like! :-) all 3 messages have the pound signs here. (££) -- Dwight A. Corrin 316.303.9385 phone ahead to fax dcorrin at fastmail.fm photo galleries at http://dcorrin.smugmug.com photo blog at http://dcorrin.aminus3.com Using IMAP with The Bat! 4.1.11.6 on Windows XP version 5,1 (Service Pack 3) Current version is 4.1.11 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
