Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 1/3/23 00:31, Onyeibo Oku wrote: > > (1) Mailman refuses to resolve to a preferred subdomain. If the > server's domain is "website.tld", I'd like mailman's homepage to be > at "list.website.tld". Mailman insists that I add "website.tld" to > the ALLOWED HOSTS, whereas "lists.website.tld" is already there as an > ALLOWED HOST (same VPS/IP address nonetheless). The result is that > the homepage ends up at "https://website.tld/mailman3/lists" when the > desired url is "https://lists.website.tld/mailman3/lists". This is a > conflict because the main domain is intended for another service. How > do I approach this? This is all configured in your web server. It needs to proxy requests for lists.website.tld to gunicorn and depending on the web server, may need more. E.g. see https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for nginx. > (2) See the traceback below: > ERROR 2023-01-03 07:40:32,078 27926 django.request Internal Server > Error: /mailman3/lists/ Traceback (most recent call last): ... > "/opt/mailman/venv/lib64/python3.10/site-packages/django/db/models/query.py", > line 650, in get raise self.model.DoesNotExist( > django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist. > > It seems a migration is missing. How should I approach this? Set SITE_ID = 0 in your Django settings. Also see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: configuring postfix local recipient table

by Mark Sapiro

On 4/25/25 01:02, Alexander Inzinger-Zrock via Mailman-users wrote: >>>> 3.1 parameter for default lookup table type >>> 3.2 pointing to command ''postmap'' >>> Both entries must be present or Mailman will error out before creating >> the postfix_lmtp file. There should be a template (actually, you can >> probably use it "as is") in site-packages/mailman/mta/postfix.cfg (or >> maybe in config/postfix.cfg). >> This file can be located anywhere, but I recommend putting it where >> mailman.cfg is (usually /etc/mailman3), and pointing to it in the >> [mta] section of mailman.cfg with the full path. > > + this file seems to be missing in my setting > + also the postmap command seemed to be unavailable for the user ''mailman''. > + [X] placed file in same dir as mailman.cfg (/etc/mailman3/) > + [X] replaced old config and pointed to it in mailman.cfg with full path: > #+begin_src txt /etc/mailman3/mailman.cfg > #configuration: python:mailman.config.postfix > configuration: /etc/mailman3/postfix.cfg > #+end_src > command ''mailman conf'' will show the new configuration path for > [mta] but no results for search term 'postmap_command' nor 'transport_file_type'. What does `mailman info` show for config file:? What does `mailman conf -s mta` show for [mta] configuration: [mta] incoming: mailman.mta.postfix.LMTP What's in /etc/mailman3/postfix.cfg? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: looking for more detailed traceback for shunted message

by Mark Sapiro

On 4/27/23 1:23 PM, bob B via Mailman-users wrote: > Had a message get shunted in > /opt/mailman/core/var/queue/shunt/. *** but that is the location in the docker environment, which we are running. > > The mailman log shows: > > Apr 26 13:09:56 2023 (31) ACCEPT: 2e0e82a5-0924-1777-bed8-34862417fe7e@[Redacted] > Apr 26 13:09:56 2023 (35) Uncaught runner exception: 'ascii' codec can't encode characters in position 1198-1200: ordinal not in range(128) > Apr 26 13:09:56 2023 (35) Traceback (most recent call last): > Apr 26 13:09:56 2023 (35) SHUNTING: 1682514596.7976818+6067e5ddeb70e4aad97977071b5ed00c41999057 > Apr 26 13:10:14 2023 (31) ACCEPT: 367fa8b7-97ac-58b3-fb99-458dbb951f5d@[Redacted] > Apr 26 13:10:14 2023 (31) ACCEPT: 367fa8b7-97ac-58b3-fb99-458dbb951f5d@[Redacted] > Apr 26 13:10:16 2023 (35) Uncaught runner exception: 'ascii' codec can't encode characters in position 1198-1200: ordinal not in range(128) > Apr 26 13:10:16 2023 (35) Traceback (most recent call last): > Apr 26 13:10:16 2023 (35) SHUNTING: 1682514616.5346222+7292ba8b651bc1bd76a9098733a39090e092add2 > > > > Is there anyway to get more info, Is there a more detailed traceback somewhere? I have never seen anything like this. There should be a complete Traceback in between the `Traceback (most recent call last):` line and the `SHUNTING: ...` line. However, I'm pretty sure the issue is a defective email which has non-ascii bytes in an explicit or implicit ascii part. You can see the raw message by pointing `mailman qfile` at the shunted .pck file(s) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Timeouts

by Mark Sapiro

On 4/25/21 4:37 PM, tlhackque via Mailman-users wrote: > The described timeouts are something that hyperkitty ought to be able to > avoid. For apache, the timeout is idle time between blocks of output. > Hyperkitty can avoid this by generating the archive in segments (based > on size, or elapsed time), flushing its output buffer, generating a > multi-file archive, and/or using Transfer-Encoding: chunked (chunked > doesn't work for http/2). It ought to be able to break the work into > blocks of "n" messages & do something to generate output. Besides > avoiding timeouts, working in segments allows the GUI to display > meaningful progress (e.g. if you're loading with XMLHttpRequest, > "onprogress") It really oughtn't be up to the user to break up the > request. It is not the web server that times out. I'm not sure about uwsgi because I don't use it, but the timeouts I see are on servers that use gunicorn as the WSGI interface to Django and the timeout is in a gunicorn worker. This is controlled by the timeout setting in the gunicorn config. <https://docs.gunicorn.org/en/stable/settings.html#timeout> Note that even 300 seconds is not enough to download the entire <https://mail.python.org/archives/list/python-dev@python.org/> archive. It may be possible to get HyperKitty to chunk the output to avoid this, but it doesn't currently do that. Care to submit an MR? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Mark Sapiro

On 5/25/24 10:00 AM, schaefer(a)alphanet.ch wrote: > > How may I automatically (from the command line) replace the example.com which is displayed in the web interface and in the From: comment field of the e-mails (the address itself is OK) -- I only found documentation about changing through the GUI so far. Any pointer? The host name displayed in the web UI is based on the SITE_ID setting in Django's settings. This is a system configuration not associated with any lists. it references an entry in the django_sites table in the database. As far as the comment/display name in From: is concerned, what specific emails are you talking about? I don't know where `example.com` would come from unless you mean email from Django in which case look at your setting for ADMINS in your Django settings. > Also, I have a question: if I import my 2.1 config for each ml, will DKIM work-arounds work (e.g. replace This User <user@domain> by This User user@domain <the-mailing-list>) ? Will Mailman 2.1 it required some config changes and also I had to modify mailman using a Debian diversion, AFAIR. The `mailman import21` command will properly import the Mailman 2.1 from_is_list and Sender filters -> dmarc_* DMARC mitigation settings. If you have some customization in this area, that probably won't be handled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Getting Archives to work - new setup on Ubuntu 18.04 (with mailman3-full pkg)

by Mark Sapiro

On 1/2/19 4:20 PM, kelly.close(a)lrewater.com wrote: > Happy New Year! > > What isn't working yet are the archives, specifically the messages sent to lists showing up at .../mailman3/hyperkitty. I'm at a loss and I'm hoping maybe the folks on this list can help me bring it home. > > Messages are distributed to subscribers as they should be - subscribers can send from their emails or from the web site. People can subscribe, etc. It's all working great. Just no archives. Presumably the list is known to HyperKitty since you appear to be able to post from there. > I'm not sure what to try next or what info to provide here for help - can anyone suggest where I can look to see why archives aren't getting created, or let me know what information would be essential for me to post to get help on this? I'm using PostgreSQL for the database, Postfix for mail and Apache2 for the web server. The first place to look is Mailman's mailman.log. Are there errors there with tracebacks? Are there messages there like <timestamp> 2018 (9606) HyperKitty archived message <message-ID> to <archive_URL> Also is there an Archived-At: header in received posts? If either or both of those, what happens if you go to the URLs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Various patches for mm3 stable 3.3.1

by Mark Sapiro

On 9/30/20 6:57 AM, Ruth Ivimey-Cook wrote: > Folks, > > For my own purposes I have created some patches which apply to the > current mailman pip package. I'm only responding here to the issue of how to suggest patches. If you hope that they could be incorporated into the distribution, posting them to this list is not very effective. It is too easy for list posts to get lost, buried or forgotten. The best thing to do is to create an issue or issues at <https://gitlab.com/mailman/mailman/-/issues> (each issue should address only one thing). Then you can either attach the suggested patch to the issue or better, create a merge request with the patch to fix the issue. Ideally, the merge request would also contain relevant additions to unit tests. The first advantage is open issues do not get lost. They are always there in the tracker. The second is that all of the above is work that needs to be done in order to actually get the patch into the master branch, and the more of it you do, the less of it needs to be done by someone else who may not be as motivated as you are. Granted, this may seem like a burden for you. After all, you fixed your problem so why bother, but open source works best if we all contribute what we can to improve the product. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Welcome message issue

by Mark Sapiro

On 10/22/24 13:34, Mohsen Masoudfar wrote: > Good afternoon > I have an issue with welcome message. > > A list owner is requesting to update the welcome message for only one of their lists. They are requesting to change the default text and insert additional URLs pointing to sites related to their list. > I know there is a URI field that you may include a web page. But this doesn't work and gets ignored. If you are referring to the `uri` field in the template table this should work if the `name` is `list:user:notice:welcome` and the `context` is the list_id of the target list. > - is there a mailman cli option to update the default template for a single list? There is no specific cli option. A site admin can address this by creating a custom template at Mailman's var/templates/lists/LIST_ID/LC/list:user:notice:welcome.txt where LIST_ID is the desired lists ID and LC is the preferred language. The list owner can create a custom list:user:notice:welcome template via Postorius. > > I couldn't find it in WUI. Do you mean GUI? If so, since at least Postorius 1.2.0 there has been a `Templates` choice in the second level nav in the lists view. > I reviewed all parameters and variables of the list and couldn't find one that might be related to it. > > We are running an old version of Mailman 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: digests are created but not sent out

by Mark Sapiro

On 1/9/19 9:33 AM, "Jörg M. Schulz" wrote: > But, also in mailman log. > Uncaught runner exception: 'ascii' codec can't encode character '\xdf' in position 157: ordinal not in range(128) > Jan 09 12:24:06 2019 (17491) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 324, in _dispose > mime = mime_digest.finish() > File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 185, in finish > footer = MIMEText(footer_text.encode(self._charset), > so the footers may not contain special characters. > Will review this one. in the above, self._charset is the character set of the lists preferred_language. The footer can't contain characters not in the character set of the list's preferred_language. For English (en) this is us-ascii. For German (de) it is iso-8859-1. These are artifacts from Mailman 2.1 You can change this for English by putting [language.en] charset: utf-8 in your mailman.cfg. This works because us-ascii is a proper subset of utf-8. For other languages, a change like this might require recoding of templates and/or a message catalog, but since we don't currently ship any non-English templates or message catalogs, that is moot at the moment. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Unable to configure mailman . Please give any information

by Mark Sapiro

On 3/13/19 11:47 PM, pradeep Kumar xplorer wrote: > Subject: [Fwd: Please list the variables i need to modify in the configure.in] > From: "Pradeep Kumar Xplorer" pradeepkumarxplorer(a)pradeepkumarxplorer.com > Date: Mon, March 11, 2019 4:04 am > To: mailman-users(a)mailman3.org > Priority: High > Read Receipt: Requested [ Send Read Receipt Now ] > Options: View Full Header | Print | Download this as a file > ---------------------------- Original Message ---------------------------- > Subject: Please list the variables i need to modify in the configure.in > From: "Pradeep Kumar Xplorer" > pradeepkumarxplorer(a)pradeepkumarxplorer.com > Date: Thu, March 7, 2019 6:36 am > To: mailman-users(a)python.org It appears you originally posted this to mailman-users(a)python.org where it would have been rejected as a post from a non-subscriber. That was probably the correct place for this as is it a Mailman 2.1 question and this list is for Mailman 3. > before running the configure script > I changed > AC_PREFIX_DEFAULT(/home1/explodi4/public_html/MAILMAN) > and it still says /home/mailman does not exist. > > Pradeep Kumar Xplorer > http://www.dhyanayoga.info > http://www.pradeepkumarxplorer.com/2016/CyberCrime/index.php You should not need to touch either configure.in or configure. Start with an unmodified configure and run `./configure --help` to see the options. It appears you may be running configure with '--prefix=/home/mailman' and that directory doesn't exist. See <https://www.list.org/mailman-install/node3.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

Search results for query "sapiro"