YAM - Yet Another Mailer (#2) - Saved messages (#58) - Message List

Saved messages
 solved

When I save a message using the "Raw format" or "Displayed txt" options, it is saved with a filename like this:

Re__Official_printer_patch.msg

Here the basename of the file is taken from the comment field of the message.

When I save the same message using the "plain text" option, it is saved with a filename like this:

Mvi7CwAIwBQ=.001,RS-1

Here the filename is the name used by YAM to store that message.

I would like to know if this difference is due to an explicit choice, or if it depends randomly on the evolution of YAM code.

Anyway, I would like less cryptic filenames in all cases. E.g. filenames like these:

Re__Official_printer_patch.raw.msg
Re__Official_printer_patch.dsp.msg
Re__Official_printer_patch.pln.msg

Cheers, Dr.Morbius_FP

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

    I would like to know if this difference is due to an explicit choice, or if it depends randomly on the evolution of YAM code.

    Anyway, I would like less cryptic filenames in all cases. E.g. filenames like these:

    Re__Official_printer_patch.raw.msg
    Re__Official_printer_patch.dsp.msg
    Re__Official_printer_patch.pln.msg
    

    That's a good question indeed. I guess the naming is really because of the evolving YAM code. So if you can come up with a good way how the naming should be done then I would be pleased to include that in one of the next versions.

    However, the scheme you were suggesting above seems to be a bit uncommon to me. Perhaps you have some more ideas/suggestion we might discuss here.

  • Message #266

    That's a good question indeed. I guess the naming is really because of the evolving YAM code. So if you can come up with a good way how the naming should be done then I would be pleased to include that in one of the next versions.

    However, the scheme you were suggesting above seems to be a bit uncommon to me. Perhaps you have some more ideas/suggestion we might discuss here.

    That scheme is only justified by the fact that, if I save a number of messages for subsequent processing, I would like to know at first sight if one of them is a message body or contains the headers, too. However, I admit that this could have null relevance for others.

    On the other hand I know many users that are rather upset by the new cryptic filenames and their false extensions (just to mention a VIP: Elena Novaretti). So, the minimal requirement that can satisfy all people is the following: "always use a filename created using the subject of the message as basename, and always add the .msg extension".

    A more advanced scheme could be achieved by adding the following extensions to the common basename:

    .msg       when the file is saved in raw format (headers+body);
    .txt       when only the message body is saved and contains plain text;
    .htm       when only the message body is saved and contains HTML text.
    

    Cheers, Dr.Morbius_FP

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

Attachments

No attachments created.