Hi all,
Thank you for your responses, Stephen. Much appreciated. I have forwarded them
to my friend. I don’t know if he is on this list, but I have recommended that
he be, so we can get over whatever hump is getting in the way.
I used the instructions on the Mailman 3 site on my own attempt.
At Mon, 25 Nov 2019 13:47:16 -0500 Jim Popovitch wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Mon, 2019-11-25 at 11:06 -0500, Jim Popovitch via Mailman-Users
> wrote:
> > On Mon, 2019-11-25 at 16:59 +0100, Johannes Rohr wrote:
> > > Am Mo., 25. Nov. 2019 um 16:47 Uhr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-11-25 at 11:06 -0500, Jim Popovitch via Mailman-Users
wrote:
> On Mon, 2019-11-25 at 16:59 +0100, Johannes Rohr wrote:
> > Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via Mailman-Users
> > :
> > > On Mon, 2019-11-25 at
On 11/25/19 7:17 AM, Matthew Pounsett wrote:
> On Mon, 25 Nov 2019 at 05:04, Johannes Rohr wrote:
>
>> The obvious big showstopper is that there is no supported upgrade path
>> from Mailman 2.* yet, according to
>>
>>
On Mon, 2019-11-25 at 16:59 +0100, Johannes Rohr wrote:
>
> Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via Mailman-Users
> :
> > On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote:
> > > Is there a timeline for that? Mailman 2.x requires python 2.x, which is
> > > EOL in
Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via Mailman-Users <
mailman-users@python.org>:
> On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote:
> > Is there a timeline for that? Mailman 2.x requires python 2.x, which is
> > EOL in about 40 days.
>
> I keep saying this a
On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote:
> Is there a timeline for that? Mailman 2.x requires python 2.x, which is
> EOL in about 40 days.
I keep saying this a lot... the EOL you are referring to is Python's
declared date that the Python team will no longer maintain Python2.
On Mon, 25 Nov 2019 at 05:04, Johannes Rohr wrote:
> The obvious big showstopper is that there is no supported upgrade path
> from Mailman 2.* yet, according to
>
> http://www.mailman3.org/en/latest/pre-installation-guide.html#how-can-i-upgrade-from-mailman-2-1-x
> and so you certainly don't
Am 25.11.19 um 07:15 schrieb Stephen J. Turnbull:
[...]
> The obvious "turn-key" installation is to use the Docker containers,
> which Abhilash keeps fairly up-to-date. But see comment below about
> universal working solutions.
[...]
Great suggestion. Is it easy to integrate it with the
Reply-To set to mailman-us...@mailman3.org.
Allan Hansen writes:
> I need to upgrade from Mailman 2.1 - my hardware needs upgrading
> (badly) and the address mangling is having my subscribers rip their
> hair out.
That's not going to go away. We have ARC support in Mailman 3, but
(a) like
Dear all happy campers,
I need to upgrade from Mailman 2.1 - my hardware needs upgrading (badly) and
the address mangling is having my subscribers rip their hair out. I need to get
this done before they start on my already thinning hair!
I’m ready and eager to move on to MM3 on a Linux box.
11 matches
Mail list logo