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

[MM3-users] Re: Postorius no connection to REST API

by Mark Sapiro

On 8/11/21 4:18 AM, Richard Rosner wrote: > Mark Sapiro wrote: >>> You are in a better position to answer that than am I. >> What does sudo netstat -lntp show? > > A lot. But since most of that isn't relevant here: > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name > tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 20241/master > tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 14076/python3 > tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 20241/master > tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 14080/python3 So some python3 process is listening on port 8001 > tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 20241/master > tcp6 0 0 :::80 :::* LISTEN 13882/apache2 > tcp6 0 0 :::465 :::* LISTEN 20241/master > tcp6 0 0 :::25 :::* LISTEN 20241/master > tcp6 0 0 :::443 :::* LISTEN 13882/apache2 > tcp6 0 0 :::587 :::* LISTEN 20241/master > >> What does ps -fwwa|grep rest show? > > root 15055 14843 0 12:58 pts/1 00:00:00 grep rest > > So whatever it's supposed to find, it's not there But whatever is listening on port 8001 is apparently not Mailman's rest server. What does ps -fww 14080 or whatever PID is currently listening on port 8001 show. >>> mailman3-web.service must also run as list. > > I changed that. It didn't like it. OK. Perhaps instead you should have uid: list gid: list in your uwsgi configuration if you don't already. > >>> So, what do you have in your apache config for proxying to uwsgi and >> what's your uwsgi configuration. > > lists-ssl.conf: > <VirtualHost *:443> > ServerAdmin admin(a)domain.de > ServerName lists.domain.de > > Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass "/mailman3" "unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost:8001/" I'm not familiar enough with this form of ProxyPass using sockets to understand what the localhost:8001 does in this context, but uwsgi should not be doing anything with port 8001. In a configuration using TCP, it would listen on port 8000. Port 8001 is where Mailman's REST API server listens. uwsgi should receive connects in your case via the unix socket and then pass them to Django via the application in wsgi.py Also, you may want other paths proxied to uwsgi, namely at least some of hyperkitty, postorius, archives, accounts, admin and user-profile. > </IfModule> ... > I guess with uwsgi config you mean the /etc/mailman3/uwsgi.ini file? > [uwsgi] > # Port on which uwsgi will be listening. > uwsgi-socket = /run/mailman3-web/uwsgi.sock > > #Enable threading for python > enable-threads = true > > # Move to the directory wher the django files are. > chdir = /usr/share/mailman3-web > > # Use the wsgi file provided with the django project. > wsgi-file = wsgi.py > > # Setup default number of processes and threads per process. > master = true > process = 2 > threads = 2 > > # Drop privielges and don't run as root. > uid = www-data > gid = www-data These should be 'list', not 'www-data'. That's your permissions issue on settings.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Error when click on mailing list: An error occurred while processing your request.

by Mark Sapiro

On 7/9/24 12:32 AM, adam.heathcote(a)utas.edu.au wrote: > Hey there, > > We have a Mailman3 server with quite a few lists all running with no issues. > Recently I imported a list from our old Mailman 2 server which went fine. > > I attempted to remove the current owner and add myself but now when clicking on the list, Postorius shows: An error occurred while processing your request. > > The output of /opt/mailman/web/logs/mailmanweb.log is here: > > ERROR 2024-07-09 17:11:33,371 2795 django.request Internal Server Error: /mailman3/lists/net-ops.list.utas.edu.au/ > Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.9/site-packages/django/core/handlers/exception.py", line 56, in inner > response = get_response(request) ... > TypeError: sequence item 1: expected str instance, NoneType found Was there more in the log? I.e., a line like The above exception was the direct cause of the following exception: followed by another traceback. If so, what was that? Is there anything in Mailman core's mailman.log? > I've tried removing it and reimporting it to no avail. Is there anything I can besides manually creating it and adding the members and owners from the old server? What do you get from Mailman's ``` mailman members -R owner your_list(a)your.domain ``` If this doesn't list you, try something like this: ``` $ mailman shell -l your_list(a)your.domain Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the your_list(a)your.domain mailing list >>> from mailman.app.membership import add_member >>> um = getUtility(IUserManager) >>> usr = um.get_user('adam.heathcote(a)utas.edu.au') >>> rr = RequestRecord(usr.preferred_address.email, usr.display_name, None) >>> add_member(m, rr, MemberRole.owner) >>> commit() >>> exit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I did that but I don't have a maillog for today 07.24.2017 Is there another place to look for? El lun., 24 jul. 2017 a las 16:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 07:41 AM, Rafael Mora wrote: > > Ok, I ran 'mailman aliases', what should I do now? > > > Assuming mail delivery is not working, look in /var/log/maillog for > messages with timestamps around the time that the mail was generated. > Then try to figure out what they are saying. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 9 months

[MM3-users] Re: Is there an easy way to set Reply-To to a lists owner?

by Mark Sapiro

On 12/4/22 01:50, Martin Lorenz wrote: > > Now the admin of theses lists (who happens to be my wife) asked me, if it was possible to change the settings such that all replys to one of these lists can only be sent to herself (i.e. the owner address) instead of being held for moderation. > > I thought of setting Reply-To to something like <list-owner> by "simply" entering a Variable into this field, instead of using the admins/owners literal email-address. First of all, you can't really control where replies will go. This is dependent on the user's MUA and what the user does. However, you can set things so that replies will likely go where you want. Here are various options for the Postorius -> Alter Messages `Explicit reply-to address` and `Reply goes to list` settings. If the sender of all the posts to the list is the list owner, just set `Reply goes to list` to `No Munging` and a `reply` will go to the sender, but `reply-all` will go to the sender and the list, and if the user's MUA offers it, `reply-list` will go to only the list. To avoid the `reply-list` issue, set `Include the list post header` to `No` and to avoid the `reply-all` issue, set `Message Acceptance -> Require Explicit Destination` to `No` and post with the list address in Bcc:. If the sender is someone else, set `Explicit reply-to address` to `LISTNAME-owner(a)LIST.DOMAIN` and set `Reply goes to list` to `Explicit Reply-to set; no Cc added`. Also set `Include the list post header` to `No` and consider setting `Message Acceptance -> Require Explicit Destination` to `No` and posting with the list address in Bcc: as above. Note that `LISTNAME-owner(a)LIST.DOMAIN` is the list posting address with `-owner` added to the local part. This address forwards to the list's owners and moderators. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

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

by Mark Sapiro

On 6/6/23 07:58, Nelson Strother wrote: > > No errors are being recorded in the mailman log files. This is GNU > Mailman 3.3.8 via `pip install mailman` on Debian 5.10.179-1 > (2023-05-12) running on a shared system where VMware gives this server > enough cycles that `mailman start` and `mailman stop` each consume from > 20 minutes to an hour of wall clock time, so I do not issue those > commands recreationally, attempting to keep the system available for > users. What should I do to help understand the cause for these failures? If a runner has died, its death and a reason should be logged in Mailman's var/logs/mailman.log with a message similar to Master detected subprocess exit (pid: 8617, why: SIGNAL 15, class: in, slice: 1/1) This may not be the case if the runner is killed by the OS for an out of memory or similar reason. For this, look in syslog. `mailman stop` can take a long time because it is waiting for a runner to stop. See https://gitlab.com/mailman/mailman/-/issues/255 but that issue was fixed long ago. I don't understand why `mailman start` would take more time than `mailman restart`. In fact, `mailman restart` effectively does `stop` and `start`, but only for those runners which are running. Since you seem to frequently have missing runners, I suspect something like an OOM condition is causing the OS to kill them. Although, I wonder if you are correctly interpreting the logs. While the absence of the `retry`, `task`, `nntp` and `archive` runners might not be noticed except for messages not being archived, if either the `in` or `pipeline` runner is not running, no list posts will be processed. > Would not it be helpful for this limitation of restart to be included in: > mailman restart --help > with a suggestion to use `mailman stop` and `mailman start` instead? I have just filed https://gitlab.com/mailman/mailman/-/issues/1082 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Yes, that was the problem, DEBUG was set to True, then it was changing to filebased the EMAIL_BACKEND. But after turning DEBUG to False I'm not getting the HyperKitty UI formatted, why is that happening?? Thanks El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 9 months

[MM3-users] Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stefan Bauer

awesome! Thank you a lot! Am Mo., 8. Nov. 2021 um 17:37 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 11/8/21 1:03 AM, Stefan Bauer wrote: > > > > how can we configure mailman3, to use STARTTLS when dropping mails to > local > > postfix for final delivery? > > > Set `smtp_secure_mode: starttls` in the `mta` section of mailman.cfg. > See > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… > > -- > 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/ >

4 years, 6 months

[MM3-users] Re: Problems configuring hyperkitty

by Mark Sapiro

On 11/18/24 09:29, Alain D D Williams wrote: > > I am running Debian 12 - Bookworm and have installed the Debian packages. The > database is Mysql. This is not a virtualenv setup. There is no documentation in > the hyperkitty package so I am following: > > https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html The primary support resource for Debian packages is Debian. See https://wiki.list.org/x/12812344 > I read the following: > > "The database can be created with the following command: > > django-admin migrate --pythonpath example_project --settings settings > " > > I assume that that will create some database tables. Hopefully this will have > been done by installing package python3-mailman-hyperkitty. > > • What database & tables will that be ? It would be really useful to be told so > that I can check. The database is configured in the DATABASES setting in your Django settings. The HyperKitty tables all have names beginning with `hyperkitty_`. > • The config file is: /etc/mailman3/mailman-hyperkitty.cfg > This does not contain any comment about databases. Where does hyperkitty get > its database parameters from ? Django, see above. > • I have several different maildomains each with several lists. Some lists in > different domains have the same name. Do I need a different > example_project/settings.py for each domain, if so what changes ? I can't really speak to Debian, but you should be using the Django settings provided as part of Django's mailman-web package, not the ones in hyperkitty/example_project/settings.py as those don't include settings necessary for Postorius. > One of the next things that I will need to do is to import archives from > mailman2. How does the command below change for the different domains ? > > django-admin hyperkitty_import --pythonpath example_project --settings settings -l ADDRESS mbox_file [mbox_file ...] In the `-l ADDRESS` argument the ADDRESS is the fully qualified list address and includes the domain. > > Is there some better documentation that I have failed to find ? Ask Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Change the default value for the General Archive Policy

by Mark Sapiro

On 6/23/25 08:03, Markus Grandpré wrote: > Dear list, > > currently, when I create a new mailing list with MM3 the value for > "Archive policy" is always set to "Public archives". I'd like to change > the default value for "Archive policy" to "Do not archive this list". > How can I do this? In Debian 12 I find in > </usr/lib/python3/dist-packages/postorius/forms/list_forms.py>: ... > but have no idea how to change the settings here. Your help is very > appreciated. Are you creating the list in Postorius. If so, you have a choice for list style. Currently those choices are: ``` Announce only mailing list style. Ordinary discussion mailing list style. Discussion mailing list style with private archives. ``` There is currently no style for a list without archives, but you can implement one. See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… for hints on how to do this with a plugin. Alternatively, you can do it with a patch like: ``` --- a/src/mailman/styles/default.py +++ b/src/mailman/styles/default.py @@ -18,6 +18,7 @@ """Application of list styles to new and existing lists.""" from mailman.core.i18n import _ +from mailman.interfaces.archiver import ArchivePolicy from mailman.interfaces.styles import IStyle from mailman.styles.base import ( Announcement, @@ -91,3 +92,25 @@ class PrivateDefaultStyle( Private.apply(self, mailing_list) Discussion.apply(self, mailing_list) Moderation.apply(self, mailing_list) + + +@public +@implementer(IStyle) +class PublicNoArchiveStyle( + + Identity, BasicOperation, Bounces, Public, Discussion, Moderation): + + """The legacy default style with no archives.""" + + name = 'legacy-default-no-archive' + description = _('Ordinary discussion mailing list style with no archive.') + + def apply(self, mailing_list): + """See `IStyle`.""" + Identity.apply(self, mailing_list) + BasicOperation.apply(self, mailing_list) + Bounces.apply(self, mailing_list) + Public.apply(self, mailing_list) + Discussion.apply(self, mailing_list) + Moderation.apply(self, mailing_list) + mailing_list.archive_policy = ArchivePolicy.never ``` If you are creating lists from the command line `mailman create`, there is a --style-name option to specify the style. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

[MM3-users] Re: How to turn off Emergency Moderation for imported MM2 lists?

by Abhilash Raj

On Thu, Aug 6, 2020, at 6:12 PM, Mark Sapiro wrote: > Mark Sapiro wrote: > > On 7/28/20 5:40 AM, Brian Carpenter wrote: > > > > > > This is the client that I asking about in my post. > > > She said what I > > > did, did not work. This is what I did: > > > > > > Get into a venv as user mailman > > > > > > #mailman shell > > > from mailman.model.mailinglist import MailingList > > > mlist = MailingList('listname(a)listdomain.org') > > > mlist.emergency = False > > > commit() > > > ctrl-d (just to be on the safe side) > > I half understand why this didn't work. Instantiating the list via > ``` > from mailman.model.mailinglist import MailingList > mlist = MailingList('listname(a)listdomain.org') > ``` > for some reason (that's the half I don't understand) does not get the > actual list object so changes you make to it don't affect the actual > list. It is because when you simply instantiate that class, it will create a new model instance, that you would need to persist by adding to database using `store.add(mlist)`. If you instead want to read that instance from database, you have to do `store.query()`, which is what the `.get()` method of IListManager does. > In `mailman shell` you need to do > ``` > mlist = getUtility(IListManager).get('listname(a)listdomain.org') > ``` > `getUtility` and `IListManager` are in the namespace in `mailman > shell`, but outside of that, e.g. just in `python` in your virtualenv, > you also need > ``` > from mailman.interfaces.listmanager import IListManager > from zope.component import getUtility > ``` > > -- > 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)

5 years, 9 months

Search results for query "sapiro"