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

[MM3-users] Re: global preferences

by Mark Sapiro

Again, please don't hijack threads. Post a new topic by composing a new message to mailman-users(a)mailman3.org, not as a reply to another list message. On 5/3/23 07:59, Christian via Mailman-users wrote: > Are checks and changes to global preferences for all lists to be made via a GUI or is it editing settings.py directly please? Thank you! You can set your global preferences via Postorius (select Mailman settings from the drop-down at the right of the top nav bar). These are the settings for the user that will apply if there is no applicable list-based or address-based setting. They are specific to the user. The defaults for these are defined in mailman/core/constants.py. They are Mailman core settings and have nothing to do with Django's settings.py. -- 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: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Mark Sapiro

On 11/25/23 16:25, Jered Floyd wrote: > Via mailman-web. I’ll try to reproduce the behavior tomorrow, once I am home from another episode of turkey overconsumption. > > I confess that I am not a python expert - once I create a new list, what’s the easiest way to inspect the object state? ``` $ mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> print(m.dmarc_addresses) [] >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Error when click on mailing list: An error occurred while processing your request.

by Mark Sapiro

On 7/9/24 6:11 PM, adam.heathcote(a)utas.edu.au wrote: > > mailman members -R owner your_list(a)your.domain > > Shows myself as an owner as well as the imported owners from the previous list. You originally wrote: "but now when clicking on the list, Postorius shows: An error occurred while processing your request." I'm guessing you are clicking the list in the Postorius `Mailing Lists` view, i.e. something like https://example.com/mailman3/ or https://example.com/mailman3/lists, and you are logged in, and the link is to https://example.com/mailman3/lists/listname.example.com. What if you go to that page without being logged in, or logged in as a different user? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: bypassing rules on an individual basis

by Mark Sapiro

On 4/4/25 08:10, via Mailman-users wrote: > I have a mailing list that, due to specific circumstances, has a requirement to allow messages from a user that sends messages with no subject. I've added the address to the "Accept these non-members" collection, but messages from that address still get held for moderation, due to the no-subect rule. Do not add the address to accept_these_nonmembers. Is the user a member? If so, go to the `Members` list, click on the user (search if necessary), scroll down to Administration options Moderation and set the dropdown to `Accept immediately (bypass other rules)` and click the Save changes button below that. If the user is not a member, do the same thing, but use the `Non-Members` list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Upgrading from 3.1 to 3.2

by Mark Sapiro

On 07/17/2018 07:29 PM, Joe Steeve wrote: > > I have a 3.1 installation. I want to upgrade to 3.2. > > Has anyone attempted this? Any gotchas I need to be aware of? Yes. The gotcha is the web UI (postorius, hyperkitty, django-mailman3 and thus the WSGI process under which Django runs is Python 2.7 in Mailman 3.1 and associates and Python 3.5+ in Mailman 3.2 and associates. This migration can be tricky depending on your exact configuration. The most difficult situation I encountered was on a server that also supported MoinMoin which is a Python 2.7 WSGI process. Thus I needed both Python 2.7 and Python 3 WSGI support. I wound up leaving the Python 2.7 mod_wsgi in Apache and proxying the Mailman 3 URLs to gunicorn for Python 3 support. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: autoresponse not sent

by Mark Sapiro

On 10/19/18 8:21 AM, shadiakiki1986(a)gmail.com wrote: > Hello. Newbie to mailman here. > I tried out mailman3 today. My setup is > - mailman3 suite using the docker-compose file from asynchronous.io > - exim4 on the local machine and configuring it as smarthost using mailgun smtp server > > The emails to the mailing list are received by the subscribers, > but the autoresponse is not being received by the sender (who is not from the subscribers list). > I'm not sure if the problem is from mailman-core, settings from mailman-web, or from exim. This is most likely <https://gitlab.com/mailman/mailman/issues/504>. The fix has been in the master branch for a couple of months but is not in 3.2.0. It may be in the asynchronous.io "rolling release". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Moving from forum to Mailman 3

by Mark Sapiro

On 10/7/20 2:52 PM, Jonathan M wrote: > What ways are there to move a forum to an existing Mailman 3 list, so that each old forum message is displayed in the archive as if it had been an email? Can you export the posts from the forum in a format that looks like email messages? Python's standard library mailbox module can be used to read a set of messages in any of Maildir, mbox, MH, Babyl, or MMDF format and write them to a mbox format file which can then be imported into HyperKitty. The requirements are that the exported messages have headers like an email message. At a minimum, From:, Date: and Subject:. See <https://docs.python.org/3/library/mailbox.html> for more detail about mailbox formats. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Footer question...

by Mark Sapiro

On 7/27/21 4:06 AM, David Partain via Mailman-users wrote: > > I migrated > 1200 lists from an old mailman2 installation. That brought along all of the footers (naturally), and now I'm trying to get rid of them but failing miserably. I've spent a fair bit of time reading archives of this list, but I'm still stuck. > > Here's what's configured... > > In /etc/mailman3/mailman.cfg: > > -------------------------------------------------------------------------------------------------------------------------- > var_dir: /var/lib/mailman3 > # Root directory for site-specific template override files. > template_dir: $var_dir/templates ... > Anyone have suggestions of what I can do? rm -rf /var/lib/mailman3/templates/lists/* This will allow the template search to fall back to the default. If you want to customize that, you can put custom templates in /var/lib/mailman3/templates/site/en/. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Issues with importing archives from a particular list

by Mark Sapiro

On 1/13/22 4:33 AM, Prasanth Nair wrote: > Hello, > > We are trying to import archives from Mailman2 to Mailman3. For a > particular list, it is not importing all of the messages. We can see that > Mailman2 has archives from 2015 to 2022. But, it only imports messages from > 2018 to 2022 to the Mailman3 server. It was not giving any errors while > importing. The problem list probably already had an archived message from 2018. If you don't specify a --since= date for hyperkitty_import, it only imports messages newer than the newest existing message in the archive. You can run it again with, e.g., --since=2000-01-01. It won't reimport the messages already imported because of duplicate message ids. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: More Mailman releases!

by Mark Sapiro

On 10/24/23 6:12 AM, Wikinaut wrote: > After installing the last program to be updated (mailman-web), the archives become unavailable due to (again) some glitches with the urls. > I did not(!) change the /etc/mailman3/ configuration files. > > before upgrade, example.com/mailman3/lists/mylist.mydomain (=> worked) > after upgrade, example.com/postorius/lists/mylist.mydomain failed Did example.com/postorius/lists/mylist.mydomain work before the upgrade? Does example.com/mailman3/lists/mylist.mydomain work after upgrade? > Why and who changed my settings? The latest mailman-web upgrade added entries to urls.py. mailman-web<0.0.8 would recognize only the /mailman3/ and /archives/ urls. mailman-web=0.0.8 still recognizes those and now also recognizes /postorius/ and /hyperkitty/ urls. If /postorius/ and /hyperkitty/ urls are not working for you now, the issue is probably in your web server configuration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

Search results for query "sapiro"