One of the teams working on the migration project with me did not do the
DNS switchover. It wasn't a mailman problem -- it was a PEBCAK :)
On Fri, May 31, 2019 at 4:49 PM Dave Stevens wrote:
> On Fri, 31 May 2019 14:34:19 -0400
> Ryan McClung wrote:
>
> > I figured it out.
>
Close this. I figured it out.
On Fri, May 31, 2019 at 1:47 PM Ryan McClung wrote:
> Greetings,
>
> Migrated mailman to another server and updated it.
>
> Site Admin can see the pending queue on all lists but the lists
> owners/administrators cannot.
>
> Running C
nothing.
Any help appreciated.
--
Ryan McClung
Systems Administrator @ Afilias Canada
A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8
<https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8=gmail=g>
W. www.afilias.info
T. +1.416.646.3304
sers
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives:
> http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe:
> https://mail.python.org/mailman/options/mailman-users/rmcclung%40afilias.info
>
--
Ryan M
The mailman 3.0 install is on the same box as 3.2. Is there a quick and
dirty way to flip over?
--
Ryan McClung
Systems Administrator @ Afilias Canada
A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8
<https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8=gmail=g
Hey All,
Looking to migrate 2.1.15 to 3.2. Right now we have a lot of lists and
pretty big archives. Is there a best practices for the migration or can
anyone offer scripts that have worked for them?
Info:
1 -- Mailman 2 server
1 -- Mailman 3 server
Both are on the same network.
Hey All,
I haven't read anything on gitlab about whether or not this has been
finalized. Is there a migration process available?
I also read about scripting it but unfortunately I can't find any resources
on a way to do so. Can anyone provide me with a best-practices on how to
migrate?
Ryan
