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

[MM3-users] Re: clone a list?

by Dave McGuire

On 1/17/22 4:16 PM, Mark Sapiro wrote: >> Hi folks. Is there a way to clone or duplicate a list in MM3, i.e. >> create a list with a different name but other settings etc being >> identical? > > The short answer is not yet. > > Would you also want to clone the list membership? If not, you could > possibly do something directly with the database mailinglist table by > adding a new row with all the column values other than id, list_name and > list_id equal to those of the existing list. No, different membership. No problem, I'm just being lazy about it; I'll just duplicate it and copy the settings over manually. I only have two clones to make so it's really not a big deal. Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years, 7 months

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

by Stanisław Findeisen

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. 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). What about this list (mailman-users). It looks this one also has From address replacement + conditional DMARC mitigation. And remove_dkim_headers: no. Correct? Thank you

4 years, 5 months

[MM3-users] Re: Hyperkitty list overview error: thread matching query does not exist

by Ken Alker

Mark Sapiro wrote: > On 6/28/23 10:17 PM, Ken Alker wrote: > > Tthere is now an implication that my daily recent_threads_cache job must not have been running, true? Is there some way to check to see if the jobs are running? I did a "crontab -l" and the cron jobs that appear are identical to what was suggested at https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=period.... > > grep 'CRON.*runjobs' /var/log/syslog > > will tell you if cron is running the various runjobs commands. It is running every morning. Is it at all possible that running it manually did something that running it from CRON would not? I'm not sure why this solved the problem when the CRON job has been running every day.

3 years, 1 month

[MM3-users] Re: [Mailman-Users] MM3 startup issues

by Mark Sapiro

Restoring original Subject:, and doesn't this thread belong on mailman-users(a)msailman3.org - CCing there. On 1/5/20 11:51 PM, Allan Hansen wrote: > > Thanks again, Mark! > My responses below. > >> On 1/4/20 5:47 PM, Allan Hansen wrote: >>> >>> a. The server was set up with the wrong domain name (our fault), so I had to add the ‘correct’ one. I had seen the command ‘Add Domain’ in >>> the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? >> >> >> What are the setytings in Postorius -> Settings -> Archiving? > > Archive policy: Private archives > Archive archivers: hyperkitty, prototype Are the messages in Mailman's var/archives/prototype/LIST@DOMAIN/new directory? Are there messages in Mailman's var/archives/hyperkitty/spool/ directory? What's the setting for base_url in mailman-hyperkitty.cfg? Are there any errors in var/logs/mailman.log? >>> b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That’s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. >> >> >> Set >> >> FILTER_VHOST = True >> >> in settings_local.py >> > > Yes, Brian told me to do the same. This is the what I wrote back: > > hansen@rccrmail:/opt/mailman/mm$ sudo vi settings.py > > Edited the setting to: > # Only display mailing-lists from the same virtual host as the webserver > FILTER_VHOST = True You shouldn't edit settings.py. You should override the setting by putting it in settings_local.py. > Then Brian told me to restart qcluster: > hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster qcluster is not what you need to restart. You need to restart whatever is supporting the wsgi interface to Django. This may be uwsgi or gunicorn or ??. Whatever it is, that's what needs to be restarted. > I then logged in, but the same lists are showing. It either takes the system a long time to reset or it has ignored the > setting. > Just tried it again, and the lists are all showing. Do I need to manually recompile the file? > >> >>> c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: >>> >>> Something went wrong >>> Mailman REST API not available. Please start Mailman core. >> >> >> Postorius is unable to access core's REST API. Is Mailman running? > > Well, I was able to post to the lists, so I assume it is. Listing at processes, I see a bunch of postgres, python3, nginx, django-adminp but > nothing explicitly with a ‘mailman’ string. If you do `ps ax|grep runner=`, what do you see? If you don't see at least three processes with `--runner=rest:0:1`, stop Mailman and start Mailman. >> If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's >> called - defined as `filename` in the `file` handler in the LOGGING >> definition in settings(_local).py. > > hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log > return Site.objects.get_current(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 60, in get_current > return self._get_site_by_request(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 45, in _get_site_by_request > SITE_CACHE[domain] = self.get(domain__iexact=domain) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", line 408, in get > self.model._meta.object_name > django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. This is because of the domain change. In settings(_local).py you have a setting for SITE_ID. Possibly, setting that in settings_local.py to a value one greater that the current setting will do. To be certain of the correct value, you need to look at the django_site table in mailman's database. That table has 3 columns, id, domain and name. The id for the row of your domain is what needs to be set as SITE_ID. > [ABH] At this point I click to accept a subsription request: > > ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not available > Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen > chunked=chunked, > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 416, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse > response.begin() > File "/usr/lib/python3.7/http/client.py", line 296, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.7/http/client.py", line 265, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without response > > So yes, the REST API is not there. How can I get it going? Stop Mailman and then start it. > Before we added the new domain, I was able to accept subscription requests to the previous domain’s lists. No more. > > Yours, > > Allan -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Mailman 3.2.0 Hyperkitty fulltext index error

by Marvin Gülker

Hi, Am 12. Juli 2018 um 08:14 Uhr -0700 schrieb Mark Sapiro: > This is due the the change from Python 2.7 to Python 3. The existing > search index is not compatible with Python 3 whoosh. Ah, I see. > I fixed this by deleting all the files in the index directory which is > defined as PATH in HAYSTACK_CONNECTIONS in your settings and running > 'django_admin update_index', but just running 'django_admin > rebuild_index' should do it. I simply followed your first suggestion, and it worked. I deleted all files in the index directory (which was "fulltext_index" in the "mailman-suite_project" directory, as we use https://gitlab.com/mailman/mailman-suite/tree/master/mailman-suite_project) and then ran update_index. That took a while, but succeeded. Since then the errors are gone. Thank you! Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

8 years, 1 month

[MM3-users] Re: Gmail emails bouncing - anybody seen this problem?

by worik

On 14/02/19 1:08 PM, Mark Sapiro wrote: > Presumably this is list mail so your list copy should be the same except > for the few headers related to delivery from Mailman to you. Nope. I cannot send *any* emails to a gmail address. So it is the first "Welcome to the list" email. As far as I can tell there is no solution to the problem, which is why I ask is any one else having this problem? Am I incredibly unlucky or is this a known problem? I have a SPF record. I have tried a new VPS on a different IP address. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

7 years, 6 months

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On May 5, 2020, at 4:01 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > As to the patch not working, there is a different patch at > <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…> > which may work. > > There is one issue with this patch. Namely it calls force_str() in the > section > >> + # https://trac.xapian.org/wiki/FAQ/UniqueIds#Workingroundthetermlengthlimit >> + # Working round the term length limit >> + word = force_str(word) >> + word_length = len(word) > > > but xapian_backend.py imports force_text > <https://github.com/notanumber/xapian-haystack/blob/master/xapian_backend.py…>. > They are actually synonymous > <https://docs.djangoproject.com/en/3.0/ref/utils/#module-django.utils.encodi…>, > but just appliing the patch without changinf force_str to force_text > won't work. The second patch did not work either. Ahh, well. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years, 3 months

[MM3-users] Re: mailman3 OWNERS_CAN_ENABLE_PERSONALIZATION option

by Henry S

Thanks Mark. That's exactly what I am looking for. On 3/12/2020 1:09 pm, Mark Sapiro wrote: > On 12/2/20 5:42 PM, Henry S via Mailman-users wrote: >> I am trying to change email "To" field to user's email instead of >> mailing list's email. e.g. "To: <user(a)gmail.com>" instead of "To: >> <mailman-users(a)mailman3.org>" > > In Postorius set Settings -> Alter Messages -> Personalize to Full. > > >> I looked around old mailman configs they mentioned about adding >> >> OWNERS_CAN_ENABLE_PERSONALIZATION option in mm_cfg.py >> >> is this feature still available in mailman3 ? Can I do it via Postorius >> or REST API? > > There is no setting in Mailman 3 to control the ability to set > personalization. It is always available. > >

5 years, 8 months

[MM3-users] Mailman 3 Installation Packaging

by ddw David Wilson

Salutations; I understand that work is in progress to provide a convenient installation tool to facilitate getting the suite of requisite programs installed and working harmoniously with a minimum of hassle? I assume that involves some combination of containers and/or virtual environments to insulate and isolate issues and facilitate portability. In addition, it would entail Mailman 3, Hyperkitty, Posterius and also Django, etc. The database selection of PostgreSQL or other. Other optionals to be configured would be the email utilities such as Postfix, etc Personally, my server of choice would run Centos. I gather Mark Sapiro was working on this as well? *Is there sufficient progress to warrant believing that such a capability might exist in the 2016 August - September time frame as was suggested some time back? Or are there any revised time-frames? Or an approximate estimated road-map?* Best regards. Dave Wilson

9 years, 11 months

[MM3-users] Re: Imported Digest Settings

by Brian Carpenter

On 2/16/21 5:21 PM, Mark Sapiro wrote: > Depends what the issue is. The two most obvious approaches are upgrade > to Mailman 3.3.3 if you aren't already there and switch from plain to > MIME digests, but I would really like to see the full raw source of this > digest messages to try to see if there is some other issue. > > >> What I did: I had the client change the list member's digest setting >> from plain-text to mime. Was that the right instruction to do? > It will probably help, but if this is Mailman 3.3.3, there's still a bug > somewhere that needs to be diagnosed and fixed. Hi Mark, The beginning of my OP stated I was using Mailman 3.3.3. Remember to use your reading glasses old man! -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 6 months

Search results for query "sapiro"