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

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by Mark Sapiro

On 3/12/21 7:36 PM, John Covici wrote: > Hi. I am having a great deal of difficulty installing mailman3 using > gentoo and sendmail. Also, I want to upgrade my old mailman2 data to > mailman3. > > What I have done so far is to install the mailman3 packages from my > repository and got this: > django-mailman3 version 1.3.4, mailmanclient version 3.3.1, mailman > version 3.3.2 (apparently the core), postorius version 1.3.3 and > hyperkitty version 1.3.3. I also have mariadb and postgresql already installed. Are these gentoo packages? If so, I have no idea how they are configured. > Now trying to read your documentation, it seems it wants me to > reinstall some packages using pip in the home directory of the mailman > user in a python virtual environment, that was the first thing. But I > would like to avoid multiple package managers wherever possible -- > gentoo is already a lot of maintainance without dealing with pip's > maintainance. The binaries also seem to be different from my gentoo packages. Our documantation generally covers installing from source. If you are installing gentoo packages, you should be looking at gentoo docs and going to gentoo for help. We recommend installing Mailman and the web components in a virtualenv, but it is not a requirement. We also suggest that postgresql is a better choice than MariaDB. > So, how do I proceed with getting mailman3 up and working, configuring > the database, configs, etc and I guess after doing that upgrading > mailman2 and getting sendmail to interface properly with mailman3? Importing lists from Mailman 2 is done with the `mailman import21` command. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>. Importing archives is done with the Django management `hyperkitty_import` command. See <https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#import…> For sendmail, see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 12/14/22 13:40, Jeremy Stanley wrote: > > Once these entries are automatically added by visiting that page, > they're all associated with the one "web host" ("site" in Django) we > have for the server, and now the list filtering functionality in > Postorius breaks and any of the vhosts all display the full set of > mailing lists on the server rather than only those associated with a > particular vhost (note that this seems to only be confusing > Postorius, Hyperkitty has them correctly filtered still). See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and also below. > Okay, so it looks like this is because the mail hosts are all tied > to the one web host. Yes. > We can create additional "sites" in the Django > admin UI and then switch the association of the mail hosts to those > distinct web hosts. But after doing so, the first vhost still seems > to show an unfiltered list of all lists in Postorius (Hyperkitty > continues to be fine), while Postorius on the other vhosts correctly > shows their filtered sets of lists instead. > > I also noticed when mailman-web is starting up, its log claims the > first site is being set as the "default domain," so have to wonder > if that's related to this behavior. Should we create an extra web > host to serve as the "default" so that all our typical vhosts get > the expected list filtering behavior, or am I completely off-base > and there's a much better approach I've missed? I'm not really sure what's going on here. You could try creating a dummy default host to see if that fixes the issue for you. There are subtle differences in the implementation between HyperKitty and Postorius that allow HyperKitty to work better, but it too will exhibit some anomalous behaviors. -- 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: Moderate mails from owner

by Mark Sapiro

On 3/22/19 6:10 AM, Malcolm Austen wrote: > On Thu, 21 Mar 2019 16:58:45 -0000, Abhilash Raj > <maxking(a)asynchronous.in> wrote: >> >> "Default Processing" means the default pipeline defined in > > Thanks, I will do some (more!) reading. > >> List > Settings > Alter Messages > 'Pipeline' ( in the bottom). This >> pipeline is >> system wide and is defined in source code, so it can't be customized by >> site administrator. > > Unfortunately, that is not available to list-owners on the system > concerned. Ancestry must have removed it. It wouldn't help you anyway. All it shows are the choices 'default posting pipeline', 'default owner pipeline' and 'virgin', not the contents. See <https://mailman.readthedocs.io/en/latest/build/lib/mailman/app/docs/pipelin…> for info on pipelines. Also, when we're talking about Default Processing in the context of moderation, we're not really talking about pipelines; we're talking about rule chains. See <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/rules.html> and <https://mailman.readthedocs.io/en/latest/src/mailman/chains/docs/moderation…>. This latter doc mentions 'defer' which is another name for 'Default Processing'. Also in the latter doc in the example under "Anne’s post to the mailing list runs through the incoming runner’s default built-in chain. No rules hit and so the message is accepted." you'll see Hits: Misses: dmarc-mitigation no-senders approved emergency loop banned-address member-moderation nonmember-moderation administrivia implicit-dest max-recipients max-size news-moderation no-subject suspicious-header The misses are the rules processed in the normal chain in order. When you set a (non-)member's moderation to Accept, at the appropriate (non)member-moderation rule, the rest of the chain is skipped and the message is accepted. If the(non-)member's moderation is Default Processing, that rule passes, but the remaining administrivia implicit-dest max-recipients max-size news-moderation no-subject suspicious-header rules are checked before the message is accepted. -- 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

[MM3-users] Re: Mailman3 Issue with Sending Mail to Yahoo/AOL

by Mark Sapiro

On 5/12/21 7:47 AM, chris--- via Mailman-users wrote: > Hi everyone. I have a dedicated Ubuntu box that is running mailman3. I have a single email list on it. The subscriber base is about 350 users. There is a good chunk of these users that are aol.com or yahoo.com users. I've been getting complaints from the Yahoo people that mail is delayed at times, or messages that come out of order. > > Looking at the mailq on the box, I can see there are plenty of emails stuck in the queue. I have all sorts of messages like this ... > > > -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- > 3576C540CB4 9917 Tue May 11 11:27:13 pcho-bounces(a)pchochat.com > (host mta6.am0.yahoodns.net[67.195.204.74] said: 452 Too many recipients tnmpmscs (in reply to RCPT TO command)) This one's easy to fix. In mailman.cfg set ``` [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 ``` This will provide potentially better bounce processing detection, but will ensure that each message from Mailman has only one envelope recipient. If you don't want the verping, you can set `max_recipients` in the `[mta]` section to a small number like 5 or 10. > (host mta6.am0.yahoodns.net[67.195.204.74] said: 421 [IPTS04] Messages from 74.112.73.65 temporarily deferred due to unexpected volume or user complaints - 4.16.55.1; see https://postmaster.verizonmedia.com/error-codes (in reply to end of DATA command)) The above changes may help with this too, but depending on where your Ubuntu box is located, you may have other issues. Presumably you have a fixed IP address, but even so, if that address is in a netblock that looks like `home networks` it may get blocked by some providers for that reason alone. Also, others in this thread have mentioned Verizon. Verizon recently sold AOL/Yahoo to a private equity firm, Apollo Global Management. What that means for the new Yahoo is still unclear. Search the web for `verizon sells aol` for more info. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 1/6/22 2:40 PM, gordon(a)dickens.com wrote: > I performed a distribution upgrade from Debian 10 Buster (which runs mailman 3.2.1) to Debian 11 Bullseye (which runs mailman 3.3.1) with the command "apt-get full-upgrade -y" and everything apparently worked properly except at the end of the upgrade when the following error dialog was generated by the mailman3-web and mailman3-full post-installation scripts: > > Setting up mailman3-web (0+20200530-2) ... > Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. > dbconfig-common: writing config to /etc/dbconfig-common/mailman3-web.conf > dbconfig-common: flushing administrative password > sed: -e expression #2, char 77: unterminated `s' command > dpkg: error processing package mailman3-web (--configure): > installed mailman3-web package post-installation script subprocess returned error exit status 1 > dpkg: dependency problems prevent configuration of mailman3-full: > mailman3-full depends on mailman3-web; however: > Package mailman3-web is not configured yet. > > dpkg: error processing package mailman3-full (--configure): > dependency problems - leaving unconfigured > Errors were encountered while processing: > mailman3-web > mailman3-full > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Now, every time that I execute "apt-get upgrade" then I continue to get the above error dialog. Also, the command "dpkg-reconfigure mailman3-web" generates this output: > > /usr/sbin/dpkg-reconfigure: mailman3-web is broken or not fully installed > > So, I am now stuck since apt-get is saying that mailman3-web is not configured yet, however, neither apt-get nor dpkg-reconfigure will successfully configure mailman3-web. > > Does anybody have any idea how to fix this? I would very much appreciate some suggestions. This is a Debian packaging issue. It looks like the underlying error is sed: -e expression #2, char 77: unterminated `s' command which is an issue in one of the installation scripts in the .deb for mailman3-web. Your best source of help for this is Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Migrating mailman3 to latest ubuntu lts

by Mark Sapiro

On 12/16/23 10:12 AM, Helio Loureiro wrote: > Hi, > > Well... not that good. Now it is mailman3-web that doesn't work. > > mailman@new-machine ~ (v3.3.9)> source venv/bin/activate.fish > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web > > Type 'mailman-web help <subcommand>' for help on a specific subcommand. > > Available subcommands: > > [django] > check > compilemessages > createcachetable > dbshell > diffsettings > dumpdata > flush > inspectdb > loaddata > makemessages > makemigrations > migrate > optimizemigration > runserver > sendtestemail > shell > showmigrations > sqlflush > sqlmigrate > sqlsequencereset > squashmigrations > startapp > startproject > test > testserver This response indicates that `mailman-web` is not getting settings.py. Have you configured /etc/mailman3/settings.py? See <https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu…>. > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check > System check identified no issues (0 silenced). > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check migrate You should run `mailman-web migrate` not `mailman-web check migrate` plus others. See <https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi…> et.seq. but first you need the appropriate settings so `mailman-web` returns something like ``` $ mailman-web Type 'mailman-web help <subcommand>' for help on a specific subcommand. Available subcommands: [account] account_unsetmultipleprimaryemails [auth] changepassword createsuperuser [compressor] compress mtime_cache [contenttypes] remove_stale_contenttypes [django] check compilemessages createcachetable dbshell diffsettings dumpdata flush inspectdb loaddata makemessages makemigrations migrate optimizemigration sendtestemail shell showmigrations sqlflush sqlmigrate sqlsequencereset squashmigrations startapp startproject test testserver [django_extensions] admin_generator clean_pyc clear_cache compile_pyc create_command create_jobs create_template_tags delete_squashed_migrations describe_form drop_test_database dumpscript export_emails find_template generate_password generate_secret_key graph_models list_model_info list_signals mail_debug managestate merge_model_instances notes pipchecker print_settings print_user_for_session raise_test_exception reset_db reset_schema runjob runjobs runprofileserver runscript runserver_plus set_default_site set_fake_emails set_fake_passwords shell_plus show_template_tags show_urls sqlcreate sqldiff sqldsn sync_s3 syncdata unreferenced_files update_permissions validate_templates [django_q] qcluster qinfo qmemory qmonitor [haystack] build_solr_schema clear_index haystack_info rebuild_index update_index [hyperkitty] attachments_to_file hyperkitty_import hyperkitty_warm_up_cache mailman_sync update_index_one_list [postorius] mmclient reset_passwords [rest_framework] generateschema [sessions] clearsessions [staticfiles] collectstatic findstatic runserver ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Internal Server Error: Reattach this thread

by Mark Sapiro

On 10/25/22 17:08, cold00water(a)gmail.com wrote: > Hey. > > Looking at other code, "subject" is a method. > > I fixed it by correcting the code. > is this a bug? python version issue? > > * /opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/views/thread.py > > 411 @check_mlist_private > 412 def reattach_suggest(request, mlist_fqdn, threadid): > 413 mlist = get_object_or_404(MailingList, name=mlist_fqdn) > 414 thread = get_object_or_404(Thread, mailinglist=mlist, thread_id=threadid) > 415 > 416 default_search_query = stripped_subject( > # change: thread.subject to thread.subject() > 417 mlist, thread.subject()).lower().replace("re:", "") > > * /opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/models/thread.py > > 69 def __str__(self): > # change: thread.subject to thread.subject() > 70 return self.subject() Did you test this?, How? I.e. where you able to produce the error without your change and then verify that your change fixed it? The existing code works in all but rare situations, and I think those are due to the thread object being instantiated with missing arguments. In any case, your changes cause the ReattachTestCase.test_suggestions test in hyperkitty/tests/views/test_thread.py to fail as follows. ``` hyperkitty/tests/views/test_thread.py:66: in test_suggestions response = self.client.get(reverse('hk_thread_reattach_suggest', .tox/py39-django32/lib/python3.9/site-packages/django/test/client.py:742: in get response = super().get(path, data=data, secure=secure, **extra) .tox/py39-django32/lib/python3.9/site-packages/django/test/client.py:396: in get return self.generic('GET', path, secure=secure, **{ .tox/py39-django32/lib/python3.9/site-packages/django/test/client.py:473: in generic return self.request(**r) .tox/py39-django32/lib/python3.9/site-packages/django/test/client.py:719: in request self.check_exception(response) .tox/py39-django32/lib/python3.9/site-packages/django/test/client.py:580: in check_exception raise exc_value .tox/py39-django32/lib/python3.9/site-packages/django/core/handlers/exception.py:47: in inner response = get_response(request) .tox/py39-django32/lib/python3.9/site-packages/django/core/handlers/base.py:181: in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) hyperkitty/lib/view_helpers.py:137: in inner return func(request, *args, **kwargs) hyperkitty/views/thread.py:445: in reattach_suggest mlist, thread.subject()).lower().replace("re:", "") E TypeError: 'str' object is not callable ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Digestion debugging

by Mark Sapiro

On 2/20/26 16:35, John Price via Mailman-users wrote: > I'm having trouble getting digests to work. When I try to manually > send one, it does nothing, and then the digest gets deleted (I > guess?). If the `mailman digests` command is run without a --send or --periodic option, it won't send any digests. See `mailman digests --help`. Messages for a list's digest are accumulated in a mailbox at Mailman's var/lists/<list_id>/digest.mmdf. They are sent when the mailbox reaches the size set as the list's digest_size_threshold and if the list's digest_send_periodic is True, when the `mailman digests --periodic` command is run - normally run daily via cron,. See <https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-cron-jobs>. > I would love it if the documentation explained a bit more how the > process works. How are the files gathered? What file can I backup and > later restore if I'm debugging it? One of the handlers run in the posting pipeline is `to_digest` which adds the message to the list's digest.mmdf file and checks if a digest should be sent based on size. > Also, how are the digest issue and volume numbers work? Is there any > way to control that? Since I've been running digests for decades, can > I set the volume and issue to what I want so that the numbering > continues from where the other installation left off? The issue number is incremented with each digest At intervals determined by the list's digest_volume_frequency The issue number is reset and the volume number is incremented. The volume can also be incremented and the issue reset by running `mailman digests` with the `--bump` option ` The current volume number is the list's volume attribute and the next issue number is the list's next_digest_number attribute. These can be manipulated via `mailman shell` or by direct manipulation of the list's entry in the mailinglist table in the database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 2 weeks

[MM3-users] Re: Auth question

by Mark Sapiro

On 1/3/19 5:33 PM, kelly.close(a)lrewater.com wrote: > Thanks Mark. I keep coming back to this and checking it again and again. The two keys match, and there are no quotes on the api_key. > > This is what I thought the problem was from the start but I just can't see anything wrong with those two settings. I'm going to look again - maybe entirely re-type the lines - what if there is a trailing space or something... I don't think trailing white space on the api_key setting is significant, and whitespace following the trailing quote in the MAILMAN_ARCHIVER_KEY setting is not significant, but embedded whitespace in the key itself could be an issue. Possibly Mailman and/or Hyperkitty aren't getting this info from the files you think they are. The command that you use to start Mailman should have a -C option pointing to Mailman's config. That in turn has a [archiver.hyperkitty] section pointing to the Mailman Hyperkitty config. That in turn contains the api_key. Then whatever process you use to run the wsgi application will set DJANGO_SETTINGS_MODULE in it's environment to point to settings.py or whatever you call it (without the .py extension) and that in turn imports overrides from settings_local.py. You need to understand what the working directory is of the process that imports the DJANGO_SETTINGS_MODULE. If you need more info, you could try modifying hyperkitty/hyperkitty/views/mailman.py at around lines 64 - 68 to: if request.GET.get("key") != settings.MAILMAN_ARCHIVER_KEY: return HttpResponse( """<html><title>Auth required</title><body> <h1>Authorization Required</h1> {} != {}</body></html>""" .format(request.GET.get("key"), settings.MAILMAN_ARCHIVER_KEY), content_type="text/html", status=401) This should display the values that don't match as part of the error response. Note that this is Python and leading whitespace is significant and if you're reading this in HyperKitty, you won't see it unless you "display in fixed font" (the "A" icon), and even then, there may be line wrap. -- 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: user self registration

by Christian Stalberg

Something strange is now going on. Now when a user tries to subscribe themself and they get the ' Please check your inbox for further instructions' no such email arrives in their mailbox. Relatedly, if I as an admin try adding someone to a list via the Mass Subscribe, they are not added to the list, but they do appear in the listing of all Users. Help! -----Original Message----- From: Christian Stalberg via Mailman-users <mailman-users(a)mailman3.org> Sent: Monday, December 8, 2025 6:16 AM To: mailman-users(a)mailman3.org Cc: 'Mark Sapiro' <mark(a)msapiro.net> Subject: [MM3-users] Re: user self registration That worked. Thank you! -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Sunday, December 7, 2025 9:26 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: user self registration On 12/7/25 07:46, Christian Stalberg via Mailman-users wrote: > Spammers have been registering and not subscribing. I want to turn off > the user self registration at https://lists.ccalternatives.org/mailman3/ . > > I edited /etc/mailman3/settings.py adding ACCOUNT_ALLOW_REGISTRATION = > False and restarted the services, but the ' Sign Up' option remains. I > assume /etc/mailman3/settings.py is my active settings file. > > What am I doing wrong? Web searches may find reference to a django-allauth setting ACCOUNT_ALLOW_REGISTRATION, but this setting doesn't exist in current django-allauth The setting you want is ACCOUNT_ADAPTER = ‘django_mailman3.views.user_adapter.DisableSignupAdapter’ See https://docs.mailman3.org/en/latest/faq.html#how-to-disable-signup or https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mail… -- 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: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to csa(a)web-analysts.net _______________________________________________ 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: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to csa(a)web-analysts.net

5 months

Search results for query "sapiro"