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

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 7/8/22 9:16 AM, kisner(a)live.com wrote: > > Just out of curiosity and to try to improve the doc I can do this a little later. But I can tell you for sure the pip install psycopg2-binary<2.9 command failed for me on Ubuntu 22.04 and Debian 11.3. I'm not saying it's *not* me, and I don't know when the last time that doc was updated but I couldn't get it to work on a few different distros. The issue is when you do ``` pip install psycopg2-binary<2.9 ``` your shell (sh, bash, zsh or whatever) interprets `<2.9` as an input redirection and probably says something like `2.9: No such file or directory`. You need to do something like ``` pip install psycopg2-binary\<2.9 ``` or ``` pip install 'psycopg2-binary<2.9' ``` I'll update the doc. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Is there a way to find out when a user subscribed to a list

by Mark Sapiro

On 4/17/24 15:14, Mark wrote: > You can query the mailman database ... > > select email, registered_on,verified_on from mailman.public.address > where email = 'mmasoudf(a)aaas.org' > > > On 2024-04-18 03:19, Mohsen Masoudfar wrote: >> Hi, >> We need to find out when a specific user joined a list. Is there a way >> to get this information? Querying the database in that way is not reliable. Yes, it is correct that the user has both a user record and an address record, and the user record has a created_on date and the address record has both registered_on and verified_on dates, but those are only the creation/verification dates for those records. They are not necessarily the date that that user/address subscribed to any list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Held messages showing a reason not in English on the Postorious

by Mark Sapiro

On 6/25/24 20:13, Alan KT So (ITSC) wrote: > We just notice a held message from a user's list showing the held reason in Ukrainian, but the interface is in US English and the list's preferred language is English (USA). We could not repeat the issue. What can be the reason behind? > > [cid:image001.png@01DAC7B9.AF2B0400] I'm assuming the image that content filtering removed was a screen shot of the held message view in Postorius. was the sender of the message a list member with preferred language Ukranian? There may be an issue here. The line at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/hold.py… calls format_reasons which will translate the reasons in whatever the current language context is. It should probably explicitly specify the list's preferred language. -- 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: Header settings and Gmail

by Mark Sapiro

On 7/29/24 12:25, erik(a)dante.de wrote: > > As a preventive measure, it helps to use DMARC mitigation action with “Replace From: with list address” and “ DMARC Mitigate unconditionally ”. But now some users are unhappy with the From header " Username via Test-liste <test(a)test-liste.org>". They would rather have their email address in it. If your Mailman core version is >=3.3.9 you can add `^.*(a)gmail\.com` to dmarc_addresses (DMARC addresses in Postorius) to apply the mitigation to gmail.com addresses instead of unconditionally, but this won't help your gmail users. > Is there a solution with which Google delivers the mailing list messages without complaining, but the sender email address is also in the “From:”? No. This is just one example of Google/gmail behaving oddly. gmail.com publishes a DMARC policy of none, yet they require incoming email From: the gmail.com domain to pass DMARC -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: DKIM signatures with message footers or subject prefixes

by Mark Sapiro

On 3/12/22 12:20, Stanisław Findeisen via Mailman-users wrote: > On Fri, Mar 11, 2022 at 10:41:00AM -0800, Mark Sapiro wrote: >> Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your >> valid DKIM signature and no prior Authentication-Results:. > > Ok, you mean after replacing the From address with the list address, right? > I can see no way (or sense) to DKIM sign arbitrary From: addresses. Your DKIM signature only says you sent the mail and if the signature validates, the mail hasn't been modified since you signed it. I.e. validation of the signature is a statement to the recipient that the mail received is what you sent. That's all. If the domain of the From: address doesn't align with your domain, the signature won't help with DMARC, but that's a separate issue and why we have DMARC mitigations suck as replacing the From: with the list address. > This actually works quite good: the recipient just gets 2 DKIM signatures. The original one is broken, the MTA-generated one (after writing my list address into From) is OK. This is good enough even for ProtonMail (no red warning). And your rewriting the From: is only necessary for DMARC. If the ProtonMail red flag is only because there was no valid DKIM signature, you shouldn't need to rewrite From:. If it is because of DMARC, you do. > What about this list (mailman-users). It looks this one also has From address replacement + conditional DMARC mitigation. And remove_dkim_headers: no. Correct? This list has DMARC mitigation action = Replace From: and DMARC Mitigate unconditionally = No and remove_dkim_headers: no. We DKIM sign all outgoing mail from lists.mailman3.org. -- 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: no mails to list members

by Mark Sapiro

On 1/4/19 6:49 AM, Thomas Stein wrote: > > While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? There are multiple ways to reference templates, but just putting them in that location should work. > Should > I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Your list was created with an older version of import21. That version named the templates it stored with underscores rather than colons and set the URI for that template to use the underscore name. Thus, without changing the URI for the template, you need to continue to use the underscore name for those templates, but for other templates, you can use the name with colons and not worry about the URI. > Is there some documentation > what variables i can put in those templates? See <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.ht…>. -- 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: Delete Django profiles not signed up to a list

by Mark Sapiro

On 2/8/21 1:22 AM, r.woithe(a)callassoftware.com wrote: > Hello, > > i did try the script and unfortunately there is a problem. The script is deleting django-users are not member,nonmember ... of any lists.But thats not the point. Its ok if a user want to be only a django-user to see the archives and work with them. If a user sign's up for an account at /accounts/signup/ and then confirms her address, she will then be a Mailman user with a user and an address record even though not a member of any lists. > The script should delete django-users who dont confirm your email address. Change one line in the script from ``` if mm_user is None or len(list(mm_user.memberships.members)) == 0: ``` to ``` if mm_user is None: ``` And it will do what you want. -- 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: moderation notices for list-owner being redirected to mailman address

by Mark Sapiro

On 2/9/22 16:12, Philippe B wrote: > Ah, thanks for that. > > I've done `owner.preferences.delivery_status = DeliveryStatus.enabled` for those 2 lists. > > Is there an easy way to find out all the other owners that don't have `<DeliveryStatus.enabled: 1>` ? ``` $ bin/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. >>> for mlist in getUtility(IListManager).mailing_lists: ... for admin in mlist.administrators.members: ... if admin.delivery_status != DeliveryStatus.enabled: ... print(f'List: {mlist.list_name}, ' ... f'Admin: {admin.address.email}, ' ... f'Role: {admin.role}, ' ... f'Status: {admin.delivery_status}') And optionally, ... admin.preferences.delivery_status = DeliveryStatus.enabled ... print('Enabled.') ... (output here) >>> 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, 10 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 8/5/22 07:02, Kimmo L wrote: > > The only concern I've observed and I'm trying to solve right now is with memory. Not sure whats consumes the memory gradually, so that it will start consume also swap memory and eventually you can find"OSError: write error" entries in uwsgi-error.log or "django.request Internal Server Error: /hyperkitty/" in mailmanweb.log > Do i need to modify my uwsgi.ini configuration maybe ? > Server has 2CPU and 5GB RAM. We have seen reports of memory leaks, but no solutions. We do not see these issues on any of the production servers we manage. The server that hosts this lists has 4GB RAM and that seems fine for a server doing just Mailman. Our servers use gunicorn, not uwsgi, so this could be a uwsgi issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Badsignature on uwsgi-error.log

by Mark Sapiro

On 3/20/24 14:25, Helio Loureiro wrote: > Hi, > > I keep receiving a lot of errors like this: > > --- Logging error --- > Traceback (most recent call last): ... > "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", > line 55, in unsign > raise BadSignature('Signature "%s" does not match' % sig) > django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" > does not match ... > > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and MAILMAN_ARCHIVE_KEY > on setting.py are the same. Of those three, the api_key on mailman-hypperkitty.cfg and MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django thing and has nothing to do with the others. See https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key If you changed it, that's the issue. If you know what it was previously, you could set the previous value in SECRET_KEY_FALLBACKS, see https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

Search results for query "sapiro"