Search results for "2021" - Mailman-users

Re: Strange messages after upgrading Mailman3

by Allan Hansen

Thank you, Mark, as always. We upgraded to the latest versions: Mailman Core Version GNU Mailman 3.3.7 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.2 (default, Feb 28, 2021, 17:03:44) [GCC 10.2.1 20210110] Also, I don't have any umbrella lists. Yours, Allan On 12/4/22, 20:33 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 12/4/22 20:09, Allan Hansen wrote: > Hi all, > > I have been getting a few of these messages after my Mailman 3 was upgraded: > > "The content of this message was lost. It was probably cross-posted to > multiple lists and previously handled on another list." > > The messages appear to come from list members and are distributed to the relevant lists, but with nothing of the original contents. > They have appeared on different lists with, apparently different senders (unless spoofed). > Other messages are going through the system unchanged. > > Anyone has any ideas? To what version did you upgrade? This is most likely https://gitlab.com/mailman/mailman/-/issues/955 which was fixed in Mailman core 3.3.6, but it could be https://gitlab.com/mailman/mailman/-/issues/1027 if the posts are to umbrella lists (lists with other lists as members). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/PTXMXLRL4XLU5O7VW6X347FMQ3DLLXIK/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org

2 years, 7 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Allan Hansen

They need to resubscribe to each list they want the new address to be used for. Subscriptions involves permissions from the moderators. It’s not a simple process, especially if you are on many lists. Yours, Allan Hansen hansen(a)rc.org > On Feb 12, 2021, at 8:47 , Andreas Barth <aba(a)ayous.org> wrote: > > * Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210212 12:04]: >> hansen(a)rc.org writes: >>> b. The ability of members to change their addresses for all lists >>> they are subscribed to. >> >> What exactly do you want here? I can think of a number of ways to >> implement that, depending on whether the old address is to be >> deactivated from the lists, unsubscribed from the lists, or deleted >> from the Mailman and/or Postorius Users. There may be other >> variables to consider, as well; I haven't thought about this. AFAICS >> this is not a trivial feature, and I'd really like to hear from people >> who want "something like" this about exactly what they want and their >> use cases. Or we'll release an insufficiently designed feature that >> causes somebody hundreds of problems.... > > I thought user could do that if they have an web account, and multiple > mail addresses are associated with the account? Or does my memory > serve me wrong there? > > > Andi > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 4 months

Re: Mailman 'requests' API call timeout when there are a number of pending members

by Abhilash Raj

On Thu, Jan 14, 2021, at 6:52 PM, Alan So wrote: > We are currently testing latest mailman suite and notice that the > requests API call will timeout if there are a number of pending > requests. > > Since the latest Postorious allow unchecking Pre confirm and Pre > approved during mass subscribe, our support staff tried to add large > number of email addresses to the list. We then found that we cannot > click into the list from the web UI to administer it and an error > message showing that "Mailman REST API not available. Please start > Mailman core." Further checked that the requests API call failed to > complete when we click the list on the web interface. > > Looks like the UI should not try to load all the pending members just > for the sake of showing the number of pending requests. Of course in > normal situations, there should not be that many pending requests. This issue has been partially mitigated by [1] making the list's index page better. Also, subscriptions pending confirmation from User don't affect the speed of the page showing subscriptions pending user confirmation. However, there is more to be done by adding support for pagination, which is reported here [2]. [1]: https://gitlab.com/mailman/postorius/-/merge_requests/559 [2]: https://gitlab.com/mailman/postorius/-/issues/420 > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 5 months

Re: Mailman import of 2000 lists

by Abhilash Raj

> On Oct 19, 2021, at 7:37 PM, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Bryan Loniewski writes: > >> We have noticed similar slowness when importing/creating/deleting >> lists. We have ~2600 lists and the bottleneck does seem to be the >> MTA alias code that reads from backend (sorts by domain and then >> list names?) and subsequently writes the (lmtp,vmap,etc) files. > > Is there a GitLab issue for this? If not, will somebody file one for > us? I'd do it but I don't really understand the issue and diagnosis > except for S-L-O-W, that part I get. I didn’t find any issue, so I created one https://gitlab.com/mailman/mailman/-/issues/953 My understanding of the issue is that Mailman tries to create the LMTP files whenever a new list is created and in their setup, the LMTP files are on a remote volume. So the latency to write to LMTP file is significant. And when 2600 of those happen, it takes a lot of time. I don’t think we can do anything about the MySQL latency though, since we have to create the lists. Although, these lists are separate rows in database, so it should be possible to do multiple imports in parallel by invoking the commands simultaneously. We should be able to fix this by adding a flag that skips creation of LMTP files after creation/import of a list. Once the imports are complete, a single run of "mailman aliases” command should generate everything. Hyperkitty has a similar mechanism to avoid indexing emails when bulk importing emails from mboxes. -- thanks, Abhilash Raj (maxking)

3 years, 8 months

Re: Dealing with hyperkitty spool files (was Re: Re: Fwd: [Django] ...)

by David Partain

> On Wed, 2021-03-03 at 08:29 -0800, Mark Sapiro wrote: > > 1. Am I correct in assuming that I can just use my favorite editor > > (vi) to remove the offending characters from the file? > No. The file is a Python pickle and you can't edit it. You would need > to get the message and the metadata from the pickle (you could at least > view it with the `mailman qfile` command), edit the message and then > re-pickle the message and metadata. And, in my impatience, I tried it before receiving your response and now I seem to have done silliness in my database :( New error in mailman-web.log: AttributeError: 'NoneType' object has no attribute 'subject' Sigh. Stupid me. If you have suggestions on fixing that... Right now, my plan is simply to remove the first message in the queue (since I assume it'll be the "broken" one) and it'll just not be in the archive. Life's hard. Even if I unpack 'em to edit, I'll find mail in, for example, in base64, and I'm not going to fix the mail by decoding, editing, re-encoding, ... Nope. > > 3. Can I do something to make hyperkitty go through the spool? > > > > I don't know what you mean. Sorry I wasn't clear. I simply meant, "Is there a way to start hyperkitty going through the spool manually?" It sounds like, though, that I don't need to do that if it's going to happen that often anyway. Cheers, David

4 years, 4 months

Re: Problem with redirection when entering alias without a / at the end

by Abhilash Raj

> On Mar 19, 2021, at 4:53 PM, Jens Günther <jens.guenther(a)posteo.de> wrote: > > Sure. It's not much, when I get it right, file was created by debian-package automatically (I only post the lines without #): > > ->/etc/mailman3/uwsgi.ini > > [uwsgi] > uwsgi-socket = /run/mailman3-web/uwsgi.sock > enable-threads = true > chdir = /usr/share/mailman3-web > wsgi-file = wsgi.py > master = true > process = 2 > threads = 2 > uid = www-data > gid = www-data > plugins = python3 > attach-daemon = python3 manage.py qcluster > logto = /var/log/mailman3/web/mailman-web.log I have no clue about where the “/mailman” is even coming from. It is possible that uwsgi isn’t aware that it is serving the website at a subpath (“/mailman3”) instead of “/“, so the redirects don’t correctly take in to account the subpath. I see that the subpath is taken into account when there is a forward slash in the end and weird things happening when it isn’t. Could be Apache not setting the “SCRIPT_NAME” var correctly always, but from the docs[2] it seems to me that your configuration is correct. Maybe you can try setting the SCRIPT_NAME explicitly using uWSGIForceScriptName to “mailman3" and see if that helps? [2]: https://uwsgi-docs.readthedocs.io/en/latest/Apache.html > > > Am 20.03.21 um 00:28 schrieb Abhilash Raj: >> Can you also share your uwsgi configuration? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

4 years, 3 months

Re: Hyperkitty download mbox

by Andrew Hodgson

Mark Sapiro wrote: >On 4/26/21 2:00 AM, Andrew Hodgson wrote: > >> Yep there is a problem with an imported mbox which seems to be present somewhere in the archive on all the lists which I imported using that method. Here is a recent trace from the download option: [...] >Thanks for the traceback. The issue appears to be with folded headers that should either be unfolded before storing in HyperKitty's database or upon retrieval for this process. This is probably because of outlook.com folding Message-ID: headers. See >https://gitlab.com/mailman/mailman/-/issues/844 for one manifestation of this. >I think if you replace the >``` > msg["Message-ID"] = "<%s>" % self.message_id ``` line at 178 in /opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py >with >``` > msg["Message-ID"] = "<%s>" % self.message_id.strip(' <>\r\n') ``` it will avoid this issue. I tried this but get the same error, hope I did the modification correctly. [2021-04-30 19:56:31 +0000] [22104] [ERROR] Error handling request Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 180, in handle_request for item in respiter: File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/views/mlist.py", line 335, in stream_mbox msg = email.as_message() File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py", line 178, in as_message msg["Message-ID"] = "<%s>" % self.message_id.strip(' <>\r\n') File "/usr/lib/python3.7/email/message.py", line 409, in __setitem__ self._headers.append(self.policy.header_store_parse(name, val)) File "/usr/lib/python3.7/email/policy.py", line 145, in header_store_parse raise ValueError("Header values may not contain linefeed " ValueError: Header values may not contain linefeed or carriage return characters Thanks. Andrew.

4 years, 2 months

Re: Non-ascii characters missing from Pipermail archive txt and gz downloads

by Mark Dale

Hi Ruth, Apologies for the late response. I posted my message to the MM3 list in error and have since reposted it to the MM2 list. However, thank you for taking the trouble to reply. The problem lies outside the choice of editor as both files are being viewed in the same editor -- with one correct and the other not. Mark Sapiro has explained (on the MM2 list) what is causing the problem. Armed with that information I just have to now find a way .... Regards, Mark -------- Original Message -------- From: Ruth Ivimey-Cook [mailto:ruth@ivimey.org] Sent: Friday, April 9, 2021, 15:24 UTC To: mark(a)postmark.io, Mailman users Subject: [MM3-users] Non-ascii characters missing from Pipermail archive txt and gz downloads > Hi Mark > > I'm not sure, but I think the problems are to do with the program you are using to view the txt file. > > A modern mail reader understands the Content-type: header and will adjust its character processing accordingly, but a .txt file has no default character encoding, so any text editor will have to "use its best judgement". Some will default to utf-8, because that is compatible with 7-bit ASCII (NOT Latin1) while others will just put characters out and hope for the best (esentially leaving the result to the encoding of the font). > > In theory, a UTF-encoded text file can begin with the "BOM" marker, a sequence of characters which is supposed to indicate which variety of Unicode is in use, but this is rarely present, especially for UTF-8. > > Try looking at your text file with a UTF-8 capable text editor **and ensure that you tell the editor to use the UTF-8 encoding**. I expect it will look ok then. > > > Hope this helps, > > Ruth > > > On 09/04/2021 13:52, Mark Dale via Mailman-users wrote: >> Mailman 2.1.34 >> Debian 10 >> Postfix >> >> Hi >> >> I'm hoping someone can shine a light on character encoding issue I've encountered. >> >> A plain-text email with non-ascii characters in the body gets posted to the list. >> >> As per Mark Sapiro's guide I've captured the incoming message to file. >> >> - https://www.mail-archive.com/mailman-users@python.org/msg73469.html >> >> The message is received by Mailman with the non-ascii characters displaying correctly. >> >> The header of that message has: >> >> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 >> Thunderbird/78.9.0 >> MIME-Version: 1.0 >> Content-Type: text/plain; charset=utf-8 >> Content-Language: en-AU >> Content-Transfer-Encoding: 8bit >> >> In the list's mbox file and archive webpage, the message displays the non-ascii characters correctly. >> >> In the archive's downloaded .txt (and also .gz) file, the non-ascii characters are missing and displayed as "?". >> >> I've copied the message text in below, from both the correct one from the email and the erroneous .txt file. Hopefully they won't get scrambled up when I send this. >> >> Any advice on getting the non-ascii characters written into the archive .txt file would be gratefully received. >> >> Thanks, >> Mark >> >> >> === Message text as okay in mbox and as shown on the archive webpage === >> >> If one goes by the definition of veḷippaṭai as given in the Tamil Lexicon that the meaning of an ambiguous word should be disambiguated by a qualifying word, then aruvi āmpal does not conform to that definition since in the case of aruvi āmpal in Patiṟṟuppattu 63, aruvi is really made up of aru+vi, a compound. Moreover, the expression aṭai aṭuppu aṟiyā is already there to clarify that āmpal is a number and not a flower. Thus, aruvi simply provides information in addition to aṭai aṭuppu aṟiyā that āmpal is not a flower. The modern commentator Aruḷampalavaṉār also does not call it veḷippaṭai. >> >> === >> >> === Message text with missing characters in te archive's txt and gz downloads == >> >> If one goes by the definition of ve?ippa?ai as given in the Tamil Lexicon that the meaning of an ambiguous word should be disambiguated by a qualifying word, then aruvi ?mpal does not conform to that definition since in the case of aruvi ?mpal in Pati??uppattu 63, aruvi is really made up of aru+vi, a compound. Moreover, the expression a?ai a?uppu a?iy? is already there to clarify that ?mpal is a number and not a flower. Thus, aruvi simply provides information in addition to a?ai a?uppu a?iy? that ?mpal is not a flower. The modern commentator Aru?ampalava??r also does not call it ve?ippa?ai. >> >> === >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 2 months

Re: The future is here?

by Stephen J. Turnbull

Jonathan M writes: > On 6 Jan 2021, at 04:25, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > > > But do be aware that you probably do have > > to make a choice between a quagmire of options and mandating a > > particular stack (or small set of them) for simplicity. > > > It would be good if Mailman could do what Discourse do here. Discourse is a different kettle of fish. They concentrate on the much more straightforward (from a network and interapp communication configuration standpoint) web service because that's what their users expect. Mail is a lot more baroque from that standpoint. We shouldn't hope to successfully "encourage" hosts to do things our way. Eg, I run Exim4 because that's what I've always done and because I'm familiar with its spam-filtering, performance-tuning, and security controls: I'm not going to switch to Postfix just because that's the most common configuration. Similar considerations apply to webserver and RDBMS (for other people; I'm comfortable with Apache and PostgreSQL). It's not just a matter of "tweaking the expert options". As far as I can see, the best we can do is what Abhilash has already done: provide a full turnkey system in a container or a Vagrant-style VM. But that has its issues, too. If somebody wants to prove me wrong, feel free. But my assessment is that there are much better uses of core developer time than chasing a one-size-fits-all configuration. A suite of scripts or better yet Ansible (etc) roles is a better fit for Mailman's audience, I think. Steve

4 years, 5 months

Re: changing the main template for subscriptions and more

by Mark Sapiro

On 2/1/22 12:40, Paul Paulchen wrote: > Hi Mark, > > thanks for your advice. Unfortunately we need some more clues. > First of all, we are using mailman docker by maxking - https://github.com/maxking/docker-mailman I do not know what the file layout is in the Docker container, so I can't verify paths. > Our version: > Mailman Core Version - GNU Mailman 3.3.5 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] > > We put an example footer.txt into the templates folder as you mentioned: > mailman3_core => var/templates/sites/de/list:member:regular:footer.txt > Mailman user can read them As I said, I can't give you an absolute path. If you can run `mailman info` in the container, that will show the location of mailman.cfg which may help Installing the template as you have should work if it's the correct path. > Created a new list, restarted the docker-container, but it always showed the default footer.txt and not our example footer.txt from the templates folder. Any guesses or clues? Where is this default footer.txt hiding anyway? Changing languages in postorius works fine and it alters between english, german etc... just won't use our custom footer.txt The default templates are in the mailman/templates/ directory where the mailman/ directory is where all the Mailman core software is. Hopefully someone familiar with Docker and the Mailman Docker container can provide better information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

Mailman-users search results for query "2021"