> There is no ’solved’ function of the mailing list. It’s not like a > forum or ticketing system, it’s just group e-mail. > > The best practice if you find a solution you want to specify or > document is to simply post it as a reply to the original > thread. (rather than starting a new one)
For those unaware, he's referring to some common pitfalls that even I made in the beginning of mailing list usage: - Changing the "Subject" header field. Don't put "Solved" or anything. In maximum, you can put "Re:", "Fw:" and "(was: ...)", and for this last one, use it in the end. If you do want to change the subject only to start a completely different topic, do so using something like this: "Sub-topic B (was: Let's talk about A)". Some email clients or webmails do some nasty stuff with the message headers and with parts of the "Subject" field, such as nationalizing "Re:", "Fw:" and "(was: ...)", this makes other clients confused. - Using "Compose new" or simple "Reply". Please use "Reply to list/group" instead. You can also use "Reply to all" but in this case the original poster will get duplicate emails unless you remove his address from the "To" field. "Reply" is for private replies to the original poster (in this case it's a good idea to change the "Subject" so that the person knows it's a private branch of the discussion). The other reply buttons are "wide replies". All in all, using reply buttons is better than "Compose new" because, if you take the time to use your email client or webmail to inspect the raw messages you receive, you will see interesting information such as "Message-ID", "In-Reply-To", and "References", all of these tell us about the hierarchy of the messages and their parent ones, when you do "Compose new", this information is lost unless you can force the email client or webmail to allow you to insert/add raw header fields to the message, in this case you will have to add the missing information manually. If I'm not mistaken, even if you happen to *not have* the original message that caome from this mailing list, you can go to the list's archive and once the message is found, you can do this: 1. The email address of the person who wrote the message is actually a "mailto" URL, copy it and take the part between "In-Reply-To=" and the next "&" (if any future "&" exists), or the part between "In-Reply-To=" and the end (if no more "&" exists). 2. You have now a percent/URL-encoded "In-Reply-To" field value. Like this: %3CCADYgSbmaLUFqw8D%2BjqWqJTTVxc7TCYaQsks3VGA65W%3DbtJEoWA%40mail.gmail.com%3E "%3C", "%40" and "%3E" are "<", "@" and ">", respectively. Be aware that you will have to watch out and decode other two letters which appear after each percent sigh ("%"). All of this assumes that you are *not* using unofficial mailing-list-to-forum forwarders such as Nabble. -- - https://libreplanet.org/wiki/User:Adfeno - Palestrante e consultor sobre /software/ livre (não confundir com gratis). - "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar instantaneamente comigo no endereço abaixo. - Contato: https://libreplanet.org/wiki/User:Adfeno#vCard - Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft Office, MP3, MP4, WMA, WMV. - Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF (apenas sem DRM), PNG, TXT, WEBM. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.