Mark,
I can reproduce the bug via CURL:
curl -u restadmin:restpass \
http://localhost:8001/3.1/domains \
--request POST \
-d mail_host=
Basically providing the "mail_host" param, but leaving it empty causes the
command to return successful, therefore creating an "empty" domain entry.
Ideally t
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
"
Oh, in that case. I've got things covered by my custom solution I'm working on
already.
The original request was to have instead of "postfix_domains" and
"postfix_lmtp" files be created as static files, that the entries could be
added to a database backend (MariaDB, PostgreSQL, etc) automatical
OS: Debian 12
Mailman Core: 3.3.10
Install Method: venv
When I apply the "count" and/or "page" param on:
/3.1/lists/name.sub.domain.tld/requests
This resulted in a "404 Not Found" error from the REST API.
If I remove the params, the API returns results.
>From what I read in the docs, paginatio
I'm confused...
___
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/ar
Steve,
I'm referring to Postfix specific records, not Mailman records which are not
the topic of conversation here.
Presently, Mailman creates two files under "/opt/mailman/mm/var/data"...
"postfix_lmtp" which is a "transport_maps" table
"postfix_domains" which is a "relay_domains" table
The i
== ENVIRONMENT ==
OS: Debian 12
Mailman Core: 3.11.2
Install Mode: venv
== QUESTION ==
I'd like to do a more advanced setup with regards to my MTA setup.
*** I have mastered the art of setting up Mailman 3 Core to use MariaDB vs
PostgreSQL ***
What I'm after is the ability to make use of MariaD
I'm starting to develop against the REST API and found what might be a bug in
the validation process.
Sending a POST request with an "empty" payload returns 201 (created):
http://localhost:8001/3.1/domains
Since "mail_host" should be required at minimum to create a domain, this seems
like ther
Mark,
Thanks!
___
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/arc
Mark,
Sorry, I should have provided more details about my environment.
Distro: Debian 12
Mailman Core: 3.3.10
Python: 3.11.2
Using your CURL example on my install, I too get the same error response.
Perhaps there's some logic error within my PHP code. Guess there might be some
additional debug
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 "j
Actually, thinking about it a bit further, I am changing my logic. Instead of
running a cron job for this, I'm just going to implement it into my frontend
code.
So, when I "create" a domain, I'll have it create a record in the database
equiv to what "postfix_domains" would have in it... In the
At least as a temporary workaround, I wrote a script which periodically syncs
the "postfix_domains" and "postfix_lmtp" entries with my database. Essentially
I let MM3 create the files, but have Postfix setup to use my database instead.
___
Mailman-users
13 matches
Mail list logo
