Search results for "Postorius" - Mailman-users

Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Abhilash Raj

On Wed, 9 Aug 2017 15:45:48 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/09/2017 02:35 PM, Abhilash Raj wrote: > > Hi, > > > > On Wed, 9 Aug 2017 13:42:20 -0700 > > Mark Sapiro <mark(a)msapiro.net> wrote: > [...] > > > > I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as > > well? > > > It's only that one and whether it's needed or not depends on list > configuration. The list has attributes digest_send_periodic and > digest_size_threshold. When a post is received it is added to the list's > digest mbox, and if that causes the size of the mbox to reach > digest_size_threshold K bytes, a digest is sent. Additionally, if > digest_send_periodic is true, a digest is sent periodically whether or > not it has reached digest_size_threshold. > > However, the sending of periodic digests depends on cron running > something periodically to actually trigger the sending. Can this be done using the REST API? If not, maybe we should do that so that Postorius can take of the periodic tasks? I am thinking mostly about the container images because the mailman-core container runs nothing else other than Core. I'd have to another cron for this which isn't a lot of overhead but since mailman-web container already has periodic tasks, it would be great if I could trigger it from there. > > Note: I've just looked at the code and there seems to be an issue with > using 'mailman digests --send' to send the periodic digests. It appears > that if a list's digest mbox has any messages, 'mailman digests --send' > will send a digest even if digest_send_periodic is false. I've just > reported <https://gitlab.com/mailman/mailman/issues/384> for this issue. Also, it seems that Postorius doesn't have any way to set `digest_send_periodic` and only has a setting to set the max_threshold for the digest. I opened another issue (https://gitlab.com/mailman/postorius/issues/211) to add this feature. -- thanks, Abhilash Raj

7 years, 8 months

Re: User management page [was: Changing subscription address]

by Abhilash Raj

> On Mar 22, 2021, at 7:56 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Abhilash Raj writes: > >> Typo :( Page in Postorius is what I meant to say. > > :D No problemo, mon, I just did it too -> > >> Is that necessarily required? Every user in Django has a corresponding >> user in Core, but the converse isn’t true and I am not sure if that is even >> required. > > I meant "accessed from Postorius or HyperKitty." :-) > >> You will be able to see: >> - Does the user have a Django account? >> - All Subscriptions for the User >> - All addresses of the User >> >> You will be able to perform following actions: >> - Add or remove a user’s address >> - Verify or un-verify an address >> - Set any address as primary for the user >> - Update display name of the user >> - Update address on any of the subscriptions > > I don't think we *need* a Django account for what I'm thinking of. I > do think that creating the account on User access from Postorius might > make the implementation logic simpler. > >> What I am on fence about: >> - Provide a full blown preferences menu to the admin for that user. This >> will also make the UI extremely complex to see and implement. > > Wait to decide on that until I have a mockup or maybe a full MR. > >> But, when you have an account in Django with a different email >> (email2) and a different Mailman user (user2) and you add a second >> email (email1) to your account and are able to prove ownership by >> verifying the address, Django will ask Core to add that second address >> (email1) to your Mailman user (user2) and absorb “user1”. This >> process is already implemented. > > Good. > >> However, if two Django accounts are created for “user1” and “user2” >> then situation becomes more tricky and currently we don’t have a >> way to resolve that short of delete one of the accounts and add the >> addresses to other account. > > Delete "that" and add its attributes to "this" is what I had in mind. We could automate the absorb other account and copy all settings and subscriptions over in a user based workflow. I don’t see a lot of unknowns in implementing that. You have to manually do it today, and deleting account will delete subscriptions so when you add them to your other account you have to resubscribe. So, the path could really use some changes. I think I have a ticket open in P to allow deleting P account but not delete the Mailman User and subscriptions, which would make this manual process much better. -- thanks, Abhilash Raj (maxking)

4 years

Mass subscribe gives HTTP Error 500 when using custom template

by Jeffrey D

Hi, I have some issues with the Mass Subscribe option on Mailman 3.2.1. When using a custom "The notice sent to a member when they are subscribed to the mailing list." template, Postorius will throw an exception after pushing the "Subscribe Users" button on Mass Subscribe. In the web interface you will see a red notification bar with the text: "HTTP Error 500: b'A server error occurred. Please contact the administrator.'". And in the Mailman.log you will see the following error message: Traceback (most recent call last): File "/usr/lib/python3.7/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 216, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ File "falcon/api.py", line 189, in falcon.api.API.__call__ File "/usr/lib/python3/dist-packages/mailman/rest/members.py", line 266, in on_post pre_approved=pre_approved) File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 520, in register list(workflow) File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 326, in _step_do_subscription self.member = self.mlist.subscribe(self.subscriber) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 494, in subscribe notify(SubscriptionEvent(self, member)) File "/usr/lib/python3/dist-packages/zope/event/__init__.py", line 31, in notify subscriber(event) File "/usr/lib/python3/dist-packages/mailman/app/membership.py", line 169, in handle_SubscriptionEvent send_welcome_message(mlist, member, member.preferred_language) File "/usr/lib/python3/dist-packages/mailman/app/notifications.py", line 52, in send_welcome_message 'list:user:notice:welcome', mlist, language=language.code)) File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 188, in get name, lookup_context, **substitutions) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 109, in get contents = protocols.get(actual_uri, **auth) File "/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line 38, in get response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) File "/usr/lib/python3/dist-packages/requests/api.py", line 75, in get return request('get', url, params=params, **kwargs) File "/usr/lib/python3/dist-packages/requests/api.py", line 60, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3/dist-packages/requests/adapters.py", line 516, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /postorius/api/templates/list/<MAILINGLIST>/list:user:notice:welcome (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f0b5ce8d8d0>: Failed to establish a new connection: [Errno 111] Connection refused')) Postorius/Mailman is running on port 8001, only Postorius still connecting on port 8000. Anyone seen something similar? Thanks in advance! Jeffrey

5 years, 2 months

message file gone, but exists in database?

by Thor Atle Rustad

I'm investigating some problems, and in the process I want to delete some messages. First, listing all messages: >>> messages = list(message_store.messages) Traceback (most recent call last): File "<console>", line 1, in <module> File "/usr/local/lib/python3.6/site-packages/mailman/model/messagestore.py", line 117, in messages yield self._get_message(row) File "/usr/local/lib/python3.6/site-packages/mailman/model/messagestore.py", line 95, in _get_message with open(path, 'rb') as fp: FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/messages/5X/7W/5X7WMWNORTGVNB6KVWTHHOI2VF2BEQ7K' Since this message should not exist in database, I try to delete it: >>> message_store.delete_message('5X7WMWNORTGVNB6KVWTHHOI2VF2BEQ7K') >>> commit() >>> messages = list(message_store.messages) Traceback (most recent call last): File "<console>", line 1, in <module> File "/usr/local/lib/python3.6/site-packages/mailman/model/messagestore.py", line 117, in messages yield self._get_message(row) File "/usr/local/lib/python3.6/site-packages/mailman/model/messagestore.py", line 95, in _get_message with open(path, 'rb') as fp: FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/messages/5X/7W/5X7WMWNORTGVNB6KVWTHHOI2VF2BEQ7K' However, it continues to exist in mailman's mind I also cannot delete messages that actually exist. For instance, I find a message in Postorius that I want to delete. I look at the headers and then run >>> message_store.delete_message('6XFISRRFY74NJEE4FTRNWOA2KGKDBZ3T') >>> commit() After that, the message continues to live, both in postorius and as a file: bash-4.3# ls 6XFISRRFY74NJEE4FTRNWOA2KGKDBZ3T What is wrong?

6 years, 7 months

Re: New Mailman Releases

by Abhilash Raj

On 10/26/22 13:48, Odhiambo Washington wrote: > Ideally, `pip` shouldn't have allowed you to install aiosmtpd in a > Python venv with 3.10, but that depends on which version of pip you are > using since the newer versions have better support for such management. > > > I followed the HOWTO by the late BC > <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> for my > installation. I did not have to choose any specific version of pip. > I just used what was in the system at that time, which was based on the > Python version on the system. So, actually, it isn't the fault of pip or yours. I check aiosmtpd and it doesn't declare an upper bound on the supported python versions since when the last release came out, the max version was 3.9 and it supported that. There hasn't been a release since 3.10 came out. > > > 2. Is it possible to downgrade the Python in a Venv down to 3.9 > without > > breaking the installation? > > You can keep the current installation running and create a 2nd > installation by simply creating a 2nd venv with 3.9. Something like, > `/opt/mailman/mm/venv-3.9/`. You can install things into that venv and > when you are done and ready to switch, you can update all the paths in > various places to use update 'venv-3.9' instead of 'venv'. > > > That procedure seems way too much work for someone not so well versed > with the PATHs used in MM3. > Since I don't remember ever having to install aiosmtpd (not even sure > what it is!) I believe I should not worry. You basically just need to follow the install instructions again, skipping any parts about creating configs, data mta etc. with the new path to venv. > > 'pip3 list | grep smtpd' yielded nothing in my install. Is that > expected? Or aiosmtpd is part of the core? Yes, it is a dependency of Core and you _should_ find it in the venv. Not sure if you have that activated, but it should result in an installed package if you are inside venv. > > In case you encounter any issues, you can always revert back to older > 'venv' in the paths wherever the are needed and bring back the old > install. Venvs are good for multiple installs so you can switch back > and > forth pretty easily. > > > Talking of moving between VENVs, you did not mention about migrating the > lists/list data between then :-) You don't need to migrate lists, as long as you keep the same configs & database, the 2nd install will just pickup the old data. Make sure you aren't downgrading the version of Mailman though when switching between VMs (which typically won't happen if you just use "pip install", unless you specify version constraints like mailman==3.3.0 for old versions). > > > > > And finally, is there documentation/procedure to upgrade a VENV > install > > in this case? > > You don't want to upgrade venv is what i've heard, you should always > create a new one if you are bumping python versions. > > > Noted. And only Python versions, right? Like 3.10 to 3.11? Yes, only Python versions! Packages inside can be upgraded. > (3) Upgrade package > Finally, upgrade your packages: > > Here, I am a little confused. The official MM3 documentation says the below: > *(venv) $ pip install -U mailman postorius django-mailman3 hyperkitty > mailman-web* > > However, thee howto by BC, there was no installation for django-mailman3 > and mailman-web. So I am unable to map 1:1 what needs to be done > to upgrade to these 5 components of > 1. Mailman Core 3.3.6 [1] > 2. Postorius 1.3.7 [2] > 3. Hyperkitty 1.3.6 [3] > 4. Mailmanclient 3.3.4 [4] > 5. Django-mailman3 1.3.8 [5] > > What should I add to the command line below so that everything is updated? > > (venv) mailman@lists:~$ pip install -U mailman postorius hyperkitty > mailman-hyperkitty This will work! Yeah, basically upgrade only the packages you installed previously. The official documentation asks you to explicitly specify all Mailman packages (even the downstream libraries like django-mailman3 and mailmanclient, which will already be upgraded when you install new version of Postorius or Hyperkitty) and mailman-web. You probably don't need "mailman-web". I'd recommend just specifying all the released packages, except mailman-web since you aren't using that. > Sorry to bother you so much. No worries :-) -- thanks, Abhilash Raj (maxking)

2 years, 5 months

Re: {Spam?} Server name in new account confirmation email

by Mark Sapiro

On 12/3/20 9:26 AM, Meehan, John wrote: > Hi, when someone creates a new account (Sign Up), an email is sent to them to confirm their email address. It has the form below. Does anyone know how I can change the server name in the URL (From server.example.com to something else)? I have an SSL proxy server that I want to direct users through. Thanks. - John This message comes from django_allauth. The domains come from the django_site database table. If you have Postorius >= 1.3.3 The Domains view will show you the SITE_ID for the domain and has an `Edit` link the the Django admin UI entry for that site. Otherwise, you can go to the Django admin `Sites` view and see the DOMAIN NAME and DISPLAY NAME for each defined site, and you can edit the domain name. You may also need to adjust the SITE_ID setting in your Django settings to match the site you want. The trick here is the SITE_IDs aren't displayed in the Django admin UI or in Postorius < 1.3.3, and they may not be sequential or start at 1. If you query the database with `SELECT * FROM django_site;` you'll see entries with columns id, domain and name which will tell you the SITE_ID. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Re: Postorius no connection to REST API

by Richard Rosner

I included now: SSLProxyEngine on SSLProxyMachineCertificateChainFile /etc/ssl/certs/dfnca.pem (same as SSLCertificateChainFile, I hope that's correct) SSLProxyMachineCertificateFile /etc/ssl/certs/lists.domain.de.cert_key.pem (basically just copied SSLCertificateFile and SSLCertificateKeyFile into one file; and since the keyfile starts with "BEGIN RSA PRIVATE KEY" it seems to fulfill the criteria). SSLProxyProtocol all -SSLv3 -TLSv1 -TLSv1.1 but no change. From apache error log: [Sun Aug 15 09:19:52.318582 2021] [core:notice] [pid 19706:tid 140315143705728] AH00094: Command line: '/usr/sbin/apache2' [Sun Aug 15 09:19:52.732381 2021] [proxy_http:error] [pid 19707:tid 140314912167680] (20014)Internal error (specific information not available): [client 37.201.214.82:9292] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:19:53.929213 2021] [proxy_http:error] [pid 19707:tid 140314912167680] (20014)Internal error (specific information not available): [client 37.201.214.82:9292] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:19:59.463974 2021] [proxy_http:error] [pid 19708:tid 140314828240640] (20014)Internal error (specific information not available): [client 37.201.214.82:9311] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:20:03.328416 2021] [proxy_http:error] [pid 19708:tid 140314828240640] (20014)Internal error (specific information not available): [client 37.201.214.82:9311] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:20:04.605617 2021] [proxy_http:error] [pid 19708:tid 140314828240640] (20014)Internal error (specific information not available): [client 37.201.214.82:9311] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:20:10.178979 2021] [proxy_http:error] [pid 19708:tid 140314828240640] (20014)Internal error (specific information not available): [client 37.201.214.82:9305] AH01102: error reading status line \ from remote server 127.0.0.1:8000

3 years, 8 months

Re: Social signup?

by Duane Raymond

Thanks Stephen, With support to dip in on how to do this, I would hope it is the start of a series of contributions to the platform :-) My starting point these days is asking chatGPT how to add the functionality. The response looks convincing but often has some glaring errors in it...but at least it helps me narrow down where I start and give me an idea of the steps/complexity of the task. I'll jump over to the developers list when I start this (I'm about to travel for a week to run an annual event in Oxford - so the far removed from programming)...but which chatGPT suggested so far was 1. Extending postorius/signups.html with a loop to get the configured social login providers PLUS adding a csrf_token field to the form 2. Modifying postorius/views.py (which doesn't seem to exist but there is a postorius/views folder) - so perhaps this is views/urls.py So with dev community support and chatGPT support I should be able to muddle through it! Probably as practice I'll convert a recent simple Flask app I built into django to get familiar with Django as a framework before I dip into postorius & hyperkitty Cheers, Duane On Wed, 15 Mar 2023 at 08:26, Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Duane Raymond writes: > > > I'll dip into the code in the next weeks and see if I can figure > > out how to add it (using the example of the login page) > > Welcome to the team! :-D > > I doubt you need any Python code; I think you just need to add buttons > in HTML in the page template, and an explanation of where the user > will end up (probably not where they expect ;-). I forget how this > works, but you might even be able to ensure a redirect to where they > expect to go in pure Django templating language. If not, it will > likely need a straightforward one-line change to the view. > > If all that makes sense to you, great! If not, feel free to ask > questions, here, or perhaps more appropriately on > mailman-developers(a)python.org. > > Steve >

2 years, 1 month

Re: How to set up mailman 3

by David Krantz

On Sat, Mar 25, 2017 at 10:35 PM, Barry Warsaw <barry(a)list.org> wrote: > Yes, I'm sorry you went down a dead end with mailman-bundler. I'm trying to > purge the world of it so others won't get led astray. I've clobbered the > README in the GitLab repo and we may at some point just archive and delete the > whole project, but I'm not quite ready to do that yet. I did get things working with the bundler at last. Quite tricky and I have deactivated archival. But I suspect that I should retrace a bit of that work and upgrade to the latest versions. I miss a few functions from mailman2, especially setting a limit for message size to discourage sending larger files to the list. I also notice that there are no modbits per user that I can reach from the web as admin. > Where did you find out about the bundler? I'd like to make sure we steer > people to the current best recommendations: The documentation can be found on several places. The one that is best formatted is this one. I used a worse formatted version of the same text but right now I cannot find the link. https://mailman-bundler.readthedocs.io/en/latest/ I notice that you changed the text on the githlab project. Better. Now I have no idea of how upgrading the different components. I might start from scratch although it probably should be possible to upgrade the parts. The best option is probably to switch to mailman2, but that has disadvantages when handling lists for multiple domains if I am correctly informed and I already have a few domains... I also found that sending mails manually (telnet to port 25) with no headers other than "Subject:" causes the "Held messages" tab to crash with a 500-error. Log below my signature. cheers // David ERROR 2017-03-25 22:54:41,762 base 17632 140529157728000 Internal Server Error: /mailman3/lists/MYLIST.COM.COM/held_messages Traceback (most recent call last): File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/generic.py", line 67, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/utils/decorators.py", line 34, in _wrapper return bound_func(*args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/auth/decorators.py", line 81, in wrapper return fn(*args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/utils/decorators.py", line 30, in bound_func return func.__get__(self, type(self))(*args2, **kwargs2) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/list.py", line 387, in get held_messages = utils.paginate(request, self.mailing_list.held, 20) File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", line 443, in held moderation_reasons=entry['moderation_reasons'], KeyError: u'moderation_reasons'

8 years

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 12:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 2:16 PM, Odhiambo Washington wrote: > > > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > > total 104 > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > > > I imagined I needed an executable. > > > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 sass > > > Those are headers for compiling some sass. Possibly you actually have a > `sassc` installed in which case you may need > > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > ) > > This change makes the error I was getting to go away. However, I cannot login to manage lists, even after restarting mailman. The error details are here: https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

3 years, 11 months

Mailman-users search results for query "Postorius"