Search results for "Postorius" - Mailman-users

Re: Apache+mod_wsgi issue

by Stephen J. Turnbull

Odhiambo Washington writes: > > 2. apache.conf > > > <CUT> > > > ... > > > Alias /static "/opt/mailman/mm/static" > > > <Directory "/opt/mailman/mm/static"> > > > Require all granted > > > </Directory> > > > # WSGIScriptAlias /mailman3 /opt/mailman/mm/wsgi.py > > > # WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py > > > # WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py > > > # WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py > > > # WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py > > > # WSGIScriptAlias /hyperkitty /opt/mailman/mm/wsgi.py > > > # WSGIScriptAlias /postorius /opt/mailman/mm/wsgi.py > > > WSGIScriptAlias / /opt/mailman/mm/wsgi.py > > > > This will send every http request to mod_wsgi except for requests to > > /static. This is OK if there are no other web sites on this server and > > the only http requests are for Django related things. > > This is just a virtual host. There are other websites on the server. If the above lines are in the virtual host element, they won't interfere with the other websites. If they are at top level, they will.

2 years, 11 months

Re: Apache Conf

by Thomas G

Same result with Alias "/static/" "/opt/mailman/static/" I have sometimes: [Fri Oct 19 22:05:52.583841 2018] [proxy_http:error] [pid 8328:tid 140435053815552] (104)Connection reset by peer: [client 1xxxxxxx1794] AH01102: error reading status line from remote server localhost:8000 [Fri Oct 19 22:05:52.583874 2018] [proxy:error] [pid 8328:tid 140435053815552] [client 1xxxxxxx:51794] AH00898: Error reading from remote server returned by /static/hyperkitty/libs/jquery/jquery-1.10.1.min.js But it's not systematic. Alias seem to be ignored by the proxy. Le ven. 19 oct. 2018 à 20:48, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/19/18 12:17 PM, Thomas G wrote: > > Hi tried both. > > > > Same result. > > > > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js > > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) > > Gecko/20100101 Firefox/60.0" > > > What's in the apache error log? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 2 months

Re: Member Issue Discovered

by Stephen J. Turnbull

Brian Carpenter writes: > This is in regard to our Affinity/Empathy UIs. I believe the issue > [about data retention] that was raised originally in this > thread/post still exists with Postorius/Hyperkitty. I don't speak *for* the Mailman team on this, but my *impression* from these conversations is that we have a consensus on the team: deleting the User data (authentication and profile) is a very big deal that should be done only on explicit request, not as an automatic side effect of other changes. We understand that others have a different opinion, but we think that this is a difference of opinion, not a mistake on either side. My own suggestion is that we *should* provide the *option* to delete the User data, and prompt for it, when that User's last subscription on the server is deleted. Note that there is a race condition where the user deletes the second-to-last subscription and an admin then deletes the last one. The user won't see the option, but the admin will. I can see this as a bad outcome, depending on user's intent, whether the admin deletes the User object or leaves it in place.

5 years, 1 month

LMTP not listening

by Bartosz Sawicki

Hi everyone :), This is my first post in this group, so let me thank all of the developers for incredible work with Mailman3. Special congratulations goes to new project leader, Abhilash :) I've been using Mailman2 from over 15 years, and recently decided that it is time to upgrade. For several days I'm playing with all of the components of the system. Currently everything looks to be working nicely :) Mailman-core, Mailman-suite (Postorius, Hyperkitty) installed directly, not using docker containers. The last step was integration with MTA. I've configured Postfix and Mailman-core according to: https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#mailman-… But messages send to the list address are not delivered to the list :( I've started to investigate whats happening and realize that Postfix can not connect to mailman using LMTP. It seems that mailman is not listening on port 8024. Nov 24 13:12:31 lists postfix/lmtp[2737]: connect to 127.0.0.1[127.0.0.1]:8024: Connection refused I've checked log files, but haven't realize anything unusual . Any ideas where I could try to find cause of the problem ? My mailman.cfg file MTA section: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost lmtp_port: 8024 smtp_host: localhost smtp_port: 25 regrds.

8 years

Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Barry Warsaw

On Dec 09, 2016, at 09:37 AM, Mark Sapiro wrote: >I understand you need to feel comfortable about everything going into >the core and this takes time and energy to review all the MRs, but I >think it is pretty important to get the DMARC mitigations into the core. >If there's anything I can do to help with this, let me know. > >I will rebase my branch again and possibly make one minor tweak, but I >think it should be OK. Thanks for pushing back on this Mark. Obviously, I have a high degree of trust in your work, but yeah, my compulsive behavior is showing through. ;) Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. >I can also work on Postorius. Also in this vein I have a question. >Should the DMARC settings be added to the Alter Messages tab in the List >Settings view or would it be better to have a separate DMARC Mitigations >tab. My gut reaction is to add a separate DMARC Mitigations tab, but Florian and Terri have final say I think. Cheers, -Barry

9 years

Re: Strange problem in user lists

by Mark Sapiro

On 12/16/21 2:25 AM, Gelpi Andrea wrote: > > I cant' understand why, but I have two members with the wrong name. > > "A B" <C(a)dom.tld> > "D E" <F(a)dom.tld> > > My problem is that A and B must be associated with F(a)dom.tld and vice-versa. > > I tried to delete the user member and recreate it, but it has always the > wrong name. Because the display name is associated with the Mailman user and unsubscribing the user from the list doesn't change the user. > Is it possible to correct those errors? How? The user can log in to the web UI and go to the Account link in the dropdown at the username at the upper right and change the first and last name there. If you have a recent enough Postorius, a site admin can go to the Users link at the top of a page find the user, click Manage and change the Display Name. Otherwise, you can do this in `mailman shell` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

Re: Installing mailman 3

by Rafael Mora

Ok, so how do I config Postfix to send emails via my domain? i.e. using the email account mailing(a)labbrands.com ?? Thanks El mar., 25 jul. 2017 a las 15:33, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 01:21 PM, Rafael Mora wrote: > > Regarding this: > > > > # To be added to Django's settings.py > > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > > EMAIL_HOST = 'localhost' > > EMAIL_PORT = 25 > > EMAIL_HOST_USER = <username> > > EMAIL_HOST_PASSWORD = <password> > > > > > > > > What should I use for username and password? > > Should I keep the localhost on the host param? > > > If you want Django (i.e. Postorius, Hyperkitty and Django > admin/auth/etc.) to deliver via localhost, you don't need > EMAIL_HOST_USER and EMAIL_HOST_PASSWORD. Those are only for > authentication to some other host. > > -- > 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, 4 months

Re: Chinese characters in list name shows question mark (?)

by Franklin Weng

Hi Mark, Mark Sapiro 於 2019/10/26 上午2:08 寫道: > The issue is the list welcome message is sent in the character set of > the new member's preferred language and if that is not set in the > subscription request, and it's not possible to do that in Postorius, it > defaults to the installation's preferred language. > > It should probably default to the list's preferred language. See > <https://gitlab.com/mailman/mailman/issues/608> > > You have two choices: > > You can set the installation's default language by putting > > [mailman] > default_language: zh_TW > > in your mailman.cfg, or you can leave the default language English and > set the character set for English to utf-8 by putting > > [language.en] > charset: utf-8 > > in your mailman.cfg. Thanks for your help. After trying I found that it only worked when I set the [language.en] charset to utf-8. If I didn't set this but only set default_language in [mailman] section to zh_TW it still sent ? in the welcome messages. I commented in the issue. Thanks, Franklin

6 years, 1 month

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

by Andreas Barth

* Brian Carpenter (brian_carpenter(a)emwd.com) [210226 13:29]: > On 2/26/21 6:55 AM, Andreas Barth wrote: > >>Hm, it completely ignores the standard way for Debian: > >>apt-get install mailman3-full > >>also exim4 as standard mailer. > >>And apache2. > >That's how I did it (for my first installation), and it worked out of > >the box. However I would recommend to directly use a real database > >(e.g. postgresql). > Except my How-to will give you the latest stable versions of Mailman > 3, Postorius, and Hyperkitty and PostgreSQL instead of sqlite. The default debian way also uses postgresql if you install postgresql and make the relevant selection while installing mailman3-full (or later with dpkg-reconfigure). Re the "latest greatest", that's always the same question for all software. If one is happy what comes from the distribution, I always recommend to use that (or just use the currently developed stable version, i.e. testing or unstable, perhaps even only for these packages). If one needs something newer / else / specific local patches, it's good to have documentation that helps. Andi

4 years, 9 months

Re: Mailman archive issues (Hyperkitty)

by Ruth Ivimey-Cook

On 03/06/2021 15:09, Mark Sapiro wrote: > On 6/3/21 1:06 AM, Kimmo L wrote: >> Thanks for the quick replay! >> If its not a big trouble, could you kindly give me some advice/guide >> how upgrade my Hyperkitty/Postorius/Django from python2 to python3. >> I would be very grateful. > > > It depends heavily on how Mailman was installed to begin with, but > essentially you just upgrade the various components to the latest > versions using pip. Some things you need to be aware of are at > https://docs.mailman3.org/en/latest/upgrade-3.2.html If you start with python libs installed using a package manager (apt, yum, etc) and later upgrade them using pip, make sure you lock the packages at their current version so they cannot be changed by package updates, or you'll eventually have the package manager do an unintended downgrade. It is usually best to start with a distinct installation from pip, into a python venv to avoid changing system libs. You can of course seed that install with the current setup first! Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 6 months

Mailman-users search results for query "Postorius"