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

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 9/21/20 3:01 PM, Mohsen Masoudfar wrote: > It seems something is fundamentally wrong with Hyperkitty: > >>From /var/log/mailman3/mailman.log > > --- > 49 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > 50 <h1>Authorization Required</h1></body></html> (401) > 51 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > 52 <h1>Authorization Required</h1></body></html> (401) > 53 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > 54 <h1>Authorization Required</h1></body></html> (401) > 55 Sep 21 21:49:26 2020 (24918) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2. 0//EN"> ... I doubt this has anything to do with the missing approved message, but what's in you mailman-hyperkitty.cfg file for api_key and does that match your settings_local.py setting for MAILMAN_ARCHIVER_KEY except for being quoted in settings_local.py and not in mailman-hyperkitty.cfg. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Cloned mailman3 from the gitlab site, having issues locating the mailman3 file to start it

by Mark Sapiro

On 5/20/24 1:08 PM, Keith Christian wrote: > Mark, > Good morning, > > If it matters, running Python3 3.6.8 on Red Hat Enterprise Linux > release 8.9 (Ootpa) > > [mailman3@wesnixtopmed mailman]$ mkdir > /home/mailman3/mailman/virtual_environment > [mailman3@wesnixtopmed mailman]$ python3 -m venv > /home/mailman3/mailman/virtual_environment > [mailman3@wesnixtopmed mailman]$ source > /home/mailman3/mailman/virtual_environment/bin/activate > (virtual_environment) [mailman3@wesnixtopmed mailman]$ pip install > /home/mailman3/mailman > > I tried to follow your instructions closely today, got these messages afterward: > > Directory '/home/mailman3/mailman' is not installable. File 'setup.py' > not found. > You are using pip version 9.0.3, however version 24.0 is available. > You should consider upgrading via the 'pip install --upgrade pip' command. Both pip and python are too old. Officially, current Mailman 3 requires Python 3 >= 3.9. It might work with older versions, but no guarantees. Also, 9.0.3 doesn't recognize pyproject.toml as replacing setup.py. It requires pip >= 10.0. see https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/ -- 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: signup / registration error - permissions and cert chains

by Mark Sapiro

On 12/31/21 5:37 PM, David Newman wrote: > > After stripping this down to the defaults: > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > > and restarting mailman3 (necessary?) No > and mailmanweb, the system emails > me (as alias for root) an error like the one pasted below after I try > creating a new user account. > > After changing EMAIL_HOST to the system's canonical FQDN and again > restarting mailman3 and mailmanweb, the error is the same, and still > from postorius@localhost. localhost is better. If you set it to the system's canonical FQDN you need to ensure that that name or IP is in Postfix mynetworks. ... > Internal Server Error: /accounts/signup/ > > SMTPRecipientsRefused at /accounts/signup/ > {'newuser(a)dom1.tld': (504, b'5.5.2 <postorius@localhost>: Sender address > rejected: need fully-qualified address')} ... > Settings: > Using settings module settings ... > DEFAULT_FROM_EMAIL = 'postorius@localhost' Try setting this to a fully qualified address, e.g., something(a)networktest.com, not @localhost. More info at https://docs.mailman3.org/en/latest/config-web.html#setting-up-email -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: How to delete large numbers of held messages

by Mark Sapiro

On 4/21/22 14:56, Chris via Mailman-users wrote: > We had a mail loop on one of our lists and ended up with over 51k messages in pending (held due to post not form a list member) > > Trying to delete them from the web UI will take forever, as the largest pagination you can view is 200 at a time. > > Tried to delete them from the Python interactive shell, but it looks like the API times out after a while. > > Is there another way to delete all these unwanted held posts? I suggest the following in `mailman shell` ``` $ bin/mailman shell -l list.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.example.com mailing list >>> from mailman.app.moderator import handle_message >>> requestdb = IListRequests(m) >>> for id, type in requestdb.held_requests: ... if type == RequestType.held_message: ... handle_message(m, id, Action.discard) ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Lost in default style creation

by Mark Sapiro

On 6/2/22 02:44, kenneth.karlsson(a)eco.cept.org wrote: > > It shows me its there, then i proceed to quit() and go back in to the shell, and do this: >>>> quit() > ecoadmin@list01:/etc/mailman3$ sudo mailman shell > Welcome to the GNU Mailman shell > >>>> from zope.component import getUtility ... More recent versions of mailman shell will tell you what the problem is. ``` $ ./mailman shell 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. >>> ``` You need to exit the shell with control-D or issue a commit() before you exit. Also, NEVER run any `mailman` commands as root. Always run `mailman` as the Mailman user. Running `mailman` as root can create files owned by root that can't be read/modified by the Mailman user. More recent versions will tell you ``` $ sudo ./mailman Usage: mailman [OPTIONS] COMMAND [ARGS]... Try 'mailman -h' for help. Error: If you are sure you want to run as root, specify --run-as-root. ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

On 12/1/22 01:43, Jan Eden via Mailman-users wrote: > > There are currently 5 (test) threads in the archive. After changing the > PATH in the HAYSTACK_CONNECTIONS dict to /opt/mailman/fulltext_index, > and fixing the issue with MAILMAN_ARCHIVER_FROM above, > /opt/mailman/web/logs/mailmanweb.log does not display new error > messages, but I do not get any suggestions for reattaching threads, and > a search for a specific thread subject ("Third test") does not return > any results. By "search for a specific thread subject", do you mean searching via the search box at the top of HyperKitty pages? This relies on the search index for Haystack (Whoosh in your case). This index is updated by the HyperKitty update_index job. Assuming you have set up the cron jobs for Django <https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…>, this will be run hourly and posts added to the archive in the last hour won't be indexed. > So reattachment works in principle, but the suggest/search function does > not. Reattachment suggest doesn't depend on the search index, but it does depend on loosely matching thread subjects. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Caching problem with templates

by Mark Sapiro

On 6/26/25 15:12, Mark wrote: > > On 2025-06-26 16:10, Mark Sapiro wrote: > >> What does the database query >> ``` >> SELECT uri FROM template WHERE name = 'list:member:regular:footer' AND >> context = '<IDENTIFIER>'; >> ``` >> return? > > ================================= > > The result of the query is: > +--- > uri > +---- > http://localhost:8000/mailman3/api/templates/list/<IDENTIFIER>/list:member:regular:footer > +---- > > I should have also said, if I delete the template, emails still use the > old footer -- not the Mailman default as I would have expected. As long as there is an entry in the template table with a uri which is not a `mailman://` scheme, that entry is cached in the file_cache table in the database with a key = the uri and a lifetime set by cache_life in the [mailman] section of mailman.cfg - default 7 days. You can delete the cached entry from the database via `mailman shell as in ``` $ mailman shell 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. >>> cm = getUtility(ICacheManager) >>> uri = 'the_uri_from_the_template_table' >>> cm.get(uri, expunge=True) >>> commit() ``` You can also delete the entry from the file_cache table, but if you do that, the actual file containing the cached data will remain. To remove it, note that the file_cache table entry has a file_id. This will be a hex digest of the sha256 hash of the uri, something like `c85210810f8824cf9227c1689817e1d081046ff132bf8abe56a7c08a89016e4e` and the file is stored in the cache/ directory in Mailman's var/ directory with a path of `file_id[0:2]/file_id[2:4]/file_id`. I.e. for the above example file_id, the file will be `var/cache/c8/52/c85210810f8824cf9227c1689817e1d081046ff132bf8abe56a7c08a89016e4e`. If you remove the entry from the file_cache table without removing the file, the file will remain forever but will be overwritten if the same uri is cached again. Rather than doing any of the above, if you want to manipulate the database, just set the expires_on column in the file_cache table entry to a date in the past. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months

[MM3-users] Re: content filtering in version 3.1

by Mark Sapiro

Resending with proper inline code quoting for the archive. On 12/20/19 1:31 AM, Dieter Leupold via Mailman-users wrote: > Hi Mark, > > Thanks for your information. But, how I said, I'm new to MM3 and I have > problems with the syntax of the mailman shell. Please, could you give me > an example to set "pass_types" via MM-Shell? > Thank you very much! The documentation of Mailman shell is at <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…>. A simple example in for setting pass_types is ``` $ bin/mailman shell -l list(a)example.com Welcome to the GNU Mailman shell The variable 'm' is the list(a)example.com mailing list >>> m.pass_types <generator object MailingList.pass_types at 0x7fd7e1489840> >>> list(m.pass_types) [] >>> m.pass_types = ['multipart', 'text/plain'] >>> list(m.pass_types) ['multipart', 'text/plain'] >>> ``` At this prompt you can enter commit() to commit your changes, abort() to reverse your changes or control-D to commit and exit. You can also enter exit() to exit, but your changes will not be saved unless you have done a prior commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Announce Only List

by Mark Sapiro

On 8/13/20 9:49 AM, joseverde(a)gmail.com wrote: > So if we want to make a list announce only (e.g. only specific folks) can post, I've found I can set the list settings to automatically discard messages from members and non-members. Then I go into the individual permissions on each user to be allowed to post without moderation. This works fine, however it seems cumbersome. My expected solution was to make the announce only members moderators - however it appears being a moderator does not give any special ability to post to the list (nor does it appear to make you a 'member' from the point of mailman when sending messages to the list, since a moderator who is not a subscriber gets treated like a nonmember from the posting permissions perspective). Is this correct? Yes, your observations are correct. This is how it's always been, at least from the beginning of Mailman 2.1. There is an alternative. Set a moderator_password for the list. Then anyone can successfully post with an `Approved: <password>` header or pseudo header if they know the password. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…>. -- 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: Where should Postfix, Django, Hyperkitty, Postorius, Dart-Sass, etc. be installed if MM3 is in a python virtual environment?

by Mark Sapiro

On 5/24/24 7:41 PM, Keith Christian wrote: > > mailman3 was installed into the below virtual environment: > (venv) [mailman3@localhost-live ~]$ pip install wheel mailman psycopg2-binary > Should, or must, any of Django, Hyperkitty, Postorius, Dart-Sass, or > any other supporting programs be installed into this virtual > environment ? If you follow the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html you will install Mailman core, psycopg2-binary, mailman-web and mailman-hyperkitty in the venv. mailman-web will install Django, django-mailman3, MailmanClient, HyperKitty and Postorius as dependencies in the venv. > PostgreSQL and Postfix have been successfully installed outside of the > mailman3 virtual environment and start properly, I assume this is > correct. Since these are not python packages, they and sassc (or Dart-Sass) are installed outside the venv. Also, Postfix in particular and possibly PostgreSQL may be used by things other than Mailman so you don't want them in the venv even if they could be installed there. -- 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

Search results for query "sapiro"