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

[MM3-users] Re: Unknown templates being used

by Brian Carpenter

On 2/14/21 1:31 PM, Mark Sapiro wrote: > On 2/14/21 5:44 AM, Tom Stoddard wrote: >> I'm a list owner who has recently (within the last week) had my lists >> migrated from mailman 2 to mailman 3. The UI that we are using is >> Affinity. > So you should be getting your support from EMWD. > > >> I've reviewed all of the list templates and begun to customize >> some of them. My issue is that I'm receiving messages that don't match >> any of the templates. Here is an example of one that I just received >> this morning. (The x's are inserted by me. The actual message provided >> valid addresses.) >> >> Thexxxxxxxxxx(a)xxxxxxxxxx.org list has 1 moderation requests waiting. >> >> >> Held Subscriptions: >> User:xxxxxxxxxx@gmail.com >> >> Please attend to this at your earliest convenience. Yeah, the funny thing here Mark is he is not asking for support for the interface. He is wanting to know why isn't there a way for List Owners to modify moderation notices. It had nothing to do with Affinity. BTW - I told this client CLEARLY there was no template for that notification but he was welcome to join the list to ask for the source of it since I did not know. Geez. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 4 months

[MM3-users] Re: MM3 to MM3 migration

by David Newman

On 1/31/23 2:01 PM, Mark Sapiro wrote: > On 1/31/23 13:34, David Newman wrote: >> >> Is this really as simple as building the new server, creating the >> same lists on the new server, and rsync’ing the archives from the old >> server? If not, how to do the migration? > > > If you want to mirror the entire installation, you can dump the > databases off the old server and import them to the new server. > Depending on the installation, everything may be in one database or > there may be separate ones for mailman core and mailman web. This is a > little tricky because some of the tables have to do with Django stuff. > > To do only selected lists is much more difficult and there are no > scripts that I am aware of. > > HyperKitty can dump a list's archive as a mbox which could then be > used as input to hyperkitty_import on the new server to move archives, > but there are no similar scripts to dump list settings, users, > memberships, etc. in a format that can be imported. Thanks for this. Would I need to create the lists first on the new server before restoring databases and running hyperkitty_import? Also, I'm unclear about there not being scripts for settings, users, etc. –– isn't that stuff in the mailman database? Thanks! dn

2 years, 5 months

[MM3-users] Re: Another interesting error...

by Darren Smith

As for the traceback - I'm assuming it's from postorius, as this happens when attempting to load the held messages in the Postorius UI. On Mon, Apr 23, 2018 at 3:29 PM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > "It's in Mailman's database in the 'message' table." > > I can see the message table - is there a way to see where it is marked as > "held"? All I'm seeing in that table is id, message_id, message_id_hash, > and path. > > I'm wanting to be able to query for held messages for a given mailing > list, as there are currently over 98,000 entries in the message table. > > -Darren > > > On Mon, Apr 23, 2018 at 3:17 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 04/23/2018 01:31 PM, Darren Smith wrote: >> > So it appears that there was a message sent to one of our mailing lists >> > that was put into the held message queue. However, when attempting to >> go to >> > the message to do the moderation, the web page returns and Error 500. >> > >> > Looking in the mailman log, I found this: >> > >> > Apr 23 14:21:02 2018 (17878) REST request handler error: >> > Traceback (most recent call last): >> > File "/opt/mailman3/conda/lib/python3.6/wsgiref/handlers.py", line >> 137, >> > in run >> > self.result = application(self.environ, self.start_response) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> database/transac >> > tion.py", line 50, in wrapper >> > rtn = function(*args, **kws) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/wsgiapp.py" >> > , line 214, in __call__ >> > return super().__call__(environ, start_response) >> > File "/opt/mailman3/conda/lib/python3.6/site-packages/falcon/api.py", >> > line 227 , in __call__ >> > responder(req, resp, **params) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/post_modera >> > tion.py", line 167, in on_get >> > resource = self._make_collection(request) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/helpers.py" >> > , line 159, in _make_collection >> > for resource in collection] >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/helpers.py" >> > , line 159, in <listcomp> >> > for resource in collection] >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/post_modera >> > tion.py", line 157, in _resource_as_dict >> > resource = self._make_resource(request.id) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/post_modera >> > tion.py", line 100, in _make_resource >> > make_header(decode_header(resource['subject']))) >> > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 174, >> in >> > make_he ader >> > h.append(s, charset) >> > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 295, >> in >> > append >> > s = s.decode(input_charset, errors) >> > UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: >> > illegal multibyte sequence >> > >> > It LOOKS as if there might be a character in the email somewhere - >> possibly >> > in the subject or sender fields? - that is somehow unexpected. >> >> >> It appears that the Subject: header is RFC 2047 encoded and there is an >> encoded word with charset gb2312 that contains an invalid encoding. >> >> The message is apparently defective, but this kind of defect shouldn't >> cause a 500 error. >> >> I can't tell for sure from the traceback if this is Postorius or some >> other application accessing the REST api. Is it Postorius or something >> else? >> >> >> > I am attempting to find the held message - can someone point me where I >> can >> > go to see the message so that I can see what might be causing the >> problem? >> >> >> It's in Mailman's database in the 'message' table. >> >> -- >> 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/ >> > >

7 years, 2 months

[MM3-users] Re: Memory footprint

by Richard Shetron

some systems also support the sar command (system activity report). If you have it read the manpages to see all the options as there are many. When looking for performance issues/problems that aren't real easy to find I like to just let 'vmstat 5' run in a window and take a look occasionally, particularly when things seem slow. I prefer the 5 second readings to see more about general trends. On 4/11/2017 8:33 PM, Mark Sapiro wrote: > On 04/10/2017 02:25 PM, David Krantz wrote: >> Hi. >> >> Now running mailman 3 I am a bit surprised that the memory footprint >> is so large. I count to 13 processes with each a virtual space of >> 160-250MB and a reserved space of about 50MB each. Not much, but quite >> much to run on smaller cloud instances which generally have limited >> memory. This is (a lot) more than the corresponding postgres >> installation uses, >> >> Is this normal? > > > Those numbers seem "normal" but you really have to look deeper to > understand if you just have a bunch of processes sitting in memory > because the memory is available and nothing else wants it, or if there's > real memory contention going on. > > The article at <https://wiki.list.org/x/4030711>, while written about > Mailman 2.1, has some general information which may be of interest. > >

8 years, 2 months

[MM3-users] Re: No DBA password when installing Mailman3 with remote database server

by Markus Ludwig Grandpré

> but apparently dpkg wants to > create databases for Mailman and Mailman Web. During the installation process dpkg creates not only a database and a database user with approriate permissions, but also many tables. Dpkg allows to skip database configuration. Is there routine or skript to create database, database user and all required tables after the installation process has finished? Best regards, Markus On 31.10.22 18:52, Mark Sapiro wrote: > On 10/31/22 07:04, Markus Ludwig Grandpré wrote: >> Dear Mailman3 list, >> >> I try to install the Mailman3 software 3.3.3-1 on a Debian 11 system >> with a remote Postgres database server. During the installation >> process dpkg is asking for the DBA password that our DBA team would >> not provide to me. So what can I do? > > > This is really a question for Debian, but apparently dpkg wants to > create databases for Mailman and Mailman Web. You will need to get your > DBA team to create these databases (probably named `mailman` and > `mailmanweb`) and a Mailman user (probably `list`) with all access to > these databases and probably manually configure the `[database]` section > of mailman.cfg and `DATABASES` on Django's settings > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, Tel: ++49 7531 88 4342

2 years, 8 months

[MM3-users] Re: Mailman 3 installation, no mails in hyperkitty, unable to add footer.

by Ugnius S

Hi, Mark. Thank You for trying to help me. I do not remember how exactly I installed mailman or by apt-get or: $ sudo pip3 install mailman ---I think, have tried this way, but it already was installed. ~/mailman-suite$ mailman info GNU Mailman 3.2.2 (La Villa Strangiato) Python 3.5.3 (default, Sep 27 2018, 17:25:39) [GCC 6.3.0 20170516] config file: /home/user/mailman-suite/mailman.cfg db url: sqlite:////home/user/mailman-suite/var/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:Rest_password MTA works correctly. Yes, I understand the error is very strange, but this exactly happens when I add footer custom template to list's regular message via web interface. "telnet loclhost 25" answers correctly. Messages about new members adding and new list creating works and reach the recipients. But Mailman for some strange reasons could not to sent messages from member to other list's members. And nothing to do more: it is enough to delete template and mailman starts send new messages correctly. One remark all messages during with customs template was active remain somewhere in between and do not go out even if template is deleted. I can't even imagine how to debug that. I have noticed that by experience - method to check does mailman work after every small update. This system is so easy to make not working, and then is so hard to understand what did happen. It would be good to read about working example how to setup, and which moments are important. There are many places documented about separate packages, but not full example. I have found one here https://lab.uberspace.de/guide_mailman-3.html, but here part of steps seems are not written as well. For example uwsgi ini and pre required environment. It could happen that for author these steps were trivial, but for person from side some small explanations are very important to understand whole picture of setup and why small parameters where set exactly that way. Of course I am very thankful for authors of that example, because that helped me as well. 2019-08-23, pn, 20:28 Mark Sapiro <mark(a)msapiro.net> rašė: > On 8/23/19 8:11 AM, ugniusviln(a)gmail.com wrote: > > I have read documentation, but still have stupid questions, could You > please help, because I can't make it working. I do not understand something > important. I have no experience with python at all. I have mailman 3, > python 3.5 in my debian OS system, and additional packages like uwsgi and > ect. using > https://buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman… > about till chapter 6. I understand mailman suite has hyperkitty already. > But I am not sure about: > > > > 1. Does mailman-suite have hyper-kitty inside? Because if I run $python > manage.py runserver - it runs. In installed it under dedicated OS user home > and fonfigured to run. > > I can create lists, event add lists to hyperkitty page using: > $django-admin runjob new_lists_from_mailman list server sends messages to > list members as well. But nothing happens more. No emails come to > hyperkitty, arciver log 0 size. > > $ python manage.py runjobs -l shows the lists of the jobs, so seems > nothing to add. > > > > How exactly did you install Mailman? The document you reference gives > alternatives. You don't say exactly what you did. > > > > 2. If I (using Postorius web interface) add footer template to my list > under regular message, something strange happens. Mailman stops to send > messages for list members. No any entries in the logs. Just Mailman log > writes: "unable to connect localhost port 25" and no more explanation. If > I delete list's footer template (web interface), mailman starts working > again. What is bad here? How to add custom footer? In mailman 2 if was > working so good and was easy to setup. > > > It appears that no MTA is listening on localhost port 25. Is your MTA > even running? It is extremely unlikely that this has anything to do with > adding a termplate in Postorius. > > You might be better off installing Debian's 'mailman3-full' package > < > https://packages.debian.org/search?keywords=mailman3-full&searchon=names&su… > >. > > -- > 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: Importing mbox file into MM3

by Mark

On 2023-06-23 12:19, Mark Sapiro wrote: > On 6/22/23 7:00 PM, Mark wrote: >> Hi All >> >> I'm trying to import a large mbox file from a MM2 list into a new list >> on MM3. >> >> The new MM3 list has 3 test emails in its archive. >> ... >> The import or rebuild has failed as it's just rebuilding the existing >> archive of the 3 test messages. >> >> What am I doing wrong? > > > Presumably, the 3 test emails are newer than the messages in the > archive .mbox. The default for hyperkitty_import is to not import > messages older than the newest message in the existing archive. > You need to specify something like `--since='1970-01-01'` on the > hyperkitty_import command to import these older messages. > Thanks Mark. That looks more promising. It's been chugging away now for 3 hours with only 4 errors reported so far. # cd /usr/share/mailman3-web/ # python3 manage.py hyperkitty_import --since='1970-01-01' -l LISTNAME@DOMAIN /home/mark/tmp/LISTNAME.mbox "Failed adding message ......(a)mail.yahoo.com>: A string literal cannot contain NUL (0x00) characters". The mbox file is about 3 GB. The errors look like they're for messages that aren't kosher (maybe misplaced "From"s in replies). I can live with a few missing messages. Back to watching the spinning pipe. Chug chug. Cheers Mark

2 years

[MM3-users] Table 'mailmansuite.django_q_ormq' doesn't exist ("Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all')

by Simon Liebold

Am 28.05.2017 um 22:24 schrieb Mark Sapiro: > 'Delete this message' is in the 'message' view. "Delete this thread" is > in the 'thread' view. Now found the message view. Thanks. > HyperKitty requires Django<1.11. The comment in the requirements in > setup.py implies this is only a django-haystack requirement > > "Django>=1.8", > # Don't upgrade to 1.11 until django-haystack supports it: > # https://github.com/django-haystack/django-haystack/pull/1499 > "Django<1.11", > > but since it works for me with Django 1.10, you might want to try that. OK, I was still running an RC version. Silly me. > In particular, this looks like Django 1.11 bug > <https://code.djangoproject.com/ticket/27975>. Which was closed in the release version that I initially upgraded to (1.11.1). Now, I get to see the confirmation view and upon confirming I see these (luckily different) errors like below (same with Django 1.10): Could not delete message P2GJLK4JPDU2K6ZKBSDUWASF2TVHCJTT: (1146, "Table 'mailmansuite.django_q_ormq' doesn't exist") Could not delete message 4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM: (1146, "Table 'mailmansuite.django_q_ormq' doesn't exist") True, this table doesn't exist in the database. It isn't created by python manage.py migrate. The error is served with HTTP-200. No stack trace in mailmansuite.log. Headscratching: Simon

8 years, 1 month

[MM3-users] Re: multiple sites on a mailman3 server question

by William Oliver

On Tue, 2021-12-28 at 18:23 -0800, David Newman wrote: > > > > [snip] > > I'm using nginx > I'd asked about this a few weeks ago for a MM3 host running Ngnix > with a > few virtual domains, one of which runs Roundcubemail as its default. > > Mark Sapiro suggested the following, and it seems to be working OK. > You'll need these lines in the Nginx config file for each virtual > host > you define. > > # begin mailman3 stuff > > location /static/ { > alias /opt/mailman/web/static/; > } > [snip] No joy. This just makes it kind of work as the mailman interface when it gets rewritten. My problem is that the url is getting referred to domainname/mailman3/lists even when I don't want it to. Adding these changes just (partially) loads the mailman3 interface when it gets rewritten. What I'm trying to figure out is where uwsgi yanks control from nginx and does the rewriting. Pulling that proxypass stuff out will stop mailman3 from coming up, and adding it allows mailman3 to show its interface, but the address gets referred regardless. Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow tell nginx not to push it to port 8000. But I don't see where nginx is getting told to go to 8000 in the www.domain.com section. billo

3 years, 6 months

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by Nelson Strother

Well, this is using the default libsqlite 3.34.1 . One improvement is to use write-ahead logging: mailman@localhost:~$ sqlite3 /var/tmp/mailman/data/mailman.db SQLite version 3.34.1 2021-01-20 14:10:07 Enter ".help" for usage hints. sqlite> PRAGMA journal_mode = WAL; wal sqlite> This setting is persistent, and based on a small sample this seems to dramatically speed up the completion of root@localhost:~# systemctl stop mailman ## consumes <2 minutes with journal_mode = WAL; root@localhost:~# ## instead of up to 20 minutes with the default journal_mode = delete But this does not make a big change the completion time for: root@localhost:~# systemctl start mailman Since there is no point in busy waiting when running on a processor with only one core (as this virtual server), the next setting that I would like to try is change the sqlite busy_timeout from the default of none to 1 or 2 seconds, e.g.: sqlite> PRAGMA busy_timeout = 2000; 2000 sqlite> However, this setting is not persistent, and thus needs to be applied to each connection (i.e. tens of database connections are made during `systemctl start mailman`). I have not yet found where to insert this directive in mailman's database wrapper for SQLite. Might someone who has read more of the source be able to offer me a clue? On 6/8/23 15:47, Mark Sapiro wrote: > I would look to your database manager for the issue.

2 years

Search results for query "sapiro"