[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKpSnpLJM1viXBgV7Qo9N7Jo7snjRd+k-jznACbBKcDvs+ALdg@mail.gmail.com>
Date: Tue, 5 Dec 2017 06:43:19 -0800
From: Jorge Almeida <jjalmeida@...il.com>
To: musl@...ts.openwall.com
Subject: Re: Why[,] ezmlm?
On Tue, Dec 5, 2017 at 6:18 AM, Solar Designer <solar@...nwall.com> wrote:
> On Tue, Dec 05, 2017 at 03:08:39PM +0100, Solar Designer wrote:
>> On Tue, Dec 05, 2017 at 12:17:31AM -0800, Jorge Almeida wrote:
>> > This is not the only list for which stuff like this happens. What do
>> > such lists have in common? ezmlm
>>
>>
>> The issue is not specific to ezmlm. All lists have to choose what they
>> support and what they break.
>
> I think the blame might be misplaced on ezmlm because other mailing list
> managers do not bother notifying recipients about delivery problems.
>
> For now, maybe we need to edit ezmlm's notification message to document
> the problem, such as - in the case of this specific list - by referring
> to this thread in list archives.
>
Thanks for the detailed explanation.
Jorge
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
