Currently, we basically don't allow requesting monthly export of hyperkitty due to abuse. One researcher needs the data and I think we can exempt them temporarily. This is done for bookkeeping.
Description
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| lists: Allow excempting ip ranges for export | operations/puppet | production | +4 -1 |
Event Timeline
The apache config that's blocking all requests is:
# Disable export endpoint (T282957)
<LocationMatch "^/hyperkitty/list/.*/export/.*">
Require all denied
</LocationMatch>BTW this exists now, we should deploy it? https://gitlab.com/mailman/hyperkitty/-/merge_requests/389/diffs
Change #1118511 had a related patch set uploaded (by Ladsgroup; author: Amir Sarabadani):
[operations/puppet@production] lists: Allow excempting ip ranges for export
Change #1118511 merged by Ladsgroup:
[operations/puppet@production] lists: Allow excempting ip ranges for export
I came across that merged Hyperkitty MR myself yesterday ('Add support for disabling archives export on a Site level.', which added the new setting HYPERKITTY_MBOX_EXPORT), & I was about to file a task asking basically the same thing :)
The only reason I didn't is actually because I'm not sure how it might work with the IP exemption code/config that got added for this task.