On 1/1/21 12:37 AM, Andreas Barth wrote:
- Mark Sapiro (mark@msapiro.net) [201231 19:28]:
On 12/31/20 2:49 AM, Andreas Barth wrote:
Looking in the source code, there is a ./cron/crontab.in.in however references to scripts in port_me/ directory.
That's all old Mailman 2.1 stuff. ignore it.
Can we replace that by a mailman3 cron tab? (I'm happy to write that as merge request if useful, but I assume that should be done rather by opening a bug report and using gitlabs features and not inline per mail)
Yes, the ideal workflow is to open an issue on GitLab and then open a merge request to fix it.
However, I don't think we need a sample crontab as we have <https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs> which should be enough.
I think the real solution is to just remove the mailman/cron directory and at least some of the mailman/port_me/ files. The cron/crontab.in.in file is just a distraction.
For the port_me files, we have:
checkdbs.py - this function is handled by mailman notify
disabled.py - handled by core's bounce processing
show_config.py - handled by mailman conf
and these for which no MM 3 equivalent exists and which could be helpful
in implementing a corresponding mailman subcommand:
config_list.py export.py find_member.py
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan