Jens Günther writes:
Am 09.12.23 um 00:27 schrieb Mark Sapiro:
You need a PUT command, not POST. Try the above with
-X PUT
.With the
-X PUT
-command, there is the following error: {"title": "400 Bad Request", "description": "Unexpected parameters: bounces_address, created_at, digest_last_sent_at, fqdn_listname, http_etag, join_address, last_post_at, leave_address, list_name, mail_host, next_digest_number, no_reply_address, owner_address, post_id, posting_address, request_address, usenet_watermark, volume"}
You should post the exact command or interactive conversation you're using.
My guess is that the REST API is expecting a single JSON object, and you sent it multiple parameters.
Have you played with the REST API interactively? The documentation at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/r... is really quite good as a tutorial. It's not a full API reference, and not organized that way, although the table of contents is very useful for what it does mention. But I think what you need (if you want to explore it that deeply) is a tutorial to get a "feel" for how the REST API "likes to talk".
Is there another way to preserve these information about the members?
You can query the REST API (you might need to fetch the subscriber roster, then iterate over that to get the details), or you can dump the database table (or the whole database) using SQL-based utilities like psql (Postgres, I forget the MySQL equivalent).
(in general I don't think a lot of people put in effort to customize there memeberships ... and furthermore they would need to register, right?)
Not sure what you mean by "register", but every address that writes to Mailman gets a temporary user until a "real" user claims it via the mailbox ownership dance. If they receive mail in a mailbox, they've done the ownership dance for that mailbox. If you don't preserve that record, they'll have to do it again.
Steve