[Mailman-Developers] Re: Migrating mailman 2 to mailman 3.1

[Mark Sapiro]

On 8/13/19 7:27 PM, sandeep kumar wrote:
> Hi Team


This message was addressed to mailman-developers@python.org and
mail...@mailman3.org. Perhaps you meant mailman-us...@mailman3.org
rather than mail...@mailman3.org.


> Now that we are ready to go into production. We are currently running mailman 
> 2 in our production. Now the biggest challenge is we have to migrate around 
> 3000 lists from mailman 2 to mailman 3. Is there any documentation or any 
> inputs from the team would be appreciated and will be very helpful. Iam 
> trying to access docs.mailman3.org but it is not opening don't why.?


docs.mailman3.org doesn't work. Use docs.list.org. Where did you find a
reference to docs.mailman3.org? We should fix that.


The basic tools are the 'mailman import21' command for importing lists
and the 'django-admin hyperkitty_import' command for importing archives.

See

and
.

The usual caveats about unescaped 'From ' lines in mbox files apply. The
Mailman 2.1 bin/cleanarch command can help with this.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3

Security Policy: https://wiki.list.org/x/QIA9

[Mailman-Developers] Migrating mailman 2 to mailman 3.1

[sandeep kumar]

Hi Team

I have successfully completed implementation of mailman with some 
customizations (like sending sms to moderators for pending lists, 
Authenticating into mailman 3 using existing LDAP,and some minor changes)

Now that we are ready to go into production. We are currently running mailman 2 
in our production. Now the biggest challenge is we have to migrate around 3000 
lists from mailman 2 to mailman 3. Is there any documentation or any inputs 
from the team would be appreciated and will be very helpful. Iam trying to 
access docs.mailman3.org but it is not opening don't why.?

This group helped me a lot in bringing my mailman 3 upto this stage. The 
process of migration would complete my project. Requesting your valuable inputs 

Regards
Sandeep

Sent from my iPhone
___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3

Security Policy: https://wiki.list.org/x/QIA9

[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

[Stephen J. Turnbull]

Aaryan Bhagat writes:

 > I am sorry but I do not understand your concern. I just mentioned
 > the cases where we actually have to make changes to the database
 > after each processing of `BounceEvents`. I do not expect `Mailman`
 > to show any undesirable behaviour here.

You wrote some posts that indicated you were specifically worried
about the timing of the warning mails.  When the conversation
continued without much explanation of your concerns, I assumed that
you were still thinking about the concurrency issues that arise in an
asynchronous system such as email.

___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3

Security Policy: https://wiki.list.org/x/QIA9

[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

[Stephen J. Turnbull]

Aaryan Bhagat writes:
 > Stephen writes:

 > >Also, you need to think about what happens if the warning fails
 > >for some address.  Probably you just treat that as equivalent to a
 > >bounce in most cases, but what happens if it's a "no such
 > >address"?  Is that already handled?
 > 
 > For the problem, you mentioned regarding `no such address`, it was
 > something which occurred to me earlier but I had not pondered upon
 > it so much. Let me clearly explain the problem.

[snipped]

 > What other implementation for this type of behaviour can be
 > implemented?  Some pointers are required on this.

If we receive a bounce that indicates that the address does not exist,
we should stop sending warnings there.  Somebody has screwed up pretty
badly, and it wasn't us.

In most cases, this deletion will be valid and intended by the user
(or well-deserved for abusing the account).  In those cases, the
address should be unsubscribed.  Questions:

1.  Do we unsubscribe on the theory that it's almost always correct to
do so, or do we keep it around and just disable without further
warnings in case of resurrection and to associate mail "From" that
address with the user?  (This has issues in case the address is
resurrected but assigned to a different person.)

2.  If the user has other addresses, should Mailman warn them about
this situation?  (This question also applies to ordinary disabled
warnings that bounce.)

3.  If the user wants to migrate the subscription to a working
address, can we make this simpler?  (Not in scope of your GSoC,
mentioned because I thought of it and want it in public.)

4.  Should the address be deleted?  It's possible that the user will
use this address in From.  Technically this is probably invalid
(the user doesn't have the right to use that address at all if
they can't receive mail there).  But I don't see a good reason not
to associate such mail with their Mailman user.

5.  Should the user be allowed to post "From" that address?  Probably
not.

Steve

-- 
Associate Professor  Division of Policy and Planning Science
http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information
Email: turnb...@sk.tsukuba.ac.jp   University of Tsukuba
Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN
___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3

Security Policy: https://wiki.list.org/x/QIA9