Search results for "Postorius" - Mailman-users

Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by Mark Sapiro

On 2/28/21 10:17 AM, blackout69 wrote: > Hello everybody,I received this error message and from that moment the > maiilan3 has stopped working.I restarted the following services mailman3 > and mailman3-web and everything started working fine.Can you tell me > what is the problem my django server has encountered? It looks to me like a race condition of some kind or possibly an incompletely deleted thread. Have you deleted any threads? I'm curious as to how you happen to be going to <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/t…> as opposed to <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/#…>. I know that ULS and similar ones are in HyperKitty's urls.py, but I don't see them exposed on any pages. Anyway, when you say "from that moment the maiilan3 has stopped working." (sic) exactly what stopped working. Did core stop delivering messages? Did Postorius stop working. If so, this all may be related to some underlying database issue or something like that that was fixed by the restarts. I don't see how this HyperKitty error could affect Postorius or Mailman core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Re: Message-Footer after migrating to Mailman3

by christopher.claus＠tgcamberg1848.de

Mark Sapiro wrote: > > ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. > > WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer > > It appears you created the new template with Postorius, but there is an > issue for Postorius templates. Possibly your Django setting for > POSTORIUS_TEMPLATE_BASE_URL needs to be adjusted. > > Obviously I have a problem with the hostname. I set > > [code] > > POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 > > [/code] > > where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost > > [code] > > wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamberg... > > [/code] > > will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? > > If that works, yes. Hi Mark, thanks for your reply and excuse my delay. I was very busy in the last weeks but made some tests. Newly created templates with POSTORIUS_TEMPLATE_BASE_URL=http://localhost:8000 did not work. I changed it to my fqdn - at the moment I am able to access the template via this URl (e.G. http://lists.example.de:8000/postorius/api/templates/list/homepage.lists.ex…) But if I try to send an email I got the following error: Jul 09 16:00:37 2021 (27) Uncaught runner exception: HTTPConnectionPool(host='lists.example.de', port=8000): Max retries exceeded with url: /postorius/api/templates/list/homepage.lists.example.de/list:admin:action:post (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fe80eaaec40>: Failed to establish a new connection: [Errno 111] Connection refused')) Jul 09 16:00:37 2021 (27) Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/urllib3/connection.py", line 159, in _new_conn conn = connection.create_connection( File "/usr/lib/python3.8/site-packages/urllib3/util/connection.py", line 84, in create_connection raise err File "/usr/lib/python3.8/site-packages/urllib3/util/connection.py", line 74, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 670, in urlopen httplib_response = self._make_request( File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 392, in _make_request conn.request(method, url, **httplib_request_kw) File "/usr/lib/python3.8/http/client.py", line 1255, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.8/http/client.py", line 1301, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.8/http/client.py", line 1250, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.8/http/client.py", line 1010, in _send_output self.send(msg) File "/usr/lib/python3.8/http/client.py", line 950, in send self.connect() File "/usr/lib/python3.8/site-packages/urllib3/connection.py", line 187, in connect conn = self._new_conn() File "/usr/lib/python3.8/site-packages/urllib3/connection.py", line 171, in _new_conn raise NewConnectionError( urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7fe80eaaec40>: Failed to establish a new connection: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/requests/adapters.py", line 439, in send resp = conn.urlopen( File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 724, in urlopen retries = retries.increment( File "/usr/lib/python3.8/site-packages/urllib3/util/retry.py", line 439, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='lists.example.de', port=8000): Max retries exceeded with url: /postorius/api/templates/list/lists.example.de/list:admin:action:post (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fe80eaaec40>: Failed to establish a new connection: [Errno 111] Connection refused')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/usr/lib/python3.8/site-packages/mailman/core/chains.py", line 79, in process link.function(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 232, in _process template = getUtility(ITemplateLoader).get( File "/usr/lib/python3.8/site-packages/mailman/model/template.py", line 188, in get contents = getUtility(ITemplateManager).get( File "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.8/site-packages/mailman/model/template.py", line 110, in get contents = protocols.get(actual_uri, **auth) File "/usr/lib/python3.8/site-packages/mailman/utilities/protocols.py", line 38, in get response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) File "/usr/lib/python3.8/site-packages/requests/api.py", line 76, in get return request('get', url, params=params, **kwargs) File "/usr/lib/python3.8/site-packages/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 530, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 643, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3.8/site-packages/requests/adapters.py", line 516, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPConnectionPool(host='lists.example.de', port=8000): Max retries exceeded with url: /postorius/api/templates/list/lists.example.de/list:admin:action:post (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fe80eaaec40>: Failed to establish a new connection: [Errno 111] Connection refused')) I set POSTORIUS_TEMPLATE_BASE_URL=lists.example.de:8000 and I have no idea, why the connection is refused. Do you see any configuration error d or have another idea? Best regards, chrclaus

5 years, 2 months

Re: Bounce counter visibility for List Admins

by Mark Sapiro

On 5/19/21 4:10 AM, smorytko(a)gmail.com wrote: > As you may know, we use MM3 but the Affinity/Empathy flavor and we only have List Administrator using the Postorious/Affinity. Unlike many here, we have no access to any server-based files. > > Can someone tell me if Postorious gives list administrators visibility into the bounce counters? User's bounce scores are not available in REST so neither Affinity nor Postorius has access to them. > While List Admins get to set various bounce counters we have no visibility of those counters until, all of a sudden, an entire source of subscribers hits the bounce threshold and gets bounced off the list. It would be really nice to be able to see the bounce counters and possibly head off trouble before users/subscriber mail hosts. It can serve as an effective early warning system that something is wrong. > > Assuming Postorious cannot, is there another way List Admins can inspect bounce counters? Email command? In the next release of Mailman core (3.3.5), lists will have a `bounce_notify_owner_on_bounce_increment` setting which if True, will send to the list admins a notice including the triggering DSN when a user's bounce score is incremented. This setting will also be exposed in Postorius 1.3.5. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

Re: seems solved (was: Re: error changed after restart)

by Guillermo Hernandez (Oldno7)

On 8/2/21 11:26, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 7/2/21 19:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> On 7/2/21 19:04, Abhilash Raj wrote: > > Well... I did reinstall all mailman relationed apps with a > > pip install --upgrade --force-reinstall --no-deps --no-cache-dir > django-mailman3 mailman mailman-hyperkitty mailmanclient > > Restarted thee apache24 server... > > Aaaaaand closed de admin session and reopened it... (just for a "what > if" sensation). > > I can not tell what have been the solution here, but now I can access > the administrative pages and attend de pending subscriptions and > discard retained messages. > > Thanks Abhilash and Mark for your support. Some things did not work well enough after that (the subscriptions pending approval, between others), and then I did an pip install --upgrade --force-reinstall --no-deps --no-cache-dir django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django (adding postorius and django to my previous reinstall) And a su -m mailman3 -c "python3 manage.py collectstatic" in the mailman dir (mailman3 is the user who exectues all mailman related things) and again a su -m mailman3 -c "python3 manage.py migrate" And it seems there were things pendig to update... Restarted the server and now it seems all is OK. Thanks all and sorry for the noise.

5 years, 7 months

Re: Mailman3 on virtual domains

by Mark Sapiro

On 10/7/23 09:25, Lars Bjørndal wrote: > [Mark] > > [...] > >> See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > Ok, so I have to create an alias_domain in Mailman. Is it possible to do that from the web interace? It has been in postorius since 1.2.0. > I find an Edit button for each domain, and then I may change name and description. But I can't find an option to add an alias_domain. As I'm blind, and using a text only browser, some information may have been missing. Or can I do it from the command line? If your Postorius is >=1.2.0, there should be 3 fields on the Edit domain page - Description, Alias Domain and Web Host. The whole page looks something like: Edit domain example.com Description Alias Domain Normally empty. Used only for unusual Postfix configs. Web Host The domain from which you want the web UI to be served from. This can be same or different from the Mail Host. You can edit the list of available web hosts here. You can also set an alias_domain in `mailman shell`. E.g., ``` >>> domain = getUtility(IDomainManager).get('example.com') >>> domain.alias_domain = 'x.example.com' >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 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)

5 years, 6 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Fri, May 14, 2021 at 11:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 12:50 PM, Odhiambo Washington wrote: > > On Fri, May 14, 2021 at 7:04 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 5/14/21 5:02 AM, Odhiambo Washington wrote: > >>> On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: > >>> > >>>> > >>>> > >>>> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> > >>>> wrote: > >>>> > >>>> /bin/sh: sass: Permission denied* > ... > >> Try `which sass` > >> > > > > root@gw:/usr/home/wash # su mailman3 > > (venv) [mailman3@gw /usr/home/wash]$ which sass > > (venv) [mailman3@gw /usr/home/wash]$ > > > > There is no sass. > > > There has to be. You can't get a permissions error on sass if it doesn't > exist (well, maybe if you don't have permission to search a > superordinate directory, but that's unlikely). > > Try `find /usr -name sass` > /usr/local/include/sass That is the only thing found that is in the base system. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

5 years, 4 months

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

9 years, 1 month

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

6 years, 7 months

Re: Moderation request email from a non existing user

by Mark Sapiro

On 5/31/22 02:15, David Lopez via Mailman-users wrote: > Every day mailman (MM 3.3.3 (Tom Sawyer)) sends me an email with a held unsubcription request from X user. This user is not subcribed to that list anymore but every day an email is sending to the list owner. On the web interface there's nothing pending for approval or similar. Is there anyway to avoid receiving this anoyning email every day? Thanks in advance. Postorius >=1.3.5 has an `Unsubscription Requests` choice in the `Subscription requests` pull down. This choice will list the request with and allow you to delete it. For earlier Postorius this needs to be done via the REST API or via mailman shell. For example: ``` $ bin/mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> pendingsdb = getUtility(IPendings) >>> for token, data in pendingsdb.find(m, pend_type='unsubscription'): ... if data['token_owner'] == 'moderator': ... pendingsdb.confirm(token) ... data about the request will be displayed here >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Mailman-users search results for query "Postorius"