There are extensive schema changes which require an update script to convert 1.x mailboxes to 2.x.

Comments

mfb’s picture

Subscribe

mfb’s picture

Status: Active » Needs review
StatusFileSize
new3.32 KB

I started working on an update script. Haven't had a chance to test this yet.

danepowell’s picture

I'll try to test it soon. It looks like this only handles the upgrade of strictly Mailhandler components - however, there's a LOT of other work that needs to go into setting up Mailhandler 2.x. I think an upgrade script should also set up the appropriate feed, appropriate Mailhandler Node Processor mappings, create the feed node, etc... as this setup process is going to be a real shock to people used to Mailhandler 1.x. If these steps can't be automated, then the script should at least provide some direction for how to do the rest of the setup manually.

Ian Ward’s picture

Priority: Normal » Major

Bump up to major

danepowell’s picture

Status: Needs review » Needs work

This will need to be updated to work with the latest dev version

danepowell’s picture

StatusFileSize
new1.7 KB

Here's a partial update- this should take care of creating the new mailboxes. However, we also need to...

  1. Create a new input format corresponding to each existing mailbox with the appropriate signature separator in place
  2. Create a new feed importer corresponding to each existing mailbox with the appropriate settings for commands and input format
  3. Possibly provide additional guidance for upgrading users

Can anyone think of anything else that needs to be addressed in the update script?

danepowell’s picture

Status: Needs work » Fixed

This has been committed, try 6.x-2.0-alpha2

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.