I think I'm done now, and everything is fine. Victory! :)
So what happened...
It became quite clear that the data-only dump I had, had it's
messageblocks already converted to bytea. Now what went wrong with
earlier restore attempts was that I was importing the data over to 2.0.9
schema where the column type is text.
Now, running the conversion script again doesn't help much, if bytea
data is imported to a text field it'll just break things and it wont work.
So I tried a different approach, created a new db with 2.2.1 schema, and
imported the data there. I was quite confident after I browsed thru some
messageblocks and I could see the all-familiar \n\n's there instead of
\012's :)
So 2.2.1 schema in, remove indexes and constraints, import data, restore
constraints and indexes, vacuum (to populate the indexes) and then
dbmail-util -by. First time I've seen the utility to go thru second time
without any errors.
Fire up the imapd, try mutt... and I have the headers and the bodies
showing up. *PHEW*.
16 hours of work, and all seems to be well. Undelivered mails are slowly
getting in from the backup MX.
Sleepy time :)
--
br,
Tommi
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
