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

[MM3-users] Re: templates

by Odhiambo Washington

On Fri, May 5, 2023 at 12:38 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/4/23 13:13, Odhiambo Washington wrote: > > Isn't that the same thing as not having them in the FS? > > If your installation is in a venv for example, the base templates are in > venv/lib/python3.x/site-packages/mailman/templates/. Isn't that part of > the FS? > <Confession> This is new knowledge that I did not posses previously as I have never seen it mentioned anywhere in the documentation that I have read. Maybe I was going to come to it one day. In the documentation that I have read, even the one from this <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>, I never imagined about the presence of some defaults so I copied the ones that you shared and edited them. I had made a point of asking a question around this statement: "There are several default templates that have incorrect or generic URLs for the web UI. To make these better, I installed these templates in /opt/mailman/mm/var/templates/site/en/ as follows.." from the above link, but it kinda escaped me. I had wondered where they were. In those days, MM3 installation process was still as scary as hell for many people, me being one of them, or was it the scare of the snake (Python) :-) True story - also one that can be gleaned from the myriad stupid questions I asked on the MM3 list over the years - it took me years to get to wrap my head around MM3! I find it hard to imagine that I have become a great supporter for this thing that scared me for ages, since the days when it was in BETA. The venv example has made the process very easy. In fact, after you and Abhilash helped me internalize what a venv is, I have been able to comfortably run other projects in virtualenv. These days I can install MM3 in just a few hours - getting all the components running - Core, Web, MTA, and Apache (whether with uWSGI, mod-wsgi or Gunicorn). </Confession> And I continue to learn new things everyday. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 10 months

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Henrik Rasmussen

Henrik Rasmussen wrote: > Abhilash Raj wrote: > > On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro > > wrote: > > each other, but Postfix is trying to deliver > > mail via lmtp to > > [172.19.199.2]:8024. Mailman's lmtp runner should be running and > > listening on port 8024. Either that is not the case or that port is not > > exposed to Postfix on IP 172.19.199.2. > > Right, that is what I was wondering, you verify that by using telnet > > on the specified IP and Port (172.19.199.2:8024). > > Yes, the postfix container listens on 172.19.199.2:8024 > [root@postfix /]# nc -v 172.19.199.2 8024 > Ncat: Version 7.50 ( https://nmap.org/ncat ) > Ncat: Connected to 172.19.199.2:8024. > 220 mailman-core GNU Mailman LMTP runner 2.0 > > > docker-compose ps lists all the running containers, > > do you see all > > the containers running? > > That also seem to be okay > [root@lstapp01pl ~]# docker ps > CONTAINER ID IMAGE COMMAND CREATED > STATUS PORTS > NAMES > bddc80799b8c maxking/mailman-web:0.2 "docker-entrypoint.sh" 16 hours ago > Up 16 hours 8000/tcp, 8080/tcp > mailman-web > be098b18aeca maxking/mailman-core:0.2 "docker-entrypoint.sh" 16 hours ago > Up 16 hours 8001/tcp, 8024/tcp > mailman-core > c47fd8ccf19d postgres:9.6 "docker-entrypoint.sh" 16 hours ago > Up 16 hours 5432/tcp > mailman_database_1 > 699264501acd mailman3-mime_htmlizer "container-entrypoint" 16 hours ago > Up 16 hours 8080/tcp > postmime > 90f381a74709 mailman3-postfix:v1.1 "./entrypoint.sh" 16 hours ago > Up 16 hours 0.0.0.0:465->465/tcp, 0.0.0.0:587->587/tcp, > 0.0.0.0:26->25/tcp postfix > > And netstat in the mailman-core container shows: > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 0 172.19.199.2:8024 0.0.0.0:* LISTEN` > > > You mentioned that Mailman is not receiving enough > > emails, do you get > > any emails from Mailman? I am trying to see if this is a perf problem > > or if Mailman's LMTP isn't reachable at all. > > Mailman do send out mails like when someone signs up for an account. > Thanks to both. And the runner is running: `Sep 19 06:55:06 2019 (36) b'220 mailman-core GNU Mailman LMTP runner 2.0`

6 years, 6 months

[MM3-users] Re: Mailman installation results in KeyError: 'env_py'

by Marvin Gülker

Am 22. October 2017 um 07:49 Uhr -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > or you can install the fix at Thanks. Applying this patch makes it work. Now I've got a different problem, though. I can't get it to connect to Postfix for sending emails it appears. After I created a superuser account using $ python manage.py createsuperuser as described on <http://postorius.readthedocs.io/en/latest/setup.html>, I tried to login using this credentials into Postorius. It then reported it sent a confirmation email to me (for an account I created on commandline?!), but Postfix' logs reveal that it didn't; there's not even a sign of an attempted delivery in /var/log/mail.log. I've configured the Postfix configuration in mailman.cfg like this: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix as was outlined on <http://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html>. mailman-suite's settings.py contains: # Change this when you have a real email backend EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 which was described on <http://docs.list.org/en/latest/config-web.html>. For completeness, the following is in Postfix' main.cf, but is not the cause of the problem as it affects the incoming direction, whereas I refer to the outgoing one: transport_maps = hash:/home/mailman/var/data/postfix_lmtp local_recipient_maps = hash:/home/mailman/var/data/postfix_lmtp I failed to locate any kind of logging information about the failed email, so I don't even know where I should start looking for the problem. var/logs/smtp.log is empty in the mailman directory, and likewise is logs/mailmansuite.log in the mailman-suite_project directory. That being said, the enormous number of configuration files to consider and dozens of cross-references to other pages in the docs make the installation guide hard to follow; it also lacks logical structure in my opinion, when it refers to parts of the configuration which are later explained. For someone like me who never programmed a Django application (Ruby dev) this is all pretty cryptic. Especially, that some parts of information are on <http://docs.list.org/en/latest/index.html> whereas other parts are scattered over readthedocs.io makes it very complicated. Greetings Marvin -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

8 years, 5 months

[MM3-users] Re: Subscription issue with ghost confirmations

by Brian Carpenter

On 10/29/20 11:33 AM, Mark Sapiro wrote: > On 10/29/20 5:23 AM, Brian Carpenter wrote: >> I have a list owner who had his subscription policy set to confirm. >> Apparently that was too hard for his list members to handle so he >> changed it to moderate only. If someone sent a subscription request that >> needed to be confirm, did not respond to it, and then tried subscribing >> again after the member policy changed to moderate, their 2nd >> subscription attempt still shows up in the confirmation queue. Is that >> normal behavior. My understanding is it is. Please let me know if I am >> wrong here. > > Are you certain that the request waiting confirmation is the second one > and not the first? Good point and I am not sure. I will try to note that if this pops up again. > > >> The real mystery here is when someone tried subscribing again >> (listname-subscribe@listdomain) hours after the subscription policy was >> changed to moderate and they still showed up in the confirm queue. How >> is that possible? I tested the list with two of my addresses and both >> showed up in the moderation queue as expected. As far as I can tell from >> the mailman logs, this was the person's first attempt at subscribing. > > I suspect it was not the first attempt and that the subscription waiting > confirmation was requested when the policy was confirm. The confirmation moderation notice had the date-time stamp that came a few hours AFTER the subscription policy was changed. Also I only saw one confirmation request sent out via Postfix' mail.log. I saw no other for this subscriber. Same thing with the smtp.log. I cannot duplicate this behavior when I try to subscribe. My subscription attempts went straight to moderation. > > The real question is if a user has a subscription waiting confirmation > and the policy is changed to moderate, is a second request rejected > because of the request waiting confirmation. If so, I think this is a > bug which should be fixed. > Do you think this is a bug with Mailman core or my system? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-27 19:36, Jan Eden wrote: > On 2022-11-27 08:01, Mark Sapiro wrote: > > On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > > > > > – but the existing directory /opt/mailman/fulltext_index (and its > > > contents) are readable and writeable by mailman:mailman: > > > > > > > drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ > > > > > > > > -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc > > > > -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg > > > > -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg > > > > -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg > > > > -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg > > > > -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg > > > > -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > > > > > I fail to see where haystack tries (and fails) to create the directory. > > > FWIW, deleting threads is not a problem. > > > > It is uwsgi trying to do this. What user is it running as? Maybe you need to > > add that user to the `mailman` group. > > That's what baffles me – uwsgi is run as the mailman user: > > mailman 3904667 1.3 0.5 129516 62188 ? Ss 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini > mailman 3904668 0.0 0.3 203248 48796 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini > mailman 3904670 0.8 0.6 220436 74464 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini I tried setting permissions on /opt/mailman/fulltext_index to 777 temporarily, but the issue remained (as expected). It occurs in the Whoosh backend of Haystack (whoosh_backend.py, line 132-133): > if self.use_file_storage and not os.path.exists(self.path): os.makedirs(self.path) where self.path is referenced, which is defined in line 110 (as part of the __init__ function): > def __init__(self, connection_alias, **connection_options): > super().__init__(connection_alias, **connection_options) > self.setup_complete = False > self.use_file_storage = True > self.post_limit = getattr(connection_options, "POST_LIMIT", 128 * 1024 * 1024) > self.path = connection_options.get("PATH") Unfortunately, I cannot see where the PATH key for connection_options is defined. - Jan

3 years, 4 months

[MM3-users] Re: Hyperkitty download mbox

by Andrew Hodgson

Mark Sapiro wrote: >On 4/25/21 2:20 PM, Andrew Hodgson wrote: >> Hi, >> >> Hyperkitty 1.3.4. >> >> I am trying to download a complete list mbox by going to all threads view and using the download option. I have tried a couple of tools (Gunzip and Winrar) and both are giving me an unexpected end of file when trying to decompress the gz file. [...] >Depending in the web server configuration, timeouts can occur when downloading large archive mboxes. instead of downloading the entire mbox with <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…>, >do it in pieces by adjusting start and end. e.g. [...] >Although, I don't think timing out is the issue, and I'm not sure what is, but I think it has something to do with messages in the archive. If I try to get the 3 pieces as above, the first piece with start=2008-02-19&end=2012-12-31 works but the others don't and even the smaller Yep there is a problem with an imported mbox which seems to be present somewhere in the archive on all the lists which I imported using that method. Here is a recent trace from the download option: [2021-04-26 08:53:12 +0000] [28181] [ERROR] Error handling request Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 180, in handle_request for item in respiter: File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/views/mlist.py", line 335, in stream_mbox msg = email.as_message() File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py", line 178, in as_message msg["Message-ID"] = "<%s>" % self.message_id File "/usr/lib/python3.7/email/message.py", line 409, in __setitem__ self._headers.append(self.policy.header_store_parse(name, val)) File "/usr/lib/python3.7/email/policy.py", line 145, in header_store_parse raise ValueError("Header values may not contain linefeed " ValueError: Header values may not contain linefeed or carriage return characters I do still have the original mbox files for the imported lists which were on Mailman 2.1. The other thing is when downloading these mbox files I noticed they aren't the raw messages as we had in Mailman 2.1 but modified with headers stripped and email addresses modified. Is there any way to get the raw mbox back as in the option we had in Mailman 2.1? Thanks. Andrew.

4 years, 11 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by David Partain

On Thu, 2021-02-25 at 13:24 -0800, Mark Sapiro wrote: On 2/25/21 6:32 AM, David Partain via Mailman-users wrote: In /etc/mailman3/mailman.cfg I see: class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8&use_unicode=1 Should I change the latter to be something like: url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8mb4&use_unicode=1 Yes, either make it charset=utf8mb4 or I think dropping the charset= option altogether will use the database default, however I'm not clear why this would be the issue as this only controls how Mailman core accesses the database, and your issue is with HyperKitty/Django and its access is controlled by the DATABASES setting in Django's settings which you say do specify 'charset': 'utf8mb4' in OPTIONS. Also, it seems Mailman core is not even using the same database - i.e. `mailman3` whereas Django's is `mailman3web`. Hi Mark, Thanks for being patient with me. I'm still baffled but might have found the problem. I've done the above, to no avail. If I look at the queries being sent to mysql, I see stuff like this: 174 Connect mailman3web@localhost<mailto:mailman3web@localhost> on mailman3web using TCP/IP 174 Query SET sql_mode='STRICT_TRANS_TABLES' 174 Query COMMIT 174 Query SET AUTOCOMMIT = 0 174 Query SET AUTOCOMMIT = 1 174 Query SET AUTOCOMMIT = 0 I note that there is nothing about the charset, so something's clearly wonky. As previously stated, /etc/mailman3/mailman-web.py has the right thing: 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, but that latter is having no effect. I then found /var/lib/ucf/cache/:etc:mailman3:mailman-web.py which doesn't have charset (but does have init_command), but I _think_ that's only about the package management system. So... I found that /usr/share/mailman3-web/settings_local.py is just a link to /etc/mailman3/mailman-web.py (which obviously has the right thing), but what about the .pyc file? # grep -i STRICT_TRANS_TABLES /usr/share/mailman3-web/settings_local.pyc Binary file /usr/share/mailman3-web/settings_local.pyc matches # grep -i charset /usr/share/mailman3-web/settings_local.pyc # It ain't in the .pyc file. Am I overly optimistic that that might the be problem? If so, I'd be grateful if someone'd tell the newbie how to recreate that file without trashing something. Cheers, David

5 years, 1 month

[MM3-users] Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Élodie BOSSIER

Thank you for your response Mark, With Mailman 2.1, the lists were split on their webpage respectively. How could I do same with Mailman 3.3.3 (Tom Sawyer) please ? My domain table SQL have this result : id, mail_host, description, alias_domain 1, ml.franceserv.fr, NULL, local.ml.franceserv.fr 2, ml.viticreation.fr, NULL, local.ml.viticreation.fr mailinglist table SQL : id, list_name, mail_host, list_id, ... 1, bar, ml.franceserv.fr, bar.ml.franceserv.fr, ... 2, viticreation, ml.viticreation.fr, viticreation.ml.viticreation.fr, ... Can I do something ? A patch somewhere ? Shall I wait issues are solved and how long approximatively please ? Which don't reassure me is I can see old discussions about FILTER_VHOST there are 2 years. I can retrieve my own old question there are 2 years when I tried to migrate from Mailman 2 to Mailman 3 : https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and in 2020 you told me it was working for you at this date. It's don't reassure me to retrieve a problem I got there are 2 years. I could set in production my Mailman 3 but the problem is my customers won't understand why they can see the lists of others domains name ... and not sure about the security ... Thank you again. Le 18/02/2022 à 00:33, Mark Sapiro a écrit : > There are issues with FILTER_VHOST due to the fact that mailing lists > do not have a web host attribute. This means when you go to HyperKitty > or Postorius when FILTER_VHOST is True, we look up the domain record > for the web host you are visiting and show you all the lists whose > mail host matches the mail host for the web host domain. This has > nothing to do with alias domains. > > What that means is if all your domains records have a unique mail > host, FILTER_VHOST will work as you expect, but if multiple domains > have the same mail host FILTER_VHOST will show you the lists for the > current web host plus all those with a matching mail host. > > I.e. if in your case, the ml.franceserv.fr domain and the > ml.viticreation.fr domain have the same mail host, FILTER_VHOST won't > separate them. If they have different mail hosts FILTER_VHOST will > separate them. >

4 years, 1 month

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Abhilash Raj

On Sat, Jul 25, 2020, at 2:17 PM, Mark Sapiro wrote: > On 7/25/20 12:54 PM, Odhiambo Washington wrote: > > > > Finally, I have adapted your init script to get some rudimentary one that I > > could use on FreeBSD. > > I have to change /opt/mailman to be owned by mailman3:mailman3 (because I > > have "live" MLs on this server, using mailman-2.1.34. > > I am not sure if they can co-exist. I suppose they could, but what might be > > the security implication, if any?? > > I manage more than one server that supports both Mailman 2.1 and Mailman > 3 running as user `mailman`. I'm not aware of any security issues. > > > > This is what the init script looks like (rudimentary!!): > > (venv) [root@gw /usr/local/etc/rc.d]# less mailman3 > > ### BEGIN INIT INFO > > # Provides: GNU Mailman > > # Short-Description: Mailman3 Service > > # Description: service control for Mailman3 > > ### END INIT INFO > > > > PATH=/opt/mailman/mm/bin:/opt/mailman/mm/venv/bin:/usr/sbin:/usr/bin:/bin:/sbin: > > DESC="GNU Mailman service" > > DAEMON=/opt/mailman/mm/bin/mailman > > NAME=mailman > > USER=mailman3 > > GROUP=mailman3 > > > > # Needed by click > > export LANG=en_US.UTF-8 > > > > # Exit if the package is not installed > > [ -x "$DAEMON" ] || exit 0 > > > > # Load the VERBOSE setting and other rcS variables > > #. /lib/init/vars.sh > > > > # Define LSB log_* functions. > > # Depend on lsb-base (>= 3.2-14) to ensure that this file is present > > # and status_of_proc is working. > > #. /lib/lsb/init-functions > > > > case "$1" in > > start) > > [ "$VERBOSE" != no ] && echo "Starting $DESC" "$NAME" > > # use --force to remove a stale lock. > > /usr/local/bin/sudo -u $USER $DAEMON start --force > > T don't recommend using --force in init scripts. It *shouldn't* matter > because even with --force the master shouldn't break the lock if the pip > that set it still exists, but I prefer not to use it. > > > > ;; > > stop) > > [ "$VERBOSE" != no ] && echo "Stopping $DESC" "$NAME" > > /usr/local/bin/sudo -u $USER $DAEMON stop > > ;; > > status) > > /usr/local/bin/sudo -u $USER $DAEMON status > > ;; > > reopen) > > /usr/local/bin/sudo -u $USER $DAEMON reopen > > ;; > > restart) > > log_daemon_msg "Restarting $DESC" "$NAME" > > /usr/local/bin/sudo -u $USER $DAEMON restart > > ;; > > *) > > echo "Usage: $SCRIPTNAME {start|stop|status|reopen|restart}" >&2 > > exit 3 > > ;; > > esac > > > > It does start mailman3 for sure, but also complains after a few seconds > > with the message: > > > > (venv) [root@gw /usr/local/etc/rc.d]# > > */opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.2b1-py3.7.egg/mailman/rest/wsgiapp.py:180: > > DeprecatedWarning: Call to deprecated function __init__(...). API class may > > be removed in a future release, use falcon.App instead.* > > * **kws)* > > > Hmm... strange, My various MM 3 installs are running falcon 1.4.0, 2.0.0 > and 3.0.0a1 and I don't see this warning, but it is only a deprecation > warning. It doesn't mean it won't work. I have seen this during development and there is an issue open for this[1]. [1]: https://gitlab.com/mailman/mailman/-/issues/733 > > > > But: > > > > (venv) [root@gw /usr/local/etc/rc.d]# ps ax | grep mailman > ... > > It seems Mailman core and the rest runner and its workers are all running. > > > > > > Assuming that I am using mod_wsgi with Apache, and that I have configured > > apache right using > > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > .. > > should I be able to access the MM3 web UI?? > > Yes, I think so. > > > > At that point, I am feeling somewhat confused as to what to try next. > > > > (venv) [root@gw /opt/mailman/mm/var/logs]# less mailman.log > > Jul 25 22:53:16 2020 (40670) Master started > > Jul 25 22:53:18 2020 (42036) bounces runner started. > > Jul 25 22:53:18 2020 (45205) out runner started. > > Jul 25 22:53:19 2020 (41191) archive runner started. > > Jul 25 22:53:19 2020 (46670) retry runner started. > > Jul 25 22:53:19 2020 (44567) nntp runner started. > > Jul 25 22:53:19 2020 (43069) in runner started. > > Jul 25 22:53:19 2020 (46960) virgin runner started. > > Jul 25 22:53:20 2020 (45720) pipeline runner started. > > Jul 25 22:53:20 2020 (47326) digest runner started. > > Jul 25 22:53:20 2020 (43755) lmtp runner started. > > Jul 25 22:53:20 2020 (45922) rest runner started. > > [2020-07-25 22:53:20 +0300] [45922] [INFO] Starting gunicorn 20.0.4 > > [2020-07-25 22:53:20 +0300] [45922] [INFO] Listening at: > > http://127.0.0.1:8001 (45922) > > [2020-07-25 22:53:20 +0300] [45922] [INFO] Using worker: sync > > [2020-07-25 22:53:20 +0300] [54732] [INFO] Booting worker with pid: 54732 > > [2020-07-25 22:53:20 +0300] [55467] [INFO] Booting worker with pid: 55467 > > Jul 25 22:53:21 2020 (42743) command runner started. > > > The above is all fine, but it is just Mailman core. > > > > How do I access the web UI for MM3 now? > > > The Apache config points to /opt/mailman/mm/wsgi.py, a sampole of which > is at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…>. > Do you have that? > > If you installed the Apache config literally, the location for Mailman 3 > is defined by > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> > and the URL would be http(s)://your.server/mm3 - have you tried that? > > -- > 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, Abhilash Raj (maxking)

5 years, 8 months

[MM3-users] Re: Wrong info in moderation mail when held due to match of a header rule

by tlhackque

On 17-Oct-20 14:31, Mark Sapiro wrote: > On 10/17/20 10:39 AM, Torge Riedel wrote: >> The message is being held because: >> >> Header "Yes" matched a header rule >> >> At your convenience, visit your dashboard to approve or deny the >> request. >> >> I think this is wrong, it should read 'Header "x-spam" matched a header >> rule'. Cause the header rule is configured for header "x-spam" and >> pattern "Yes". > > The message is defined as > > 'Header "{}" matched a header rule' > > where {} is replaced with the value of the matching header. I agree it > would be better if it were something like > > 'Header value "{}" matched a header rule for {}:' > > with {}s replaced with the header value and name. That would make it in > your case > > 'Header value "Yes" matched a header rule for x-spam:' > >> I haven't found a bug report for this yet on gitlab. If someone of the >> developers confirm this is wrong, I will file a bug on gitlab for it. > > Please do file a bug. It won't be fixed until after the upcoming 3.3.2 > final release because we not making i18n changes between the candidate > and final releases. Also, if you don't like my suggestion, feel free to > suggest something else. > FWIW, I suggest: Header "{name}": rule matched value "{value}" Name tends to be short and must be simple ASCII. Value can be very long and encoded, so it may wrap. Name will be short and recognizable. Plus the name provides the context for the value - and name:value is the way the header appears in the e-mail. So I think name before value obeys the UI principle of least surprise. I might also add the rule number or config filename:line, as in Header "{name}": rule in {file}:{n} matched value "{value}" This would be helpful when backtracking from a rejected message to the cause. A sample expansion might be: Header "X-Spam": rule in foo.conf:83 matched value "yes"

5 years, 5 months

Search results for query "sapiro"