Closed Bug 758416 Opened 12 years ago Closed 12 years ago

Discussion Forum: mozilla.hispano.general

Categories

(mozilla.org Graveyard :: Server Operations, task)

All
Other
task
Not set
trivial

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: Nukeador, Assigned: mburns)

Details

(Whiteboard: [nov-24/25])

List Name: mozilla.hispano-general
List Admin: nukeador@mozilla-hispano.org, willyaranda

Short Description:


Long Description:


Justification / Special Instructions:
Ops, I press enter too soon ;)
Summary: Discussion Forum: mozilla.hispano-general → Discussion Forum: mozilla.hispano.general
So we want to migrate our general community mailing list to mozilla infrastructure, the main problem is that we don't know if it's possible to migrate archives from the old one:

https://groups.google.com/group/comunidad-mozilla
I have no problem with this; over to server-ops so they can give an opinion on archive migration.

Nukeador: if there's no possibility of migrating the archives, do you still want to move?

Gerv
Assignee: gerv → server-ops
Component: Discussion Forums → Server Operations
QA Contact: justdave → phong
(In reply to Gervase Markham [:gerv] from comment #3)
> I have no problem with this; over to server-ops so they can give an opinion
> on archive migration.
> 
> Nukeador: if there's no possibility of migrating the archives, do you still
> want to move?
> 
> Gerv

We should, but I'm going to consult the rest of the core contributors.
Assignee: server-ops → dgherman
Also we want to know if the google group link is working for new mailing lists, since it seems that it stopped working months ago and it's key for us.
Google started to re-create new lists, so this is possible to do now.
As for migration, if you have the messages saved in Thunderbird, we can ingest them in mailman and Google will pick them up.
So migrating the messages from Thunderbird is the only way... Eml or mbox format?

I'll be away till end of August but maybe Willyaranda or stripTM can chime in if they have time.
Unfortunately yes, if you need those messages, we have to get them from a Thunderbird profile.
If they're sorted into a folder in Thunderbird, there'll be two files in the profile for it, one with just the name of the folder and one with an .msf suffix. We want a copy of the extensionless one.
Ok, I will try to do that. Anyway, if there is new messages in the "comunidad-mozilla" mailing list in the transition, there won't be inyected, right? Or is there something that I'm missing?

Thanks!
Correct, those that are not in your Thunderbird folder won't be moved.
Severity: normal → trivial
Whiteboard: [pending action]
Anything we can help with this bug?
Or can we close?
Thanks!
cross-assigning this to me. ETA: this week.
I've checked this, and I don't have all messages in my inbox. Just from the thread:

[Comunidad-Mozilla] [MozCampChile] Notas de la reunión de hoy

that dates back to 09-October-2009, but we started the group on late 2007.

And I can't find older messages in my inboxes. Do you know if there is any way to download the archive from Google Groups?
Doing a global search looking for To: comunidad-mozilla@googlegroups.com, the first one I have is from 31/5/2007. 

I've selected all messages and use the "Save as" feature. I'm going to let Thunderbird save all emls (maybe more than 15k) to a local folder and see what happens.

Can we move these emls to a format you can import?
@nukeador: don't you have a label for the comunidad-mozilla mail? I think if you sync that in your thunderbird profile, it's easier to export (just copy the file, as :dumitru said.
@nukeador: I think you have the first message, since google groups archive starts from that day (31-5-2007), with the title "Configuración de este grupo", by Ricardo.
Currently I have 15739 emls (176 MB) on a folder, but reading previous comments it seems that it would be easier if I have just these emails on a Thunderbird profile folder.

I'm going to copy them to a local thunderbird folder.
@dumitru I have the mbox file, it's 179 MB, do you need it now to test it and then we can import new messages, or it's better to wait and do it once we do the real migration?
@dimitru How should we proceed?
I apologize for the lack of response.
I am currently working on other projects, but :mburns can take this and help you further.
Assignee: dgherman → mburns
QA Contact: phong → jdow
Hi,

mburns, any need on next steps?
Flags: needinfo?(mburns)
no more action on your part needed. I'll be importing these messages and they should show up shortly.
Flags: needinfo?(mburns)
(In reply to Michael Burns [:mburns] from comment #23)
> no more action on your part needed. I'll be importing these messages and
> they should show up shortly.

Keep in mind this is a super high traffic list, even one day can make a difference in terms of new messages. Can we integrate new messages since Comment 19 or should we generate a new file with all messages again?

In any case, we have to coordinate for a date to put the old list on maintenance mode, move the messages and move the subscriptions.
I see. We can schedule that time at your convenience. Maybe a saturday when traffic is less?


When we choose a date for maintenance, we will need to create 1 more email dump of all the messages posted from #comment19 until start of maintenance. This can be multiple exports, if need be (everything from #comment19 until today, and then another one taken at the beginning of maintenance, for instance.

Let me know when is best to schedule for this work and we can move forward.
Whiteboard: [pending action] → [pending maintenance scheduling]
mburns, is it possible to do the migration next weekend?

The plan would be:
* On Saturday (24/11) we close the list and send you the remaining emails.
* Emails are imported in the new mozilla.hispano.general list.
* On Sunday (25/11) we export and import users.

Does it work for you?
Flags: needinfo?(mburns)
mburns, is it possible to do the migration next weekend?

The plan would be:
* On Saturday (24/11) we close the list and send you the remaining emails.
* Emails are imported in the new mozilla.hispano.general list.
* On Sunday (25/11) we export and import users.

Does it work for you?
Ruben, that can work for me.

The message import is simple, but will take an unknown amount of time, given the volume of messages. The user migration should be quick, <30 minutes.
Flags: needinfo?(mburns)
Whiteboard: [pending maintenance scheduling] → [nov-24/25]
Great, Willyaranda will help to coordinate this effort.
Hi,

As scheduled, we are about to close the old google groups list in a few minutes and we'll export and link the remaining messages here.

In the meantime maybe the hispano-general list could be created to also export/import subscribers.

Note: I think we haven't commented yet, but we want a full mailing list (list+news group+ggroups archive) and should be public.
Great, 

Messages part 1: comment 19
Messages part 2: comment 31

mburns, ping us when we can configure and import subscribers.

List admins should be:

nukeador at mozilla-hispano.org
willyaranda at mozilla-hispano.org
striptm at mozilla-hispano.org

Thanks!
Flags: needinfo?(mburns)
comment 19: #15735 messages imported.

comment 31: #02439 messages imported.
Flags: needinfo?(mburns)
The list was created and configured. Subscribers were imported.

The messages are still bouncing:

Delivery to the following recipient failed permanently:

     hispano-general@lists.mozilla.org

Technical details of permanent failure: 
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.1.1 <hispano-general@lists.mozilla.org>: Recipient address rejected: User unknown in local recipient table (state 13).
Any news?
Flags: needinfo?(mburns)
Can you try to send an email again and see if this works?
Dont work. ->

Delivery to the following recipient failed permanently:

     hispano-general@lists.mozilla.org

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.1.1 <hispano-general@lists.mozilla.org>: Recipient address rejected: User unknown in local recipient table (state 13).

----- Original message -----

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=6INx3NZwB0R66U5mhxBW2nB3P2C9H0gNSfyw+JYzpkg=;
        b=VjoQDaRMGZwBmdYPM0xj4uwEBdZpr9TWa9uix8XQO8jtKAlp+K1soa5HorAvx7y57c
         ylWC4jdtlUnSoWSLqCu5axShRSolCrx10uzbGpfa9iQjRvJp1wJT7zh31w4c5PU16dBr
         8neCmPIGnfmVp3ZerQH68dMpkMRBTUYF+q/seygf7fKy1Zf7SOfwistlkqxLBRO1btBB
         uz0mMW8/iX0nylu89E2TtAI5XE8M4kZbbZ2gXJrNY4akPes1i1/Yn4EHdRjktkri5M+z
         Ne+vXWpojdSOJ2WKVhI5/fHIHb8r1dhsK0hxMmPuAIxmGZdHM38TV0jRzWuzQieZ0+/Q
         EcUw==
Received: by 10.68.229.194 with SMTP id ss2mr39860700pbc.17.1353950480214;
 Mon, 26 Nov 2012 09:21:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.66.189.234 with HTTP; Mon, 26 Nov 2012 09:20:59 -0800 (PST)
From: stripTM <striptm@gmail.com>
Date: Mon, 26 Nov 2012 18:20:59 +0100
Message-ID: <CAK9puJsZW8ecozXDraN2Pc_uE1kREgUEJ_JLrHW0cQe5VCL+gg@mail.gmail.com>
Subject: Test de nueva cuenta 26/11/2012 18:20
To: hispano-general@lists.mozilla.org
Content-Type: text/plain; charset=ISO-8859-1


Hoy estamos a 26/11/2012 18:20
This problem was tracked down alongside bug 815259. Postfix became broken somehow due to corrupt hash tables that it generates. Removing and rebuilding them for all of lists.mozilla.org allowed the spice to flow.

Test emails to the list have shown up in the Moderation que. Looks good to me. :)
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(mburns)
Resolution: --- → FIXED
Awesome, thanks.
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.