[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [tdf-discuss] Re: Communication in Mailinglist
[Thread Prev] | [Thread Next]
- Subject: Re: [tdf-discuss] Re: Communication in Mailinglist
- From: Kevin Vermeer <reemrevnivek@gmail.com>
- Date: Tue, 23 Nov 2010 13:25:40 -0500
- To: discuss@documentfoundation.org
On Tue, Nov 23, 2010 at 12:58 PM, Christian Lohmaier <
lohmaier+ooofuture@googlemail.com <lohmaier%2Booofuture@googlemail.com>>wrote:
> Hi Larry, *,
>
> On Tue, Nov 23, 2010 at 6:53 PM, Larry Gusaas <larry.gusaas@gmail.com>
> wrote:
> > [...]
> > Gmail very capable for mailing lists.
>
> Except for the very one drawback you just demonstrated:
> When changing the subject, gmail will break the thread (start a new
> one) as it will remove the references from the reply.
>
This only happens on this list, because every subject is prepended with
[tdf-discuss] and some replies get Re: inserted after it while others
insert the Re: before the [tdf-discuss] token, leading to four kinds of
subjects like:
1. [tdf-discuss] Communication in Mailinglist
2. Re: [tdf-discuss] Communication in Mailinglist
3. [tdf-discuss] Re: Communication in Mailinglist
4. Re: [tdf-discuss] Re: Communication in Mailinglist
Having these four different styles instead of just two is what causes
conversations to break. gmail (and possibly others) use the first and second
styles, and don't recognize that the third is a reply to the first,
generating the fourth. What clients generate the third?
One solution to the problem is to agree on using either the second or third
style, and punish anyone who uses the banned version. This will be
difficult, as most people don't realize where the Re: goes in their own
replies, and some mail clients will default to the other version. The
better solution in my mind is to remove the [tdf-discuss] part of the
subject. I know it's the [tdf-discuss] mailing list because of the address
"discuss@documentfoundation.org" and the signature, and this information
doesn't have to be duplicated in the subject line. Most modern mail
clients include some filter functionality to help differentiate between
mailing lists - browsing a list of subjects and expecting anyone who
communicates with you to label themselves with a token in brackets is rather
old-fashioned. Also, having that token in every subject is redundant when
browsing properly filtered emails.
--
Kevin Vermeer
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived for eternity ***
| [tdf-discuss] Re: Communication in Mailinglist | Larry Gusaas <larry.gusaas@gmail.com> |
| [tdf-discuss] Request: Installation Instructions | "Craig A. Eddy" <tyche@cox.net> |
| Re: [tdf-discuss] Request: Installation Instructions | Friedrich Strohmaier <damokles4-listen@bits-fritz.de> |
| Re: [tdf-discuss] Request: Installation Instructions | Michael Wheatland <michael@wheatland.com.au> |
| [tdf-discuss] Communication in Mailinglist (was:Re: Request: Installation Instructions) | Friedrich Strohmaier <damokles4-listen@bits-fritz.de> |
| [tdf-discuss] Re: Communication in Mailinglist | Larry Gusaas <larry.gusaas@gmail.com> |
| Re: [tdf-discuss] Re: Communication in Mailinglist | Christian Lohmaier <lohmaier+ooofuture@googlemail.com> |
- Prev by Date: Re: [tdf-discuss] Re: Communication in Mailinglist
- Next by Date: Re: [tdf-discuss] Re: Communication in Mailinglist
- Previous by thread: [tdf-discuss] Re: Communication in Mailinglist
- Next by thread: [tdf-discuss] Re: Communication in Mailinglist
- Index(es):
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the GNU Lesser General Public License (LGPLv3). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.