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

[MM3-users] Re: The doubled entries issue

by Mark Sapiro

On 11/11/23 23:56, Lars Bjørndal wrote: > > Thank you. The script I try to run, is found here: https://gitlab.com/mailman/mailman/-/issues/657 > > I named the script fix-doubled-entries.py. When I try > > `mailman shell --run ./fix-doubled-entries.py` I get: This is not the way to run a script with `mailman shell`. See ``` mailman shell --details ``` for info. However, that script cannot be run as is by `mailman shell --run`. It can be run by invoking `mailman shell` interactively and copying and pasting it, or if your Mailman is installed in a venv it can be run with the venv active by `python ./fix-doubled-entries.py`. However, that script will not fix your issue because you don't have multiple mhonarc entries for a list. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and as it says, Tell us more about the "duplicate entries" error, and if possible copy it exactly from where you found it originally, including any traceback. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: add / remove / set moderation bit of non-members via mailman shell

by Mark Sapiro

On 2/7/24 02:37, Zaheer Abbas wrote: > > I do the above via postorius because I couldn't find a way to do this via > mailman shell. Something like ``` mark@msapiro:~$ 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(a)example.com mailing list >>> NEW_NONMEMBERS = [('First User', 'user1(a)example.com'), ... ('Second User', 'user2(a)example.com'), ... ('Third User', 'user3(a)example.com'), ... ] >>> from mailman.app.membership import add_member >>> from mailman.interfaces.subscriptions import RequestRecord >>> for display_name, email in NEW_NONMEMBERS: ... record = RequestRecord(email, ... display_name=display_name, ... delivery_mode=None, ... ) ... member = add_member(m, record, role=MemberRole.nonmember) ... member.moderation_action = Action.accept ... >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: mailman addmember/syncmember commands print undecoded UTF-8 [ADD] or [DEL] mail addresses in its messages like "[ADD] =?utf-8?q?John_=....."

by Mark Sapiro

On 8/5/25 13:12, Wikinaut wrote: > > After a new add/syncmember, that spooky entry was up again! And were any of the spooky entry email addresses in the input to that command? If so what was the exact display name for the line containing that address. If that looked normal, > Then I used mailman delmembers --fromall --no-goodbye-msg --no-admin-notify -m <this@address>: > Then after a new add/syncmember, that entry was gone and the correct entry was shown. > > That means, that somewhere some remains were stored somewhere. Possibly in an Address record. Display names are in User Records and Address records. The script you ran to delete users should have removed User records, but an Address record for the address with the odd display name may have remained. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

[MM3-users] Re: No resend after delivery bouned

by Mark Sapiro

On 1/31/22 06:47, Axel Rau wrote: > My listserver has been blocked with 550 and I received > bounce score on <list_add> has been incremented. > notifications. > After resolving the block issue, I'm now waiting for mailman to resend > the mails. > Now, after 3 hours, nothing has happened so far. And nothing will. Mailman sent the message originally and when it was done sending it, it discarded the outgoing message. The message may have been archived depending on the list's archiving settings, but that's it. No version of Mailman 2.1 or Mailman 3 has ever automatically resent bounced messages. If the failures are temporary, the MTA should keep the message queued and retry up to a limit before reporting a bounce, but that's it. The best you can do is get the messages from the archive (you can export a mbox from Hyperkitty or get the messages from Mailman's var/archives/prototype/LIST_ADDRESS/new/ directory) and manually resend them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 1/30/23 10:32, Jeremy Stanley wrote: > > I'm not having any luck finding an API or CLI which I > can use to create sites and domains rather than manually doing it in > the Django admin WebUI. Does such a thing exist, or an I going to > need to resort to directly performing database inserts (which I'd > rather avoid since it could break if the schema changes). It appears > there's a foreign key relationship involved, which could make DB > manipulation like this even more fragile. Domains can be created via Postorius or via the Mailman Core REST API that postorius uses or implicitly by the `mailman create` command when creating a list in a new domain. However, none of this can create a new site. You can do this through the Django admin site at sites/site/add/. See https://docs.djangoproject.com/en/4.1/ref/contrib/sites/ for methods you can use to do this programmatically. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

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

by Mark Sapiro

On 8/5/24 12:45, Odhiambo Washington via Mailman-users wrote: > > Yes, those are Cloudflare IPs and I don't know why 2! > All I know is that in DNS, I created an A record for the hostname and chose > the "proxy" option in the cloudflare DNS management interface. OK, I know nothing about how cloudflare proxying works, so ignoring that and assuming it's OK, ... ... > I don't know. However, those IPs you see in the Nginx logs, none belong to > me! I have two possible IPs - one domiciled in KE and another domiciled in > the US (when I use VPN). I think I've misunderstood. Is it the case that the messages you report like /opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css" failed (2: No such file or directory) ... are in the nginx log on the mailman server. If so, see https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura…. Is that what you have? If not, post your nginx configuration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Mark Sapiro

On 4/25/24 14:01, Thomas Stein wrote: > Am 2024-04-25 22:03, schrieb Mark Sapiro: >> >> I don't know how things are arranged in the Debian/Ubuntu package, but >> you may have a settings.py which at the end does something like >> ``` >> try: >> from settings_local import * >> except ImportError: >> pass >> ``` >> If that is the case, adding the above snippet to the end of >> settings_local.py should work. > > Yes, that's the case. I added the snippet in question to > settings_local.py but this leads to another error: > > File "/usr/share/mailman3-web/settings.py", line 503, in <module> > from settings_local import * > File "/usr/share/mailman3-web/settings_local.py", line 194, in <module> > x = list(MIDDLEWARE) > ^^^^^^^^^^ > NameError: name 'MIDDLEWARE' is not defined > dpkg: error processing package mailman3-web (--configure): Yes. I understand. In your case, MIDDLEWARE is only defined in settings.py and not in settings_local.py. As I understand it originally you added ``` x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` to settings.py and you say it didn't help. I don't know why that wouldn't work as long as there is no setting for MIDDLEWARE in settings_local.py and you added that after the MIDDLEWARE setting in settings.py. When you say it didn't help, do you mean you still get the django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE message or something else? I note that the original post in this thread refers to /etc/mailman3/mailman-web.py which is presumably where the package ultimately puts the Django settings, and I don't know what `dpkg --configure` is doing. One thing you could try is in settings_local.py, put ``` from settings import MIDDLEWARE x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` to work around the NameError. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: RHEL 7 + Mailman 3 : Need help and guidance

by Mark Sapiro

On 7/15/19 8:27 AM, vgandhi(a)fdu.edu wrote: > Thank you so much for the guidance. We ended up installing version 2.1.15 on RHEL7 using yum. We don't want mailing lists' email addresses with the same domain as the server has. For example: server is example1.fdu.edu . We would like to have email addresses of the mailing lists to end with @fdu.edu so that someone sends email to list1(a)fdu.edu and the subscribers of the the mailing list list1 will receive it. Can you please provide us some guidance on how can we accomplish this? This is not the list for Mailman 2.1 questions. Please join the mailman-users(a)python.org list at <https://mail.python.org/mailman/listinfo/mailman-users> and post your request there. Also note that while the RHEL7 package for Mailman may be 2.1.15, that version is 7 years old and the current release is 2.1.29. You may wish to install from source - <https://www.list.org/mailman-install/>. -- 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: Running mailman3 on AWS and dealing with SES email verification

by Mark Sapiro

On 5/1/20 6:54 AM, Mohsen Masoudfar wrote: > Thank you Mark, this is really very helpful. I am going to work on the details. It would be breat, if there were a way to set some of this options as default, like DMARC mitigation is default to no, I changed it to unconditionally and replace From to with list address and got good results, but the default is no. How may I changed the default, do that the list owner/creator does not need to update these fields. There are two ways to do this. Both require some code modification. The simplest is just to change the lines at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py…> to: mlist.dmarc_mitigate_action = DMARCMitigateAction.munge_from mlist.dmarc_mitigate_unconditionally = True The other way is to create a new list style that has these settings and chose it when creating a list. See <https://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: spanish localization

by Mark Sapiro

On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > I contributed in january to translate to spanish all the items left in > Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I > thought they will be used in the next upgrade, but I cannot see any > improvement and there are many words untranslated. The Spanish translations for Mailman core and HyperKitty are currently completely up to date with weblate. django-mailman3 differs in one string that was translated on Feb 10 and hasn't yet been merged. Postorius also differs in a few places from the Feb 10 version that hasn't yet been merged. Other than that, the translations should be good. > Is there any way to upgrade the .po files in order to get the last > translation? For the web UI you need to run the django management `compilemessages` command. For Mailman core you need to run ``` cd mailman/messages/es/LC_MESSAGES msgfmt -o mailman.mo mailman.po ``` to compile the mailman.po file for gettext. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Search results for query "sapiro"