From: Geert Stappers <stappers@stappers.nl>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Why (above why not)
Date: Thu, 10 Jan 2019 18:54:26 +0000 [thread overview]
Message-ID: <20190110185426.trs7jdinafy2u5ga@gpm.stappers.nl> (raw)
On Thu, Jan 10, 2019 at 11:28:48AM -0500, Fabian Aldo Santiago wrote:
> On 2019-01-09 08:47, Zhang Huangbin wrote:
> > > On Jan 9, 2019, at 9:40 PM, Mayuresh <mayuresh@acm.org> wrote:
> > >
> > > I am about to give mlmmj a try to set up a mailing list.
> >
> > Last commit was 19 months ago, you name it. :(
> > I???d like to pay developers for some new feature.
> >
>
> it's a shame. i see the utility of it but it felt lacking in some features
> so i switched it out for mailman 2.x in my mail server implementation.
>
> Zhang, in iredmail, why not use MM instead? or rather, how/why did you
> choose mlmmj?
My reason for choosing mlmmj is that it integrates fine with postfix
and has simple configuration files.
It also provides a working replacement for .forward configs.
Groeten
Geert Stappers
Some what uncomfortable upon seeing the "defend your choice" request
--
Leven en laten leven
reply other threads:[~2019-01-10 18:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190110185426.trs7jdinafy2u5ga@gpm.stappers.nl \
--to=stappers@stappers.nl \
--cc=mlmmj@mlmmj.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 read-only IMAP folder(s) and NNTP newsgroup(s).