7 Aug
2024
7 Aug
'24
10:04 a.m.
On 8/7/24 10:52, IEM Network Operation Center (IOhannes m zmölnig) wrote:
With the dump and other utilities from your database manager. Almost everything is in the database. There are some things in Mailman's var/ directory, but those can simply be moved.
sorry for keeping you all busy, but: which "things in Mailman's var/" need to be copied over to the new host?
in my old instance (from Debian packages) i find in /var/lib/mailman3/:
- ./archives: dirtree without files
- ./cache: (afaict) currently active templates for mailinglist mails (hashed filenames) - i assume that these can safely be ignored and will be restored from the db?
- ./data: empty
- ./lists: empty directories named after each list (i think these are used by the MTA to determine whether it should hand over a mail to the mm3-ltmp)
- ./locks: plenty of lock-files, most of them rather stale (as in: 3 years old)
- ./messages: a couple of old messages (i think all of them have been held for approval)
- ./queue: dirtree without files
- ./templates: more templates for the existing mailinglists, though they don't seem to be used (are these the fallbacks when I remove a template via the webinterface?)
- ./web/static/*: seem to be copied over from various Debian packages (dependencies of mm3), with minor differences in icons and jquery (I assume these files get copied over when the mm3 instance is created, and do not get updated when the corresponding Debian packages get updated)
- ./web/static/CACHE - can these be ignored?
- ./web/fulltext_index: are these files regenerated when running "update_index"?
so i think the only stuff that needs to get recreated from mailman's var is the ./lists directory. is this correct?
mgfdasr IOhannes
Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt.
Content-Type: application/pgp-keys Name: OpenPGP_0xB65019C47F7A36F8.asc