Search results for "Postorius" - Mailman-users

Re: timezone in hyperkitty

by d-mailman＠undone.org.uk

I've had to find and fix this on an installation today .. If, like mine, all your users will be OK defaulting to one timezone, you can change the default in the database model. I think that, ideally, the application would pick something sensible at account creation time instead .. but this is good enough for me today.. Find the models.py file in django3-mailman eg, if you installed in a venv, it might be somewhere like /opt/mailman/venv/lib/python3.7/site-packages/django_mailman3/models.py Find this line: timezone = models.CharField(max_length=100, choices=TIMEZONES, default="") and change the default to be what you want, eg: timezone = models.CharField(max_length=100, choices=TIMEZONES, default="Europe/London") Now the model needs to be updated, and the software restarted: $ mailman-web makemigrations Migrations for 'django_mailman3': venv/lib/python3.7/site-packages/django_mailman3/migrations/0003_auto_20210521_1212.py - Alter field timezone on profile $ mailman-web migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying django_mailman3.0003_auto_20210521_1212... OK # systemctl restart mailman-web Test by creating a new account and viewing the profile.

3 years, 6 months

Re: URLs in moderation messages

by Mark Sapiro

On 3/3/23 01:55, Tim Cutts wrote: > > I’ve clearly got something wrong in my configuration, but I can’t work out what. > > All my URLs seem to have the “mailman3” part duplicated, i.e. > > Https://example.com/mailman3/mailman3/lists > > Is where I have to go to get a list of my mailing lists, which just doesn’t seem right. > > In my settings.py file I have: > > POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com/mailman3/' > > If I change the value of this to just https://example.com/ it doesn’t change this, That setting has nothing to do with your issue. It only determines the base part of the URL that's used to retrieve templates set in Postorius. What is your web server configuration? This is probably where the problem lies. See https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for a suggested nginx config and https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… for Apache. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

Re: ValueError: ...:EVP_DigestInit_ex:disabled for fips

by Ralf Wiegand

Hello Mark, Can I substitute Django with something that will be FIPS complaint? Can I do without it? Thank You, Ralf On 5/19/20 1:02 PM, Mark Sapiro wrote: > On 5/19/20 5:57 AM, Ralf Wiegand wrote: >> (venv-3.6) [root@maildev mailman-suite_project]# python manage.py migrate >> Operations to perform: >> Apply all migrations: account, admin, auth, contenttypes, >> django_mailman3, django_q, hyperkitty, openid, postorius, sessions, >> sites, socialaccount >> Running migrations: >> Applying contenttypes.0001_initial...Traceback (most recent call last): > ... >> File >> "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/utils.py", >> line 221, in names_digest >> h = hashlib.md5() >> *ValueError: error:060800A3:digital envelope >> routines:EVP_DigestInit_ex:disabled for fips* >> >> >> >> Hello group, I am running into this error. any idea what is going >> wrong here? > This is a Django issue, not Mailman per se. The migration that's failing > is django/contrib/contenttypes/migrations/0001_initial.py. A brief > search seems to indicate that this won't work with NSS FIPS. >

4 years, 6 months

Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Élodie BOSSIER

Le 18/02/2022 à 18:23, Mark Sapiro a écrit : > If you go to https://example.com/mailman3/domains/ (the Domains view > in Postorius) you will see at least two entries, one with Mail Host > ml.franceserv.fr and one with Mail Host ml.viticreation.fr. > > What are the Web Host entries for these? > You should have two separate site entries in the django_site table > (https://example.com/admin/sites/site/) for these domains. Ah alright, now I understand how to proceed and it's working perfectly. I need to add domains through https://ml.franceserv.fr/admin/sites/site/ and define a new site_id for each domain name. Thank you very much for your help. This is my result : https://images.franceserv.fr/images/2022/02/18/06d4eb84a0ded88d55c0296ff0c3… Now, I need to find how to set it automatic when I will add a new list. Perhaps I could do it with an an SQL command if there are no bash command ? I will check with "mailman create" and the --domain argument. Thank you again for your help.

2 years, 9 months

Re: Any possible way to reduce robot spam accounts?

by Franklin Weng

Hi Stephen, Thanks for your reply. Stephen J. Turnbull 於 2023/7/20 21:11 寫道: > Franklin Weng writes: > > > * just let users join from email (lists-join(a)lists.url) instead of > > registering on the mailman instance? or > > What I do is open up the firewall only to ips I have legit users at. > You probably can't do that, but if you can, it's quite effective. > > You could restrict it to email-only subscription in one of the > following ways, > > You can edit the template for the list information to remove the > subscription form. Could you please tell me how to do it? I thought of removing the register link from the web page (upper right corner of /mailman3/postorius/lists/ ) but I couldn't find any web page templates like that. I tried /var/lib/mailman3/web/static but I couldn't even find any keywords like "accounts" or "signup". I don't know how to deal with javascripts. Thanks, Franklin

1 year, 4 months

Re: List description as sender

by Mark Sapiro

On 09/17/2018 01:04 AM, Henrik Rasmussen wrote: > It is the description in the Settings -> List Identity -> Description that is used in the list overview https://list.example.com/postorius/lists/ and also as the "From:" in the mails sent to the subscribers. And it is only the From: in posts delivered to the list members if the list is anonymous. Otherwise the From: is that from the original post to the list or possibly a mumged version thereof in the case of DMARC mitigations. I think your choices are: 1) Don't configure the list as anonymous. 2) Make the list's Description what you think is appropriate for the display name part of the From: header. 3) Modify mailman/handlers/cleanse.py to use something else in the From: header of anonymized posts. 4) Submit an RFE at <https://gitlab.com/mailman/mailman/issues/new> asking for the solution you want and possibly a merge request implementing it. 5) Live with it as is. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

Re: still up to date?

by Abhilash Raj

Specifically, this one https://gitlab.com/mailman/hyperkitty/merge_requests/175 On Tue, Aug 27, 2019, at 11:43 AM, Abhilash Raj wrote: > On Tue, Aug 27, 2019, at 7:14 AM, mailman3(a)malevil.cc wrote: > > I have subscribed to the following rss feeds to keep track of updates: > > > > https://libraries.io/pypi/mailman/versions.atom > > https://libraries.io/pypi/mailman-hyperkitty/versions.atom > > https://libraries.io/pypi/HyperKitty/versions.atom > > https://libraries.io/pypi/postorius/versions.atom > > https://gitlab.com/mailman/mailman-suite/commits/master?feed_token=yitiVdhX… > > > > but none of them was updated for half a year, is that actually the > > status? No current releases or updates for mailman3? > > I am planning a new release, but waiting to find some time to > fix a blocker issue in Hyperkitty. > > > > > _______________________________________________ > > 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) -- thanks, Abhilash Raj (maxking)

5 years, 2 months

Search problem in 3.2.1?

by Mark Dadgar

Anyone seen this before? This is the result of any search query I run. I installed ElasticSearch as the search engine yesterday and this is the result. It is still indexing (large archives). Mailman 3.2.1 from the debian packages in Ubuntu 19.10. - Mark ----- mark(a)pdc-racing.net | 408-348-2878 Begin forwarded message: From: root(a)pdc-racing.net Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/search Date: October 22, 2019 at 7:44:49 AM PDT To: mark(a)pdc-racing.net Internal Server Error: /mailman3/hyperkitty/search UnboundLocalError at /hyperkitty/search local variable 'search_exception' referenced before assignment Request Method: GET Request URL: https://mail.pdc-racing.net/mailman3/hyperkitty/search?q=Ken Django Version: 1.11.22 Python Executable: /usr/bin/uwsgi-core Python Version: 3.7.5 Python Path: ['.', '', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/usr/local/lib/python3.7/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Tue, 22 Oct 2019 14:44:49 +0000 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/paginator.py" in count 79. return self.object_list.count() File "/usr/lib/python3/dist-packages/haystack/query.py" in count 522. return len(self) File "/usr/lib/python3/dist-packages/haystack/query.py" in __len__ 86. self._result_count = self.query.get_count() File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in get_count 619. self.run() File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in run 951. results = self.backend.search(final_query, **search_kwargs) File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in wrapper 33. return func(obj, query_string, *args, **kwargs) File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in search 524. _source=True) File "/usr/local/lib/python3.7/dist-packages/elasticsearch/client/utils.py" in _wrapped 84. return func(*args, params=params, **kwargs) During handling of the above exception (search() got an unexpected keyword argument 'doc_type'), another exception occurred: File "/usr/lib/python3/dist-packages/hyperkitty/views/search.py" in search 90. request.GET.get('count'), File "/usr/lib/python3/dist-packages/django_mailman3/lib/paginator.py" in paginate 72. objects = paginator.page(page_num) File "/usr/lib/python3/dist-packages/django/core/paginator.py" in page 57. number = self.validate_number(number) File "/usr/lib/python3/dist-packages/django/core/paginator.py" in validate_number 46. if number > self.num_pages: File "/usr/lib/python3/dist-packages/django/utils/functional.py" in __get__ 35. res = instance.__dict__[self.name] = self.func(instance) File "/usr/lib/python3/dist-packages/django/core/paginator.py" in num_pages 91. if self.count == 0 and not self.allow_empty_first_page: File "/usr/lib/python3/dist-packages/django/utils/functional.py" in __get__ 35. res = instance.__dict__[self.name] = self.func(instance) File "/usr/lib/python3/dist-packages/django/core/paginator.py" in count 84. return len(self.object_list) File "/usr/lib/python3/dist-packages/haystack/query.py" in __len__ 86. self._result_count = self.query.get_count() File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in get_count 619. self.run() File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in run 951. results = self.backend.search(final_query, **search_kwargs) File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in wrapper 33. return func(obj, query_string, *args, **kwargs) File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in search 524. _source=True) File "/usr/local/lib/python3.7/dist-packages/elasticsearch/client/utils.py" in _wrapped 84. return func(*args, params=params, **kwargs) During handling of the above exception (search() got an unexpected keyword argument 'doc_type'), another exception occurred: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 41. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 187. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/search.py" in search 100. if not isinstance(e, search_exception): Exception Type: UnboundLocalError at /hyperkitty/search Exception Value: local variable 'search_exception' referenced before assignment Request information: USER: admin GET: q = 'Ken' POST: No POST data FILES: No FILES data

5 years, 1 month

List archives Recent Posts problem

by Mark Dadgar

In the last day or so, hitting the Recent page in my list archives results in a spinner and an error message: Internal Server Error: /mailman3/hyperkitty/list/trackjunkies(a)pdc-racing.net <mailto:mailman3/hyperkitty/list/trackjunkies@pdc-racing.net>/recent-threads AttributeError at /hyperkitty/list/trackjunkies(a)pdc-racing.net <mailto:hyperkitty/list/trackjunkies@pdc-racing.net>/recent-threads 'NoneType' object has no attribute 'subject' Request Method: GET Request URL: https://mail.pdc-racing.net/mailman3/hyperkitty/list/trackjunkies@pdc-racin… <https://mail.pdc-racing.net/mailman3/hyperkitty/list/trackjunkies@pdc-racin…> Django Version: 2.2.12 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.2 Python Path: ['.', '', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Thu, 18 Jun 2020 08:58:02 -0700 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/template/base.py" in _resolve_lookup 829. current = current[bit] During handling of the above exception ('Thread' object is not subscriptable), another exception occurred: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py" in inner 135. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py" in overview_recent_threads 194. return render(request, "hyperkitty/fragments/overview_threads.html", { File "/usr/lib/python3/dist-packages/django/shortcuts.py" in render 36. content = loader.render_to_string(template_name, context, request, using=using) File "/usr/lib/python3/dist-packages/django/template/loader.py" in render_to_string 62. return template.render(context, request) File "/usr/lib/python3/dist-packages/django/template/backends/django.py" in render 61. return self.template.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in render 171. return self._render(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in _render 163. return self.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in render 937. bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in render_annotated 904. return self.render(context) File "/usr/lib/python3/dist-packages/django/template/defaulttags.py" in render 309. return nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in render 937. bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in render_annotated 904. return self.render(context) File "/usr/lib/python3/dist-packages/django/template/defaulttags.py" in render 209. nodelist.append(node.render_annotated(context)) File "/usr/lib/python3/dist-packages/django/template/base.py" in render_annotated 904. return self.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in render 987. output = self.filter_expression.resolve(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in resolve 671. obj = self.var.resolve(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in resolve 796. value = self._resolve_lookup(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in _resolve_lookup 837. current = getattr(current, bit) File "/usr/lib/python3/dist-packages/hyperkitty/models/thread.py" in subject 108. return self.cached_values["subject"]() File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py" in __call__ 59. return self.get_or_set(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py" in get_or_set 55. value = self.rebuild(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py" in rebuild 47. value = self.get_value(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/models/thread.py" in get_value 223. return self.instance.starting_email.subject Exception Type: AttributeError at /hyperkitty/list/trackjunkies(a)pdc-racing.net <mailto:hyperkitty/list/trackjunkies@pdc-racing.net>/recent-threads Exception Value: 'NoneType' object has no attribute 'subject' Request information: USER: admin Thoughts? Other than that I really need to migrate off the Ubuntu packages and into the latest docker image. 😁 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 5 months

Re: Easiest way to install a new mailman3 deployment?

by Matthew Alberti

I had a very similar experience. I don't mean to knock the dev team; Mailman3 is an awesome tool that really meets a need. It is really much much more than a 'tool.' A very comprehensive software suite. For me, I ended up using the docker option on Ubuntu 20.04. My advice is to give up on the idea of using OS package managers. They just aren't current enough (certainly for Ubuntu LTS), or updated frequently enough, for the current development of Mailman3. Nothing but problems for me on Ubuntu, and Debian is about the same. Pypi, or installation in a virtualized environment, was equally challenging. I strongly recommend the docker installation method. It is not quite turnkey, but the documentation is close enough where it might 'just work' in your environment. I used MariaDB, and that introduced some challenges. If you are using postgre, postfix, and nginx, you are pretty close to a very easy installation. This list is very supportive, with very frequent responses from the core dev team. And there are guys like me who really struggled to get to a production instance. Please let us all know what isn't working in the docker approach, and we will try to help I'm sure. - Matt Alberti ⁣Get BlueMail for Android On Dec 31, 2020, 8:15 PM, at 8:15 PM, ieso(a)johnwillson.com wrote: >So I've been trying for the last two weeks to get a new mailman3 server >running on a virtualized server (any server), and I'm turning to this >list after having failed many times and running out of holiday time. > >I started trying a non-docker installation on Ubuntu 18.04 >(https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) >, which got me the closest. Except I had a problem with inbound email >only being triggered when it came from certain accounts. But that >clearly wasn't good enough for production, so after many attempts to >figure out where it was failing, I decided to turn to docker as a >solution that should be cleaner. > >A few attempts at doing a docker installation on digitalocean.com >failed, which I realized might be due to it not routing private IP >addresses, so I moved to AWS after checking that their VPC policy would >fit mailman's docker requirements. I found a great but slightly >outdated guide on how to do this >(https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/). >By this point I knew enough to correct a number of places where the >environment had changed since the procedure was written, but postorius >still failed at the curl test. > >The challenge for me has been the difficulty to know how to >troubleshoot the different different systems and network infrastructure >that are used to keep mailman3 humming. I've tried about 7 different >installation walkthroughs (there are no recent ones on Youtube by the >way, in case anyone wants to seize that opportunity!), and the good >guides provide ways to check each stage to try to help you a bit on >that front. > >Nonetheless, I feel stuck and thought I'd ask the simple question... >for a completely basic, barebones new installation, what's the easiest >way to get a mailman3 installation up-and running? (e.g. Which server >provider? Which operating system and version? Docker or otherwise?) > >Any pointers highly appreciated. Google Groups is clearly on its way >out, as it no longer allows for people to easily join groups by sending >an email or clicking a link, so that should be a big opportunity for >mailman3 to step up and help give those mailing list migrants a new >home... which is what we're looking for. We're just not quite as smart >as you guys. ;-) >_______________________________________________ >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

Mailman-users search results for query "Postorius"