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

[MM3-users] Re: Upgrade path

by Mark Sapiro

On 08/08/2017 04:42 AM, David Krantz wrote: > > What is the rekommended way to upgrade to the newest version? (newest > _usable_ version, of course)? Is it docker-only with a migration from > the current solution to a docker based? If so, any ideas or pointers > on how to go about this? You may find this wiki article helpful <https://wiki.list.org/x/17891998>. I started with bundler on both this (lists.mailman3.org) and the mail.python.org installs, but have been updating from the heads of the various gitlab branches since very early on. At the moment, these installations are somewhat ahead of the 3.1 release, but I am not updating as the latest core has dropped Python 3.4 support, and I haven't yet installed Python 3.5 or 3.6 on these (Ubuntu 14.04) servers. (I will probably install 3.6 from source at some point.) Please feel free to ask here if you have more specific questions. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: Welcome Message

by Mark Sapiro

On 4/16/19 9:18 AM, brian(a)emwd.com wrote: > Thanks Mark. I added the POSTORIUS_TEMPLATE_BASE_URL to my settings: > > /opt/mailman/web/settings_local.py > > Now I get the following errors: ... > requests.exceptions.SSLError: HTTPSConnectionPool(host='mailman3.emwd.com', port=443): Max retries exceeded with url: /postorius/api/templates/list/testlist.mailman3.emwd.com/list:user:notice:welcome (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:841)'),)) > Apr 16 15:38:44 2019 (28) 172.19.199.3 - - "POST /3.1/members HTTP/1.1" 500 59 > > I am confused by the SSL errors. I have a valid SSL certificate installed on mailman3.emwd.com. These errors occur whether the POSTORIUS_TEMPLATE_BASE_URL is using http or https. I'm confused too. What happens if you just do in a python3 interactive session >>> import requests >>> response = requests.get('https://mailman3.emwd.com/postorius/api/templates/list/testlist.mailman3.em…') and if you get this far >>> response.status_code >>> response.text -- 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

[MM3-users] Re: Hyperkitty issue(s)

by Mark Sapiro

On 5/28/20 3:00 PM, brylon(a)oit.rutgers.edu wrote: > > I seem to have archives working on posts now, however, during my troubleshooting I moved away some archives/hyperkitty/spool/*.pck files and was wondering if/when I put them back is there a django-admin/hyperkitty command to run and process those again? (and if not I'm pretty confident the next post to any list? would slurp them all into hyperkitty anyway?) Your confidence is not misplaced. Every time mailman_hyperkitty receives a post from Mailman to be archived, it first tries to reprocess all the messages queued in archives/hyperkitty/spool/. There is no Django command because neither Django nor HyperKitty is directly involved. This is all mailman_hyperkitty which is a shim between Mailman and HyperKitty. Mailman talks to mailman_hyperkitty directly via the configured mailman_hyperkitty.Archiver class ``` [archiver.hyperkitty] class: mailman_hyperkitty.Archiver ``` and mailman_hyperkitty talks to HyperKitty via the API at the base_url configured in mailman-hyperkitty.cfg. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 10/7/20 12:39 AM, r.woithe(a)callassoftware.com wrote: > Hallo, > cause of we import our lists from mailman 2.1 to mailman3 as Alex Schuilenburg did, i did take a look in hyperkitty_sender and find an address like it is discribed above ( "firstname surename"@... ); i did insert,update and delete this address. > Now the sync is working and all is fine. Good. I'm glad you solved it. > Well, excuse my ignorance; cause of i have import the patch and set the logging level to debug but i could not find any more detailed error messages into the log files. I don't know why the patch didn't work. It should have produced warning level messages in the Django log as configured in settings(_local).py. Anyway, the issu is solved and you can remove the patch. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[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, 7 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, 5 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

9 months, 3 weeks

[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

4 years, 9 months

[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, 3 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, 3 months

Search results for query "sapiro"