Administrator
|
I just realized that post & reply via email
using nabble seems to have stopped working. (If anybody can confirm .. Let's see if this email passes through, 2nd attempt.) I consider Mailman <https://www.list.org/features.html> for a replacement, since the email list workflow is important me. One task would be to extract all forum posts as emails, to be spooled into Mailman. I just did another backup. Since April 2019, Nabble seems to be Open Source <http://support.nabble.com/Nabble-is-now-open-source-td7603082.html>. Even though a LICENSE file is missing here <https://bitbucket.org/frschmidt/nabble/src/default/> it should enable one to extract the posts with the given Nabble backup file (PG SQL). Suggestions and other ideas welcome. Volunteers are even more welcome of course. ~Sven |
Administrator
|
Looks like Nabble has fixed the email issue, good.
So the move to Mailman can wait a little :) Regardless, if anybody likes to build the data extraction tool 'Nabble Backup -> email', we could move to a normal mailinglist and keep Nabble as a backup. ~Sven On 2/11/20 3:55 PM, Sven Gothel [via jogamp] wrote: > I just realized that post & reply via email > using nabble seems to have stopped working. > > (If anybody can confirm .. > Let's see if this email passes through, 2nd attempt.) > > I consider Mailman <https://www.list.org/features.html> > for a replacement, since the email list workflow > is important me. > > One task would be to extract all forum posts > as emails, to be spooled into Mailman. > I just did another backup. > > Since April 2019, Nabble > seems to be Open Source > <http://support.nabble.com/Nabble-is-now-open-source-td7603082.html>. > Even though a LICENSE file is missing > here <https://bitbucket.org/frschmidt/nabble/src/default/> > it should enable one to extract the posts > with the given Nabble backup file (PG SQL). > > Suggestions and other ideas welcome. > > Volunteers are even more welcome of course. > > ~Sven |
Administrator
|
Hello
Is it just a plain Postgresql SQL dump? https://www.postgresql.org/docs/12/backup-dump.html Which email format would you like to target? eml (mostly plain text) or mbox? Personally, I would restore the database with the SQL dump file and use JDBC (JPA is probably overkill here).
Julien Gouesse | Personal blog | Website
|
Administrator
|
On 2/13/20 12:47 PM, gouessej [via jogamp] wrote:
> Hello > > Is it just a plain Postgresql SQL dump? > https://www.postgresql.org/docs/12/backup-dump.html yes, you (as an admin) can get the backup zip and it looks like PQ SQL dump .. hmm. +++ sven@risa:/usr/local/projects/JogAmp/admin/forum-nabble$ unzip -l site_762907_1040770263.zip Archive: site_762907_1040770263.zip Length Date Time Name --------- ---------- ----- ---- 0 2020-02-11 03:26 pg_backup/ 46 2020-02-11 03:26 pg_backup/schemas.sql 0 2020-02-11 03:26 pg_backup/schemas/ 0 2020-02-11 03:26 pg_backup/schemas/s762907/ 368 2020-02-11 03:26 pg_backup/schemas/s762907/sequences.sql 3679 2020-02-11 03:26 pg_backup/schemas/s762907/tables.sql 0 2020-02-11 03:26 pg_backup/schemas/s762907/tables/ 348 2020-02-11 03:26 pg_backup/schemas/s762907/tables/configuration 21 2020-02-11 03:26 pg_backup/schemas/s762907/tables/file_site 53 2020-02-11 03:26 pg_backup/schemas/s762907/tables/module 609 2020-02-11 03:26 pg_backup/schemas/s762907/tables/registration 21 2020-02-11 03:26 pg_backup/schemas/s762907/tables/site_property 21 2020-02-11 03:26 pg_backup/schemas/s762907/tables/tweak 39 2020-02-11 03:26 pg_backup/schemas/s762907/tables/version 1867514 2020-02-11 03:26 pg_backup/schemas/s762907/tables/file_avatar 786319 2020-02-11 03:26 pg_backup/schemas/s762907/tables/file_temp 21 2020-02-11 03:26 pg_backup/schemas/s762907/tables/paid 129160962 2020-02-11 03:26 pg_backup/schemas/s762907/tables/file_node 21 2020-02-11 03:26 pg_backup/schemas/s762907/tables/mailing_list 595 2020-02-11 03:26 pg_backup/schemas/s762907/tables/node_property 21 2020-02-11 03:26 pg_backup/schemas/s762907/tables/user_property 81 2020-02-11 03:26 pg_backup/schemas/s762907/tables/site 32865 2020-02-11 03:26 pg_backup/schemas/s762907/tables/subscription 9374 2020-02-11 03:26 pg_backup/schemas/s762907/tables/tag 54867 2020-02-11 03:26 pg_backup/schemas/s762907/tables/view_count 516303 2020-02-11 03:26 pg_backup/schemas/s762907/tables/visited 42176453 2020-02-11 03:26 pg_backup/schemas/s762907/tables/node_msg 234026 2020-02-11 03:26 pg_backup/schemas/s762907/tables/user_ 4841209 2020-02-11 03:26 pg_backup/schemas/s762907/tables/node 0 2020-02-11 03:26 pg_backup/schemas/s762907/views.sql 1687 2020-02-11 03:26 pg_backup/schemas/s762907/indexes.sql 4094 2020-02-11 03:26 pg_backup/schemas/s762907/constraints.sql --------- ------- 179691617 32 files +++ 'file_node' looks like a binary blob to me. > > Which email format would you like to target? eml (mostly plain text) or mbox? Anything email, best eml (plain text) can be handled easily. Either inject manually to a sendmail or dovecot-tool or otherwise. If we would get this task slowly rolling, I would analyze this in more detail for the actual product we would use (Mailman, ..). > > Personally, I would restore the database with the SQL dump file and use JDBC > (JPA is probably overkill here). If possible, sure. I glanced at the Nabble source code, which has some Export class/tool build in. Sure, this task sadly would take some time :-/ But gladly it is somewhat possible, reason we always moved it to the future :) ~Sven |
Free forum by Nabble | Edit this page |