Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Customising hyperkitty and postorius

by Mark Sapiro

On 11/18/20 5:16 PM, peter(a)chubb.wattle.id.au wrote: > > Hi, > I've put up a mailman3 instance, with hyperkitty enabled, and > imported all my mailman2.1 archives -- it all seems to be > working. > > How do I now customise the look and feel of my site? > > In particular, I'd like to render archived emails with a > monospace font, and I'd like to change the colour scheme and > styles of all the pages to match other pages on the same website. HyperKitty will display a message in monospace if you click the 'A' icon at the bottom of the message. I don't know offhand how you would make that the default. For styles, they are mostly SCSS in the directory hyperkitty/static and CSS in the directory postorius/static/postorius. I think you'd have to find the relevant styles and edit them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Error Logging - what changed with the New Year releases?

by Mark Sapiro

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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Configure new list via REST API - trying to add moderators

by Mark Sapiro

On 9/11/24 14:32, Andy Matthews wrote: > One quick follow up. I'm making a subscribe request for a moderator. I'm passing in list_id, subscriber, and role (moderator). The request is returning a 201 response, but when I shell into the mailman server and inspect the list directly it shows there are no moderators. I've confirmed the list id, and I can see a list of regular members, but when I use the command line, the only version of the query which shows members is the default: `mailman members <list name>`. Does `mailman members <list name> --role moderator` show the moderator? The following works for me: ``` curl -urestadmin:restpass \ --request POST \ -H 'Content-Type: application/json' \ --data-binary '{"list_id": "list.example.com", "subscriber": "someone(a)example.com", "role": "moderator"}' \ http://localhost:8001/3.1/members ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Re-send subscription response and file permission error in queue

by Mark Sapiro

On 9/11/20 2:18 PM, Mark Sapiro wrote: > On 9/8/20 10:56 PM, accounts-mailman(a)holbrook.no wrote: >> A user sent subscription request to the `..-join@` address of a list. Email domain wasn't set up properly, so response got rejected. Now, if the user tries to send another request, no reponse comes back. In the log I find a python stack trace saying subscription already pending. >> >> ``` >> Sep 08 10:32:44 2020 (19918) Traceback (most recent call last): >> File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 171, in _one_iteration >> self._process_one_file(msg, msgdata) >> File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 264, in _process_one_file >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/lib/python3/dist-packages/mailman/runners/command.py", line 196, in _dispose >> mlist, msg, msgdata, parts, results) >> File "/usr/lib/python3/dist-packages/mailman/commands/eml_membership.py", line 104, in process >> ISubscriptionManager(mlist).register(subscriber) >> 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 227, in _step_sanity_checks >> raise SubscriptionPendingError(self.mlist, self.address.email) >> mailman.interfaces.subscriptions.SubscriptionPendingError >> ``` > > > I'll look at this when I get some time. I'm still catching up after > being off line for 12 days. This exception should also send a response to the user's email saying "User <user(a)example.com has a pending subscription for list(a)example.net" Was this sent? To fix, >> How can I remove the pending subscription, or re-send the response email? > > In Postorius, pull down Subscription Requests and select Pending > Confirmation and delete the request. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Five Year Old Issue

by Mark Sapiro

On 3/13/21 8:07 PM, Brian Carpenter wrote: > Any chance to get this implemented in time for the next Mailman 3 core > release? > > https://gitlab.com/mailman/mailman/-/issues/19 > > It's been 5 years. It's not simple. The issue is delivery_mode is an attribute of the member, and when an email join command is processed, there is no member yet because the request is waiting confirmation so join processing can't just set the delivery_mode. It would require an additional argument to the ISubscriptionManager interface register() method for the delivery mode and then carrying that with the subscription workflow until there is actually a member to apply it to. And tests have to be written for all of that. That's not to say that it shouldn't be fixed, just that it's not something that can be knocked out in an hour. Anybody care to take it on? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Issue converting table charset to utf8mb4 on mysql

by Mark Sapiro

On 3/23/24 12:14, Helio Loureiro wrote: > So the question is whether it is possible to change the types in this table. > > MariaDB [mailman3]> desc pendedkeyvalue; > +-----------+----------------+------+-----+---------+----------------+ > | Field | Type | Null | Key | Default | Extra | > +-----------+----------------+------+-----+---------+----------------+ > | id | int(11) | NO | PRI | NULL | auto_increment | > | key | varchar(255) | YES | MUL | NULL | | > | value | varchar(20000) | YES | MUL | NULL | | > | pended_id | int(11) | YES | MUL | NULL | | > +-----------+----------------+------+-----+---------+----------------+ > 4 rows in set (0.001 sec) > > key and value are varchar. Can any of them be changed to text instead? > Perhaps even both? I wouldn't bother. The keys and values in the pendedkeyvalue table should all be OK as latin1. That's why that table wasn't included in the migration at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/database/alemb… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Mark Sapiro

On 05/28/2016 02:19 PM, Rubén Rivero Capriles wrote: > > (please note that I earlier replied this by email, as I notice that it doesn't show up on the list website I am reposting. Hopefully it won't be repeated. I've been looking through archive posts and some are double. Would be interesting to check if my reply from half an hour ago will eventually get posted. If it gets, my apologies!) Your initial reply was sent to the list members. It should have been archived, but it wasn't. That is my fault as I was experimenting with a Python 3 version of mailman.client which didn't work and then for a short time I had stopped the web services but not the core, and your post arrived during that window and was unable to be archived. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 3 months

[MM3-users] Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Mark Sapiro

On 12/10/2016 12:52 AM, Barry Warsaw wrote: > > Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. Done. There is one "temporary" commit in my MR to work around <https://github.com/sphinx-doc/sphinx/issues/3212> and get "docs" to pass. >> I can also work on Postorius. Also in this vein I have a question. >> Should the DMARC settings be added to the Alter Messages tab in the List >> Settings view or would it be better to have a separate DMARC Mitigations >> tab. > > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and > Terri have final say I think. I have a WIP MR at <https://gitlab.com/mailman/postorius/merge_requests/194> that adds a tab. Maybe Florian and Terri can look at that and chime in. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

[MM3-users] Re: Log rotation

by Mark Sapiro

On 04/10/2018 03:04 PM, Darren Smith wrote: > > 1) Has anyone come up with a good log rotation strategy that doesn't > necessitate a restart of the service? I think Abhilash has answered this, but for completeness, here's what I use on lists.mailman3.org which uses nginx and gunicorn Mailman's logs /opt/mailman/mailman-bundler/var/logs/*.log { missingok sharedscripts su mailman mailman postrotate /opt/mailman/mailman-bundler/bin/mailman reopen &>/dev/null || true if [ -r /opt/mailman/mailman-bundler/var/gunicorn.pid ]; then PID=`cat /opt/mailman/mailman-bundler/var/gunicorn.pid` kill -s USR1 $PID fi endscript } mailman-web log /var/log/mailman-web/*.log { missingok notifempty delaycompress su mailman mailman } And here's mail.python.org with apache and mod_wsgi Mailman's logs /opt/mailman/mailman-bundler/var/logs/*.log { missingok sharedscripts su mailman mailman postrotate /opt/mailman/mailman-bundler/bin/mailman reopen &>/dev/null || true endscript } mailman-web log /var/log/mailman-web/*.log { missingok notifempty delaycompress su mailman mailman } -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/20/20 7:24 PM, Ruth Ivimey-Cook wrote: > > ... the Body of reply, with the JSON text: > > { > "start": 0, > "total_size": 1, > "entries": [ > { > "alias_domain": null, > "description": null, > "mail_host": "ch-bc.org.uk", > "self_link": "http://0.0.0.0:8870/3.1/domains/ch-bc.org.uk", > "http_etag": "\"5d474f0be89222e6122b6dc375a18ff01190419d\"" > } > ], > "http_etag": "\"c6f15186189ff5cf5b67f2d06dcf4ea97ea447a9\"" > } All these self_link references are generated from self.api.path_t which is a reference to (in the case of 3.1) <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/api.py#L6… which gets the host portion from config.webservice.hostname, i.e. the value of hostname in the webservice section of mailman.cfg, and actually <sigh>, looking back at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> that's exactly where you said you set it to 0.0.0.0. Change that to greyarea-post -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

Search results for query "sapiro"