X-Original-To: alpine-infra@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id CECB6F84DA9 for ; Wed, 3 Apr 2019 10:08:01 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 8A1369E1D06; Wed, 3 Apr 2019 10:08:01 +0000 (UTC) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id BC2ED9E03FF; Wed, 3 Apr 2019 10:08:00 +0000 (UTC) Date: Wed, 3 Apr 2019 12:07:54 +0200 From: Natanael Copa To: Drew DeVault Cc: alpine-infra@lists.alpinelinux.org Subject: Re: [alpine-devel] Improving Alpine Linux's email stack Message-ID: <20190403120754.5c46a3ec@ncopa-desktop.copa.dup.pw> In-Reply-To: <20190320040551.GA2283@homura.localdomain> References: <20190320040551.GA2283@homura.localdomain> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-alpine-linux-musl) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi! Sorry for late response. On Wed, 20 Mar 2019 00:05:51 -0400 Drew DeVault wrote: > There was some discussion about this on IRC last night, but I had an > event to attend so we decided to take it to the ML. Here's a summary of > the issue(s) and possible solutions. ... > Solutions: > > Many of you know that I have a conflict of interest, as I maintain > lists.sr.ht, an open source mailing list driver, archive, and hosted > service. Take the following with the requisite grain of salt, as it's > basically an ad. > > lists.sr.ht is free & open source software[0] (AGPL) and can be hosted > on Alpine infrastructure, The AGPL is not my favorite license due to it may scare off companies. > though you're welcome to use my hosted service > for experimentation and/or production uses. I have a mirror of the > aports list here[1], though threading is currently broken because of the > issues with mlmmj. Here's[2] a list where threading does work, if you > want to peruse the archives. What is the strategy for dealing with spam? If a spam message gets through, can it be deleted from the archive? (I believe some spam is to get higher search engine ranking). Can you send to the mailing list without being subscribed, and have those messages moderated? We currently moderate messages from non-subscribers. Does this require subscribers to have yet another user account/password? ... > Patches are given special treatment on the archive, with patchworks-like > highlighting, links to specific lines & files, and so on: > > https://lists.sr.ht/~sircmpwn/alpine-aports/%3C20190312025245.20168-1-sir%40cmpwn.com%3E > > A gerrit-like interface for doing patch review on the web or via email > is planned to be implemented within the next few months, at least in its > basic form - which should provide a nice alternative to patchworks. Can this be integrated with gitlab? > I I depend on Alpine Linux a lot and I'm eager to give back in any > way I can. This is very appreciated. I don't have any objection to replace the mailing list software, but I want the infra team to decide. -nc