Sorry for the late reply, Mark.
I just checked it.
mailman lists shows maillist2@example.com as a component of the output.
Also, localhost:8001/3.0/lists/maillist2@example.com/ shows full JSON
details about mailllist2@example.com.
{
"display_name": "Maillist2",
"fqdn_listname": "maillist2@example.com",
"list_id": "maillist2.example.com",
"list_name": "maillist2",
"mail_host": "example.com",
"member_count": 3,
"volume": 1,
"description": "NA",
"self_link": "http://localhost:8001/3.0/lists/maillist2.example.com",
"http_etag": "\"d4966cd892c82a3dbbe663fe41e321ff166a4c5b\""
}
But the hyperkitty send button is still showing the KeyError named 'file'. Its traceback being the one I sent before.
On Sat, Mar 9, 2019 at 10:03 AM Mark Sapiro mark@msapiro.net wrote:
On 3/8/19 8:18 PM, NAYAN KHANNA wrote:
Is the HyperKitty list you are trying to post to known to Mailman core? I didn't quite understand this? List known to Mailman core as in? Please elaborate a bit.
Known to mailman core as in appears in the output of 'mailman lists'.
I ask because it appears the error you posted was due to HyperKitty getting the url 'http://localhost:8001/3.0/lists/LIST-NAME' and getting a 404 response which should only happen if the REST api doesn't know a list named LIST-NAME.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan