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

[MM3-users] Re: Link to account

by Lars Bjørndal

Thanks a lot! After further consideration, I will stay with the defaults, e.g. have accounts, archive etc at the same level as mailman3. Lars On Wed, Apr 12, 2023 at 08:32:27AM -0700, Mark Sapiro wrote: > On 4/11/23 23:08, Lars Bjørndal wrote: > > > > I would like to have postorius at .../mailman3 and admin, accounts etc. under .../mailman3/admin .../mailman3/accounts etc. > > > Try this. > > In urls.py > ``` > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), > permanent=True), > ), > path('mailman3/archives/', include('hyperkitty.urls')), > path('', include('django_mailman3.urls')), > path('mailman3/accounts/', include('allauth.urls')), > path('mailman3/admin/', admin.site.urls), > path('mailman3/', include('postorius.urls')), > ] > ``` > > In apache > ``` > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "/mailman3/archives" > "http://127.0.0.1:8000/mailman3/archives" > ProxyPass "/mailman3/accounts" > "http://127.0.0.1:8000/mailman3/accounts" > ProxyPass "/mailman3/admin" "http://127.0.0.1:8000/mailman3/admin" > ProxyPass "user-profile" "http://127.0.0.1:8000/user-profile" > ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" > </IfModule> > ``` > > -- > 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 lars(a)lamasti.net

3 years, 6 months

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

by Mark Sapiro

On 3/1/21 11:53 AM, David Partain via Mailman-users wrote: > 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. I think that's correct. I doubt that that's the problem, but if all else fails, you might just remove it. I don't think that would hurt as it's purpose is just todetect on upgrade of the package if you've changed the file from the distributed one and ask you what you want to do about it. > 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. This is a bit strange: Here's how it works. .pyc files are byte-compiled versions of the corresponding .py file. When Python runs or imports from a .py file, it first looks for a corresponding .pyc file and if that is as new or newer than the .py, it uses the .pyc. If not, it uses the .py and byte-compiles it and if it has permission, writes an updated .pyc Except recent Python3 (at least I think 3.5 and newer doesn't use a .pyc in the same directory as the .py Its uses a __pycache__ directory in the same directory as the .py and within that directory a file like in this case settings_local.cpython-37.pyc (or whatever the python version is) In any case, I would remove the existing settings_local.pyc. That can't hurt, but I'm curious what ls -lR /usr/share/mailman3-web/ shows. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command

by Perry Kollmorgen

Ok, thanks for the information. Regards, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, 10 June 2024 2:10 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command On 6/9/24 5:26 PM, Perry Kollmorgen wrote: > Hi, > > This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. > > I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt > > When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. > > However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. This is a bug. Currently only `mailman create` sends this notice, but as you note, list creation via rest should do it too. I have created https://gitlab.com/mailman/mailman/-/issues/1156 for this. -- 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 pcjkollmorgen(a)hotmail.com

2 years, 4 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/28/20 10:51 PM, joseverde(a)gmail.com wrote: > Okay, I *think* I killed the processes. When I run > > ps -fwwA|egrep 'master|runner' > > I just get > > root 7595 1 0 Jul26 ? 00:00:04 /usr/lib/postfix/sbin/master -w > mailer 21851 21001 0 22:45 pts/1 00:00:00 grep -E --color=auto master|runner Yes, there are no mailman processes running. > As far as the permissions, you asked does your systemd script set the user to the Mailman user? I don't know how to check that, but I saw many files in /var/lib/mailman3 were owned by a user named list. Last time I tried to run mailman status, it threw a permission error on mailman.cfg, which was owned by root. I changed owner to list, and it produced a different error. So I'm guessing we are on the right path? There was no mention of a user named mailman in the system before, but maybe I need to check something. You are apparently using the Debian/Ubuntu packages. In those, the Mailman user is `list`. There is no `mailman` user. As far as what user the systemd script sets, just look at the script, but if it was installed by the Debian/Ubuntu package, it's probably OK. The script is named xxx.service where 'xxx' is the name you might use in systemctl commands (probably 'mailman3'). It should be at /etc/systemd/service/ or one of the subdirectories. > Lastly, I deleted everything in /var/lib/mailman3/locks. > > However, running mailman status now throws this permission error > > File "/usr/bin/mailman", line 11, in <module> > load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() > File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main > initialize(config_path) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 188, in initialize > initialize_1(config_path) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 123, in initialize_1 > mailman.config.config.load(config_path) > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 107, in load > self.push(filename, user_config.read()) > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 113, in push > self._post_process() > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 125, in _post_process > self.ensure_directories_exist() > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 227, in ensure_directories_exist > with Lock(lock_file): > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 334, in __enter__ > self.lock() > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 203, in lock > self._write() > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 417, in _write > with open(self._claimfile, 'w') as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/mailman-cfg.lck|[redacted server name]|21787|3720843219351355903' > > That file was removed when you told me to clear the locks folder (I save a copy, however). So I'm stuck again. Sorry for all the questions and thanks very much for the help. Does the `list` user own /var/lib/mailman3/ and /var/lib/mailman3/locks/? Are you running `mailman` commands as user `list`? Also see <https://wiki.list.org/x/12812344>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Before changing the DEBUG var to false everything was working fine after I changed it started the problems... 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, 2 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail. I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)." Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list. Also after clearing the browser cache, the above behavior is seen. Best Regards,Eric On Sunday, December 13, 2020, 03:58:47 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 5:24 PM, Eric Broens via Mailman-users wrote: > I just notice in the webserver logfile, the same request for the same mlist, msgid and key several times per second for about 3 hours now: > "GET /archives/api/mailman/urls?mlist=....&msgid=...&key=... HTTP/1.1" 200 105 "-" "python-requests/2.25.0" Is there a message in Mailman's var/archives/hyperkitty/spool/ directory? If so, what's logged in mailman's mailman.log -- 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/

5 years, 10 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 1:08 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 3:00 PM, Odhiambo Washington wrote: > > On Sat, May 15, 2021 at 12:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Those are headers for compiling some sass. Possibly you actually have a > >> `sassc` installed in which case you may need > >> > >> COMPRESS_PRECOMPILERS = ( > >> ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > >> ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > >> ) > >> > >> > > This change makes the error I was getting to go away. However, I cannot > > login to manage lists, even after restarting mailman. > > > > The error details are here: https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ > > > The relevant part of which is > > OfflineGenerationError at /accounts/login/ > You have offline compression enabled but key > "fa788b08b65fd318d68cfc5afebc18acd3e93cebffadb54d863572ad1754f368" is > missing from offline manifest. You may need to run "python manage.py > compress". Here is the original content: > > I.e., something went wrong with your compress command. Try it again. > I have successfully run the following commands: /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 /opt/mailman/mm/bin/django-admin compress /opt/mailman/mm/bin/django-admin compilemessages /opt/mailman/mm/bin/django-admin migrate But the error at https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ persists. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

5 years, 5 months

[MM3-users] Re: Could not locate column in row for column 'user.id'

by Mark Sapiro

On 7/27/20 2:48 AM, Shashikanth Komandoor wrote: > Hi Mark, > > Thank you for your response. And sorry for not giving you > complete information as I am not sue what to share with you. > > I am using Postgresql-11.7 as my backend database. The below is > the structure of the address table in* mailman *database: > > mailman=# \d address; > Table "public.address" > Column | Type | Collation | Nullable | > Default > ----------------+-----------------------------+-----------+----------+------------------------------------- > id | integer | | not null | > nextval('address_id_seq'::regclass) > email | character varying | | | > _original | character varying | | | > display_name | character varying | | | > verified_on | timestamp without time zone | | | > registered_on | timestamp without time zone | | | > user_id | integer | | | > preferences_id | integer | | | > Indexes: > "address_pkey" PRIMARY KEY, btree (id) > "ix_address_email" UNIQUE, btree (email) > "ix_address_preferences_id" btree (preferences_id) > "ix_address_user_id" btree (user_id) > Foreign-key constraints: > "address_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES > preferences(id) > "address_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) > Referenced by: > TABLE ""user"" CONSTRAINT "_preferred_address" FOREIGN KEY > (_preferred_address_id) REFERENCES address(id) ON DELETE SET NULL > TABLE "autoresponserecord" CONSTRAINT > "autoresponserecord_address_id_fkey" FOREIGN KEY (address_id) REFERENCES > address(id) > TABLE "member" CONSTRAINT "member_address_id_fkey" FOREIGN KEY > (address_id) REFERENCES address(id) > TABLE "onelastdigest" CONSTRAINT "onelastdigest_address_id_fkey" > FOREIGN KEY (address_id) REFERENCES address(id) > > The below is the structure of *user* table: > > mailman=# \d user; > Table "public.user" > Column | Type | Collation | Nullable > | Default > -----------------------+-----------------------------+-----------+----------+---------------------------------- > id | integer | | not null > | nextval('user_id_seq'::regclass) > display_name | character varying | | > | > password | character varying | | > | > _user_id | uuid | | > | > _created_on | timestamp without time zone | | > | > is_server_owner | boolean | | > | > _preferred_address_id | integer | | > | > preferences_id | integer | | > | > Indexes: > "user_pkey" PRIMARY KEY, btree (id) > "ix_user__user_id" btree (_user_id) > "ix_user_preferences_id" btree (preferences_id) > Foreign-key constraints: > "_preferred_address" FOREIGN KEY (_preferred_address_id) REFERENCES > address(id) ON DELETE SET NULL > "user_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES > preferences(id) > Referenced by: > TABLE "address" CONSTRAINT "address_user_id_fkey" FOREIGN KEY (user_id) > REFERENCES "user"(id) > TABLE "domain_owner" CONSTRAINT "domain_owner_user_id_fkey" FOREIGN KEY > (user_id) REFERENCES "user"(id) > TABLE "member" CONSTRAINT "member_user_id_fkey" FOREIGN KEY (user_id) > REFERENCES "user"(id) > > mailman=# \dn > List of schemas > Name | Owner > --------+---------- > public | postgres > (1 row) > > mailman=# select * from user; > user > ---------- > postgres > (1 row) > > *The above command output is not showing any fields. But if use the table > as public.user (schema.tablename) with select command, it is showing the > data. But without schema name this table is not showing those fields. Not > sure if this the expected behavior or not.* This is expected. psql gets confused because it has its own user table. The above table definitions look fine. Is there any entry in the `address` table for which `id` is not an integer? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 11:56 AM, David Newman wrote: > > I created a pending subscription request on a test list. Here is the > text I'm using in a file called 'list:admin:action:subscribe.txt' (minus > the rows of hypens): > > ---------- > > > As list administrator, your authorization is required for a mailing list > subscription request approval: > > For: $member > List: $listname > > At your convenience, visit: > > https://${domain}/mailman/admindb/lists/${short_listname}.${domain}/ This looks like a Mailman 2.1 URL. Are you sure you don't want something like https://${domain}/mailman3/lists/${short_listname}.${domain}/ > > to approve or deny the request. > > ---------- > > Instead the message that goes out at midnight daily reads like this: That's a different message. It is sent from the `mailman notify` command run by cron. It's built from the list:admin:notice:pending template. > > On successive nights I have placed copies of the > 'list:admin:action:subscribe.txt' file above in these locations: > > mm/var/templates/lists/test.lists.domain.tld/en I hope you mean /opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en > /opt/mailman/mm/var/templates/site/en Either of those should work. The lists one will take priority over the site one for that list. > and then in Postorius, with the same contents as above. If you set a template in Postorius, it takes priority. If you later decide you want to use one in /opt/mailman/mm/var/templates/ you have to delete the postorius one. > The file > versions are owned by the mailman user, and have 0644 permissions. Not > sure this is necessary but I've restarted the mailman3 and mailmanweb > services each time after a change. > > There is no sign of trouble in the MM3 or web logs. The only thing I see > is in the Postfix log, where the shorter and less helpful message goes > out each night. I don't see anything in the template docs about this. > > Questions: > > 1. What to do to get the custom message working? It should work. I suspect you need to go to the list's Settings -> Automatic Responses and set `Admin immed notify` to Yes. > 2. Is there a way to trigger a subscribe reminder for one list only? If by subscribe reminder you mean the `list:admin:action:subscribe.txt` message, yes that's the above list setting. If you mean the one sent from the `mailman notify` command, see `mailman notify --help` for the options. You can specify one or more lists (default is all lists) via options and put them in your cron. > Asking because there are other lists on this server with other requests > pending, and I don't want to bother other moderators with multiple > reminders per day. Not a big deal, but it would be nice to test this > with one list rather than waiting up to 24 hours after each change. You can test `mailman notify` at any time by running it by hand. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Mailman 3 Installation

by Mark Sapiro

On 1/16/21 6:06 PM, bruce.dubbs(a)gmail.com wrote: > I am trying to set up Mailman 3 on a new server. So far I have run: > > pip3 install Django==3.1.5 This will be a minor issue. django-mailman3 requires Django>=2.0,<3.2; HyperKitty requires Django>=2.2,<3.2, but postorius requires Django>=1.11,<3.1. We really should be more consistent with these requirements, but what this means is > pip3 install postorius will install Django 3.0.11 alongside Django 3.1.5. > pip3 install Hyperkitty > pip3 install mailman > pip3 install uwsgi > > All that went well. I've been struggling with the configuration though. I am using /etc/mailman.cfg and that seems to be explained in the documentation OK. From there I am confused. > > I do have sqlite installed, but the documentation discusses mysql/mariadb and postresql. What are the considerations as to why I would need one of these other DBs? You can use sqlite, but if you don't already have a mysql/mariadb database on the server, we recommend postgresql for performance and robustness. I personally have had issues with mysql and use postgresql on one production server that uses mysql for other applications. > I think I can follow the instructions to set up postfix. > > In the section 'Configure Web Frontend', it discusses setting up the administrator. As I want to put Mailman on /srv/mailman I can create that, but what should the owner/permissions be? Later the docs discuss editing Django's settings.py. Where do I find that file? I'll note here that my experience with python is quite limited and my knowledge of Django is nil. There should be a 'mailman' user that is the user under which you run things. Don't run things as root. sudo chown -R mailman:mailman /srv/mailman For settings.py and some others, see <https://gitlab.com/mailman/mailman-suite/-/tree/master/mailman-suite_project>. The end of settings.py imports from settings_local so you put your local overrides in settings_local.py in the same directory as settings.py > Later in the section 'Set up HyperKitty', it sends me to a page that discusses installing it. I did that with pip3. Then it says to 'Setup your django project'. What django project is that. Postorius and HyperKitty. See settings.py. These files, settings.py and settings_local.py need to be in a directory that also includes an empty __init__.py so python can import from it and this directory needs to be in the path that Django runs with. This is a shell script I use to run django. It uses a virtualenv, but that isn't necessary. Also my stuff is in /opt/mailman/mm/, but it could just as well be /srv/mailman. #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ > I would appreciate advice or a pointer to where I can figure this out. Thanks. There is a work in progress you may find more helpful. See <https://gitlab.com/mailman/mailman-suite-doc/-/merge_requests/55#note_48712…> and the 'Rendered documentation' linked therefrom. You might also find <https://wiki.list.org/x/17891998> and/or the docs linked from its first paragraph to be helpful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

Search results for query "sapiro"