YAM - Yet Another Mailer (#2) - Invisible message (#44) - Message List

Invisible message
 solved

I recently received a message on the MorphOS mailing list. It appeared to be blank but I knew that it shouldn't. Indeed I saved it in raw format and veryfied that it was not blank.

I played with the raw file, an editor, and YAM for a while and found that the problem was in the "Content-Type" field of the header.

The original "Content-Type" that prevents message displaying is this:

Content-Type: text/plain; charset=ISO-8859-1 + Euro

The edited "Content-Type" that allows message displaying is this:

Content-Type: text/plain; charset=ISO-8859-1

I don't know if the original "Content-Type" is illegal or not, but I suspect that the actions of YAM (or codesets.library?) are too much fussy...

Best regards.

Dr. Morbius

Tree View Flat View (newer first) Flat View (older first)
  • Message #231

    Actually there is no need to compile YAM on your own to get rid of the expiration requester. It is sufficient a simple CLI script.

    I always use updated nightly builds. However, I was forced to write this script because of an emergency occurred one year ago (approximately).

    (1) The new YAM 2.5 version required an updated MUI class (I do not remember what), but this new class was buggy under MorphOS, so YAM did not work anymore.

    (2) The new YAM 2.5 version refused to run with the previous non-buggy MUI class.

    (3) The old YAM 2.5 version refused to run because of the expiration requester.

    (4) It was impossible to revert to YAM 2.4 *AND* have all recent messages available because the filename convention for stored messages was changed.

    [Note: Well, now I remember it was Toolbar.mcc, according to a thread I opened in this forum. YAM expired just the day after that message.]

    So I added two lines (that call usual OS commands stored in "C:") to the script that I use to run YAM, and fooled the expiration requester... In such a way I was able to use the expired YAM with the old MUI class until a debugged new class was distributed a few weeks later...

    But don't fear :wink:, I will not make this script public because it is only an *emergency* tool for my own use.

    Cheers, Dr.Morbius

  • Message #230

    Well, I mentioned your comment to the involved guy, who was using a version of YAM compiled by himself.

    He has compiled a newer source and set a new font within YAM, and the problem is gone away.

    Well, that's indeed a very good example why I dislike that everyone is compiling YAM on their own just because to get rid of the expiration requester. People should really use the nightly builds instead and should be forced to update regularly. Otherwise you run into such problems like you faced.

  • Message #229

    Well, I mentioned your comment to the involved guy, who was using a version of YAM compiled by himself.

    He has compiled a newer source and set a new font within YAM, and the problem is gone away.

    Cheers, Dr.Morbius

  • Message #228

    I recently received a message on the MorphOS mailing list. It appeared to be blank but I knew that it shouldn't. Indeed I saved it in raw format and veryfied that it was not blank.

    I played with the raw file, an editor, and YAM for a while and found that the problem was in the "Content-Type" field of the header.

    The original "Content-Type" that prevents message displaying is this:

    Content-Type: text/plain; charset=ISO-8859-1 + Euro

    The edited "Content-Type" that allows message displaying is this:

    Content-Type: text/plain; charset=ISO-8859-1

    I don't know if the original "Content-Type" is illegal or not, but I suspect that the actions of YAM (or codesets.library?) are too much fussy...

    That's definitly a sign that the author of that message used a very old nightly build that was still buggy in that respect and inserts this "+ Euro" instead of stripping it. I would strongly suggest you remind the author of that message that he should upgrade to the very latest version where this issue has been fixed.

    Well, I guess that really supports my impression that the timeout of the nightly build is definitly necessary or people may keep on using potiential buggy versions forever just they are lazy to upgrade :)

Tree View Flat View (newer first) Flat View (older first)

Attachments

No attachments created.