[OT] Subject needs to have [gnucash-user]

[whwtan]

Hi Amm,

Welcome to the list. :)

You can easily do this within your own email program to sort out any 
mail from the gnucash.org domain.
There are even those programs which allow you to add those [gnucash] tag 
in front of your subject line too.
You could even create a new mail address to subscribe to specific 
mailing lists.

I am on a number of mailing lists and the ones who add the [mailing list 
name] in front of the subject actually frustrate me more since it takes 
up the precious space for a subject which I use myself for things such 
as [QUESTION] [SOLVED] [MAINT] etc.

So what I really want to convey is that one man's poison is another 
man's wine.
It is actually easier for you to filter gnucash lists' mail using 
incoming mail address filter than for a person like myself to use a 
tokenizer to remove the tag.

If there was ever a vote on whether we should add a tag into the 
subject, I would vote against it. I like it just the way it is.

William

On 5/4/2013 11:32 AM, Amm wrote:
> Hi,
>
> I am new to this list as well as Gnucash. I like the program and its intuitiveness.
>
> I would like to suggest that the subject field of e-mails sent by list should have identification tag [gnucash-user].
>
> This is a standard practice observed by most mailing lists and it helps easily identify mailing list emails. It easily helps filter out e-mails to "Mailing list" folder.  And even if one does not use filters one can easily identify a mailing list e-mail because of presence of square brackets.
>
> Currently due to absence of this tag, it becomes difficult to differentiate between personal e-mails and mailing list emails. (Because they all look same)
>
> So please implement this tagging of subject.
>
> Regards,
>
> Amm.
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>
>