[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171205141831.GA26963@openwall.com>
Date: Tue, 5 Dec 2017 15:18:31 +0100
From: Solar Designer <solar@...nwall.com>
To: musl@...ts.openwall.com
Subject: Re: Why[,] ezmlm?
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
>
> Apparently, newer ezmlm-idx includes a workaround for DMARC, but it's
> not something I'd be happy to deploy. I am unaware of a workaround that
> wouldn't have major drawbacks. I guess eventually we'll have to bite
> the bullet, but I'd rather postpone that.
>
> 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.
Alexander
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.
