From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: ezmlm mail headers
Date: Sat, 27 Apr 2019 01:05:36 +0000 [thread overview]
Message-ID: <emd00bd832-4b17-426f-9523-8c500514171f@elzian> (raw)
In-Reply-To: <1657751556324962@sas2-c434f6e124b6.qloud-c.yandex.net>
>there is a "problem" when ezmlm meets gmail:
There's much more than one problem ^^"
It's difficult for gmail and mailing-lists to coexist. People
using gmail regularly get unsubscribed because gmail fails to
answer probes several times in a row. It's a pain, and there's not
much I can do about it.
>the ezmlm mailing list manager used for this list seems
>(unlike other solutions like sympa and mailman) not to
>set a "List-Id" mail header field which the dumb gmail
>"filter" facilities seem to require to recognize postings to
>mailing lists as such.
But that one seems easy to fix. Thanks for the report.
Let's see if it behaves better from now on. (Please move
that discussion off-list if you want to reply.)
--
Laurent
prev parent reply other threads:[~2019-04-27 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 0:29 Jeff
2019-04-27 1:05 ` Laurent Bercot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=emd00bd832-4b17-426f-9523-8c500514171f@elzian \
--to=ska-supervision@skarnet.org \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).