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

[MM3-users] Bug in email.generator:_handle_text? [was: store/export existing Mailman lists ...]

by Stephen J. Turnbull

Mark Sapiro writes: > This apparently confuses the Python email package so that the > get_payload() method returns a list of strings rather than a list of > message objects. Yes, I got that far too. I'm guessing that in the absence of a Content-Type, which then *should* default to text/plain, the email package goes ahead and detects the MIME headers anyway (although I don't think it should do that) and breaks the message into MIME parts. I would think we'd raise an Exception here. If there's a reason for the email package to do that detection (*shrug*, it seems to work), then the dispatching in _handle_text should be done on the Python type rather than the MIME Content-Type. I forget exactly how the code is structured, the relevant dispatching may be in _dispatch or in _dispatch_meth. Steve

3 years, 5 months

[MM3-users] Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question

by Ken Alker

--On Saturday, June 24, 2023 2:09 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/23/23 10:44 PM, Ken Alker wrote: > > > 4) python3: can't open file 'manage.py': [Errno 2] No such file or directory > > > > The last one looks the most concerning, and is looping. > > > If you installed the mailman-web package from PyPI, the django admin > command is bin/mailman-web in your venv, not manage.py. I found that in /etc/mailman3/uwsgi.ini and changed it and it solved the problem. Thank you! I sent a reply to my original email this morning but when I view it in the web archives, it see that it didn't get threaded with my original email. I hope this one does. I wonder why the original did not. Ken

2 years, 7 months

[MM3-users] Re: Mailman-web showing "An error occurred while processing your request."

by C. Souza

Hello Guys, Thank you for the help. Mark, I followed your recommendation running your code and it's done, problem solved. Just for curiosity, does anyone know the reasons for this kind of problem and how to avoid it? Thank you very much. -- Carlos Adean On Thu, Feb 9, 2023 at 1:55 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/8/23 08:34, C. Souza wrote: > > I'm trying to manage 2 held messages in a specific list and I'm getting > > this error below when I click on /held_messages. It never happened > before. > ... > > ==> mailmanweb.log <== > > ERROR 2023-02-08 16:01:30,149 1516 django.request Internal Server Error: > > /mailman3/lists/mylist.domain.com/held_messages > > Traceback (most recent call last): > ... > > File > > > "/opt/mailman/venv/lib64/python3.6/site-packages/django/utils/dateparse.py", > > line 107, in parse_datetime > > match = datetime_re.match(value) > > TypeError: expected string or bytes-like object > > > I'm not certain, but it looks like one of the held messages has a bad or > possibly missing Date: header. Working around this is tricky. You can do > the following in mailman shell. > ``` > $ mailman shell -l list(a)example.com > > 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. > The variable 'm' is the list.example.com mailing list > >>> requests = IListRequests(m) > >>> msgstor = getUtility(IMessageStore) > >>> for request in requests.held_requests: > ... key, data = requests.get_request(request.id) > ... if data['_request_type'] == 'held_message': > ... print(f'request ID = {request.id}Message-ID = {key}\n ' > ... f'message = {msgstor.get_message_by_id(key)}') > ... > This will print for each held message output like > > request ID = nnn > Message-ID = <the message id> > message = the message content > > > You can then handle these messages with > > >>> from mailman.app.moderator import handle_message > >>> handle_message(m, nnn, action) > > where nnn is the request ID and action is either Action.discard to > discard the message or Action.accept to accept it. And finally > > >>> commit() > ``` > If you decide you want to edit the message content before accepting it, > you could find the message in the file system. One of the headers in the > displayed message is something like > > Message-ID-Hash: IWL2EUW3FT7IIUA3QYTZEX4W4JBZ26HL > > the message is saved as a python pickle in the file system in Mailman's > var/messages/ directory. This has subdirectories of the first two > characters of the Message-ID-Hash value and those have subdirectories of > the second two characters of the Message-ID-Hash value, so if the above > were the actual Message-ID-Hash the pickle would be at > var/messages/IW/L2/IWL2EUW3FT7IIUA3QYTZEX4W4JBZ26HL. You would need to > pickle the new message content and save that over the existing file. > > -- > 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 skooperit(a)gmail.com >

3 years

[MM3-users] Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Stephen J. Turnbull

Mail Person writes: > Hello everyone. I am trying to sort out an error happening when > messages are sent to the mailman server. The emails are being sent > to the list but I get this error each time: > > Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\x90\\xBA\\x0A\\x0A...' for column 'content' at row 1") This looks like the MySQL "we don't do 4-byte UTF-8" bug. > File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute > 209. res = self._query(query) and it is MySQL, so the problem is most likely that your MySQL is not configured to handle Unicode properly. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… for a lot of information about this. All the posters have useful comments but start with Mark Sapiro's.

2 years, 6 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Stephen J. Turnbull

Mark Sapiro writes: > On 4/7/25 17:45, MegaBrutal via Mailman-users wrote: > > So it's even weirder – however, I'm really not sure if this is > > the address HyperKitty is checking for, as I have 3 attached to > > my account! How may I know which one it's trying to use? > > If you go to https://example.com/user-profile/ what Primary email > and Other emails do you see? Do you see all three? And if you go to > https://example.com/mailman3/users and click Manage for your > address, do you see all 3 under Addresses? Is it possible this is a weird new symptom of the "multiple entries for archiver" bug? -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

10 months, 1 week

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

by iMark

>> On 1/26/26 03:25, iMark wrote: >> In Mailman 3, is there an equivalent to the Mailman 2 script command >> of "bin/find_member <EMAILADDRESS>" ? > On 2026-01-26 20:10, Mark Sapiro wrote: > ``` > 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. > ``` > > -- Thank you yet again Mark. # su mailman (venv) mailman@... $ mailman findmember imark(a)postmark.net

3 weeks, 3 days

[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

2 years, 2 months

[MM3-users] Re: Where are the subject templates hidden?

by Thor Atle Rustad

2017-11-29 7:40 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > On 11/28/2017 02:56 AM, Thor Atle Rustad wrote: > > Using Docker. Suppose I've overcome > > https://gitlab.com/mailman/mailman/issues/359 and I can make Mailman use > > the templates/site/no directory for my customized templates. Yes, it > seems > > to be working, no hickups when national characters are used in the > > templates. > > > > but... > > > > the welcome message still says "Welcome to the "listname" mailing list" > in > > English. Is it possible to change that? > > > Have you put the desired template in > templates/site/no/list:user:notice:welcome.txt ? > > -- > Yes, I put it there, and the text in that file is what is shown in the welcome mail. However, the subject does not change (still English) Thor

8 years, 2 months

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

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

Search results for query "sapiro"