Search results for "Postorius" - Mailman-users

(venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Stephen J. Turnbull

Wikinaut writes: > I followed all single steps until this: > https://docs.list.org/en/latest/install/virtualenv.html#run-database-migrat… > (I will improve the documentation with the missing parts later > today), > > Now I got this and got stucked and need your help: > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE If you use the mailman-web setup, the allauth, allauth.account, and allauth.socialaccount applications are present in the initial INSTALLED_APPS tuple in the settings package. The example_projects in Postorius and HyperKitty each provide a very similar settings.py but with more extensive provision of socialauth providers. I strongly recommend you use the mailman-web settings package as a template for your own. Regarding the PostgreSQL bias, PostgreSQL is just more Mailman-friendly. We'll be happy to add more MySQL documentation, but I don't think any of the core devs use it where they have to make a choice. (For example I myself use MySQL only in my MediaWiki instance and I have done zero configuration of it.) There is at least one known gotcha for default installations of MySQL (it's terribly ungraceful when there are non-BMP UTF-8 characters), but any other warts or optimizations would be very welcome. Steve

2 years, 3 months

Re: Something wrong with my Hyperkitty base_url?

by Andrew Hodder

Ah, I thought that only was affecting the web ui, didn't realize. Confirmed; that did the trick, thank you so much Abhilash! Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Mon, Oct 2, 2017 at 3:38 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Mon, Oct 2, 2017, at 12:29 PM, Andrew Hodder wrote: > > from django.conf.urls import include, url > from django.core.urlresolvers import reverse_lazy > from django.views.generic import RedirectView > from django.contrib import admin > > urlpatterns = [ > url(r'^$', RedirectView.as_view( > url=reverse_lazy('hk_root'))), > url(r'^hyperkitty/', include('hyperkitty.urls')), > #url(r'^postorius/', include('postorius.urls')), > url(r'', include('django_mailman3.urls')), > url(r'^accounts/', include('allauth.urls')), > # Django admin > url(r'^admin/', include(admin.site.urls)), > url(r'^hyperkitty/admin/', include(admin.site.urls)), > I removed the archives from the base_url, it still errors out just with a > different path: > > ValueError: <h1>Not Found</h1><p>The requested URL /api/mailman/archive > was not found on this server.</p> > > Now I should note, I'm running the web ui for hyperkitty on nginx with > http://FQDN/hyperkitty/ (where the non-/hyperkitty/ path would just go to > postorius). > > > > That is what you should be using for hyperkitty's `base_url` then: > > http://<whatever django is listening on>/hyperkitty/ > > > > > > > Sincerely, > > Andrew Hodder > Systems Administrator > Support Operations, Afilias > E-mail: drew(a)afilias.info > Phone: +1 416.673.4164 > Fax: +1 416.646.1541 > > On Mon, Oct 2, 2017 at 3:22 PM, Abhilash Raj <maxking(a)asynchronous.in> > wrote: > > > > On Mon, Oct 2, 2017, at 12:17 PM, Andrew Hodder wrote: > > Finally have everything stood up and working, except for HyperKitty > > mailman > > plugin. I'm getting a path issue of sorts I can see in the archiver.log > > (have it set to debug log level in the mailman core): > > > > Oct 02 19:12:37 2017 (8144) Traceback (most recent call last): > > File > > "/opt/mailman/venv3/lib/python3.4/site-packages/mailman_ > hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", > > line 154, in _archive_message > > url = self._send_message(mlist, msg) > > File > > "/opt/mailman/venv3/lib/python3.4/site-packages/mailman_ > hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", > > line 210, in _send_message > > raise ValueError(result.text) > > ValueError: <h1>Not Found</h1><p>The requested URL > > /archives/api/mailman/archive was not found on this server.</p> > > > > > > My base_url in the mailman-hyperkitty.cfg: > > Can you show the contents of 'urls.py' in mailman-suite or whatever > Django project you are using to deploy hyperkitty? That would give more > ideas about whether the '/archives/' URL is valid or not. > > > -- > Abhilash Raj > maxking(a)asynchronous.in > > > -- > Abhilash Raj > maxking(a)asynchronous.in > > >

8 years, 4 months

Re: 3rd Party Account is not working

by Matthew Alberti

Same thing happens to me. If I comment out all the socialauth plugins, the web service doesnt work. Are you using the docker-mailman installation method? ⁣Get BlueMail for Android On Feb 16, 2021, 7:32 PM, at 7:32 PM, kwp.klein(a)gmail.com wrote: >Here is my /mailamn/config/mailman-web/settings_local.py. I get an >error message > >curl http://172.19.199.3:8000/postorius/lists/ >curl: (7) Failed connect to 172.19.199.3:8000; No route to host >Please comment out all the lines that are not necessary. > > >MAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' >EMAIL_HOST = '172.19.199.1' >EMAIL_PORT = 25 >USE_SSL = False > >INSTALLED_APPS = ( > 'hyperkitty', > 'postorius', > 'django_mailman3', > # Uncomment the next line to enable the admin: > 'django.contrib.admin', > # Uncomment the next line to enable admin documentation: > # 'django.contrib.admindocs', > 'django.contrib.auth', > 'django.contrib.contenttypes', > 'django.contrib.sessions', > 'django.contrib.sites', > 'django.contrib.messages', > 'django.contrib.staticfiles', > 'rest_framework', > 'django_gravatar', > 'paintstore', > 'compressor', > 'haystack', > 'django_extensions', > 'django_q', > 'allauth', > 'allauth.account', > 'allauth.socialaccount', > #'django_mailman3.lib.auth.fedora', > #'allauth.socialaccount.providers.openid', > #'allauth.socialaccount.providers.github', > #'allauth.socialaccount.providers.gitlab', > #'allauth.socialaccount.providers.google', >) >_______________________________________________ >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/

5 years

Re: Bounce processing HTML

by Mark Sapiro

On 11/25/25 8:51 AM, pashdown(a)xmission.com wrote: > Where do I set forward_unrecognized_bounces_to ? I can't find documentation on this. If you have Postorius it's Settings -> Bounce Processing -> Forward unrecognized bounces. It is a list attribute with 3 possible values which are discard them, forward to list owners/moderators or forward to the site admin. The default value when lists are created is forward to list owners/moderators. However none of this is relevant to your situation because the bounces you are getting that result in the Bounce message for a non subscriber log messages you are seeing are not unrecognized. As I said at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I think these are spam sent to the list-bounces address that one of the heuristic recognizers treats as a real DSN and parses those non-addresses. In order to see the actual messages, you will have to configure your MTA to deliver them to a human or you could apply this patch ``` --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -49,6 +49,7 @@ class BounceRunner(Runner): # List isn't doing bounce processing? if not mlist.process_bounces: return False + maybe_forward(mlist, msg) # Try VERP detection first, since it's quick and easy context = BounceContext.normal addresses = StandardVERP().get_verp(mlist, msg) ``` to copy all bounce messages to the forward_unrecognized_bounces_to destination. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 3 weeks

Domain ownership issues

by peter＠chubb.wattle.id.au

Hi, I wanted to give another user the ability to create lists, so added that user as 'owner' of the domain. But he does not see the 'create list' button. I decided to try deleting him as owner, and the result is a python exception: KeyError: 'file' ERROR 2021-03-01 20:35:07,195 550 django.request Internal Server Error: /postori us/domains/sel4.systems/owners/b55d58c434c94f6dbd19ae338502dd2e/remove Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py", line 40 , in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view return view_func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/auth/decorators.py", line 75, i n wrapper return fn(*args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/domain.py", line 182, in remove_owners remove_email = client.get_user(user_id).addresses[0].email File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 324, in get_user display_name=display_name)) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 111, in call raise HTTPError(url, response.status_code, urllib.error.HTTPError: HTTP Error 404: 404 Not Found Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.9.0+ (default, Oct 19 2020, 09:51:18) [GCC 10.2.0] Peter C

4 years, 11 months

Upgrading mailman 3 venv installation

by Morris Jones

Congratulations on the new release for Mailman 3 Core! I'm not a daily pip/python user, so I'm probably behind on the safe and proper way to update my installation (which is working pretty well). In my virtual environment, I ran `pip list -o` and got a significant list. I noticed that all of the mailman packages seemed to be "Type sdist" and the framework packages "Type wheel". (Dunno what "Type" means in this context.) So I tried `pip list -o | grep sdist` and got a smaller list: (venv) mailman@mail:~$ pip list -o | grep sdist atpublic 2.1.1 2.3 sdist django-allauth 0.43.0 0.45.0 sdist django-mailman3 1.3.4 1.3.7 sdist flufl.i18n 3.1.3 3.2 sdist flufl.lock 5.0.3 6.0 sdist HyperKitty 1.3.3 1.3.4 sdist lazr.config 2.2.2 2.2.3 sdist mailman 3.3.2 3.3.5 sdist mailmanclient 3.3.1 3.3.3 sdist mysqlclient 2.0.1 2.0.3 sdist postorius 1.3.3 1.3.6 sdist Is this a reasonable list of the packages that I should update? Are there framework updates I should be concerned with? I'm remembering that a specific non-current version of django was required for mailman. The one I have installed is 3.0.11, with 3.2.7 listed as Latest. My plan is to archive the virtualenv directory, upgrade the packages listed above. If something breaks, I should be able to restore the archived virtualenv. I'm running a single server, Ubuntu 18.04.6, with Zimbra running alongside. Best regards, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

4 years, 4 months

Re: Error Logging - what changed with the New Year releases?

by Odhiambo Washington

On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/23 01:19, Odhiambo Washington wrote: > > Apart from all the defaults in settings.py (derived from gitlab), I also > > have this line: > > LOGGING['handlers']['file']['filename'] = > > '/opt/mailman/mm/var/logs/mailmanweb.log' > > > > Before the New Year releases of MM3, I used to get errors written to this > > file. > > Not anymore after I updated to the New Year releases. > > Another thing that I have realized is that prior to the New Year > releases, > > I would get an error logged to that file and also mailed to me. > > I don't think that I have changed anything in settings,py related to > > logging. > > > Nothing in those releases per se would affect this. This is Django and > django-allauth. Perhaps when you updated the Mailman packages, you also > updated these dependencies. > Which dependencies would those be? When I upgraded, the command I ran was: pip install --upgrade --force mailman mailmanclient postorius hyperkitty mailman-hyperkitty django-mailman3 And how do I find out what is suppressing the logging for the social accounts? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

Re: Importing config and archives only partially succeeded?

by Eric Broens

The settings - Archiving, are not different from the ones that do show the messages:"Private Archives" selected, and Active archivers "hyperkitty" also selected. I was trying to find out how the hyperkitty page gets the mails from the database, and if I can start from there.Or maybe something is not completely correct in the database tables. Best Regards,Eric On Sunday, December 13, 2020, 01:27:53 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- 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/

5 years, 2 months

Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 1/2/23 03:54, Onyeibo Oku wrote: > > I pulled the plugs on uwsgi and installed Gunicorn. Gunicorn gave more > mileage but something is still not right. When I visit the mailmanweb > home with a browser, I see the following: > > "Server Error. An error occurred while processing your request." > > Mailmanweb and mailman3 services are running. I perused the log file > at /opt/mailman/web/logs/mailmanweb.log and found the following: > > > raise MailmanConnectionError( > mailmanclient.restbase.connection.MailmanConnectionError: ('Could not > connect to Mailman API: ', > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'localhost\', > port=8001): Max retries exceeded with url: > /3.1/lists?advertised=true&count=0&page=1 (Caused by > NewConnectionError(\'<urllib3.connection.HTTPConnection object at > 0x7f7f4b128c40>: Failed to establish a new connection: [Errno 111] > 0x7f7f4b128c40>Connection refused\'))"))') Postorius is unable to connect to Mailman core's REST API. Are your settings for accessing Mailman's REST API correct? E.g., does MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' match $ mailman info ... REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Note the 3.1/ in REST root url is not included in MAILMAN_REST_API_URL. What do you get from, e.g. curl -urestadmin:restpass http://localhost:8001/3.1/lists It should return JSON with information about your lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

Circumstances in which a subscriber is added to Pending Confirmation list

by David Owen

Hi I wondered if anybody would be able to assist me in my understanding of the Pending Confirmation list, please. In our Mailman mailing list, our Member Policy settings for both Subscription Policy and Un-subscription Policy are set to Open. Therefore we don't require subscribers to confirm their subscription after they submit a request to join our mailing list. Despite this, a number of subscribers seem to be arriving in the Pending Confirmation (Subscriptions pending user confirmation) list. Others correctly arrive in the Members list, as we would expect. All subscription requests are made by the subscriber sending an email to our "join" email address with the subject "subscribe". I've looked at the settings carefully and can't seem to see any that may cause the above behaviour at any time (although I may have missed something of course). Therefore, does anybody know the circumstances in which subscribers to an open mailing list may somehow arrive in the Pending Confirmation list? If I could understand the cause(s) I could then consider ways to manage it or prevent it from happening. Our Mailman installation is hosted centrally in a large organisation so we while we can alter our mailing list's settings in Postorious, we can't alter the source code or similar, so we don't have great room for manoeuvre. Our Postorius version is 1.3.6. Thanks and regards David

1 year, 8 months

Mailman-users search results for query "Postorius"