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

[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

6 years, 5 months

[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, 4 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

3 years, 8 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

1 year, 8 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

2 years, 10 months

[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

6 years, 8 months

[MM3-users] Re: mailman 3.x upgrade and downgrade

by C. Souza

Ok, thanks! On Tue, Jul 12, 2022 at 1:44 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/12/22 9:35 AM, C. Souza wrote: > > > > I can't see the mistune package, maybe it wasn't a requirement for that > > version of mm3. > > > > 1 Package Version > > 2 ------------------- ---------- > > ... > > 39 HyperKitty 1.3.3 > > > Correct. It is not a requirement until HyperKitty 1.3.5 > > -- > 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/ >

3 years, 2 months

[MM3-users] Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 5:40 PM, Paul Arenson wrote: > >> Assuming MUA means a mail application. And if that mail application has no reply list function then the setting doesn't work. MUA means Mail User Agent which is another name for mail application, YES. > Uh-oh: I AM LOST AGAIN. (will all caps give me a larger font?) > >> It is the presence of the >> List-Post: header in the message that allows the MUA to offer/process >> the "reply-list" function. > > Ok, I asked how to make it ANNOUNCE ONLY and you said to use "allow_list_posts is False" which is the same as "Include the list post header". Not exactly. You asked what settings were different between discussion style and announce only style. What I answered was that the only setting that differed as set by the style was what Postorius calls "Include the list post header". What I didn't say explicitly was that this is not sufficient to prevent posting to the list. > So does this mean that for a subset of users I cannot make it ANNOUNCE ONLY? And is it some other setting (send to moderator) that prevents it from being a DISCUSSION list? What exactly do you want? You found some info on configuring an announce only list and I referred you to a FAQ on that subject. Both of these do not directly address Mailman 3, but they do give useful information. I am going to stop guessing at what you want to accomplish, so tell me what you want to happen when someone sends a post to the list either from HyperKitty or by email. What should happen to the message? What if anything should be sent to the user? Should this behavior be the same for all users or just a subset. If a subset, how do you identify that subset and what should happen when others attempt to post? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: moving lists to another server

by Mark Sapiro

On 11/20/23 00:58, Odhiambo Washington wrote: > > What is the command to export the archive as a mbox from the DB? > I can't figure out which option it is by looking at 'mailman-web -h'. Normally you do this on the old server via the HyperKitty web UI which has download buttons which do things like https://example.com/archives/list/list@example.com/export/list@example.com.… or for a partial archive https://example.com/archives/list/list@example.com/export/list@example.com-… However, in your case I don't think you have the old installation working any more so the above won't help. > BTW, how will ' mailman addmembers' treat a file containing: > ``` > Firstname Lastname <email@address> > Onlyname <email2@address> > ``` Correctly. It will import email@address with display name = 'Firstname Lastname' and email2@address with display name = 'Onlyname'. > I have opted for the simple way to do this: > 1. Create the site in Django Admin and create/configure the list in > Postorius > 2. Add the members from the file dump, with delivery set to regular. > 3. Send the members an email informing them that they need to set their > delivery preferences. > > I am stuck on the issue of exporting the archives to mbox file as already > stated above. Perhaps you can export the mbox via the web UI on the old server or maybe temporarily create a second mailman-web on your server with the old mailman-web database and use that web UI. Otherwise, if you have a working mailman-web that can access this database, you could try something like ``` $ mailman-web shell >>> from hyperkitty.lib.compat import get_list_by_name >>> mlist = get_list_by_name('list_name_only', 'list_domain') >>> with open('output.mbox', 'wb') as fp: ... for email in mlist.emails.order_by("archived_date").all(): ... fp.write(email.as_bytes() + b'\n') ... >>> ``` -- 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: Update a member's display_name

by Mark Sapiro

On 1/17/19 8:45 AM, Nick Wynja wrote: >> user_manager = getUtility(IUserManager) >> u = user_manager.get_user('aperson(a)example.com') >> u.addresses[0].display_name = "Anne" >> commit() > > It seems this method updates the display_name for the user across all lists. Is there a way to update just a single instance of "member" of a list rather than the site-wide user? > > I've tried this: > > mailman shell -l test(a)example.com > >>>> mem = m.members.get_member('a(a)example.com') >>>> mem > <Member: a(a)example.com on test(a)example.com as MemberRole.member> >>>> mem.display_name > 'Anne' >>>> mem.display_name = "Anne P" > Traceback (most recent call last): > File "<console>", line 1, in <module> > AttributeError: can't set attribute That's because mem.display_name is a "calculated" attribute. The definition of the IMember class says > display_name = Attribute( > """The best match of the member's display name. > > This will be `subscriber.display_name` if available, which means it > will either be the display name of the address or user that's > subscribed. If unavailable, and the address is the subscriber, then > the linked user's display name is given, if available. When all else > fails, the empty string is returned. > """) and > subscriber = Attribute( > """The object representing how this member is subscribed. > > This will be an ``IAddress`` if the user is subscribed via an explicit > address, otherwise if the the user is subscribed via their preferred > address, it will be an ``IUser``. > """) So there is no member display_name per se. The display_name is the display_name of the associated IUser or IAddress, and these are global. The bottom line is there is not a way to update just a single instance of "member" of a list rather than the site-wide user or address? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

Search results for query "sapiro"