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

[MM3-users] Re: Default moderation for new members

by Mark Sapiro

On 11/14/19 7:37 AM, Seth Seeger wrote: > > I’m loving Mailman3 so far! Great work on it. Thank you. > I’d like to have new members who join my lists have their posting ability set to moderated. (After their first legitimate post, they would set to be unmoderated.) I haven’t been able to find this, though I’m suspecting the language has changed. In Postorius set Settings -> Message Acceptance -> "Default action to take when a member posts to the list" to Hold for moderation. This is the action which will be taken for a post from a member whose individual Moderation is List Default as it is for all new members. Then when a post from that member is held, if you click the subject in the held messages view, a dialog opens showing the message content with Accept, Reject and Discard buttons and a dropdown list you can use to set that member's Moderation to Default processing. Default processing is generally what you want as it bypasses the moderation hold but still applies other tests such as header filters, administrivia, implicit-dest, max-recipients, max-size, etc. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/22/21 8:51 AM, Marco Marinello wrote: > Hi everybody, > > as per subject, I'm getting this error in the hyperkitty log when mailman daemon tries to archive a mail. > I've setup the hyperkitty.cfg file with api_key = MAILMAN_ARCHIVER_KEY in settings_local.py but still nothing. > I've seen here and in GitLab issues some errors concerning a wrong api key but here it says that it wasn't sent at all. > All packages installed via pip install + latest .zip release, including mailman-hyperkitty. Currently running on apache with mod_wsgi_py3 without https. The following combinations should work: mailman-hyperkitty 1.2.0 with HyperKitty 1.3.5 mailman-hyperkitty <1.2.0 with HyperKitty <1.3.5 The following will not work: mailman-hyperkitty 1.2.0 with HyperKitty <1.3.5 mailman-hyperkitty <1.2.0 with HyperKitty 1.3.5 Do you see a message like 'The MAILMAN_ARCHIVER_KEY is now required to be sent over the Authorization HTTP header, you need to upgrade the mailman-hyperkitty package to 1.2.0 or newer.' In your Django log and/or your mailman.log? These will only be logged with HyperKitty 1.3.5 and mailman-hyperkitty < 1.2.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Problems getting MM3 to work

by Mark Sapiro

On 4/24/23 4:53 PM, Mark London wrote: > > Mark - I encountered the same problem and it wasn't clear from the > documentation what to do about it. > > So I eventually changed the name from example.com using the /admin link. > > But if I now set SITE_ID = 0, and restart the server, it is not happy > and tells me it encountered an error. > > raise > self.model.DoesNotExist(django.contrib.sites.models.Site.DoesNotExist: > Site matching query does not exist. I'm not sure about this. It may only work if there is more than one site. On the other hand, it requires that the requesting domain match a site. I.e., I think if the site's domain is example.com, but the request is from www.example.com, that could cause it to fail. Also, if proxying to a wsgi server, the web server has to pass the host. I.e., for nginx, proxy_set_header Host $host and for Apache ProxyPreserveHost On > I guess I should just let it be set to 1 and be done with it? - Mark Yes, I think so. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Congrats on the instructions for installation on ubuntu, what about migration?

by Mark Sapiro

On 10/8/24 5:45 PM, Bill Oliver wrote: > > Is there a tutorial/instructions on migrating data from an old system > to a new one? It's actually not the end of the world if I don't get > all the old emails transferred, but I'd like to get the email addresses > of the participants moved over easily... I believe that I set it up > in 2020, but did not do any version upgrades since then... There's no explicit doc, but there are some posts in the archives of this list, e.g. <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. The easiest scenario is if you want to migrate everything. You just dump the database on the old server and load it on the new one using the database manager's tools. If you only want to move some, but not all lists, it's more complicated, but possibly the easiest thing is to migrate everything and then delete the unwanted lists and their archives from Postorius and HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: confirm mail rejected

by Mark Sapiro

On 10/02/2017 05:21 AM, Marc Sluiter wrote: > > In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp. > Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps? I think so. See the note I just added at <https://gitlab.com/mailman/mailman/issues/401#note_42163915>. > For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/ > > Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)? > Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?) I'll be working on a fix. My inclination is to change all the regexp -confirm and -bounces table entries from, e.g., /^list-bounces(a)example\.com$/ to /^list-bounces(+.*)?(a)example\.com$/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Dealing with hyperkitty spool files (was Re: Re: Fwd: [Django] ...)

by Mark Sapiro

On 3/2/21 11:33 PM, David Partain via Mailman-users wrote: > > In this regard, I have three questions: > > 1. Am I correct in assuming that I can just use my favorite editor (vi) > to remove the offending characters from the file? No. The file is a Python pickle and you can't edit it. You would need to get the message and the metadata from the pickle (you could at least view it with the `mailman qfile` command), edit the message and then re-pickle the message and metadata. > 2. If I cannot find the offending character, is it safe to just remove > the file so that subsequent archiving can proceed? Yes. > 3. Can I do something to make hyperkitty go through the spool? I don't know what you mean. Every time there is a new post to any list, Mailman core invokes the mailman_hyperkitty process to archive the message and the forst thing that process does is attempt to reprocess all the messages in the spool which fails because of the utf8mb4 issue. -- 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: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 10/7/24 11:23, jkoral(a)luc.edu wrote: > HI Mark, I was off for a couple days. I have a feeling postfix is misconfigured because I see that port 25 is open. The server is not receiving mail at all. Are there any tips for things I can check. The logs are not showing much because the mail doesn't seem to reach it. According to Oct 2 22:26:59 listservls01 postfix/smtp[139911]: B1FD27ED: to=<test(a)listservnew.example.com>, orig_to=<olivertest(a)lists.luc.edu>, relay=listservnew.example.com[x.x.x.x]:25, delay=0.01, delays=0/0/0.01/0, dsn=4.4.2, status=deferred (lost connection with listservnew.example.com[x.x.x.x] while receiving the initial server greeting) The old server is attempting to send mail to the new server. Are there any `postfix/smtpd` messages in the mail.log on the new server. If so, they may help. If not, the port 25 connect is not reaching Postfix and the new server is disconnecting before connecting to Postfix. Is Postfix listening on port 25? Does `sudo netstat -lntp` show Postfix `master` process listening on port 25? If not check /etc/postfix/master.cf. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Broken paths

by Mark Sapiro

On 07/13/2016 12:30 PM, Jean-Luc Wasmer wrote: > > I followed the instructions on: https://gitlab.com/mailman/mailman-bundler/ > I didn't have Python 3.4 installed at all... had to install it to > complete Mailman's installation. So you should have two virtualenvs, a Python 2 virtualenv at /opt/mailman/mailman-bundler/venv and a Python 3 virtualenv at /opt/mailman/mailman-bundler/venv-3.4 (I'm pretty sure bundler won't install with Python 3.5). >>> - shell scripts expect bash to be at /bin/bash (mine is at >>> - /usr/local/bin/bash) >> >> Which shell scripts? Mailman itself doesn't ship any shell scripts, >> so again, >> I'm guessing you're talking about the ones in your vent? > > I'm referring to: > ./bin/mailman-post-update > ./bin/mailman-web-django-admin createsuperuser Those scripts are created by bundler you should be activating the Python 2 venv before running them. I.e., source ./venv/bin/activate I'm not sure this will help. It looks like bundler has #!/bin/bash hard-coded in the templates for these scripts. You might file an issue on this at <https://gitlab.com/mailman/mailman-bundler/issues>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

[MM3-users] Re: Mail going to Held Messaging even the moderation is set to Accept Immediately

by Mark Sapiro

On 7/21/20 8:09 AM, Shashikanth Komandoor wrote: > > As per my understanding on Mailman 3, if the moderation attribute is > set to "Accept immediately (bypass all other rules)" then without checking > any rules, it should be delivered to the recipients of the list > irrespective of the message or body of the message but is there any such > checking if the body content or subject or any thing else is checked even > if the moderation bit is set to "Accept immediately". Member moderation Accept Immediately does not bypass ALL rules. It only bypasses those rules after member-moderation. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/builtin…>. However, I don't think that's the issue here. I think the issue is the poster is both an owner and a member. There is an issue in Postorius such that in cases like this, setting the member's moderation action actually sets that of the owner which has no effect on posting. See <https://gitlab.com/mailman/mailman/-/issues/659> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: spanish localization

by Mark Sapiro

On 2/13/21 4:08 PM, Victoriano Giralt wrote: > > Mark, please, how do you check when translations happened? Nov 7th is a > very significant date for me (it is my wedding anniversary) and I'm 90% > sure that I dedicated time to Weblate after that date... With respect to Mailman core, all I'm doing is downloading the .po for Spanish and comparing it to mailman/messages/es/LC_MESSAGES/mailman.po from the Mailman core 3.3.3 package on PyPI and they are identical. If there are translated strings on weblate that are different from that, they don't show up in the downloaded <https://hosted.weblate.org/download/gnu-mailman/mailman/es/>. > All strings related to Mailman (core, django_mailman3, postorius and > hyperkitty) are translated into Spanish 100%, but the interfaces, after > updating to the latest releases, are still in Englanish (more English than > Spanish). > > This is not a fight, we want to help, but do not know how. And I too want to help. It would be a help to me if you can give me examples of specific strings whose weblate translation differs from what's in the distributed .po files. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Search results for query "sapiro"