sandeep kumar writes:
> 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
There's a small amount, but we're not sati
On Wed, Aug 14, 2019, at 10:08 AM, Stephen J. Turnbull wrote:
> sandeep kumar writes:
>
> > 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
Stephen writes:
>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
Stephen writes:
>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.
That is the main hurdle, bounce extraction cannot determine the exact cause so
we cannot ever say with surety t
On Wed, Aug 14, 2019, at 10:28 AM, Abhilash Raj wrote:
>
>
> On Wed, Aug 14, 2019, at 10:08 AM, Stephen J. Turnbull wrote:
> > sandeep kumar writes:
> >
> > > Now that we are ready to go into production. We are currently
> > > running mailman 2 in our production. Now the biggest challenge i
