Search results for "2021" - Mailman-users

Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Mark Sapiro

On 10/25/21 1:45 AM, Stefan Bauer wrote: > Dear Users, > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > web-interface via > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > I receive > > Not Found: /mailman//postorius/lists/ > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core > 1) > > Where does the wrong path come from (mailman vs. mailman3) See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ... > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> Others have found that removing the trailing slash from ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ to make it ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost fixes the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: Trying to set up mailman3 on my mail server

by Mark Dadgar

On Oct 15, 2021, at 7:46 AM, Shawn Heisey <mailman(a)elyograg.org> wrote: > On 10/14/21 10:09 PM, Mark Dadgar wrote: >> I REALLY encourage you not to install via the Ubuntu packages. A number of us here have done so and it always ends in tears. I ended up paying someone to re-install for me via pip so I had a clean baseline to admin from going forward. > > I had lots of trouble with the pip/venv setup. So I decided to give the docker route a try. Having trouble with that too. Looking over the instructions, I seem to have missed some of the info on my first try. I will give it another whirl after my work shift ends today. That’s actually why I paid someone to do in the initial install. While I have 3+ decades of UNIX-like admin experience, I am not even remotely well-versed in Python and its ecosystem and/or Docker. Unfortunately, the person I hired, who did a great job and has contributed mightily to this community, is no longer with us. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

3 years, 8 months

Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sat, 2021-12-25 at 11:01 -0500, William Oliver wrote: > > . > [snip] > However, when I try to sent an email *to* the list from either > account, > I get the following error: > > This is the mail system at host mail.libertyfp.org. > > I'm sorry to have to inform you that your message could not > be delivered to one or more recipients. It's attached below. > > For further assistance, please send mail to postmaster. > > If you do so, please include this problem report. You can > delete your own text from the attached returned message. > > The mail system > > <"lmtp:[mail.libertyfp.org]:8024"@libertyfp.org> (expanded from > <fplist(a)libertyfp.org>): unknown user: > "lmtp:[mail.libertyfp.org]:8024@libertyfp.org" > > Apparently, fplist(a)libertyfp.org is getting rewritten to > 8024(a)libertyfp.org. Another data point. When Ichange the port number in mailman.cfg, the error changes to reflect it. When I change the port to 8055, I get: The mail system <"lmtp:[mail.libertyfp.org]:8055"@libertyfp.org> (expanded from <fplist(a)libertyfp.org>): unknown user: "lmtp:[mail.libertyfp.org]:8055@libertyfp.org"

3 years, 6 months

Re: Mailman 3 Installation

by Mark Dadgar

On Jan 16, 2021, at 7:31 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/16/21 6:06 PM, bruce.dubbs(a)gmail.com wrote: >> I do have sqlite installed, but the documentation discusses mysql/mariadb and postresql. What are the considerations as to why I would need one of these other DBs? > > You can use sqlite, but if you don't already have a mysql/mariadb > database on the server, we recommend postgresql for performance and > robustness. I personally have had issues with mysql and use postgresql > on one production server that uses mysql for other applications. I’ll word this a little more strongly: do not use sqlite for a production server. Do not "just start with sqlite to get it running and then I’ll migrate it to something else down the road.” There is currently no validated way to migrate a mailman3 instance from sqlite to something else, and by “no validated way” what I actually mean is “no one has managed to get this to work, me included.” Put in the extra effort to start with posgresql or mysql/mariadb up front. You’ll regret it if you don’t. Ask me how I know. 😁 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 5 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, 1 month

Re: accept mails from several Users, not list members beside members, howto

by Abhilash Raj

On Mon, Jul 12, 2021, at 6:23 AM, Lars Schimmer wrote: > Hi > > I do look out for a method to accept mails from list members and a > number of 20-30 Email addresses (not list members) to a mailing list. > All others should be denied to post to the list. > > I can add those as non-members, but AFAIK I cannot define a special rule > for them in "message acceptance". You can go to Users -> Non-Members and find the non-members you want to allow posting for and then go into their preferences and set their Moderation Action to "Default processing". > Under "message acceptance" the line "non-members" is set to deny, but if > I set it to "default procesessing" - will it allow ALL email addresses, > or just the group of "non-member" users? Yes, that will allow all non-members to post, which probably isn't what you want from what I gather. You want the default policy to be deny and then set moderation action on each individual non-member. -- thanks, Abhilash Raj (maxking)

3 years, 11 months

Re: Mailman import of 2000 lists

by Abhilash Raj

On Thu, Oct 7, 2021, at 11:23 AM, dancab(a)caltech.edu wrote: > I'm working on importing nearly 2000 lists and have been doing some > testing prior to migrating from Mailman2. > > I'm using the mailman create command via for loop. It takes quite a > while to do all the work including updating MySQL and re-generating the > LMTP files for each list. As the number of lists increases the process > gets slower. > > Do you have any recommendations for speeding up this process? I am > running the system in AWS using EFS for storage of the LMTP files. There isn't a way to disable creation of LMTP files, but if this instance you are running on isn't live, then you can configure Mailman with NullMTA so it won't try to generate LMTP files. [mta] # NullMTA is just implementing the interface and thus satisfying Mailman # without doing anything fancy outgoing: mailman.mta.null.NullMTA You need to add ^ to mailman.cfg, commenting out the _real_ outgoing MTA configuration. Once you are done with the migration, you can configure the right MTA and run `mailman aliases` command to generate them. -- thanks, Abhilash Raj (maxking)

3 years, 8 months

Mailman 3 centos7 installation issues

by Stephen J. Turnbull

bader(a)cchmc.org writes: Note: Abhilash already answered the installation questions. I have nothing to add there. My recommendations on using 3.6 are my personal take, YMMV. > Also, we are using python 3.6, will that be a major issue? It shouldn't be. In a quick look I see no features in Python 3.7 or 3.8 that would make us want to bump our minimum supported Python version soon. However, Python 3.6 is in source-only, security fixes only support, and that will end in December. I would be uncomfortable with exposing that to the Internet. I would check if the distro package up to date (current Python.org release is 3.6.13 on 2021-02-15, or at least 3.6.12 on 2020-08-17)? > or should spend the time to install 3.7 from source? I don't recommend investing effort in 3.7 because it is already in source-only, security fixes only support, although that goes until mid-2023. 3.8 goes into that mode in May of this year. If you're going to install from source just for Mailman, I would recommend bumping to 3.9 at least if it's supported for your version of Centos, and 3.8 if for some reason 3.9 doesn't want to work on your system. Steve

4 years, 3 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Brian Carpenter

On 2/13/21 10:37 AM, Jim Popovitch via Mailman-users wrote: > On Sat, 2021-02-13 at 08:01 -0500, Brian Carpenter wrote: >> Features are not the only thing about a modern UI, UX design plays a >> MAJOR role in the modern UI. Postorius should have at least matched MM2 >> in features in regards to something as important as Member management >> but instead it took a step back into the dark ages. > I'm gonna be a dick and remind you that less than 1 year ago you were > trying to convince me that MM3 was a gift from god and that it was time > for me to jump from MM2 to MM3 because it was sooo easy and such a time > saver.. or something like that. The point being, you yourself just > still aren't happy with MM3. Welcome to the club. I am very happy with MM3 just not with Postorius. MM3 allowed me to come up with my own admin interface. Mailman 2 would never allowed me to do that. So please leave your Mailman 2 bondage and come over to Mailman 3. We have cookies! -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 4 months

Re: error changed after restart (was: KeyError: 'get_requests_count' after an upgrade)

by Abhilash Raj

On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > I restarted de server and the error changed. Now the log shows > "KeyError: 'subscription_mode'": Did you also restart Mailman Core after the upgrade? > > ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server > Error: /mailman3/mailman3/lists/name_and_domain.of.the.list > Traceback (most recent call last): > File > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > line 119, in __getattr__ > return self._get(name) > File > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > line 86, in _get > raise KeyError(key) > KeyError: 'subscription_mode' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", > line 34, in inner > response = get_response(request) > File > "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", > line 115, in _get_response > response = self.process_exception_by_middleware(e, request) > File > "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", > line 113, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File > "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", > line 71, in view > return self.dispatch(request, *args, **kwargs) > File > "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", > line 74, in dispatch > return super(MailingListView, self).dispatch(request, *args, **kwargs) > File > "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", > line 97, in dispatch > return handler(request, *args, **kwargs) > File > "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line > 295, in get > member.subscription_mode == > File > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > line 124, in __getattr__ > self.__class__.__name__, name)) > AttributeError: 'Member' object has no attribute 'subscription_mode' > *********************** > some info about the installed versions via pip list: > pip list | grep django > django-allauth 0.44.0 > django-appconf 1.0.4 > django-compressor 2.4 > django-extensions 3.1.0 > django-gravatar2 1.4.4 > django-haystack 3.0 > django-mailman3 1.3.5 > django-picklefield 3.0.1 > django-q 1.3.4 > djangorestframework 3.12.2 > > pip list | grep mailman > django-mailman3 1.3.5 > mailman 3.3.3 > mailman-hyperkitty 1.1.0 > mailmanclient 3.3.2 > > pip list | grep postorius > postorius 1.3.4 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I've just upgrade mailman 3 installation following Mr. Sapiro advice: > > did a > > > > pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient > > mailman-hyperkitty postorius > > > > I did a "python3 manage.py migrate" after, too. > > > > And all seemed to run well. > > > > All the lists showed in postorius via web, but when I try to accesss > > into one of them the browser shows an error. > > > > In the log you can see: > > > > *-*-*-*-*-*-* > > > > Traceback (most recent call last): > > File > > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > > line 119, in __getattr__ > > return self._get(name) > > File > > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > > line 86, in _get > > raise KeyError(key) > > KeyError: 'get_requests_count' > > > > ... (And after all the traceback lines) > > > > AttributeError: 'MailingList' object has no attribute > > 'get_requests_count' > > > > *-*-*-*-*-*-*-* > > > > The lists seem to be distributing messeages well.. but I cannot acces > > via web administration (django/postorius) > > > > Can anyone point me in the right direction to solve this, please? > > > > _______________________________________________ > > 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/ > -- thanks, Abhilash Raj (maxking)

4 years, 4 months

Mailman-users search results for query "2021"