[Mailman-Users] What does rmlist remove?
Dear all, what files are being removed by rmlist (without -a). I suppose, /var/lib/mailman/lists/$LISTNAME/config.pck and the entries in /var/lib/mailman/data/virtual-mailman When I restore both, have I restored the list? Mailman2 uses no database, so maybe the answer is yes? Background: testing migration to mailman3, and I want to start with a partial migration, affecting only one little used virtualhost. I thought that deleting the lists this virtualhost from mailman2 will allow me to play around with them in mailman3 (after making the required changes to the postfix configuration). But if I find that mailman3 has too many drawbacks, I would prefer to undo the changes. Alternatively, instead of calling rmlist I could just manually remove the lists from virtual-mailman of mailman2, although, virtual-mailman get automatically rewritten with each list creation or deletion, but that's rather infrequent over here) Cheers, Johannes -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Upgrading to mailman3 maybe?
So looking at upgrading to mailman 3 but had some questions. Background: we use mailman as email distribution lists, not really for back and forth communication, so having said that… * Does mailman3 have a way to automatically prune archives, i.e. delete old archived messaged that are X days/years old automatically? * Also in looking in the documentation states “Some configuration and settings aren’t available in Mailman 3’s UI yet,” is there a list of what is not available? * What OS have distro packages for Mailman 3 ready to go? * Anything else I am not thinking of? -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: [ext] Upgrading to mailman3 maybe?
* Bader, Robert (Bob) : > So looking at upgrading to mailman 3 but had some questions. > Background: we use mailman as email distribution lists, not really for back > and forth communication, so having said that… > > > * Does mailman3 have a way to automatically prune archives, i.e. delete > old archived messaged that are X days/years old automatically? mailman2 does that? I know the prune_arch script, yes, but automatically? > * What OS have distro packages for Mailman 3 ready to go? I think it's installable via pip Ralf Hildebrandt Charité - Universitätsmedizin Berlin Geschäftsbereich IT | Abteilung Netzwerk Campus Benjamin Franklin (CBF) Haus I | 1. OG | Raum 105 Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 ralf.hildebra...@charite.de https://www.charite.de -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: [ext] Upgrading to mailman3 maybe?
Right, mailman 2 does not automatically prune archives, and I have used the prune script before, just curious if this was not a feature… But I am also just checking to see what the advantages/disadvantages there are for going to mailman 3 over 2. Sure 2 is no longer being developed, BUT having said that our 2 environment is solid, and I understand it. I am a mailman admin, but not a full time Linux system admin, so Hyper kitty, Django, Virtualenv and all the other components of mailman 3 are not my forte. I have been playing around with just trying to stand up a mailman 3 in an isolated VM and not having much luck, and in searching around I am thinking mailman 3 is defiantly more of a commitment to get it installed/working at this time. -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: What does rmlist remove?
On 3/23/2021 4:18 AM, Johannes Rohr wrote: what files are being removed by rmlist (without -a). I suppose, /var/lib/mailman/lists/$LISTNAME/config.pck and the entries in /var/lib/mailman/data/virtual-mailman When I restore both, have I restored the list? Mailman2 uses no database, so maybe the answer is yes? glancing at the code (in the ./bin directory), rmlist removes contents of the /lists/ directory held messages stale locks any MTA-specific aliases (e.g. aliases or virtual-mailman) archives the config.pck file -is- the "database" for each list. Read up on how the virtualization stuff works, too. z! -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] What does rmlist remove?
Carl's message arrived just as I was about to post this, looks accurate. If you want more detail, here it is. Johannes Rohr writes: > what files are being removed by rmlist (without -a). I suppose, > /var/lib/mailman/lists/$LISTNAME/config.pck and the entries in > /var/lib/mailman/data/virtual-mailman This depends on your MTA. The generic Mailman files removed are: 1. Any (stale) lockfiles for that list. 2. Any held messages for that list (you want to decide about these before deleting the list!) 3. The list configuration directory and all files in it. This may include a backup of the config.pck, pending.pck, and request.pck as well. You probably don't need any of those, though, except for config.pck. It appears your MTA is Postfix. In that case, it attempts to modify (NOT remove) the "aliases" and "virtual-mailman" files in Mailman's DATA_DIR, then asks the MTA to merge them to the system aliases file. I haven't analyzed carefully but although it takes some care, it does not seem to be bullet-proof against hand-edited files. If it's not Postfix, there are no MTA-specific files removed in stock Mailman: you have to edit the MTA config files that "hook up" the appropriate aliases to Mailman. > When I restore both, have I restored the list? Not quite. You need to regenerate the alias maps in Postfix. There may be a better way (Mark will know) but the function _update_maps in Mailman/MTA/Postfix.py can be used (as root or the owner of Postfix files) # cd /path/to/mailman/Mailman/MTA # python >>> import Postfix >>> Postfix._update_maps() >>> quit() > Background: testing migration to mailman3, and I want to start with a > partial migration, affecting only one little used virtualhost. I thought > that deleting the lists this virtualhost from mailman2 will allow me to > play around with them in mailman3 (after making the required changes to > the postfix configuration). But if I find that mailman3 has too many > drawbacks, I would prefer to undo the changes. > > Alternatively, instead of calling rmlist I could just manually remove > the lists from virtual-mailman of mailman2, although, virtual-mailman > get automatically rewritten with each list creation or deletion, but > that's rather infrequent over here) This is all you need to do. However, you must be extremely careful not to disturb the stanza markers for other lists, because that will cause problems for removal (including removing or corrupting aliases for lists that aren't being removed) and possibly creation. Also, note that AFAIK there's no standard way to revert archives from HyperKitty to your Mailman 2 format. I believe HyperKitty can export mbox files, which means that pipermail can import them, but I'm not sure how that works, or whether that will preserve archive URLs. Steve -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: [ext] Upgrading to mailman3 maybe?
Bader, Robert (Bob) writes: > But I am also just checking to see what the > advantages/disadvantages there are for going to mailman 3 over 2. > Sure 2 is no longer being developed, Neither is Python 2, which is far more worrying given that Mailman is an Internet-facing application. Among other things, I'm pretty sure the TLS protocols are not being updated. YMMV on that, but I advise you to check and think about your plans for the future. You wouldn't want to wake up one day and find that something doesn't work because Python 2 doesn't support a recent enough version of TLS or something. I'm not an expert on this, I'm just suggesting 15 minutes of paranoid Googling may save you an unpleasant surprise. > * Also in looking in the documentation states “Some configuration > and settings aren’t available in Mailman 3’s UI yet,” is there > a list of what is not available? No, and it's a rapidly moving target anyway. Whatever list we give you now will (a) be invalid next week, and (b) not include some of the deficiencies in an early 2020 Mailman 3 that have since been implemented. Current releases have most of the settings people use as far as I know, especially in core. Postorius is a little behind, and HyperKitty is a completely different application from pipermail so I doubt a comparison would be meaningful. > * What OS have distro packages for Mailman 3 ready to go? None, really. Debian and Fedora both have packages, but they are quite far behind the current release. They may be servicable for your purpose, but that's not something I can advise on without more information about your requirements and the version of Mailman that's in the distro-of-choice package. Steve -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Fwd: Bounce action notification
On 3/22/21 10:11 PM, Vako Nicolian wrote: > I forwarded only one of the bounces, check the list on this link: > https://www.dropbox.com/s/auuylwltwjpvqxo/MM2.jpg?dl=0 Which says nothing except there are lots of bounces. > The attachment mentions the following and it's different for each > bounce. Mainly *Lost connection while receiving the initial server > greeting*. This is an issue between the sending MTA and the recipient MTAs. It almost certainly has nothing to do with Mailman. Mailman has delivered the message to the outgoing MTA and it or some downstream MTA is encountering this issue when attempting to deliver to the recipients. You need to talk to whoever is responsible for that MTA. If that is you, you need to get help from whoever supports that MTA software. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Fwd: Bounce action notification
Vako Nicolian writes: > I forwarded only one of the bounces, check the list on this link: I'm a volunteer with limited time. I analyze what you summarize. > Mainly *Lost connection while receiving the initial server > greeting*. I have zero interest in those. Nothing Mailman can do can affect that. It's a mailchannels problem, not a problem with the mail being sent or the sender. Unless that message means something completely inconsistent with the normal, RFC 5321 usage of "initial server greeting", it means that the only thing that the remote host knows is the IP of relay.mailchannels.net. It hasn't even seen HELO yet, so even SPF doesn't apply. My first guess is that mailchannels got itself on a commonly-used RBL, or they screwed up their DNS. > I have never encountered such bounces with my regular email, that's > why I was pointing to MM, but I maybe wrong. That's reasonable first-cut analysis, but I assure you, unless mailchannels is completely confused about "initial server greeting," Mailman has absolutely nothing to do with it. Steve -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: [ext] Upgrading to mailman3 maybe?
On 3/23/21 8:45 AM, Bader, Robert (Bob) wrote: > Right, mailman 2 does not automatically prune archives, and I have used the > prune script before, just curious if this was not a feature… There is nothing currently planned or implemented, but a script to remove archived messages for --list older than --date shouldn't be too difficult to implement. The tricky part is what to do about threads containing messages both older and newer than the cutoff. My MM 2.1 prune_arch script ignores this issue, but it makes sense to consider it for HyperKitty. Perhaps an option to a) delete the entire thread, b) keep the entire thread or c) delete the older messages from the thread would be in order, although maybe the a) option isn't needed. > But I am also just checking to see what the advantages/disadvantages there > are for going to mailman 3 over 2. ... Answered in Steve's reply. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
