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

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

ok Thank you Mark for your valuable time. I will try this method and let you know the status. Thanks once again. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 12:44 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/28/20 12:08 AM, Shashikanth Komandoor wrote: > > I tried this way but in this method I don't find any files to edit for my > > customizations like > > 1. Removal of social accounts, > > 2. Addition of SMS integration and so. > > > > If I can do my required customizations through pip installation I am fine > > with that. > > If you follow the instructions for installing in a virtualenv, in say > /opt/mailman/venv, all the component files will be in > /opt/mailman/venv/lib/python3.x/site-packages > > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 6 months

[MM3-users] Re: MM3 in virtualenv - FreeBSD-11

by Mark Sapiro

On 1/11/19 6:51 AM, Odhiambo Washington wrote: > > Now that I look at it, I think you should clarify that if one is not > interested in using PostgreSQL (which is what `pip install psycopg2-binary` > is for), > then there should be some different binary they need to install, no? And > which one is it? I have added a note to the comment at https://wiki.list.org/DOC/Mailman%203%20installation%20experience which says: """Also, please note the first paragraph of the introduction. This is documentation of my decisions and experiences. It is not a how-to and does not replace the documentation at http://docs.list.org/""" In particular, documentation of the requirements for different databases is at <https://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html>. > Under your "*Recommended Configuration*", I have followed each step, > getting the files and editing them to suite my needs, until I got to where > you refer to: > /opt/mailman/mm/settings.py (copy of the mailman-suite settings.py file but > with DEBUG = False) > I tried to get this file using `git clone > https://gitlab.com/mailman/mailman_suite.git` and realized that > authentication is required in order to get it. Because you should be getting <https://gitlab.com/mailman/mailman-suite.git> (hyphen, not underscore) which works without authentication. Or you could just go to <https://gitlab.com/mailman/mailman-suite/blob/master/mailman-suite_project/…> and copy it from there. > What is the reason you did not include a copy like for the rest?? Because it's available on GitLab. > I have created the executables - all of them. > I have created the templates and did `find . -type f -exec sed -i.BAK 's/ > mailman3.org/mydomain.name/g' {} \;` > Maybe you should state explicitly that once one gets these templates, they > need to change the url to match theirs. You said it, but it doesn't come out > forcefully :0 I added "Of course, if you use these you need to edit the URLs for your site." > In your "MTA" section, I suppose you need to be a little more generic as > well and accommodate Exim users. > First I suggest you clearly state that one needs to edit /opt/mailman/mm/ > mailman.cf to ensure that the values under [mta] match what is required. > Maybe there is a different file to edit for MTA settings??? Again, I'm documenting MY experience, not trying to replace the official documentation. I refer to <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#postfix> because I use Postfix. That same page also has Exim documentation. > So far ..... > > Next, I will be looking into "Running Things".... which is where I believe > things will get thicker .... Perhaps when you're done you will write u your experiences with FreeBSD and Exim. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: hyperkitty failed to create a thread

by Danil Smirnov

Thank you very much for the quick fix, Mark and Abhilash! Abhilash, could you include the fix into the "latest" version of mailman-web container please? Btw I wasn't able to find a changelog of Mailman docker images anywhere and 'Releases' page in Github is quite outdated too... Is there any other place I should check? Danil вт, 12 февр. 2019 г., 4:06 Mark Sapiro <mark(a)msapiro.net>: > On 2/11/19 9:47 AM, Danil Smirnov wrote: > > > > What could be a reason of HyperKitty failing to create a thread from > > chained emails? > > > > For example, see "RECENTLY ACTIVE DISCUSSIONS" on page > > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/ > > > > "Openvpn and Network mapping" discussion displayed as five threads > instead > > of only one... > > > > Any ideas how to improve HyperKitty ability to detect threaded messages? > > > Thanks for the report. > > The MR at <https://gitlab.com/mailman/hyperkitty/merge_requests/125> > will fix this. > > -- > 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/ >

7 years, 2 months

[MM3-users] Re: Question about whitlisting a domain for specific mailing list

by Zaheer Abbas

Thanks, Mark & Odhiambo for providing options for the solution. I will try the 'postorius header filters' hacky way as it's more suitable to my requirement, however, if it didn't work as expected, then filtration through exim filter is also an acceptable option. Thanks again for the quick response. On Thu, Mar 30, 2023 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/30/23 11:07, Odhiambo Washington wrote: > > So the MTA option that doesn't involve any regex is better than no? > > Partly it's a matter of taste and possibly a matter of necessity. I.e. a > list admin can do this with header filters and may not have access to > the MTA config. > > Also, it's not clear to me that doing this in Postfix is less > complicated than understanding a regex. > > -- > 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 zaheer.psg(a)gmail.com >

3 years, 1 month

[MM3-users] Re: Errors while importing mm2 list archives

by Mark Sapiro

On 12/10/22 01:13, Odhiambo Washington wrote: > On Thu, Dec 8, 2022 at 10:41 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> In the DATABASES['default'] definition, you need to set `'OPTIONS': >> {'charset': 'utf8mb4'}` >> > > I added that: > > [database] > class: mailman.database.mysql.MySQLDatabase > url: mysql+pymysql://mailman_user:XXXXXXXXX@localhost > /mailmansuite?charset=utf8mb4&use_unicode=1 The above is for Mailman core. It doesn't affect HyperKitty. For that you need to look at the DATABASES definition in /etc/mailman3/settings.py <https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mail…> and ensure that in addition to the other settings under `default {` you have ``` 'OPTIONS': {'charset': 'utf8mb4'}, ``` ... >> You might also need to modify the tables, particularly hyperkitty_email >> with something like >> ``` >> ALTER TABLE hyperkitty_email >> DEFAULT CHARACTER SET utf8mb4, >> MODIFY subject varchar(512) >> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci, >> MODIFY content >> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; >> > > > So I removed my list, dropped the database, and proceeded as follows: > > create database mailmansuite CHARACTER SET utf8mb4 COLLATE > utf8mb4_0900_ai_ci; > ALTER TABLE hyperkitty_email DEFAULT CHARACTER SET utf8mb4; > ALTER TABLE hyperkitty_email MODIFY subject varchar(512) CHARACTER SET > utf8mb4 COLLATE utf8mb4_unicode_ci; > ALTER TABLE hyperkitty_email MODIFY content longtext CHARACTER SET utf8mb4 > COLLATE utf8mb4_unicode_ci; > ALTER TABLE hyperkitty_email MODIFY sender_name varchar(255) CHARACTER SET > utf8mb4 COLLATE utf8mb4_unicode_ci; > ALTER TABLE hyperkitty_email MODIFY in_reply_to varchar(255) CHARACTER SET > utf8mb4 COLLATE utf8mb4_unicode_ci; > > I did all those (although looks overzealous) just to be on the safe side. I > have seen people putting emojis in their names. None of that should be necessary. `mailman-web migrate` should create the database and tables as needed. > After that, I did the mailman-web migrate, created the list, imported the > config from MM2 and then proceeded to import the archives. > However, the errors still are there, and several messages were not imported Do you have the OPTIONS setting in your DATABASES definition in settings.py? ... > Warming up cache > Traceback (most recent call last): > File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> > sys.exit(execute_from_command_line()) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", > line 446, in execute_from_command_line > utility.execute() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", > line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", > line 402, in run_from_argv > self.execute(*args, **cmd_options) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", > line 448, in execute > output = self.handle(*args, **options) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_import.py", > line 411, in handle > call_command("hyperkitty_warm_up_cache", list_address) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", > line 198, in call_command > return command.execute(*args, **defaults) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", > line 448, in execute > output = self.handle(*args, **options) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_warm_up_cache.py", > line 53, in handle > self.warm_up_mlist(mlist, options) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_warm_up_cache.py", > line 61, in warm_up_mlist > for thread in mlist.recent_threads: > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", > line 162, in recent_threads > return self.cached_values["recent_threads"]() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/common.py", > line 58, in __call__ > return self.get_or_set(*args, **kwargs) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", > line 317, in get_or_set > return [Thread.objects.get(pk=pk) for pk in thread_ids] > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", > line 317, in <listcomp> > return [Thread.objects.get(pk=pk) for pk in thread_ids] > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/manager.py", > line 85, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/query.py", > line 650, in get > raise self.model.DoesNotExist( > hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does > not exist. > (venv) [mailman@gw ~/mm]$ I have no idea what would cause this in a newly created database with no archives before running hyperkitty_import. -- 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: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Mark Sapiro

On 8/27/20 5:44 PM, Simon Handfield via Mailman-users wrote: > > Traceback (most recent call last): > File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) > File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get > resource = self._make_collection(request) > File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection > for resource in collection] > File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> > for resource in collection] > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict > resource = self._make_resource(request.id) > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 78, in _make_resource > resource['msg'] = msg.as_string() > File "/usr/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/lib/python3.6/email/generator.py", line 272, in _handle_multipart > g.flatten(part, unixfrom=False, linesep=self._NL) > File "/usr/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text > msg.set_payload(payload, charset) > File "/usr/lib/python3.6/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) > > I'm sorry if this is a query that's answered already but I have not been able to find matching thread that seems to relate to my error. Sorry for not answering earlier and for not being able to devote more time to this now as I'm going away within the hour, but this looks as if the message is somehow defective. Basically, the message can't be flattened by its as_string() method because of unicode issues. This can occur because of non-ascii characters is the message headers or in body parts explicitly or implicitly declared as ascii. We have had workarounds for this for some time, but I don't think they are in 3.1.1, See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/message.…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/29/22 05:48, Jacob Sievert via Mailman-users wrote: > Hello, > > we seem to have the same problem right now. > > We are still on python3.6 and postgresql 12.9 > > I looked at our Table pendedkeyvalue and we have roughly 35k rows in > that table, > is that normal or shouldn't those get cleaned up after a while? Yes they should. This is https://gitlab.com/mailman/mailman/-/issues/257 fixed in Mailman core 3.3.5. Also in Mailman 3.3.5 is a new Task runner that runs periodic tasks, one of which is to remove orphaned pendings. This may also be the issue for the OP in this thread if that pendedkeyvalue table is also large. Here is a `mailman shell` script that will clean that up. ``` # Prior to Mailman 3.3.5, some tokens for user confirmations were pended with # too long a lifetime. This script removes those pendings based on when they # were pended and the configured pending_request_life rather than their # expiration. # Also prior to Mailman 3.3.5, pended held_message tokens for email handling # of the message were not removed when the message was handled via REST. This # script removes those pendings too. # This is run with # mailman shell -r delete_orphans_expireds # after saving it as # /opt/mailman/mm/venv/bin/delete_orphans_expireds.py from datetime import datetime from lazr.config import as_timedelta from mailman.config import config from mailman.database.transaction import transactional from mailman.interfaces.pending import IPendings from zope.component import getUtility pendings = getUtility(IPendings) def is_request(id): if config.db.store.execute( 'SELECT * FROM _request WHERE id = {};'.format(id)).rowcount > 0: return True return False then = datetime.now() - as_timedelta(config.mailman.pending_request_life) thenm = datetime.now() - as_timedelta(config.mailman.moderator_request_life) def fromisoformat(x): if hasattr(datetime, 'fromisoformat'): return datetime.fromisoformat(x) try: return datetime.strptime(x, '%Y-%m-%dT%H:%M:%S.%f') except ValueError: return datetime.strptime(x, '%Y-%m-%dT%H:%M:%S') @transactional def delete_orphans_expireds(): count = 0 for token, data in pendings.find(pend_type='held message'): if data and not is_request(data['id']): result = pendings.confirm(token, expunge=True) count += 1 print(f'expunged {count} orphaned pended held messages') count = 0 for token, data in pendings.find(pend_type='data'): if data and data['_mod_hold_date']: when = data['_mod_hold_date'] if isinstance(when, str): when = fromisoformat(when) if when < thenm: result = pendings.confirm(token, expunge=True) count += 1 print(f'expunged {count} expired held messages') pends = list(pendings.find(pend_type='subscription')) pends += list(pendings.find(pend_type='unsubscription')) count = 0 for token, values in pends: if values and values['token_owner'] == 'subscriber': when = values['when'] if isinstance(when, str): when = fromisoformat(when) if when < then: result = pendings.confirm(token, expunge=True) count += 1 print(f'expunged {count} expired (un)subscription confirmations') ``` The above says to save the script at /opt/mailman/mm/venv/bin/delete_orphans_expireds.py but that path may need to be adjusted based in where Mailman's bin/ directory is in your installation. -- 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: installing a new instance of mm3

by Christian Stalberg

mailman.log is showing this: ERROR 2021-10-18 22:19:12,385 616 django.security.DisallowedHost Invalid HTTP_HOST header: 'subdomain.domain.tld'. You may need to add 'subdomain.domain.tld' to ALLOWED_HOSTS. ERROR 2021-10-18 23:01:15,318 616 django.security.DisallowedHost Invalid HTTP_HOST header: '192.168.0.1'. You may need to add '192.168.0.1' to ALLOWED_HOSTS. Where do those entries go? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 22, 2021 11:44 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: installing a new instance of mm3 On 10/22/21 6:37 AM, Christian Stalberg via Mailman-users wrote: > Is this document that Brian Carpenter wrote still valid? > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 As Steve said, it should be. > Brian installed my instance. Now its broken. My lists are down. I'm > getting nowhere with diagnostics and troubleshooting (which was easier > with mailman 2). What's broken? Postorius, Hyperkitty, mail delivery, all of them? Do you find any clues in the logs at /opt/mailman/mm/var/logs/? Particularly mailman.log for core and mailmansuite.log for Postorius and Hyperkitty. We will try to help if we have information to help identify the problem. -- 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/

4 years, 6 months

[MM3-users] Re: Mailman3 Docker question and importing lists from MM2

by Andrew Hodgson

bin/mailman import21 I saw this in the image, do you have any idea about what may be missing from this? I may shelve this project again for the time being if we can't do the migration, but good to know I can get a production like Docker instance running relatively painlessly. Andrew. -----Original Message----- From: Mark Sapiro [mailto:mark@msapiro.net] Sent: 01 September 2017 16:43 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman3 Docker question and importing lists from MM2 On 09/01/2017 07:09 AM, Andrew Hodgson wrote: > > I had a question regarding the parameter: SERVE_FROM_DOMAIN. > > I want to use multiple domains, what is the best way to specify multiple domains in this environment variable? I don't know the answer to this. > Furthermore, is there a recommended way to get data from MM2 (list configs and archives) into MM3? There are two things. For importing list configs there is bin/mailman import21 but it is not up to date and probably doesn't work. For importing archives there is django-admin hyperkitty_import [--settings=if.needed] which works well using the MM 2.1 LISTNAME.mbox/LISTNAME.mbox file as input. -- 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 https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years, 8 months

[MM3-users] Re: Mail configuration

by Darren Smith

Mark, This is Mailman3. On Mon, Mar 26, 2018 at 1:53 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 03/23/2018 10:05 AM, Darren Smith wrote: > > > > We have been told that "warming up" the IP is the way to go - that is, > > cutting over just some of the traffic a little at a time. So what I am > > looking for is a way for all mail on our domain to be sent to our current > > mailman installation, and based on some configuration (certain mailing > > lists?) certain emails being sent out to the list subscribers will first > be > > forwarded to the new server and be sent from the new IP address. > > > > Does that make sense? > > > > Does anyone know a way that mailman/postfix can be configured to > accomplish > > this? > > > Is this Mailman 3 or Mailman 2.1? The Mailman side of this would be > different depending on which. If it's Mailman 2.1, a better list is > mailman-users(a)python.org > <https://mail.python.org/mailman/listinfo/mailman-users> > > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 1 month

Search results for query "sapiro"