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

[MM3-users] Re: Avoiding non-members to be saved.

by Mark Sapiro

On 8/7/21 4:55 AM, Stephen J. Turnbull wrote: > Guillermo Hernandez (Oldno7) via Mailman-users writes: > > > Yesterday I had a problem with a private list. A spammer sent a mail > > forging one address that was a non-member (in fact was an "accept this > > no subscriber mails" from mailman 2.1 import) with very bad intentions > > and it was distributed. > > If you upgrade from Mailman 2 to Mailman 3, the accept_these_nonmembers > list for each list is grandfathered into the Mailman 3 list (from > rules/moderation.py): > > # Check the '*_these_nonmembers' properties first. XXX These are > # legacy attributes from MM2.1; their database type is 'pickle' and > # they should eventually get replaced. > for action_name in ('accept', 'hold', 'reject', 'discard'): > legacy_attribute_name = '{}_these_nonmembers'.format( > action_name) > > > There were no list of "accept this non members" in the Postorius > > config > > If there is no such list in Postorius, I would guess that some > developer thought "OK, this is a legacy feature and I'll get back to > it when we move it to the proper database" (unfortunate, but most of > us have open-subscription member-posts-only lists, and the current > workflow seems to work well, so this feature may not be so salient). Moderation in MM 3 works as follows: Is poster address a member. If so apply the member's moderation action, else Does poster address appear or match a pattern in the legacy (accept|hold|reject|discard)_these_nonmembers (first match in that order). If so, apply the appropriate action, else If the poster address is not a non-member, add it as a nonmember and apply the default nonmember moderation. > > I think it is solved now (deleting all and putting to hold just the > > non-members addresses that I would want to pass messages on) > > This should not be necessary, unless there were pre-approved addresses > that are no longer appropriate. But Mailman can't know that! The import21 process imports *_these_nonmembers by adding any regexps to the corresponding MM 3 *_these_nonmembers and adding any addresses as nonmembers with the appropriate moderation action. > > The fact is that any sender address of mails sent to the list is saved > > as a "non member", and it make me nervous as it will grow despite it is > > a legitimate message or not. This is the way MM 3 works. The only reason *_these_nonmembers exists in MM 3 is to support the legacy regexps from MM 2.1. For non-regexp addresses the address is a nonmember with the appropriate moderation action. I actually find this convenient. When a nonmember posts spam to a list and that spam is held, I discard the spam in Postorius and at the same time set the nonmember's moderation action to discard so I never see any more from that address. Also, when someone who I recognize as a list member posts from an alternate nonmember address, I can accept that post and set the nonmember address moderation action to default processing. > As far as I can see there is no other rule except that legacy rule > (and the rule that accepts all posts, which is rarely used) that will > accept a post from nonmembers. As I note above, nonmembers and members alike have a moderation action which can be any of Hold, Reject (with notice), Discard (no notice), Accept (without any further checks), Default Processing (continue with additioal checks) or the list's default action for (non)members. -- 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: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Thank you Mark, Then I will try to upgrade the version Thank you once again. On Fri, Jun 18, 2021 at 8:01 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/21 6:48 AM, Shashikanth Komandoor wrote: > > Dear Mark, > > > > FYI, I observed this issue with the postfix that receives the > > mails from the previous MTA and hands it over to the mailman. But I fixed > > at postfix by upgrading it to the version postfix 3. > > > > But still Mailman is not able to understand Hindi (Indian > local > > language) in which language the display names of the email ids are there. > > > > So, now what to do at Mailman so that it can also understand > > local languages or any work around or other alternate solutions for these > > sort of cases. > > > As noted in my reply at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > the issue is a Mailman bug which is fixed in the next release. It has to > do with the fact that the display names are RFC 2047 encoded and not the > particular encoding. > > Actually, the fix at > https://gitlab.com/mailman/mailman/-/merge_requests/841 depends on > https://gitlab.com/mailman/mailman/-/merge_requests/652 which was > released in Mailman 3.3.2. A complete patch for versions < 3.3.2 is > attached. > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 2 months

[MM3-users] Re: New year releases!

by Mark Sapiro

On 1/4/23 13:54, Dan Caballero wrote: > I'm attempting this upgrade in my test environment which is a Docker container with Python 3.9.10 virtual environment. I was able to upgrade all the Python requirements but when I run mailman-web migrate I get an error. It seems related to the mailman-web package. See output below. > > > "(mailmanve) mailman@1d0e3a230c94:/var/www/mailman-www$ mailman-web migrate > Traceback (most recent call last): > File "/opt/mailmanve/bin/mailman-web", line 33, in <module> > sys.exit(load_entry_point('mailman-web==0.0.6', 'console_scripts', 'mailman-web')()) > File "/opt/mailmanve/lib/python3.9/site-packages/mailman_web/manage.py", line 37, in main > execute_from_command_line(sys.argv) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line > utility.execute() > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/__init__.py", line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 402, in run_from_argv > self.execute(*args, **cmd_options) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 448, in execute > output = self.handle(*args, **options) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 96, in wrapped > res = handle_func(*args, **kwargs) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/commands/migrate.py", line 97, in handle > self.check(databases=[database]) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 475, in check > all_issues = checks.run_checks( > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/checks/registry.py", line 88, in run_checks > new_errors = check(app_configs=app_configs, databases=databases) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/checks/urls.py", line 14, in check_url_config > return check_resolver(resolver) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/checks/urls.py", line 24, in check_resolver > return check_method() > File "/opt/mailmanve/lib/python3.9/site-packages/django/urls/resolvers.py", line 494, in check > for pattern in self.url_patterns: > File "/opt/mailmanve/lib/python3.9/site-packages/django/utils/functional.py", line 57, in __get__ > res = instance.__dict__[self.name] = self.func(instance) > File "/opt/mailmanve/lib/python3.9/site-packages/django/urls/resolvers.py", line 715, in url_patterns > patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module) > File "/opt/mailmanve/lib/python3.9/site-packages/django/utils/functional.py", line 57, in __get__ > res = instance.__dict__[self.name] = self.func(instance) > File "/opt/mailmanve/lib/python3.9/site-packages/django/urls/resolvers.py", line 708, in urlconf_module > return import_module(self.urlconf_name) > File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1030, in _gcd_import > File "<frozen importlib._bootstrap>", line 1007, in _find_and_load > File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 680, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 850, in exec_module > File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed > File "/var/www/mailman-www/urls.py", line 20, in <module> > from django.conf.urls import include, url > ImportError: cannot import name 'url' from 'django.conf.urls' (/opt/mailmanve/lib/python3.9/site-packages/django/conf/urls/__init__.py)" In Django 3.1 django.conf.urls.url was a deprecated alias to django.urls.re_path and in Django 4.0 it was removed. See, e.g. <https://docs.djangoproject.com/en/3.2/ref/urls/> and <https://docs.djangoproject.com/en/4.0/ref/urls/>. However, the above Traceback doesn't identify which module contains the from django.conf.urls import include, url import. If I look through our sources, I only find this import in mailman-suite/mailman-suite_project/urls.py as an example. You need to look at your urls.py files. Try something like grep -r 'from django.conf.urls import include, url' /opt/mailmanve/lib/python3.9/site-packages/ to find which module contains that import. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Problems after upgrading from bullseye to bookworm

by Thomas Ward

FYI I updated my workaround on the linked issues on Gitlab to reflect this. Technical Note that this may not apply after the PDM backend updates which are in the works to not normalize metadata (which causes this problem). I have not tested a fresh setup yet since the issue was first identified but it is possible the issue is easily resolved once updated versions of these flufl libraries land in PyPI with the pdm backend fixes in place for the build envs of those libraries. Sent from my Galaxy -------- Original message -------- From: Mark Sapiro <mark(a)msapiro.net> Date: 6/26/23 16:23 (GMT-05:00) To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Problems after upgrading from bullseye to bookworm On 6/26/23 12:35 PM, Ken Alker wrote: > I'm brand new to this, so take this with a grain of sale, but, I had a similar problem a few days ago, however, mine was "flufl.i18n>=3.2". Perhaps the same thing is happening with flufl.lock (but that didn't bite me). > > I solved my problem by following this: <https://gitlab.com/mailman/mailman/-/issues/1085> and, ultimately modifying "$VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires.txt" per that thread (see <https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929> by Thomas Ward section called "The WORKAROUND"). Maybe you need to do the same thing, but for flufl.lock. Yes, the same issue now affects flufl.lock as well as flufl.i18n. You will need to change both flufl.lock->flufl_lock and flufl.i18n->flufl_i18n. -- 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 teward(a)thomas-ward.net

3 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I have installed rubygem-sass and added the config to settings.py previously and even executed this command: # Copy all the static files to one single location. $ python2 manage.py collectstatic I tested the commands you suggested and this is what I got: (env2) [mailman@localhost mailman-suite_project]$ pwd /var/lib/mailman/mailman-suite/mailman-suite_project (env2) [mailman@localhost mailman-suite_project]$ django-admin collectstatic --clear No Django settings specified. Unknown command: 'collectstatic' Type 'django-admin help' for usage. El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > find them: > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > > > > > Should I run any command to activate the CACHE dir? > > > You need to ensure you have a working sass compiler. As I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > Then you need to run commands like > > django-admin collectstatic --clear > django-admin compress > > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

9 years

[MM3-users] Re: Hyperkitty Text/Markdown/HTML

by Mark Sapiro

On 9/8/25 15:38, Sam Darwin via Mailman-users wrote: > > Or, the more the topic is discussed, I see there are two parts. Hyperkitty rendering is one of them. The other being to find a way to sanitize HTML of outgoing emails. If you want to accept HTML in posts, you should ensure that only trusted users can post. This is good practice anyway to avoid spam on the lists. Then you don't have to be too concerned about malicious HTML. >> I was asking if you envisioned that a text/html part outside of a multipart/alternative part would cause mailman to create a text/plain alternative and package it with the text/html part in a multipart/alternative part. But if that was not your intent, OK. > > I hadn't thought about that situation. > > Maybe it is relevant after all. And then, you said that you are not interested in doing that. It might need to be investigated along with these other features. Not sure. You can currently convert HTML to plain text, but that replaces the HTML. I understand you want both so your users have the option of seeing one or the other depending on MUA settings, but I don't see a demand for a feature like that. >> The issue is not in the plain text converted from the HTML by Mailman's Convert html to plaintext feature. The issue is in the text/plain alternative created by Yahoo when a message is composed as "rich text" and created by Yahoo as multipart/alternative. Were you looking at that text/plain alternative part from Yahoo., i.e. what you see in the outgoing mail if Collapse alternatives is Yes. > > The list's settings are Collapse alternatives=Yes and Convert html to plaintext=YES. Standard "plain" URLs are ok, but I was just now able to replicate some sort of problem. Using the yahoo toolbar, a fully HTML hyperlink with an href and name failed to render in plain text. It resulted in just plain text without appearing as a "link". If you are saying it resulted in the URL being rendered in the text/plain alternative as a text string, that is not what I see. I just composed a message from Yahoo to a non-yahoo address. I created the message in Yahoo's HTML editor. It simply said "Hi mark. Here's a link." after which I pasted today's Google Doodle link. In the resultant message the HTML part rendered as Hi mark. Here's a link. Google Search where "Google Search" was the above link I had pasted and this was also followed by a Google Search graphic which was also the same link. However the text/plain part in its entirety (minus my signature) was > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: quoted-printable > > Hi mark. Here's a link. Google Search > > |=20 > |=20 > | |=20 > Google Search > > > | > > | > > | > > > > The display text "Google Search" was in the text plain part, but the text of the link itself appeared nowhere in the text/plain part > interesting... The future plan would be to set all filtering to NO. All MIME parts delivered. But then, what if a plain-text version is missing somehow. Then the message will contain only the HTML. But if you do that, malicious HTML and missing plain text will be the least of the things to be concerned about. All sorts of malicious malware can be attached to email in other than HTML parts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

[MM3-users] Re: 'Failed adding message' error when migrating a list from mailman2 to mailman3

by Prasanth Nair

Thank you, Mark. Kind regards, Prasanth On Thu, 14 Oct 2021 at 19:17, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/14/21 9:04 AM, Stephen J. Turnbull wrote: > > Prasanth Nair writes: > > > > > *2%Failed adding message <mailman.2.1593699619.32248>: 'ascii' codec > can't > > > encode character '\ufffd' in position 252: ordinal not in > range(128).* > ... > > > I ran the check_hk_import script before migrating and it was not > > > giving any error. > > > > In order to catch this kind of error, the check script would have to > > pretty much do the import but throw it away. > > > The check_hk_import script > <https://www.msapiro.net/scripts/check_hk_import> is designed to detect > and report conditions which would cause the django hyperkitty_import > process to abort and stop processing the mbox. It doesn't catch errors > like the above, but these are non-fatal and just cause the offending > message to be skipped. > > As Steve says, the Message-ID was reported so find it in the mbox and if > you want it in the archive, extract it from the mbox, fix it and then > just rerun the import with just that message as input[1] and a > --since=1970-01-01 option. > > Note the issue could be in a header, but also could be in a body part > implicitly or explicitly declared as charset="us-ascii". > > -- > 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/ >

4 years, 10 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Odhiambo Washington

I'll create the merge request. On Sat, Jan 28, 2023, 21:49 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/28/23 09:39, Odhiambo Washington wrote: > > Now that you have mentioned > > > https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v…, > , > > please show me how to import it, edit. Then I can submit a diff. > > Alternatively, I'd love to be given access to edit that document (and the > > edit can be reviewed before getting published) to make it easy to follow > by > > someone with zero python background. > > I am willing to invest some time in improving it for laymen. > > > There are multiple ways to proceed. The simplest is to just download > > https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v… > (there's a download button on that page), edit that and post the edited > file somewhere where we can get it to look at. > > The better way is more complex. That way is for you to create a personal > project space at https://gitlab.com/users/sign_up and clone the > mailman/mailman-suite-doc project into your personal space and edit it > there and then create a merge request to merge your edits into the > mailman/mailman-suite-doc project. GitLab documentation is at > https://gitlab.com/help > > -- > 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 odhiambo(a)gmail.com >

3 years, 6 months

[MM3-users] Re: cannot bind to lmtp host address through lmtp port(OSError: [Errno 99] error while attempting to bind on address: cannot assign requested address)

by Mark Sapiro

On 10/18/22 11:28, Paul Ssekamatte via Mailman-users wrote: > i have successfully set up mailman3 instance by following the guide at https://gitlab.com/mailman/mailman-suite-doc/blob/master/source/install/vir… and from this mailing list. > my setup uses an alias domain i.e the mail server is different from the lists server. That is not what alias domains are for. You do not want an alias domain. > I have successfully created an alias domain and mailing list through Postorius but I keep getting this error in syslog. > OSError: [Errno 99] error while attempting to bind on address ('xxx.xx.xx.xx', 8024): cannot assign requested address. > Even when I change the port number, I still get the same error > Kindly assist. First, remove the Alias Domain from your domains. > here is my mailman.cfg config > [paths.here] > var_dir: /opt/mailman/mm/var > > [mailman] > layout: here > site_owner: postmaster(a)mail.example.com > > [database] > class: mailman.database.postgresql.PostgreSQLDatabase > url: postgres://mailman:#passwd@localhost/mailman > > [archiver.prototype] > enable: yes > > # For the HyperKitty archiver. > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > > [shell] > history_file: $var_dir/history.py > > [mta] > verp_confirmations: yes > verp_personalized_deliveries: yes > verp_delivery_interval: 1 > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: mail.example.com The above is wrong. You want the default lmtp_host: 127.0.0.1 > lmtp_port: 8024 > smtp_host: mail.example.com smtp_host should be the mail server, not the list host. Is it? > smtp_port: 25 > configuration: python:mailman.config.postfix These next 3 do not belong in mailman.cfg. They are Postfix main.cf settings: > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no and this next one is a Mailman 2.1 mm_cfg.py directive and is not for Mailman 3. > POSTFIX_STYLE_VIRTUAL_DOMAINS= ['example.com'] > > /etc/mailman3/settings.py file is as follows not relevant for this issue. > /etc/postfix/main.cf is as follows > smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) > biff = no > append_dot_mydomain = no > readme_directory = no > compatibility_level = 2 > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases > mydomain = example.com > myhostname = lists.example.com > mydestination = $myhostname, localhost.$mydomain, localhost > relayhost = mail.example.com > myorigin = $mydomain > mynetworks = 127.0.0.0/8, 10.0.0.0, 192.0.0.1, [::ffff:127.0.0.0]/104 [::1]/128 > mynetworks_style = subnet > mailbox_size_limit = 4096000000 > #message_size_limit = 2048000000 > recipient_delimiter = + > inet_interfaces = all > #inet_protocols = all > inet_protocols = ipv4 > unknown_local_recipient_reject_code = 550 > owner_request_special = no > virtual_mailbox_domains = example.com You probably don't want this, at least not if the mailman server is example.com > virtual_mailbox_base = /var/vmail > virtual_uid_maps = static:20000 > virtual_gid_maps = static:20000 > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap and you don't want this virtual_alias_maps. > postfix domains as follows: > lists.example.com example.com > > postfix lmtp as follows: > testlist(a)lists.example.com lmtp:[mail.example.com]:8024 > testlist-bounces(a)lists.example.com lmtp:[mail.example.com]:8024 > testlist-confirm(a)lists.example.com lmtp:[mail.example.com]:8024 The host in lmtp: is the Mailman server. > postfix vmap as follows: > testlist(a)example.com nmutest(a)lists.example.com > testlist-bounces(a)example.com nmutest-bounces(a)lists.example.com > testlist-confirm(a)example.com nmutest-confirm(a)lists.example.com You don't want that at all. -- 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: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

Looking at the code in gitlab it looks like it wasn’t merged until 1.3.6: https://gitlab.com/mailman/postorius/-/blob/1.3.6/src/postorius/urls.py#L53 But it’s not in 1.3.5: https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49 Thats ok, I’m going to 1.3.6 in a few days so that should solve my issue. -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:39 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 7:27 PM, Simon Coggins wrote: > Oops sorry I hit send to soon. If I try to go > to /lists/listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests> > <http://listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests>> I get a 404, it > looks like unsubscription_requests > <http://listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests>> isn’t in my > urls.py list for Postorius? It should be. It was added by https://gitlab.com/mailman/postorius/-/commit/0aba874cae15b1baae2839dca57d3…<https://gitlab.com/mailman/postorius/-/commit/0aba874cae15b1baae2839dca57d3…> -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years, 9 months

Search results for query "sapiro"