Mail archive

Re: [alpine-devel] Improving Alpine Linux's email stack

From: Natanael Copa <>
Date: Wed, 3 Apr 2019 12:07:54 +0200


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
>, 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.
> 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

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:
> 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.

Received: from (unknown [])
        by (Postfix) with ESMTP id F2C9AF85513
        for <>; Thu, 4 Apr 2019 09:13:23 +0000 (UTC)
Received: from SZUJBOEJJES4JTM ([]) by localhost via TCP with ESMTPA; Thu, 04 Apr 2019 17:13:00 +0800
MIME-Version: 1.0
From: vssan <>
Sender: vssan <>
Reply-To: vssan <>
Date: 4 Apr 2019 17:13:00 +0800
Subject: =?utf-8?B?JW5ld3MlLSVuZXdzJSQ+LiJcJl8kICAtLS0tLQ==?=
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

Received on Wed Apr 03 2019 - 12:07:54 UTC