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

[MM3-users] Re: REST API authorization failed

by Mark Sapiro

On 1/10/22 1:58 AM, Axel Rau wrote: >> >> Anyway, the above is saying that restadmin:??? doesn't match what's configured in Mailman core and reported by `mailman info`. Please check carefully that these are the same in both mailman.cfg admin_pass and settings MAILMAN_REST_API_PASS. > > Yes, again with password disclosed: > - - - ... > (mailman_33) [root@lists5 /usr/local/mailman3]# grep admin var/etc/mailman.cfg > admin_user: restadmin > admin_pass: restpass Does `mailman info` show the same password? > What am I doing wrong? Nothing. > Is something wrong with my installed python packages? The relevant code is at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/rest/wsgiapp.p… Does that match yours? -- 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: Inline display of attachments

by Mark Sapiro

On 1/26/22 10:01, Axel Rau wrote: > Can this come to work with a plugin? > >> Am 19.01.2022 um 14:28 schrieb Axel Rau <Axel.Rau(a)chaos1.de>: >> >> Signierter PGP-Teil >> I have turned on HYPERKITTY_RENDER_INLINE_IMAGE and Archive Rendering mode set to Markdown text, but images in JPEG or PDF format are not displayed inline. >> Should this work or are my expectations to high? As it says in the docs at https://docs.mailman3.org/projects/hyperkitty/en/latest/rendering.html#imag… you have to include markup like ``` ![Image's alt text](http://image.com/file.png "Image Title") ``` in the message text to display the image inline. The `!` is important. -- 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: MTA authentication and smtpd_sender_login_maps

by Mark Sapiro

On 11/25/22 11:00, Jan Eden via Mailman-users wrote: > > I obviously do not want to add an entry to the map file for each mailing > list created by someone on the server. Is there a way to > programmatically create a sender login map with Mailman? You could modify mailman/src/mailman/mta/postfix.py to create a smtpd_sender_login_maps file with the desired content or you could create a script that creates the file using data in the generated var/data/postfix_lmtp. If the latter, you might be able to create a plugin <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do…> to run the script whenever a list is created or deleted -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Subscription requests = 0 ? Bug or feature?

by Mark Sapiro

On 3/24/23 04:15, Odhiambo Washington wrote: > Even though I have a "Pending confirmation" request, the total entries > under the subscription requests reads zero. > I thought it should read whatever the total of (pending confirmation + > pending approval) is. It only counts the requests waiting moderator approval because this is the number requiring moderator action. It doesn't count the requests waiting user confirmation. The only reason these are even available in the moderator interface is so the moderator can discard them in cases where the user has lost the confirmation email and can't confirm and can't subscribe again because of the pending confirmation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Is there a bin/find_member in MM3

by Mark Sapiro

On 1/26/26 03:25, iMark wrote: > Hi, > > In Mailman 3, is there an equivalent to the Mailman 2 script command of > "bin/find_member <EMAILADDRESS>" ? ``` mailman findmember -h Usage: mailman findmember [OPTIONS] PATTERN Display all memberships for a user or users with address matching a pattern. Because part of the process involves converting the pattern to a SQL query with wildcards, the pattern should be simple. A simple string works best. Options: -r, --role [all|owner|moderator|nonmember|member|administrator] Display only memberships with the given role. If not given, 'all' role, i.e. all roles, is the default. -h, --help Show this message and exit. ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 3 weeks

[MM3-users] Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/10/21 3:22 PM, David Newman wrote: > On 12/10/21 12:57 PM, Mark Sapiro wrote: >> >> Are you using uwsgi or some other wsgi server. > > uwsgi, per the venv and PDF docs. Thanks for the fix. > > Regarding the uwsgi_pass docs, would 'uwsgi_pass_header' directives > replace the 'proxy_set_header' ones in the venv doc? > > Looking at the uwsgi doc, it seems they might do different things. If you are using uwsgi and proxy_pass http://127.0.0.1:8000 is working for you, then I'm satisfied that the docs are OK now and we don't need to say anything about uwsgi_pass. > It's not the situation I have to deal with, though. Short of changing a > long-standing URL, what I'm looking to do is have "/" continue to > default to roundcubemail, and have users type in longer URLs for MM3 and > other services. I think you can set the document root to the roundcubemail root and then set locations for the Mailman destinations as, e.g. location /mailman3/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /archives/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /accounts/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /admin/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /user-profile/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } I haven't tried anything like this, so I'm not sure it will work, but I think so. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Extracting mailing list users

by Mark Sapiro

On 1/1/23 08:14, Eggert Ehmke via Mailman-users wrote: > I edited this file: > venv/lib/python3.9/site-packages/mailman/commands/cli_members.py > > The content at line 107ff is: > #patch of Mark Sapiro > # if email_only: > if email_only or not address.display_name: > print(address.original_email, file=outfp) > else: > # print(formataddr((address.display_name, address.original_email)), file=outfp) > print(f'{address.display_name} <{address.original_email}>', file=outfp) > > This file is actually executed when I call mailman members. I verified this by uncommenting the first (old) print line. Now each address is printed twice (as expected), with the utf8 code in both lines in case of umlauts. In that case the address.display_name value is the RFC 2047 encoded name. One way this can happen is if the subscribe was via email prior to Mailman 3.3.3. See https://gitlab.com/mailman/mailman/-/issues/802. You could try something like this to fix these. ``` mailman shell 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. >>> um = getUtility(IUserManager) >>> from email.header import decode_header, make_header >>> for address in um.addresses: ... decoded = str(make_header(decode_header(address.display_name))) ... if decoded != address.display_name: ... address.display_name = decoded ... print(f'Fixed {decoded}') ... >>> # while you're at it do users too. >>> for user in um.users: ... decoded = str(make_header(decode_header(user.display_name))) ... if decoded != user.display_name: ... user.display_name = decoded ... print(f'Fixed {decoded}') ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Do not show archives to public

by Mark Sapiro

On 6/18/19 5:21 PM, Andrew Bernard wrote: > > This resulted in dozens of messages about Django errors, when I turned on > Private Archives, and then accessed the page. Is that to be expected? [Hard > to imagine.] Perhaps you have to wait? But how long typically? This is definitely not expected. What are the errors? Including tracebacks from logs if any. As far as waiting is concerned, I think the thing you might be waiting for is the Django sync_mailman job which, if you have set up cron to run the periodic Django jobs, runs daily, but you can run it manually via the Django admin `runjob sync_mailman` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Mark Sapiro

On 10/29/19 8:21 PM, Franklin Weng wrote: > Yes, it is checked. Have you checked Mailman's logs - Mailman's var/logs/mailman.log in particular? Do messages received from the list have an Archived-At: header? What's in /etc/mailman3/mailman-hyperkitty.cfg? In particular does the [general] setting base_url define a URL that accesses hyperkitty and does the [general] setting api_key match the MAILMAN_ARCHIVER_KEY setting in /etc/mailman3/mailman-web.py, but note that the MAILMAN_ARCHIVER_KEY setting is quotes because it is a Python string assignment and the api_key setting is not quoted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Easiest way to install a new mailman3 deployment?

by Mark Sapiro

On 1/5/21 3:37 PM, Ruth Ivimey-Cook wrote: > > I have only split mailman in two: mailman-core with the email-related > parts, and postorius for the UI. As yet, although Hyperkitty "works", I > haven't addressed the fact that mails get archived in folders on the > email host and so (for me) hyperkitty can't see them. Ideally, they > would be on the postorius/hyperkitty host, or possibly network shared The emails that get archived in folders on the Mailman core host are archived by the 'prototype' archiver, not by HyperKitty. HyperKitty archived emails are in tables in Django's database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

Search results for query "sapiro"