Moving MM2 to a new server (revisited).
I saw several recent msgs about moving MM2 from one server to another, but I need some more specific advice for my situation:
Old server (Ubuntu 10.04 LTS, 64-bit)
apache: version 2.2.14 (2.2.14-5ubuntu8.15) postfix: version 2.7.0 (2.7.0-1ubuntu0.2) mailman: version 2.1.13 (1:2.1.13-1ubuntu0.2)
MM2/Postfix stopped sending messages back in April. I was clueless until after I shutdown postfix a couple of days ago and have done nothing to the old server's files. I'm almost positive there is undelivered mail there.
New server (Debian 7, 64bit)
openssl: version 1.0.2d
I am successfully running Apache 2.4.16 with several virtual hosts.
I am going to install the latest Postfix (from src). I will install the latest MM2 (from src).
Plan
Get a working MM2 with one or more new lists associated with one or more virtual hosts (with no new names conflicting with names from the dormant lists).
Follow previous threads on transferring old lists to the new, working MM2.
Question:
Is is necessary to restart Apache2, Postfix, and MM2 on the old server in order to recover the undelivered mail, or can I somehow magically copy files to the new server before that effort. Note I haven't yet looked at the logs on the old server.
Thanks.
Best regards,
-Tom
On 08/14/2015 05:38 AM, Tom Browder wrote:
No. You shouldn't need to start the web server, mail server or Mailman on the old server.
What you do need to do depends on where this undelivered mail is. There are 4 possibilities - queued in Postfix to be delivered to Mailman, in Mailman's qfiles/in queue waiting to be processed by Mailman, in some combination of Mailman's qfiles/out and qfiles/retry queues waiting to be delivered to Postfix or queued in Postfix for delivery to list members.
As far as Mailman's queues are concerned, you should be able to just move the qfiles/*/*.pck files to the new server AFTER moving the lists/*/config.pck files.
As far as Postfix is concerned, it should be possible to move those queue entries too, but it's probably easier to start Postfix on the old server and let it deliver outbound mail if any and queue inbound mail if any in Mailman's qfiles/in before you move it.
There may also be Mailman held messages. For these, you need to move the data/heldmsg* files to the new server and either move the lists/*/request.pck files or use a script like <https://www.msapiro.net/scripts/hold_again> to reprocess the data/heldmsg* files.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 08/14/2015 05:38 AM, Tom Browder wrote:
No. You shouldn't need to start the web server, mail server or Mailman on the old server.
What you do need to do depends on where this undelivered mail is. There are 4 possibilities - queued in Postfix to be delivered to Mailman, in Mailman's qfiles/in queue waiting to be processed by Mailman, in some combination of Mailman's qfiles/out and qfiles/retry queues waiting to be delivered to Postfix or queued in Postfix for delivery to list members.
As far as Mailman's queues are concerned, you should be able to just move the qfiles/*/*.pck files to the new server AFTER moving the lists/*/config.pck files.
As far as Postfix is concerned, it should be possible to move those queue entries too, but it's probably easier to start Postfix on the old server and let it deliver outbound mail if any and queue inbound mail if any in Mailman's qfiles/in before you move it.
There may also be Mailman held messages. For these, you need to move the data/heldmsg* files to the new server and either move the lists/*/request.pck files or use a script like <https://www.msapiro.net/scripts/hold_again> to reprocess the data/heldmsg* files.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Tom Browder