Search results for "Postorius" - Mailman-users

Re: Installing Mailman3 on Debian Bullseye

by Stephen J. Turnbull

Franklin Weng writes: > Thanks for your comments! Thank you for following up on my queries. > > As far as I know, Debian packages use the system Python and the > > system Django. Is that correct? > > Correct. This means that you're stuck with the Debian version of the Mailman 3 suite until they update which can be slow. Mailman 3 is now mature enough that if you're still happy with the Debian version a month after installing, you'll probably still be happy with it when Debian updates. It's a good tradeoff for the majority. But for example mixing a "testing" Mailman with a "stable" Python is likely to end badly because we frequently upgrade required levels of dependencies. So you either have to get a Debian upgrade of Mailman of your current Debian version, or you need to move to a whole not-stable Debian system. Not a pleasant choice if you think you need new features or a bugfix *now*. This is why we recommend the venv or other isolated installations. They allow you to upgrade the dependencies as well as the core packages without interfering with the rest of your system. > IIRC I got some errors about handling characters encoding if I > don't set up charset in language.master and language.en > section. But the memory is vague and I don't want to go back > retesting that... I suspect that you set up charset in .master and realized that it doesn't work because .en overrides it with ASCII, and then fixed .en. That's what happened to me. > Honestly I was totally confused by all these, and as I have said, > the MM3/Django/Hyperkitty/... documents didn't help much. Upstream documents are rarely very helpful with whole sets of large packages from distros in my experience. You install the packages, you go through a bunch of configuration screens, and you finish knowing *nothing about how anything works*. Then you need a little tweak that the configuration screens don't deal with, and you don't even have the vocabulary to grep or Google effectively. :-( Then again, I'm the kind of person who prepares to sleep by reading software manuals. ;-) But I do think you lose quite a bit of knowledge by using packages, and it's painful to find obscure details without it. Django doesn't actually show its face much in Mailman, so Django docs are not much use even to the site admin, unless you actually hack on Mailman. The only exceptions are authentication and the template language. Authentication is just hard, with more details then the Lego set in the Lego store. The templating docs are pretty good, IMO. The Mailman docs are in somewhat sad state. The content is actually quite comprehensive and detailed as these things go, but much of it is hard to discover. The original idea was to keep the docs in the sources, as doctests for examples and in the docs directory for exposition. These docs are more developer-oriented, obviously. Then there were several attempts to create a suite package which would require core, Postorius, and HyperKitty and streamline the setup process. The "mailman-suite" version came with a companion "mailman-suite-docs" package, which I think is now the basis for mailman.readthedocs.io aka docs.mailman3.org. However mailman-suite turned out to more trouble than it was worth, and mailman-web was developed to address the more useful approach of unifying some mailman-to-Django APIs for Postorius and HyperKitty (the django_mailman3 package) and configuration (a unified settings.py, as well as standardized top-level urls.py and views.py). Of course each of these contributed more documentation, some of it redundant, older versions left to slowly become obsolete (ie, incorrect) .... "Someday" I'd like get the documents reorganized, eliminate as much redundancy as possible and make things more discoverable. But it's a mammoth task. Steve

2 years, 1 month

Deactivate list without deleting it?

by Colin Watson

Hi, I'm experimenting with a port of Launchpad's mailing list infrastructure to Mailman 3. If Barry's reading, he may remember that this is no trivial task, so I'm very definitely not promising that it will be done any time soon. :-) However, for the most part it looks relatively tractable with the aid of the plugin improvements in Mailman 3.2.0; I have the rough outline of a plugin that implements much the same feature set as our current pile of monkey-patches against Mailman 2.1 in a much nicer way. One of the major things I haven't figured out yet is list deactivation and reactivation. In our current 2.1-based code, you can deactivate a list in a reversible way, which basically tars up the list directory so that the list archives can be restored later. This isn't a native operation in 2.1, but it could be done because everything lived on the filesystem. In 3, it's less trivial. We could go to some effort to dump things out of the HyperKitty database and restore it on reactivation, but that seems rather complex and a bit silly. Ideally, I'd like mailing lists to have a "deactivated" state in addition to full deletion. In this state, the list would appear nonexistent for most purposes: incoming email would be rejected, Postorius would deny its existence, etc. There'd need to be corresponding extensions to the IArchiver interface which caused the archiver to put its archives of that list into a corresponding deactivated state, in which it would retain the messages but queries for them would return 404 or similar; these extensions would need to be optional, since while it should be relatively easy to do this in HyperKitty it could be hard or impossible for other archivers, and perhaps this should be a separate operation from deactivating the list itself since people may want to close a list while leaving its archives accessible. Has there been any discussion of this in the past, or any advice as to implementation strategy? Thanks, -- Colin Watson [cjwatson(a)ubuntu.com]

7 years, 9 months

Re: Welcome message template errors

by Mark

> Did you delete and recreate the template after changing > POSTORIUS_TEMPLATE_BASE_URL? If not, the template table still has the > old URI. Yes. Every test is: delete template and users (via Postorius), make any config changes, restart everything, then new template and new user (via Postorius). > What does `ps -fwwu mailman|grep runner` show? # ps -fwwu mailman|grep runner mailman 375726 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 mailman 375727 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 mailman 375728 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 mailman 375729 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 mailman 375730 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=lmtp:0:1 mailman 375731 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 mailman 375732 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 mailman 375733 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 mailman 375734 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 mailman 375735 375716 0 02:00 ? 00:00:00 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 mailman 375736 375716 0 02:00 ? 00:00:00 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=task:0:1 mailman 375737 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 mailman 375738 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 mailman 375790 375734 0 02:00 ? 00:00:00 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 mailman 375791 375734 0 02:00 ? 00:00:00 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1

1 year, 5 months

Re: Bulk delivery status change?

by Stephen Daniel

OK. Ran the script. No errors while running it, but when I look at the users through Postorius GUI, they still show as 'Disabled by Bounces' ?? On Sun, Nov 10, 2024 at 11:42 AM Stephen Daniel <swd(a)pobox.com> wrote: > Thanks all! I will use these pronto. > > On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: >> > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: >> > >> >> Mistakes were made, and for while every single outbound email bounced. >> >> I've fixed the mistakes, but now in my largest and most active email >> list, >> >> every single user's delivery status is "Disabled by Bounces". >> >> >> >> Is there a way to bulk fix this? Or do I have to go into each user, >> one at >> >> a time, and fix them? >> > >> > Please see this thread: >> > >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> The script in that post does all lists. For a single list see >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> but note that the command line >> ``` >> $ shell -l list(a)example.com >> ``` >> should be >> ``` >> $ mailman shell -l list(a)example.com >> ``` >> >> -- >> 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 swd(a)pobox.com >> >

11 months, 1 week

Re: To what extent can mailman 3 handle images and html?

by Mark Sapiro

On 10/20/19 2:11 AM, Paul Arenson wrote: > Hi > > The other day I attempted to send a message from my mail client (Apple computer, Mail program, html--well, what they call Rich Text). While a user was able to send a message previously that contained an image, I was unsuccessful. It should be the same as Mailman 2.1. What are your settings for content filtering. In Postorius the only thing exposed are Settings -> Alter Messages -> Filter content, Collapse alternatives and Convert html to plaintext. If this Filter content Yes, content is filtered according to the other two settings and MIME parts may be removed according to the list settings filter_types, pass_types, filter_extensions and pass_extensions. These settings exist in core, but aren't exposed in Postorius. For a new MM3 list these settings are empty, but for a list imported from Mailman 2.1, they are set according to the corresponding MM 2.1 settings. I suspect in your case the issue is Filter content and Collapse alternatives are both Yes. Or perhaps the issue is HyperKitty's rendering of the message > As well, links were weird. > > LINKS > ===== > Because My wordpress often has a Japanese URL and they can become very long, I tried both the URL as is and embedded (made a clickable html link). > > URL > === > So while I typed > https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis.... > > It came out double as > > https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... > <https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... > (The full link was truncated with ... at the end, and the link appeared twice with the second instance preceded by "">") I think the doubling is due to your MUA. The truncation of the displayed link in HyperKitty is expected, but the link itself should reference the full URL. > The embedded one did not come out embedded buy showed the text like this: > Alternate link: 多摩川河川敷に男性の遺体、増水した川に流されたか > <https://www.tokyoprogressive.org/%e5%a4%9a%e6%91%a9%e5%b7%9d%e6%b2%b3%e5%... What do these look like in the message received from thge list as opposed to HyperKitty? > QUESTION 1: Is there a preferred way to write links, or will there always be problems with the mail clients? > (Even the web archive shows this problem though): > > https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… See what this looks like at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > See the top item Homeless man drowns in river during Typhoon and what I mean. The first of those 3 links actually works. The other two don't work because the Japanese characters have been encoded as hex values by your MUA (which may be HyperKitty if you are posting via HyperKitty. To answer your question, you can just type the URL as you did above in your thread link, or you can surround it with angle brackets as I did in my message link. If you don't use angle brackets, it should be surrounded by whitespace to avoid ambiguity. See <https://www.rfc-editor.org/rfc/rfc3986#appendix-C> > IMAGE > No image appears though one was added inline. > > And, as I said, a user was previously able to add one. I do not know how she did it. I also posted it to my web site instead of the newsletter for unrelated reasons. But there was an image (Originally got a warning the message was held because the attachment or something). > > So are there guidelines one whether/how to attach an image so that it makes it? Are you posting via email or HyperKitty? If by email, I suspect the issue is Filter content and Collapse alternatives are both Yes. If by HyperKitty you can only post plain text. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

Thank you very much Abhilash! Could you set up 'latest' tag in postotius repo <https://hub.docker.com/r/maxking/postorius/tags> please - as it exists for core/web? I'd like to have consistent approach across the images... Also it would be really great to extend image labelling used for *quay.io/maxking/mailman-*:rolling <http://quay.io/maxking/mailman-*:rolling>* images to Docker Hub ones... Version identification is quite hard for Docker... With my best regards, Danil сб, 2 мар. 2019 г. в 03:19, Abhilash Raj <maxking(a)asynchronous.in>: > > > On Thu, Feb 28, 2019, at 10:18 PM, Danil Smirnov wrote: > > Hi Abhilash, > > Thank you very much - the previous error is fixed now. > > But I have another one now, which causes the same 500 Server Error: > > bash-4.3# cat /opt/mailman-web-data/logs/uwsgi-error.log > *** Starting uWSGI 2.0.18 (64bit) on [Fri Mar 1 05:42:09 2019] *** > compiled with version: 6.3.0 on 01 March 2019 01:52:42 > os: Linux-3.10.0-693.11.1.el7.x86_64 #1 SMP Mon Dec 4 23:52:40 UTC 2017 > nodename: mailman-web > machine: x86_64 > clock source: unix > detected number of CPU cores: 2 > current working directory: /opt/mailman-web > detected binary path: /usr/local/bin/uwsgi > !!! no internal routing support, rebuild with pcre support !!! > setgid() to 101 > setuid() to 100 > chdir() to /opt/mailman-web > your memory page size is 4096 bytes > detected max file descriptor number: 1048576 > building mime-types dictionary from file /etc/mime.types...1168 entry found > lock engine: pthread robust mutexes > thunder lock: disabled (you can enable it with --thunder-lock) > uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 8 > uwsgi socket 1 bound to TCP address 0.0.0.0:8000 fd 9 > Python version: 3.6.8 (default, Jan 30 2019, 23:58:16) [GCC 6.3.0] > Python main interpreter initialized at 0x55a2df7f57e0 > python threads support enabled > your server socket listen backlog is limited to 100 connections > your mercy for graceful operations on workers is 60 seconds > mapped 166752 bytes (162 KB) for 2 cores > *** Operational MODE: threaded *** > Traceback (most recent call last): > File > "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", > line 20, in import_string > return getattr(module, class_name) > AttributeError: module 'django.contrib.auth.middleware' has no attribute > 'SessionAuthenticationMiddleware' > > The above exception was the direct cause of the following exception: > > Traceback (most recent call last): > File "wsgi.py", line 38, in <module> > application = get_wsgi_application() > File "/usr/local/lib/python3.6/site-packages/django/core/wsgi.py", line > 13, in get_wsgi_application > return WSGIHandler() > File > "/usr/local/lib/python3.6/site-packages/django/core/handlers/wsgi.py", line > 136, in __init__ > self.load_middleware() > File > "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line > 34, in load_middleware > middleware = import_string(middleware_path) > File > "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", > line 24, in import_string > ) from err > ImportError: Module "django.contrib.auth.middleware" does not define a > "SessionAuthenticationMiddleware" attribute/class > unable to load app 0 (mountpoint='') (callable not found or import error) > *** no app loaded. going in full dynamic mode *** > *** uWSGI is running in multiple interpreter mode *** > spawned uWSGI master process (pid: 1) > spawned uWSGI worker 1 (pid: 37, cores: 2) > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > > As per my investigation, this error possibly caused by Django upgrade: > > *The SessionAuthenticationMiddleware class is removed. It provided no > functionality since session authentication is unconditionally enabled in > Django 1.10.* > > See https://docs.djangoproject.com/en/2.0/releases/2.0/ > > After I've removed the line > > https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… > from settings.py, the container is finally working. > > I've placed PR in github: > https://github.com/maxking/docker-mailman/pull/314 > > > Thank you for your contributions! > > I have merged your pull request and it should now be out (hopefully!). > > > Thank you for your help. > > Danil > > > пт, 1 мар. 2019 г. в 04:33, Abhilash Raj <maxking(a)asynchronous.in>: > > > > On Thu, Feb 28, 2019, at 5:19 PM, Abhilash Raj wrote: > > On February 27, 2019 11:53:34 PM PST, Danil Smirnov <danil(a)smirnov.la> > wrote: > > >Hi Mark, > > > > > >Actually all this stuff happens inside the container after it's started > > >and > > >initialized without errors. I didn't amend the image anyhow. > > > > > >Also I have the configuration based on docker-compose.yaml provided in > > >the > > >repository which works just fine for mailman-web image. > > > > > >The very same config with postorius image (+ UWSGI_STATIC_MAP param) > > >fails > > >with 500 error... > > > > > >Now answering your questions: > > > > > >ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > > > > > >> do you have django-q in INSTALLED_APPS in your Django settings and > > >what > > >> is set for Q_CLUSTER? > > >> > > > > > >I've checked settings.py inside the container and I haven't found any > > >of > > >the mentioned configurations there. > > > > > >Does the manage.py that's being run here point to the right > > >settings.py? > > >> > > > > > >No clue. > > > > > >Also I wonder why we have some Hyperkitty-related cronjobs in non-HK > > >configured image? > > > > > > > https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… > > > > Because I am a dum dum ;-) > > > > Will work on removing those crons and stuff. Would be nice if you > > opened an issue on Github so that I don't forget. > > Should now be fixed in the latest image. > > > > > >Danil > > > > > > > > > > > >> -- > > >> 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/ > > >> > > >_______________________________________________ > > >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/ > > > > > > -- > > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > -- > thanks, > Abhilash Raj (maxking) > > > -- > thanks, > Abhilash Raj (maxking) > > >

6 years, 7 months

Re: My list has been switched from public to private archives, but they are still visible

by Abhilash Raj

On Thu, Sep 19, 2019, at 11:42 AM, Enrique Terrazas wrote: > Thank you Abhilash, > I appreciate your prompt response. What about the once private archives becoming public after setting a list to “Do not archive this list”? Is this something you are observing? It is most definitely a bug, Hyperkitty should leave the archive in whatever previous state they were in before the "Do not archive this list" setting was added. My suspicion is that when Do Not archive list setting is enforced, Hyperkitty sets the default visibility, which I think is Public. Can you file a but at gitlab.com/mailman/hyperkitty/issues ? > Regards, > Enrique > > >> On Sep 19, 2019, at 1:38 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> >> On Thu, Sep 19, 2019, at 11:15 AM, Enrique Terrazas wrote: >> >>> I am having a very similar issue. Here is what I have found: >>> >>> There are basically three archive settings we can select via the >>> postorious web front end for archives. These can be found in: Settings >>> >>>> Archiving and they are: >>> Public archives >>> Private archives >>> Do not archive this list >>> >> >> This is interface of Mailman to set the archives. >> >> >>> >>> In the Django administrative interface we can find those >>> same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists >>> >>>> Mailing List object(x) > Archive policy: >>> never >>> private >>> public >>> >> >> This is basically a hotline to the database. You can change these values, >> but they would be overriden with the values that are in Mailman Core on >> the daily cron job run. >> >> I would suggest not to tinker with values there since you could leave >> database in a corrupted state. Since there is an ORM layer there, chances >> are less but still a possibility :) >> >> >>> >>> I’m not sure which of the two takes precedence. My guess is postorius >>> since that is a list owner accessible setting and the Django >>> administrative interface would typically not be accessible to list >>> owners. We have noticed the following odd behavior, not sure if it is a >>> bug. For existing lists with private archives, when switching to “Do >>> not archive this list” in postorious, the desired effect of no longer >>> archiving the list is instantaneous. However, after the daily cron job >>> that syncs with Mailman Core happens, the existing archives now become >>> publicly accessible. Is this behavior based on the assumption that the >>> list will no longer be archived and will therefore be purged? >> >> >> Source of truth is Mailman Core's database. Postorius is a front-end to >> change that and owners have permissions to do that. >> >> Hyperkitty only syncs back that information daily. I have a fix in the >> master which makes such that this information is synced synchronously >> and is available immediately to Hyperkitty. >> >> For now, you could either run the "python manage.py runjobs --daily" or >> wait for a day if that is possible. >> >> >>> Enrique >>> >>> >>>> On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>>> >>>> On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote: >>>> >>>>> Can anyone help with this? >>>>> >>>>> I set my list to private archives today. Up until then, it was pubic. >>>>> And yet, if you go to the list page, you will see that if you click >>>>> archives (top left), you can see them. (Filled with a bunch of tests >>>>> posts for now) >>>> >>>> This change takes a bit of time to sync up Hyperkitty. THere is a daily >>>> cron job which syncs this information from Mailman Core. >>>> >>>> I have made a change which should fix this problem and the process would >>>> become synchronous. >>>> >>>> You can run `python manage.py runjobs --daily` command to force sync >>>> that information. >>>> >>>> >>>>> >>>>> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.toky… >>>>> >>>>> Am I misunderstanding what a private archive is? >>>> >>>> Not really, your expectation is right. >>>> >>>> >>>>> >>>>> Is something wrong with my setup (which is hosted)? >>>>> >>>>> Thank you. >>>>> _______________________________________________ >>>>> Mailman-users mailing list -- mailman-users(a)mailman3.org >>>>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >>>>> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… >>>>> >>>> >>>> -- >>>> 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… >>> >>> >> >> -- >> 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… -- thanks, Abhilash Raj (maxking)

6 years, 1 month

Re: Confusing mailman user model

by Gilles Filippini

Mark Sapiro a écrit le 19/07/2020 à 17:30 : > On 7/19/20 8:10 AM, Gilles Filippini wrote: >> Hi, >> >> I'm trying to understand the Mailman user model, and I'm confused about >> the respective roles of tables 'auth_user' and 'user'. > > > auth_user is a Django auth table. These are the users listed in the > Django admin web UI. > > user is Mailman core's users. > > >> Both have an 'id' column referred to as 'user_id' when used as a foreign >> key. But there seems to be no relation at all between them as they use >> different ids for the same user. > > > Right, they are unrelated. > > >> Our mailman server was migrated from mailman2 to mailman3 about 1.5 year >> ago, and there is an inconsistency I'd like to fix: >> 2 of our users have a registered Mailman account with their respective >> email addresses in table 'auth_user', but these very same addresses in >> the 'address' table are linked to another old admin account in the >> 'user' table. > > Their Mailman account is the 'old' one. the auth_user account is a > Django account >> >> Then if add one of these addresses as a domain owner, it it the old >> admin address which is selected instead. How could I fix that? > > > That's because domain owner in a Mailman thing and involvs the Mailman > user. You could delete the Django users via the Django admin UI and then > re-register them via Postorius. That *might* work. When login into postorius, it is the Django account that is used, right? Then how is the mailman account retrieved from there? It seems UUIDs are used in the process, but I fail understanding how, so far. Wouldn't it be safe to retrieve the new Mailman account associated to these Django users, and link there emails from 'address' table' to them? _g.

5 years, 3 months

Re: Counter-intuitive header filter processing

by Jonas Meurer

Hi Mark, Am 18.09.2018 um 20:48 schrieb Mark Sapiro: > On 09/18/2018 10:26 AM, Jonas Meurer wrote: >> >> Apparently, that's not the case. If the default message acceptance >> setting for members is set to "reject", then mails from >> *(a)freesources.org get rejected even though the header filter says >> "accept". In other words, the default message acceptance action seems to >> overrule any header filters. >> >> Is this expected behaviour? > > > Yes. Rules are normally checked in a sequence defined in > mailman/chains/builtin.py and that sequence checks several things > including member moderation before checking header matches, so if > "Default action to take when a member posts to the list" is anything > other than "Default processing", that action will take precedence over > header matches. Thanks for the clarification. Maybe then the description for chain "accept" in postorius needs to be adjusted. Currently it says "Accept immediately (bypass other rules)". This gives the impression, that it will overrule the default action. A related followup question: what configuration is recommended for an announcement list where only specific senders (e.g. sender(a)example.org) should be allowed to post and mail from all (other) subscribers should be rejected? The only way I see to achieve this currently is: * Set default action for member posts to "Default processing" * Add a header filter to accept "sender(a)example.org" * Add a header filter to reject ".*" In my eyes, that's very counter-intuitive and cumbersome to configure. But maybe I just missed a more obvious and elegant solution to achieve the same? And one more comment: if I make the list an "anonymous list" (i.e. "hide the sender of a message, replacing it with the list address"), then header filters for the "from" header don't work any longer. That's kind of unexpected as well. I would have expected mailman to process the header filters at reading the incoming mail, not after rewriting headers of the outgoing mail? Cheers jonas

7 years, 1 month

Re: Post-installation documentation?

by Mark Sapiro

On 11/24/21 9:40 AM, David Newman wrote: > > IMO post-installation docs for list admins would be a big help in > Mailman3 adoption. I'm willing to help with this. Thank you for being willing to contribute. I think the place for list admin docs would be in the https://gitlab.com/mailman/mailman-suite-doc project which is the source for https://docs.mailman3.org/en/latest/. There is currently a userguide there at source/userguide.rst and referenced from source/index.rst. the addition of an adminguide.rst would be welcom if you want to work on that. > When I say "working": I'm looking to migrate Mailman2 mailing lists to > Mailman3, but am struggling with even basic setup tasks before we > attempt list migtration. > > For example, on admin page I've set up two lists, one public and one > private (each with unique list IDs), but neither appear in the site's > list index. Here are the steps to migrate a 2.1 list named `alist(a)example.com` and its archives. run Mailman's `bin/mailman create alist(a)example.com` follow that with ``` bin/mailman import21 alist(a)example.com /path/to/mailman2.1/lists/alist/config.pck ``` That will create the list and import its members and settings. To import archives run the Django admin command with arguments ``` hyperkitty_import -l alist(a)example.com /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox ``` > And I don't know where to add list members. For imported lists, they are already added, but for new lists, you can add them in Postorius under Mass operations -> Mass subscribe or via the bin/mailman commands `addmembers` or `syncmembers`. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > And clicking the site archives link throws this error: > > django.urls.exceptions.NoReverseMatch: Reverse for 'hk_list_overview' > with keyword arguments '{'mlist_fqdn': 'wheee'}' not found. 1 pattern(s) > tried: ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/$'] Did you specify the list's fqdn as in https://www.example.com/archives/list/list@example.com/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

Mailman-users search results for query "Postorius"