YAM - Yet Another Mailer (#2) - Content-Transfer-Encoding header (#19) - Message List

Content-Transfer-Encoding header
 unsolved

Hello,

I manage a mailing list using Listar and lately one of my member have his messages Base64 encoded on the ML (which is not easy to read ;-) ) We eventually ended at spotting the fact that in each of his emails there is the header Content-Transfer-Encoding: base64 while mine have the header Content-Transfer-Encoding: quoted-printable

We are both using the latest nightly-build of YAM (25th feb.). I would like to know how Yam set this header and how he can change that.

Regards,

Alexandre.

  • Message #57

    I would like to know how Yam set this header and how he can change that.

    YAM does an automatic check. It counts the number of binary chars, too long lines, etc. The decision which content type to use is then made like this:

    1. no binary or "unsave" chars, but lines longer than 998 chars

    ==> quoted-printable, to avoid too long lines

    1. some unsave chars, but no binary chars and all lines are shorter than 998 chars and 8bit encoding is allowed

    ==> 8bit encoding

    1. more than a certain percentage of unsave or binary chars or the attachment is an application

    ==> base64 encoding

    1. nothing of the above

    ==> quoted-printable

    "unsave" chars is anything beyond 0x7f which may not be displayable in every character set.

    • Message #58

      I would like to know how Yam set this header and how he can change that.

      YAM does an automatic check. It counts the number of binary chars, too long lines, etc. The decision which content type to use is then made like this:

      1. no binary or "unsave" chars, but lines longer than 998 chars

      ==> quoted-printable, to avoid too long lines

      1. some unsave chars, but no binary chars and all lines are shorter than 998 chars and 8bit encoding is allowed

      ==> 8bit encoding

      1. more than a certain percentage of unsave or binary chars or the attachment is an application

      ==> base64 encoding

      1. nothing of the above

      ==> quoted-printable

      "unsave" chars is anything beyond 0x7f which may not be displayable in every character set.

      I quess that by "8bit encoding is allowed" you mean the option "mail server accept 8bit" is checked in the config, aren't you ? Anyway I asked him and this option is *not* checked. I'd like to add that this is a constant behaviour : every of his emails are like that and it's only plain text (so I don't think there is either a certain percentage of unsafe or binary chars nor a problem with the attachement (as there is none)). If you wish i can send you one of his emails sent both to the list and directly to me so you can see the difference.

      • Message #59

        If you are interested in more details just look at YAM's source. The function WhichEncodingForFile() does all the magic for all attachments and the mail text itself.

        Alternatively a MIME debug log produced by the debug version could also bring some light into this issue. Posting the raw mails might also be helpful.

        And yes, "8bit encoding allowed" corresponds to the "mail server accept 8bit" option.

        • Message #60

          He just checked this option ("mail server accepts 8bit") and now his emails are not base64 encoded anymore on the ML... What is strange is that previously (i.e. before using the latest nightly build) all was working great like that... Do you still want to see raw messages ? And where here or privately by email ?

          Regards.

          • Message #61

            The big question is: what exactly is wrong about base64? You say it is hard to read. Yes, it is. But why doesn't Listar decode such mails before displaying them? Even quoted-printable mails must be decoded, otherwise you will end up with text like "Thore B=C3=B6ckelmann" or even "=?UTF-8?B?VGhvcmUgQsO2Y2tlbG1hbm4=?=" which is equally unreadable. This is definitely a bug in Listar and not in YAM.

            If you like you can send me and Jens the mail privately, as I doubt attachments are possible here.

            • Message #62

              Okay I did send you both privately the email at fault and did not heard back from you. Did you ever received them ?

              The big question is: what exactly is wrong about base64? You say it is hard to read. Yes, it is. But why doesn't Listar decode such mails before displaying them?

              Listar does not display anything it's a ML managing software that is dispatching mails to registered mail addresses.

              • Message #63

                Okay I did send you both privately the email at fault and did not heard back from you. Did you ever received them ?

                It seems it got lost. At least I cannot find it here in my work's Thunderbird account. Please send it again.

                The big question is: what exactly is wrong about base64? You say it is hard to read. Yes, it is. But why doesn't Listar decode such mails before displaying them?

                Listar does not display anything it's a ML managing software that is dispatching mails to registered mail addresses.

                But does it add some kind of footer to the mails? Maybe that disturbs YAM somehow.

                • Message #64

                  It seems it got lost. At least I cannot find it here in my work's Thunderbird account. Please send it again.

                  I sent it Monday, March 16th, around 18:00+1 to you with CC to Jens. Okay I'm resending it right now.

                  But does it add some kind of footer to the mails? Maybe that disturbs YAM somehow.

                  Yes it *is* adding a footer. But what I don't understand is why this suddenly happened to this guy after an update ? The ML setup was not changed recently neither was YAM's settings. And moreover I am using YAM without any problem on this ML...

                  • Message #65

                    Ok, I just had a deeper look at the mail and came to the conclusion that YAM is doing everything right, because it cannot do anything else.

                    Let me explain. Both attached mails have this ContentType header:

                    Content-Type: text/plain; charset="iso-8859-1"
                    Content-Transfer-Encoding: 8bit
                    

                    This clearly declares the following text to be nothing else than plain text, even if it is in fact base64 encoded stuff. Hence YAM displays it as exactly this: plain text. Even Thunderbird displays the base64 encoded mail as plain text and hence one reads the raw base64 stuff instead of the wanted text.

                    So, from my point of view there is nothing we can do about that. Maybe Jens knows better.

                    If listar creates such mails (converting plain text to base64), then it is listar's fault, because it doesn't reflect this conversion in the ContentType header.

                  • Message #66

                    Some more infos.

                    Both mails were originally created by Outlook. Maybe listar is the wrong software to be blamed, but Outlook instead. Anyway, the one mail's headers don't reflect its true nature and hence gets displayed wrong. I have no idea what could be tweaked in Outlook, because up to today I *never* used this (well known buggy) program.

                    • Message #67

                      Both mails were originally created by Outlook.

                      No they don't, if I display the attached emails I find the following header :

                      User-Agent: YAM/2.6-dev-20090225 (AmigaOS4; PPC; rv:20090225)
                      

                      Which clearly indicates they were created by YAM 2.6-dev compiled on February, 25th, 2009.

                      On the other hand *I* did used Outlook to send you the email (because I am currently at work where I don't have priviledges to choose which emailer to install no matter how buggy I can think the choosen one is). I think you read the headers of the container email whereas I'm speaking about the attached one.

                      If you prefer, and just in case for an unknown reason the headers of the attached emails were changed I can try to resend them to you this evening using YAM on my A1/OS4.

                      EDIT: Okay just did a quick test, you are right this btard is modifying headers of the attached emails !! I'll try to send them to you using YAM this night.

Attachments

No attachments created.