On 02/12/2016 09:37 AM, Shea Alterio wrote: > I used to run a (entirely plain text) Mailman 2 list, but I'm now setting up > Mailman 3, built last month by the mailman-bundler package. > > Most things are working great! There are a couple problems I'm trying to work > around, though.
We are working on setting up mailman3-users at mailman3.org (running on MM 3 of course), but there are still infrastructure issues to work out before that list will be operational. In the mean time the best list for Mailman 3 and particularly HyperKitty, Postorius and MailmanBundler issues is [email protected] or you can try the #mailman IRC channel on freenode. > 1. I can't seem to find a way to send multipart emails. I have a script which > generates a multipart email. It only has a plain text and a text/HTML > segment. No matter how I have tried to send it into Mailman, the message that > gets posted to the list is the raw multipart email as I sent it in. How do I > get mailman to realize it's a multipart email and should be formatted as such? It seems you are saying that you send a multipart/alternative message with text/plain and text/html alternative parts to the list and you receive back from the list a text/plain message whose content is the raw message body that you sent. Are you sure your script is generating the multipart/alternative mail correctly? What happens if you sen such a message from your MUA as opposed to your script? Is the problem with all such mail or just mail generated by your script? > 2. I confirmed with the help of others that Mailman 3's behavior is the > password you provide in making the django superuser is the password you can > use to accept emails to be moderated by email. This always fails. You always > get "Results: Confirmation token did not match" and "Unprocessed: Approved: > <key>". However, Postorius still works for approving messages. > Source: > https://github.com/terencehonles/mailman/blob/master/src/mailman/rules/approved.py Assuming MM 3.0, the code is <https://gitlab.com/mailman/mailman/blob/release-3.0/src/mailman/rules/approved.py>. In any case, that code is verifying the list's moderator_password which is not the Django super password. In fact, this is the core engine which knows nothing about Django or Postorius. Now if you are talking about approving held mail via the Postorius Web UI, that's a different issue, and I *think* the Django superuser PW should work, but it has nothing to do with pre-approval via an Approved: <password> header which is the only thing mailman/rules/approved.py is doing. Other's, Particularly on mailman-developers or IRC will have more insight on this. > Lastly, it's already reported as a bug, but you can't open the Held Messages > in Postorius unless you comment out the 443rd line in _client.py. Now it's > working for us just fine. OK. -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
