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

[MM3-users] Re: No option 'postmap_command' in section: 'postfix'

by Mark Sapiro

On 1/30/23 02:44, Odhiambo Washington wrote: > The documentation > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> > says that I need to create /path/to/postfix-mailman.cfg containing: > [postfix] > transport_file_type: regex > > Then append the path to the [mta] section of mailman.cfg, viz: > > [mta] ... > configuration: /path/to/postfix-mailman.cfg > > That is exactly what I have done on my test platform, but I get the error > below when creating a list. > Perhaps I overlooked something? ... > "/opt/mailman/venv/lib/python3.9/site-packages/mailman/mta/postfix.py", > line 87, in __init__ > self.postmap_command = mta_config.get('postfix', 'postmap_command') > File "/usr/local/lib/python3.9/configparser.py", line 792, in get > raise NoOptionError(option, section) > configparser.NoOptionError: No option 'postmap_command' in section: > 'postfix' This is a bug. Whether it is a bug in documention or code is not completely clear. Current code requires there be a `postmap_command:` setting in the [postfix] configuration even though it isn't used if `transport_file_type:` is set to regex. You can fix this in one of two ways. Either apply this patch ``` --- a/src/mailman/mta/postfix.py +++ b/src/mailman/mta/postfix.py @@ -84,9 +84,10 @@ class LMTP: def __init__(self): # Locate and read the Postfix specific configuration file. mta_config = external_configuration(config.mta.configuration) - self.postmap_command = mta_config.get('postfix', 'postmap_command') self.transport_file_type = mta_config.get( 'postfix', 'transport_file_type') + if self.transport_file_type == 'hash': + self.postmap_command = mta_config.get('postfix', 'postmap_command') def create(self, mlist): """See `IMailTransportAgentLifecycle`.""" ``` (watch for possible wrapped lines in above) or add postmap_command: unused to /path/to/postfix-mailman.cfg. Note however that hash tables for Postfix are more efficient than regex tables and the only reason we support regex tables is for a Docker container that doesn't have Postfix installed in the Mailman container. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/

by Mohsen Masoudfar

Sorry, I found it! Thanks Mohsen -----Original Message----- From: Mohsen Masoudfar <mmasoudf(a)aaas.org> Sent: Wednesday, December 28, 2022 2:49 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/ [EXTERNAL EMAIL] Thank you Mark for your help. I see fedora under Django administration: Home > Social Accounts > Social Accounts as a provider listed, but we do not use it and I would like to remove it. So far I did not find a way to delete it. We do not need Hyper Kitty either, because we do not archive any emails. I appreciate if you could point me how I may delete Fedora as a provider. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, December 27, 2022 4:25 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/ [EXTERNAL EMAIL] On 12/27/22 10:27, Mohsen Masoudfar wrote: > Hi, > I am getting the following errors starting some days ago. It is unclear to me what is causing this. I searched internet, there are some similar reports that mention bugs causing this. I am running mailman3 as Ubuntu 18 package and they do not provide any update for this. These are probably from some spammer trying to post to the sec_g_zoom(a)listserv2.aaas.org list from hyperkitty and trying to login via the fedora OpenID app which is not properly configured on your server. Do you actually want to support fedora as an OpenID provider? If not, you might remove 'django_mailman3.lib.auth.fedora', from INSTALLED_APPS in your Django settings. Otherwise, see https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdjango-al… -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… This message sent to mmasoudf(a)aaas.org _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… This message sent to mmasoudf(a)aaas.org

2 years, 8 months

[MM3-users] Re: Custom Archiver

by Mark Sapiro

On 4/1/23 16:33, Peter Knowles wrote: > Mark, > > The whole reason I'm developing my own "frontend" for both "list management" and "archive" access is because Python isn't really the language I speak... I'm a PHP guy, and so I'm working to build with the language I know and love, while utilizing Mailman for what it does best... In addition to implementing the frontend the way I want it (expose/hide feature that are useful/unuseful to our users), I want to fully customize the visual appearance to represent the SaaS offering properly. This is exactly the reason why Mailman core was decoupled from archiving and the web UI. HyperKitty and Postorius were developed because we knew that almost no one would use Mailman core without archiving and a web management UI, but we always hoped that others might develop and contribute other web based archiving and management interfaces. Brian Carpenter of EMWD who tragically died of COVID did exactly that with his Affinity and Empathy PHP applications that interface with Mailman core via the REST API. EMWD hosts lists that use those interfaces, and had Brian not died, some version of those might be open sourced, but his initial thrust was to keep them proprietary for his business reasons. There is an early description of Brian's concept for Affinity at https://gitlab.com/mailman/affinity. > *** we're not try to hide that Mailman is in the equation, just how the overall interface is visually represented *** > > That all being said, on a slight segway... Aside from using the REST API, is it practical or possible to manipulate the database directly? That is, in doing so would it just work or are there extra moving parts when an API request is issued? It probably is possible, but I would definitely discourage it. The REST API should provide everything you need without your having to reimplement everything it does. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Setting up Admin Account

by Mark Sapiro

On 11/14/2017 08:13 PM, Pierre Abbat wrote: > So I installed a crontab for list and read about configuring the DB (I think > I'll use SQLite). I got to http://docs.mailman3.org/en/latest/config-web.html > . Because of the dollar sign, I assume that the commands are to be run as > list. Here's what I did: > > root@lists:~# ls > root@lists:~# sudo list > sudo: list: command not found The command you want there is something like sudo -u list bash or whatever shell you want. > root@lists:~# su list > This account is currently not available. Probably because the default shell for list is nologin. But, I see you eventually figured it out. > root@lists:~# ls /var/list > ls: cannot access '/var/list': No such file or directory > root@lists:~# locate mailman-suite_project > root@lists:~# mkdir /var/list > root@lists:~# chown list.list /var/list > root@lists:~# su list > This account is currently not available. > root@lists:~# man su > root@lists:~# su -s /bin/bash list > list@lists:/root$ cd > list@lists:~$ cd mailman-suite_project > bash: cd: mailman-suite_project: No such file or directory > list@lists:~$ mkdir mailman-suite_project > list@lists:~$ cd mailman-suite_project > list@lists:~/mailman-suite_project$ python manage.py createsuperuser > python: can't open file 'manage.py': [Errno 2] No such file or directory > list@lists:~/mailman-suite_project$ locate manage.py > /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.py > /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.pyc > /usr/local/lib/python2.7/dist-packages/example_project/manage.py > /usr/local/lib/python2.7/dist-packages/example_project/manage.pyc > /usr/local/lib/python3.5/dist-packages/falcon/bench/dj/manage.py > > Which manage.py should I use? Probably /usr/local/lib/python2.7/dist-packages/example_project/manage.py but your apparent lack of basic system administration skills is not making things easy for you. You might be better off looking at <http://docs.list.org/en/latest/prodsetup.html#mailman-3-in-docker>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: New messages not being archived

by Mark Sapiro

On 7/15/21 12:55 PM, Sarah H wrote: > > The log is mostly these three errors repeatedly with the same above wall of html between them, some of them end with (404) after the last html tag indicating url not found and browsing to them gives the same custom 404 page for postorius. The code is if result.status_code != 200: logger.error("HyperKitty failure on %s: %s (%s)", url, result.text, result.status_code) raise ValueError(result.text) > Jul 15 12:37:08 2021 (471314) HyperKitty failure on http://lists.client.org/hyperkitty/api/mailman/archive: So the above log entry should be followed by result.text and result.status_code. The next entry below is from the `raise ValueError(result.text)` What do you get from curl http://lists.client.org/hyperkitty/api/mailman/archive and what if you change the scheme in the base_url setting to https? > Jul 15 12:37:08 2021 (471314) Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message > raise ValueError(result.text) > ValueError: And this one below is is because of the above exception. > Jul 15 12:37:08 2021 (471314) Exception in the HyperKitty archiver: > > I was able to find (about 5000 lines up in the log for a single post attempt... it's a bit excessive to print the html response every error) this when I dug through instead of tailing the last 500 lines. > > [15/Jul/2021:12:37:06 -0700] "GET /3.1/addresses/sarah.h@email HTTP/1.1" 200 380 "-" "GNU Mailman REST client v3.3.2" > > and at the start of the block: > > [15/Jul/2021:12:37:03 -0700] "GET /3.1/lists/admin.lists.client.org/member/sarah.%40email HTTP/1.1" 200 516 "-" "GNU Mailman REST client v3.3.2" > Jul 15 12:37:05 2021 (471317) ACCEPT: <162637782380.3116.619498070458942231@sysname> These are from the Mailman REST API and are not relevant to your issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Hyperkitty no longer archiving

by Mark Sapiro

First, my apologies for not taking note of your MAILMAN_ARCHIVER_FROM setting in your OP. On 11/22/22 08:52, Hirayama, Pat wrote: > Steve wrote: >> 2. Does settings.py have "from settings_local import *" in it? > > Yes. I assume that overrides the MAILMAN_ARCHIVER_FROM and other related settings defined at the top of the settings.py file? Or should I update settings.py based on what is in settings_local.py? Assuming the `from settings_local import *` is at the end of settings.py, anything defined in settings_local.py will override the definition in settings.py. There's no need to change settings.py. >> 3. Are there multiple copies of settings.py lying around? > > Well, there are these: > > ./usr/local/lib/python3.8/site-packages/rest_framework/settings.py > > ./usr/local/lib/python3.8/site-packages/postorius/doc/settings.py > > ./usr/local/lib/python3.8/site-packages/django_q/tests/settings.py > > ./usr/local/lib/python3.8/site-packages/django_extensions/settings.py > > ./usr/local/lib/python3.8/site-packages/mailmanclient/restobjects/settings.py > > ./usr/local/lib/python3.8/site-packages/example_project/settings.py > > > Only the last has MAILMAN_ARCHIVER_FROM defined in it, but I was assuming from the example_project subdirectory name that this was just a sample file, and besides, "from settings_local import *" is also set in it. Yes, those are all samples. The ``` ERROR 2022-11-22 00:25:40,365 7 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.31.0.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured ``` message comes from https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/mailma… which only occurs if '172.31.0.1' is not in MAILMAN_ARCHIVER_FROM. Given that it is in MAILMAN_ARCHIVER_FROM as defined in settings_local.py, the only thing I can conclude is that the Django settings actually used is not the settings.py you think it is. I don't know offhand even what wsgi service is used in the docker container or how it is configured, but it needs to set its working directory to the directory containing settings.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: cc'd e-mail addresses rewritten with @invalid.domain

by Mark Sapiro

On 9/23/20 12:48 PM, pwilliam(a)fredhutch.org wrote: > Hi Mailman Users, > > I've done some more testing with this issue and have determined that this seems to be an issue with how commas within the display name in cc'd messages are being processed with messages sent from the Outlook client. > > Here are some test scenarios. Note I set the mailing list I was testing with to hold messages in moderation. Once the message was held I copied the information from the headers directly from Postorius held message information into the space below: > > Test Scenario 1: > Display name in Outlook: Williamss, Peterr C > Outcome: Does not work as intended. The CC address is formatted as Williamss(a)invalid.domain in messages received by mailing list members, oddly the "Peterr C" part of the display name is not present anywhere in the CC addresses received by mailing list members. > Header information from held message in Postorius > CC: "os-x-lion(a)lists.test.org" <os-x-lion(a)lists.test.org>, > "Williamss, > Peterr C" <peterbw(a)test.com> "Williamss, Peterr C" <peterbw(a)test.com> is correct for how this address spec should be represented. If in fact, it is split into two lines "Williamss, Peterr C" <peterbw(a)test.com> as it appears above, it looks to me as if the actual header should be > CC: "os-x-lion(a)lists.test.org" <os-x-lion(a)lists.test.org>, "Williamss, Peterr C" <peterbw(a)test.com> but is being folded on the whitespace between Williamss and Peterr. This is <https://gitlab.com/mailman/mailman/-/issues/725>, fixed at <https://gitlab.com/mailman/mailman/-/merge_requests/652>. The fix will be in the next (3.3.2) release of Mailman core. This is really an Outlook issue. See <https://gitlab.com/mailman/mailman/-/issues/725#note_351314868> for why folding within a quoted string is allowed, but in cases like this SHOULD not be done. -- 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: Installing mailman 3

by Rafael Mora

As Abhilash said I checked the django configuration for email but nothing happens when the program sends the confirmation email. Is there any other configuration file for django emails? On Tue, Aug 1, 2017, 23:18 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

[MM3-users] Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 4/19/19 6:33 PM, kevin(a)coastalaska.org wrote: > We have a couple of people trying to subscribe to our list but receive an error similar to: > {"title": "409 Conflict", "description": "Subscription request already pending"} > > If I try to Mass Subscribe them in Postorius I get this error: > HTTP Error 409: b'{"title": "409 Conflict", "description": "Subscription request already pending"}' > > In Postorius I don't see them hung up in Subscription requests. Postorius since 1.2.3 does not show subscription requests waiting user confirmation, only those waiting moderator approval. Thus, if the list's subscription policy is confirm or confirm then moderate, the subscribing user will be sent an email requesting confirmation. If the user hasn't answered that email, the request is pending user confirmation, and since 1.2.3, you won't see it in Postorius. [Update: this is fixed in 1.2.4] > What to do? 1) have the user find the confirmation request email and confirm, or 2) wait for the request to expire (default 3 days) 3) using mailman shell or the REST api or direct interaction with the database, find the token and confirm it. A shell example is ``` mailman shell -l your.list.id Welcome to the GNU Mailman shell The variable 'm' is the your.list.id mailing list >>> util = getUtility(IPendings) >>> list(util.find(mlist=m,pend_type='subscription')) ``` This returns a list of items like ('hex_token'), {'token_owner': 'subscriber', 'email': 'user(a)example.com', 'display_name': 'Jane User', 'when': '2019-04-09T01:26:08', 'type': 'subscription', 'list_id': 'your.list.id'}) You then do ``` >>> util.confirm('hex_token') ``` Note that https://gitlab.com/mailman/postorius/issues/314 which was responsible for removing the subs waiting user confirmation from the Postorius listing suggested "there could be a different place to see the ones pending user approval, so that a moderator can look and/or delete those.", but that hasn't been done. [Update: this is fixed in 1.2.4] -- Mark Sapiro mark(a)msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Mark Sapiro

On 1/16/21 7:49 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > I can't find any log entry which indicate a problem with this subscription request. > The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. It is unclear and confusing, but the requests are not in the _request table. See <https://gitlab.com/mailman/mailman/-/issues/768#note_415536043>. So this is normal. > The token is found in the pended table: > > +-----+------------------------------------------+---------------------+ > | id | token | expiration_date | > +-----+------------------------------------------+---------------------+ > | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | > +-----+------------------------------------------+---------------------+ > > These are the relevant entries in the pendedkeyvalue table: > +------+--------------+-------------------------------------+-----------+ > | id | key | value | pended_id | > +------+--------------+-------------------------------------+-----------+ > | 1130 | type | subscription | 115 | > | 1131 | list_id | "********************" | 115 | > | 1132 | email | "***********************@*********" | 115 | > | 1133 | display_name | "" | 115 | > | 1134 | when | "2021-01-06T16:17:38" | 115 | > | 1135 | token_owner | "moderator" | 115 | > +------+--------------+-------------------------------------+-----------+ > > Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Adding to the _request table won't help. Try confirming by emailing listname-confirm+4d6b4b11266c7332684c5a492eb3f92c531f761b(a)list.domain You could also try confirming via mailman shell mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/app/subscriptions.py", line 570, in confirm raise LookupError LookupError In my case, I get the LookupError because the token doesn't exist, but I think it should work for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

Search results for query "sapiro"