[teampractices] Email naming in Google Apps Mail

Max Binder mbinder at wikimedia.org
Mon Jun 15 18:16:24 UTC 2015


The full description shows when composing an email, but not when receiving
one (which is arguably more important, since most emails are read, but not
all replied to). In my case, I'm not using digest mode and the issue
remains.

My understanding is that mailman is not aggressive enough to control the
naming, but the list definitely affects the naming, as the names are
identical to the descriptions. If mailman can't be wrangled to avoid the
description as a name, I would suggest a happy medium of description and
underscores. :)

On Mon, Jun 15, 2015 at 11:09 AM, Gergo Tisza <gtisza at wikimedia.org> wrote:

> On Mon, Jun 15, 2015 at 9:43 AM, Arthur Richards <arichards at wikimedia.org>
> wrote:
>
>> I have no idea why this also gets used as the sender's name, but
>> presumably it's something that mailman (our mailing list software) is
>> doing. This would be a good question to ask about on wikitech-l or of the
>> WMF ops staff (eg in #wikimedia-operations on freenode) since they maintain
>> our lists infrastructure.
>>
>
> Normally, it does not.  (It is used in the Reply-To: field, but From: is
> the person who wrote the mail, and that's the one Gmail displays.) I
> suspect Max is using digest mode. (With Gmail there is no reason to do that
> IMO, it is great at grouping related conversations.)
>
> The only places where the list name shows up clipped in Gmail is the To:
> field, and that reflects whatever the post author's mail client put there,
> which is in Gmail's case the name of the contact. Renaming the list
> probably would not change it.
>
> _______________________________________________
> teampractices mailing list
> teampractices at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/teampractices
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.wikimedia.org/pipermail/teampractices/attachments/20150615/7c98000c/attachment-0001.html>


More information about the teampractices mailing list