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

[MM3-users] Re: Filter who can send on mailman3 list?

by marcus.granath＠gmail.com

Thank you @Mark Sapiro for you quick reply. So by doing the following settings, then ALL the messages sent to the list will be hold for moderation: Settings -> Message Acceptance "Default action to take when a member posts to the list": "Hold for moderation" "Default action to take when a non-member posts to thelist": "Hold for moderation" Members -> Administration options -> Moderation: "List default" BUT I don't really follow you when you say that those 3 allowed users to send on the list should also have set to "Moderation: List default"? How will they then be able to send messages, or what do I misunderstand here? Also, how do I create a "non-member" user "no-reply(a)abc.com"? Do you mean that I do that under the "Mass operations -> Mass subscriptions" ? Can I add a "fake address" there?

4 years, 6 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Jered Floyd

The difference in behavior was using social login buttons for an existing account vs. creating a new account. This is another damn django-allauth regression, starting in 0.57.0. It seem to be this commit that is to blame: https://github.com/pennersr/django-allauth/commit/be779dfee5a328a3a42edc2c9… In allauth/socialaccount/models.py:lookup(self):285 there is an attempt to look up the social account as one that already exists. If that fails, this commit calls self.account.get_provider() without passing the request object, which leads to the eventual error. I believe this is a django-allauth bug, and have submitted a pull request to fix it here: https://github.com/pennersr/django-allauth/pull/3548 Patch also included below. --Jered --- a/allauth/socialaccount/helpers.py +++ b/allauth/socialaccount/helpers.py @@ -205,7 +205,7 @@ def _add_social_account(request, sociallogin): def complete_social_login(request, sociallogin): assert not sociallogin.is_existing - sociallogin.lookup() + sociallogin.lookup(request) try: get_adapter().pre_social_login(request, sociallogin) signals.pre_social_login.send( --- a/allauth/socialaccount/models.py +++ b/allauth/socialaccount/models.py @@ -274,12 +274,12 @@ class SocialLogin(object): return False return get_user_model().objects.filter(pk=self.user.pk).exists() - def lookup(self): + def lookup(self, request=None): """Look up the existing local user account to which this social login points, if any. """ if not self._lookup_by_socialaccount(): - provider_id = self.account.get_provider().id + provider_id = self.account.get_provider(request).id if app_settings.EMAIL_AUTHENTICATION or app_settings.PROVIDERS.get( provider_id, {} ).get("EMAIL_AUTHENTICATION", False): ----- On Dec 6, 2023, at 3:21 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/6/23 11:00, Jered Floyd wrote: >> > These errors are generated to me as the admin, and in the elided > environment section SITE_ID is indeed 0, but I'm at a loss to imagine > why this happens only sometimes! > > For me, on a test installation with SITE_ID = 0, this only occurs at > https://example.com/accounts/social/connections/ > > Other URLs such as https://example.com/accounts/password/change/ and > https://example.com/accounts/email/ do not throw this exception. > > Here's the code: > ``` > def get_current(self, request=None): > """ > Return the current Site based on the SITE_ID in the project's > settings. > If SITE_ID isn't defined, return the site with domain matching > request.get_host(). The ``Site`` object is cached the first > time it's > retrieved from the database. > """ > from django.conf import settings > > if getattr(settings, "SITE_ID", ""): > site_id = settings.SITE_ID > return self._get_site_by_id(site_id) > elif request: > return self._get_site_by_request(request) > > raise ImproperlyConfigured( > 'You\'re using the Django "sites framework" without having ' > "set the SITE_ID setting. Create a site in your database and " > "set the SITE_ID setting or pass a request to " > "Site.objects.get_current() to fix this error." > ) > ``` > > I tried patching it from > ``` > if getattr(settings, "SITE_ID", ""): > ``` > to > ``` > if getattr(settings, "SITE_ID", None) is not None: > ``` > but that's even worse. It throws a bunch of > "django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist." errors. > > Somehow, get_current is being called without a request object in the > cases where it fails. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

1 year, 10 months

[MM3-users] Re: Can't remove footer(s)

by Henrik Rasmussen

Mark Sapiro wrote: > On 10/02/2018 12:14 AM, Henrik Rasmussen wrote: > > Did I miss something in order to remove the footers? > > Removing the files won't work because Mailman will fall back the the > built-in footer. You have to create empty files. The easiest thing is > just to 'cp /dev/null' to the footer files created by import21 Copying /dev/null doesn't help. It seems to be the same old content of the footer files before I removed the files and restarted Mailman, as if Mailman keeps the cache. I've just (again) ran # docker exec -it mailman-core mailman shell -l [LISTNAME_FQDN] >>> getUtility(ITemplateManager).delete('list:member:digest:footer', m.list_id) >>> getUtility(ITemplateManager).delete('list:member:regular:footer', m.list_id) after copying /dev/null to the files in /opt/mailman/core/var/templates/lists/[LISTNAME_FQDN]/da/list_member_digest_footer.txt and list_member_regular_footer.txt ,but that doesn't change anything. -- Henrik Rasmussen

7 years

[MM3-users] Re: Clearing webserver cache - Nginx

by Odhiambo Washington

On Wed, Aug 7, 2024 at 2:08 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/6/24 14:27, Mark Sapiro wrote: > > > > Is this with only one browser? It's a long shot, but clearing browser > > cache might work. > > > Actually, I see the same issues from my browsers, so it's not a browser > caching issue. The only thing left is nginx caching, but, while I know > very little about nginx, I think it doesn't cache by default and I don't > see where in your posted config it's enabled. Perhaps there's more in > your config that you didn't post. > > If there is a proxy_cache_path directive in your config try > > find /the/proxy/cache/path -type f -delete > > to clear the cache. > > As a last resort, your /opt/mailman/mm/static/CACHE/ directory should > contain a css/ directory with 3 files and a js directory containing one > file and a manifest.json file with a template for the `link` directives > referencing those files. > > The js/ directory is easy as its only one file, so your server is > looking for /static/CACHE/js/output.3aaa7705d68a.js and you could create > a symlink in the js/ directory from output.3aaa7705d68a.js to the actual > file. For the css directory, your server is looking for > output.158acc288604.css and output.6dab123e4897.css, and I don't see the > third file in the logs you posted, but if I go to pages in your archive > that I see as unstyled and look at the stylesheet references, they are > to output.44ea6c55e917.css, output.e68c4908b3de.css and > output.9efeb5f3d52b.css so you could just symlink those to the actual > files, it doesn't matter which as all three are loaded on each page. > Could you allow me to revisit this issue since I haven't solved it? First, I bypassed CloudFlare DNS proxying just to ensure I have nothing is coming in between my browser and the web server. That did not help with the issue of the "missing" CSS files. Ideally, I should not be creating these symlinks, right? On my old server the symlinks weren't necessary. I have created some symlinks and that appears to help with Apache. I will test with Nginx and see how it goes. ``` root@eu:/opt/mailman/mm/static/CACHE/css# ls -al total 196 drwxr-xr-x 2 mailman mailman 4096 Sep 29 10:40 . drwxr-xr-x 4 mailman mailman 4096 Mar 21 2024 .. lrwxrwxrwx 1 mailman mailman 23 Sep 29 10:40 output.ac23d5f5127c.css -> output.d29798365ddb.css lrwxrwxrwx 1 mailman mailman 23 Sep 29 10:31 output.bacec526ec98.css -> output.e69dbb26da3b.css -rw-r--r-- 1 mailman mailman 1209 Mar 21 2024 output.d29798365ddb.css -rw-r--r-- 1 mailman mailman 569 Mar 21 2024 output.e68c4908b3de.css -rw-r--r-- 1 mailman mailman 180904 Mar 21 2024 output.e69dbb26da3b.css root@eu:/opt/mailman/mm/static/CACHE/css# ``` My question though: What is the source of truth for the files that should be in /opt/mailman/mm/static/CACHE/css/ ?? Maybe that is what I need to focus on. If need be, then I should *fix* the contents of that file so that it doesn't contain the nonexistent files, no? Lastly, why is it that my https://mm3-lists.kictanet.or.ke/archives/ does not display content similar to what https://lists.mailman3.org/archives/ does? What change should I make in which settings.py? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year

[MM3-users] Re: Link in the top-left corner of Hyperkitty

by Seth Seeger

On May 8, 2020, at 10:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/8/20 7:34 AM, Seth Seeger wrote: >> >> There is a link to the root of Hyperkitty in the top left corner of my Hyperkitty pages. It links to the correct domain, but the text isn’t right - it’s the first domain name I was using at the beginning of my install for testing. I’d like to update it, but can’t find what to change. > > > You have to edit the display name for the domain in the Django web admin > Sites section. Huh. I had it properly set for the domain that is active, but it wasn’t taking affect. I changed it for the (old) test site, and it changed it. So the name that is showing doesn’t match the domain name that I was changing it for. Thanks, Seth

5 years, 5 months

[MM3-users] Re: hyperkitty.views.mailman Could not archive the email with message-id '<snip>': A string literal cannot contain NUL (0x00) characters

by Gilles Filippini

Mark Sapiro a écrit le 12/03/2021 à 00:59 : > On 3/11/21 3:10 PM, Gilles Filippini wrote: >> >> Looking at the offending message with 'mailman qfile', it appears it is >> a legitimate one actually, sent from an Android phone. >> >> Couldn't hyperkitty be a bit less strict? > > > Possibly. It looks like this may be > <https://gitlab.com/mailman/hyperkitty/-/issues/271>, fixed? by > <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215>. What > HyperKitty version is this? > <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215> is in 1.3.2. > > If your HyperKitty is >= 1.3.2, please file a new issue at > <https://gitlab.com/mailman/hyperkitty/-/issues> This is Hyperkitty 1.3.4. I'll file an issue tomorrow. Thanks, _g.

4 years, 7 months

[MM3-users] Re: Django: An error occurred while processing your request.

by Florian Sukup

Thank you both very much. On 5/26/25 18:30, Mark Sapiro wrote: > On 5/26/25 12:08 PM, Florian Sukup wrote: >> >> When I received emails from postorius, then it came from example.com >> which is nonsense as I worked with the real lists. So I deleted >> example.com. > > > Set DEFAULT_FROM_EMAIL and SERVER_EMAIL appropriately in your Django > settings. > seem to produce reasonable results >> When I call https://.../mailman3/admin or any of the lists, the result >> is: >> Server error >> An error occurred while processing your request. > > You need to set SITE_ID appropriately in your Django settings. See > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > This made the difference. I set it to 0 now as I have more than one site/domain. Thanks again, Florian.

4 months, 4 weeks

[MM3-users] Re: Deleting messages from HyperKitty archive

by Mark

On 2024-03-26 08:45, Mark Sapiro wrote: > On 3/25/24 13:00, Mark wrote: >> >> Regarding updating, the Hyperkitty docs say to (a) update the code >> base; and (b) update the database schemas. >> >> Although updating the database is mentioned, there isn't anything >> about updating the code base. > > Updating the code base just means installing an updated version. E.g. > upgrading from 1.3.8 to 1.3.9. > Thanks Mark. Was another case of "If all else fails, read the instructions..." $ sudo systemctl stop mailman3 $ sudo systemctl stop mailmanweb (venv) $ pip install -U mailman postorius django-mailman3 hyperkitty mailman-web (venv) $ mailman-web migrate (venv) $ mailman-web compress (venv) $ mailman-web collectstatic (venv) $ mailman-web compilemessages $ sudo systemctl start mailman3 $ sudo systemctl start mailmanweb https://www.mailman3.org/en/latest/upgrade-guide.html Successfully upgraded to Hyperkitty 1.3.9 and the delete message link now shows for the list owners. Best, Mark

1 year, 7 months

[MM3-users] Re: Extracting mailing list users

by Jan Eden

On 2022-12-30 10:29, Mark Sapiro wrote: > On 12/30/22 03:25, Jan Eden via Mailman-users wrote: > > On minor issue: All user names with > > non-ASCII characters appear with quoted-printable encoding (e.g. > > =?utf-8?q?J=C3=BCrgen?=). Is there a way to output UTF-8 instead of QP? > > I just created https://gitlab.com/mailman/mailman/-/issues/1048 for this. I > think this patch > ``` > --- a/src/mailman/commands/cli_members.py > +++ b/src/mailman/commands/cli_members.py > @@ -104,10 +104,10 @@ def display_members(ctx, mlist, role, regular, digest, > if nomail is not None: > if member.delivery_status not in status_types: > continue > - 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)), > + print(f'{address.display_name} <{address.original_email}>', > file=outfp) > > ``` > (line may be wrapped) will fix it. Excellent – thank you! - Jan

2 years, 9 months

[MM3-users] Re: uncaught bounce messages

by David Bremner

David Bremner <david(a)tethera.net> writes: > Mark Sapiro <mark(a)msapiro.net> writes: >> >> Thank you. I tested that DSN with current flufl.bounce and it is >> recognized as a temp failure for the reported address and that in turn >> should just be ignored by Mailman's bounce runner and not reported as >> unrecognized. >> >> What version of Mailman core is this and what version of flufl.bounce? >> > > Sorry, meant to reply on list with the rest of the details, but got > distracted by making dinner. So it sounds like the problem is old > versions of flufl.bounce. > > This particular machine is running debian oldstable, so things are a bit > out of date. mailman-core is 3.2.1 and flufl.bounce is 3.0. I'll look > into upgrading at least flufl.bounce. Oh. It's actually 3.0.1. Still not new enough, but 3 years newer. d

4 years

Search results for query "sapiro"