Mailman Core: REST API: Member Subscription Invitation

Product: Mailman Core Version: 3.3.10
When I post an "invite" to the REST API:
http://localhost:8001/3.1/members
Params: list_id = list.domain.tld subscriber = some@email.address display_name = Some Name invitation = true
Should Mailman Core be attempting to send an "invitation" email to the "subscriber" address, or is this the job of the "client" calling the API?
I understand the API does return "token", and "token_owner" on success, which I assume the "token" would be used for a subsequent "verification" process.
I'm developing my own "frontend" for "subscribers", "moderators", "list admins", and "system admins" respectively. Sort of working through understanding what Core does and does not do itself.

Peter Knowles via Mailman-users writes:
When I post an "invite" to the REST API:
http://localhost:8001/3.1/members [,,,] Should Mailman Core be attempting to send an "invitation" email to the "subscriber" address, or is this the job of the "client" calling the API?
Mailman core will send the invitation email.
In general, there are three kinds of work done outside of Mailman core: UI presentation, user authentication and authorization, and managing archived messages. Everything else is done by Mailman core.
Steve

Stephen,
Thanks for the clarity :-)
Looks like this was an error on my end. Seems Postfix has a second "journalctl" unit that logs the delivery attempts, whereas I was polling "journalctl -u postfix.service" which gave me the impression message delivery was not being attempted, it turns out "journal -u system-postfix.slice" actually had the relevant data, then it also dawned on me I should have been also checking "mailq" which clearly showed there was an email delivery issue that was caused by the server itself.
Ugh a bug.
Anyways, all is good now. Moving onto the next challenge.

Peter Knowles via Mailman-users writes:
Ugh a bug.
No apologies necessary. systemd is a huge conceptual bug. I'm beginning to get the hang of it -- like ten years after adoption by Debian, my primary and supremely preferred[1] distro :-), but it is insanely overengineered, and the documenation really sucks for running a couple of hosts.
FWIW, on my Debian system, I use
journalctl -e --facility=mail|less
That might give you everything Postfix.
Hm. I should look into adding Mailman to --facility=mail.
Footnotes: [1] For no particular reason these days. Almost 30 years ago I had two bad experiences with Red Hat that surely wouldn't happen today, and Debian Just Worked[tm].
participants (2)
-
Peter Knowles
-
Stephen J. Turnbull