Search results for "2021" - Mailman-users

Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/22/21 9:22 PM, David Newman wrote: > > On my system that file lives here: > > /opt/mailman/venv/lib/python3.9/site-packages/mailman_web/urls.py It appears that you have installed following https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… and in that case, this is the file. > But the error persists after this addition and restarting MM3 and > mailmanweb and nginx: > > url(r'^mailman/', include('postorius.urls')), > > There is this 404 error in uwsgi.log: > > [pid: 73356|app: 0|req: 3/3] 127.0.0.1 () {48 vars in 1544 bytes} [Wed > Dec 22 21:13:48 2021] GET /mailman/admindb/listname => generated 5328 > bytes in 14 msecs (HTTP/1.0 404) 6 headers in 197 bytes (1 switches on > core 0) However, that's not the issue. You originally reported and I didn't look closely enough: > Update: The above worked fine until MM3 informed a list owner of pending > subscription requests, with a URL like this: > > https://lists.example.com/mailman/admindb/listname > > and that URL returned a 404 error. That URL is from a Mailman 2.1 installation. Are you still running Mailman 2.1? If so, you need to support Mailman 2.1's CGIs. In Apache, this would be something like ScriptAlias /mailman/ /parh/to/mailman/cgi-bin/ but nginx doesn't do that. You would need something like location /mailman/ { proxy_pass <something that can serve Mailman 2.1's CGIs.> } The something could be apache or ?? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Re: How to import mailman2 into mailman3 in Docker, getting error with archives.

by Abhilash Raj

On Thu, Sep 16, 2021, at 6:45 AM, bob B wrote: > I am a sorry i still don't understand, > > > So for docker I need to run the command via "docker exec -it > mailman-web" right? Does this run it as user mailman in the docker > image? Yes. > > I have my archive copied from the old server and but in a location on > my new docker host where it can be accessed by mailman-web image i.e > /opt/mailman/web. which is the same location as /opt/mailman-web-data > from inside mailman-web, right? That is correct. > I then run the command > > docker exec -it mailman-web python manage.py hyperkitty_import -l > [Redacted](a)[Redacted].[Redacted].org > /opt/mailman-web-data/[Redacted].mbox > > but I get the error: > > OCI runtime exec failed: exec failed: container_linux.go:380: starting > container process caused: exec: "python": executable file not found in > $PATH: unknown > > > isn't this showing that it can't find python in the docker container to > run the import???? Sorry, I made a typo in the previous email. You want to run that command with `python3` instead of `python`. ``` docker exec -it mailman-web python3 manage.py hyperkitty_import -l [Redacted](a)[Redacted].[Redacted].org ``` And turns out the typo also exists in the docs at one place. I just opened this[1] report to fix it. [1]: https://github.com/maxking/docker-mailman/issues/507 -- thanks, Abhilash Raj (maxking)

3 years, 9 months

Re: spanish localization

by Abhilash Raj

On Sat, Feb 13, 2021, at 9:26 PM, Mark Sapiro wrote: > On 2/13/21 5:42 PM, Abhilash Raj wrote: > > > > You can actually translate the templates in Weblate too. That is > > actually the whole > > reason to go with monolingual template format in Mailman Core. > > > > Mailman uses the template file's name as the msgid for translations and > > all in-tree > > templates are copied into English's .po file when we re-generate them. > > > > For example in here: > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC… > > > > > > The english .po file is considered as reference in Weblate and used for > > source string. > > > But it appears that we are lacking a mechanism (other than some manual > process which isn't reliably done) to move the translated templates from > the translated .po file to the appropriate templates/<lc>/ directory. Yeah, you are absolutely right. I thought in my head that I had modified the lookup mechanism to use gettext for in-source templates, but that doesn't seem to be the case. https://gitlab.com/mailman/mailman/-/issues/825 I have opened an issue to track 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)

4 years, 4 months

Re: External Mail-Server?

by Florian Schulze

Hi! But LMTP is the "Local" Mail Transfer Protocol. I only have access to IMAP, POP3 and SMTP. Outgoing seems to be simple, but what about incoming? Regards, Florian Schulze On 11 Sep 2021, at 21:21, Jörg Michael Schulz via Mailman-users wrote: > Hi, > > yes, this should be possible. > > See the parameters in your mailman.cfg: > > [mta] > # The class defining the interface to the incoming mail transport > agent. > incoming: mailman.mta.exim4.LMTP > #incoming: mailman.mta.postfix.LMTP > > # The callable implementing delivery to the outgoing mail transport > agent. > # This must accept three arguments, the mailing list, the message, and > the > # message metadata dictionary. > outgoing: mailman.mta.deliver.deliver > > smtp_host: mail.yourfavoritedomain.de > smtp_port: 25 > smtp_user: > smtp_pass: > > Am 11.09.21 um 19:53 schrieb Florian Schulze: >> Hi! >> >> Is it possible to use an external Mail-Server? Does mailman3 support >> that directly, or would I have to setup a local MTA which somehow >> fetches incoming mails from the external inbox and uses the external >> Mail-Server for delivery? >> >> Does anyone do that and have example configurations? >> >> Regards, >> Florian Schulze >> _______________________________________________ >> 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/ > > > _______________________________________________ > 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/

3 years, 9 months

Re: Unwanted E-mail to Maillists Submitted via Postorius Interface

by Matthew Alberti

Well, I actually received what appears to be a SPAM response to my original email post. No joke. If mods want a copy of it, let me know. Matt Alberti ⁣Get BlueMail for Android On Aug 25, 2021, 7:43 PM, at 7:43 PM, matthew(a)alberti.us wrote: >Hi Everyone, > >I’ve seen a recent uptick in SPAM messages making it into mailing >lists. Looking at the raw, it seems that the e-mails are being >submitted thru the Postorius/Hyperkitty “Start a New Thread” interface. >Is there a way to turn that off? We would want people to only be able >to post via e-mail. Part of the problem is that our anti-spam system >RSPAMD trusts the mailman-web IP… so it doesn’t scan things originating >from there.. ☹ > > > >Another uestion: Is there a way to implement captcha, or is there a >recommended gate that can be put in the signup process? Apparently bots >are finding a way thru the signup process, and then sending messages to >the list via the Postorius web interface. There seems to be a Django >plugin for it; but it appears the Mailman code would have to be >adjusted to implement it. > > > >I’m open to any suggestions, including on places to check for >misconfiguration. 😊 > > > > Thanks. > > > >- Matt Alberti > >_______________________________________________ >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/

3 years, 10 months

Re: Message is received but is not sent out. Another, similar message, is processed fine.

by Allan Hansen

Thank you both. Since the first message she sent was UTF-8 and the second iso-8859-8-I, I have asked her what she did diffently between the two messages. No response yet... But now being aware that this can happen when non-ASCII messages are sent, and how to find the issue when it does, is good. Yours, Allan On 6/27/23, 07:57, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 6/27/23 12:30 AM, Stephen J. Turnbull wrote: > > That said, if the users are unable or unwilling to use UTF-8, it would > be possible to create a codec for "iso-8859-8-i", I don't know how to > do that, and I doubt Mark does. You could ask on > python-list(a)python.org <mailto:python-list@python.org>, or file an RFE on Python's GitHub tracker. See https://github.com/python/cpython/issues/90079 <https://github.com/python/cpython/issues/90079> filed by me in Nov 2021. -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/4WPWU3SKGWM2BTG5AK3LWNG7FDIBVSTP/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

2 years

Re: Database deadlock when trying to delete a member.

by Simon Coggins

> On 18 Mar 2021, at 5:05 pm, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > Hi Simon, > > > On Mar 17, 2021, at 10:16 PM, Simon Coggins <s.coggins(a)cqu.edu.au> wrote: > > > > Hi, > > > > I’ve got a strange error. I migrated from mailman 2.1 to 3 using the migration guide on the website and things have been working fine. But I’m in the process of testing the new syncmembers command to replace some inhouse mailman API code we wrote. I’ve tracked my problem down to what appears to be a deadlock in the postgresql database. When trying to delete certain users the SQL query hangs and never returns. > > > > After doing some tracing and tracking it down to the database, I enabled DB logging of all queries and saw that the following query was never returning: > > > > DELETE FROM member WHERE member.id = 166814 > > > > If I try to run it manually I get the same issue, in psql it never returns. > > mailman=# explain analyze DELETE FROM member WHERE member.id = 166814; > > [… 60 seconds passes…] > > ^CCancel request sent > > ERROR: canceling statement due to user request > > CONTEXT: while deleting tuple (2998,72) in relation "member" > > I’m just wondering if there are any commands or scripts I can run to verify the database and it’s constraints to see if there is some error in the database data? Or where you’d recommend I go from here? It only impacts the user on this specific list. If I add this user to another list and remove them, everything works fine. > > Are you able to retrieve that Member object using API? > > This[1] the Python code which would try to delete a Member object and I > am assuming is being called from syncmembers command. I am not entire > sure about what would cause the database to hang, if there was some database > constraint that failed, I would imagine some error to be returned. > > [1]: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/member.p… > Ok I think I’m getting closer. It appears to be an open transaction that is locking the database record. While mailman is running, if I try to execute "DELETE FROM member WHERE member.id = 166507;” on the mailman table in psql the query hangs and never returned. But if I shutdown mailman and try to run the query again, it executed immediately. So I’m pretty sure there is an open transaction that is causing the entry to be locked. > One thing you can try is see if you can unsubscribe the user using the API or > `mailman shell` command. > > You can unsubscribe from API by calling a `DELETE` method at > > http://localhost:9001/3.1/members/<member_id> > > This would give us some indication about whether there is some bug > in the implementation of syncmembers command or if there is something > else going on. > Trying via shell or via API to delete the user all fail and hang. I’m able to receive the user/membership/list data without any issue both via mailman command and via the API. > > > > This is on a test system so I can do various testing. I’m trying to find the root cause so that I can verify my production system isn’t impacted by the same thing. > > > > > > Setup Details: > > OS: Oracle Linux 7 (Redhat) > > Installed using pip via virtualenv talking to a local pgsql database on the same box. > > Data was migrated from a mailman 2.1 install into mailman3 using migration instructions on the website. > > > > PIP Modules versions: > > django-mailman3 1.3.5 > > mailman 3.3.3 > > mailman-hyperkitty 1.1.0 > > mailmanclient 3.3.2 > > postorius 1.3.4 > > psycopg2-binary 2.8.5 > > What is the version of sqlalchemy package? There is a new 1.4.0 version that came out recently > and is incompatible with Core right now. There are backwards incompatible changes which might > need some changes in Core to add support. > SQLAlchemy 1.3.19 > > > > RPM packages: > > postgresql12-12.6-1PGDG.rhel7.x86_64 > > postgresql12-server-12.6-1PGDG.rhel7.x86_64 > > postgresql12-libs-12.6-1PGDG.rhel7.x86_64 > > postgresql12-devel-12.6-1PGDG.rhel7.x86_64 > > > > > > -Simon > > > > > > _______________________________________________ > > 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) > > > _______________________________________________ > 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/ --- Simon Coggins, Principal Systems Engineer Digital Services Directorate CQUniversity, Lvl 6.14, 160 Ann Street Brisbane, QLD, 4000 Email: s.coggins(a)cqu.edu.au Web: http://www.cqu.edu.au/

4 years, 3 months

Re: Installing mailman3 from Ubuntu 20.04 repository

by Abhilash Raj

> On Aug 23, 2021, at 10:48 AM, Andy Cravens <acravens(a)uen.org> wrote: > > I’m testing Mailman3 on Ubuntu 20.04 and installing the packages from the default Ubuntu repo. I’m not sure I’ll perform the install this way once we move to production. I don’t know what group is responsible for keeping the Mainlam3 package in the Ubuntu repository up to date but I’d like to find out how committed that groups is to keeping the package current. We patch often and it would be convenient if the Mailman3 package is kept updated and current. If there is going to be some significant lag time I may decide to install manually when we go to production. Any thoughts on this? This isn’t responsible for maintaining Ubuntu packages, I am not sure who does. I may be completely wrong on this, but my understanding is that Ubuntu uses the packages from Debian directly and the Debian packaging team handles the packaging of Mailman which you can find the contact for here the package details [3]. You can compare the current version in Ubuntu repos[1] with Mailman releases[2] to get an idea, but they usually lag behind a couple of versions. Having said that, from what I understand, the Debian packages for new versions of Mailman packages are built and made available pretty soon (unless there is an issue with a missing dependency or required a patch to get into Debian) after the release, even if they aren’t included in the Debian releases immediately. [1]: https://packages.ubuntu.com/focal/mailman3 [2]: https://pypi.org/project/mailman/#history [3]: https://packages.debian.org/sid/mailman3-full -- thanks, Abhilash Raj (maxking)

3 years, 10 months

Re: User settings triggers error

by Mark Sapiro

On 6/18/20 3:33 PM, Mark Dadgar wrote: > > Any thoughts on how to salvage ~20 years of list archives? The archives shouldn't be an issue. I don't think they are involved in the corruption, but anyway, hopefully you still have the archive mbox you imported. Then for the messages since then, you should be able to get a mbox from hyperkitty with something like https://example.com/hyperkitty/list/listname@example.com/export/arbitrary-n… with the obvious substitutions and appropriate start and end dates. The list is trickier. If you are going to start over with a clean install, and if you have a config.pck that you imported from MM 2.1, I suggest the following: Use the `mailman members` command to get a list of all members. Then depending on how much work you want to do, also get separate lists of plaintext and mime digest members and members with delivery disabled. Then on the new install, import the config.pck with `mailman import21` and import the archive mboxes with hyperkitty_import. Run `mailman members --sync` with the full current membership list, and record the [ADD]s. Then you can match the [ADD]s against the plain and mime digest members and those with delivery disabled and set their options. That's a lot to do, but it should get you close. On the other hand, if you can wait, we might be able to figure out how to fix this, and it's even possible the underlying issue isn't database corruption. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Andreas Barth

* Lars Schimmer (l.schimmer(a)cgv.tugraz.at) [210301 09:10]: > On 27/02/2021 04:02, Stephen J. Turnbull wrote: > >Lars Schimmer writes: > > > > > Hm, it completely ignores the standard way for Debian: > > > apt-get install mailman3-full > > > also exim4 as standard mailer. > > > And apache2. > > > >Right. The idea is that Debian is a *component* of *Brian's* system, > >not that Brian is installing a Debian system. One problem is that a > >lot of people like to run Debian Stable, which lags our releases by > >many months, sometimes a couple of years. A lot of people run a > >Debian Stable system plus a couple of mission-critical apps from > >source or from upstream repositories. > > Maybe the debian packages are old because people do not care about > and use always upstream because debian packages are old? Eh, sorry, but stable means: only essential (i.e. security) bugfixes get into that version. This is not a problem, it's a feature. If someone wants the latest greatest version of all packages, run testing or unstable. And if you need it for just one package, install the required package by hand. This works usually quite well. The testing/unstable branch contains version 3.3.3 as of writing this which is the currently released version, see https://packages.qa.debian.org/m/mailman3/news/20210205T001903Z.html (and which was uploaded about a day after release - not a bad timing). I would be quite careful speculating that someone may be not careing about something. Andi

4 years, 4 months

Mailman-users search results for query "2021"