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

[MM3-users] Re: config incoming email in my domain cpanel

by Mark Sapiro

On 08/03/2017 10:42 AM, Rafael Mora wrote: > > I've found the MX records on my cpanel but how do I redirect the emails > going to my list to my private server? You have to configure the MTA that is the MX for the domain to relay the mail to the Mailman server. > I still don't get it. What if I just suscribe the members and then send the > email to the suscribers the thing is that the email has to be received by > mailman in order to resend it to the list suscribers right? If all you want to do is send mail that you generate, you can use mailman inject to deliver the mail to Mailman on the local machine. The drawback of not being able to receive mail from the outside is Mailman won't receive bounce DSNs from remote servers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 4/11/19 6:40 PM, brian(a)emwd.com wrote: > > Also Kelly are you sure this is correct: > > "There are two configuration files that have a key in them that must match for Hyperhitty to authorize and be able to store archives (the paths should be as follows): > /etc/mailman3/mailman-hyperkitty.cfg (set the api_key without any quotes) > /etc/mailman3/mailman-web.py (set the ‘SECRET_KEY’ - include single quotes around the key)" > > It was the MAILMAN_ARCHIVER_KEY that I needed to make sure it was being matched by the API key in mailman-hyperkitty.cfg. I believe the SECRET_KEY setting has nothing to do with the auth errors that Hyperkitty was displaying. Yes. SECRET_KEY is used internally within Django. See <https://docs.djangoproject.com/en/2.1/ref/settings/#secret-key>. It is the MAILMAN_ARCHIVER_KEY setting that must match the api_key setting in mailman-hyperkitty.cfg (modulo quoting). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: How to configure a mailing list?

by Mark Sapiro

On 3/10/20 6:44 AM, Patrick Ben Koetter wrote: > Greetings, > > I do have mailman 3 installed via virtualenv and it is up an running. Now I'd > like to create a mailing list, but I can't find any instructions how I should > do this. > > Is there a resource online I missed? If not, can anyone on this list tell me > how to do it preferrably using a command line tool? There is a bin/mailman command in your venv. It needs to be run with a -C option pointing to your mailman.cfg. I use a wrapper like #!/bin/bash exec /opt/mailman/mm/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ Give the mailman command with no args for a list of sub-commands and ultimately mailman create --help for instructions on creating a list. See <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/commands…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/18/22 09:53, Élodie BOSSIER via Mailman-users wrote: > > Now, I need to find how to set it automatic when I will add a new list. > Perhaps I could do it with an an SQL command if there are no bash > command ? I will check with "mailman create" and the --domain argument. Part of adding a new list is specifying the domain. If it's one of the existing domains, i.e., ml.franceserv.fr, or ml.viticreation.fr, that's all that needs to be done. e.g. `mailman create newlist(a)ml.franceserv.fr`. If it's a new domain, you need to add the domain to the django_site table perhaps directly or via the django admin UI and then after `mailman create newlist(a)new.domain` you may need to edit the domain via Postorius' domains view to specify the correct Web Host. -- 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: Question about whitlisting a domain for specific mailing list

by Mark Sapiro

On 3/30/23 08:55, Zaheer Abbas wrote: > Hi All, > > I need to whitelist a domain for a specific mailing list on your platform. > Only *(a)example.com email addresses should be allowed to post messages to > this list. > > Could you please provide me with documentation or instructions on how to > achieve this? I have already searched the knowledge base and user manuals > without success. In Postorius Header filters add a filter with Header = from, pattern = ^.*(a)(?!example\.com(\W|$)) and Action as desired. That pattern will match anything in a From: header which contains an @ followed by anything other than example.com and a non-alphanumeric or the end of string. I.e., things that won't match are for example xxx(a)example.com xxx(a)example.com> xxx(a)example.com yyy Things that will match are for example xxx(a)other.domain xxx(a)example.comp -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Internal Server Error: /archives/

by Mark Sapiro

On 11/29/24 7:51 AM, Christian via Mailman-users wrote: > What is this error and how can I fix it please? Running Debian 4.19.316-1 ... > Request Method: GET > Request URL: https://lists.domedoman.ie/archives/?sort=active%22%27! ... > Traceback (most recent call last): > None ... > GET: > sort = 'active"\'!' Some remote user has requested `https://lists.domedoman.ie/archives/?sort=active"'!` The `"'!` appended to the sort=active query fragment caused the error. This sort of thing happens when bots and script kiddies crawl your web site. You can find the request in your web server logs for more information about where it came from, but the bottom line is this will happen from time to time and it's not an indication that anything is broken. It would be possible to harden HyperKitty to defend against malformed URLs like this, but without a traceback it is not clear where to do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: MTA setup

by Mark Sapiro

On 12/22/24 20:10, Arte Chambers via Mailman-users wrote: > I'm not sure how to check mailmans shunt queue. `ls var/queue/shunt` > I'm not seeing any errors in mailman logs > > There are several .pck files in Mailman's > var/archives/hyperkitty/spool/ These are message that failed to archive. There should be messages in mailman.log about these failures indicating what the issue is. > I can send email from the server using mail utilities as long as the "from > email address" contains the server's domain name. I also notice that in > this MM3-Users list the "from" email shows senders(a)emailaddress.com VIA > mailman3.org. I'm wondering if I've missed something that would allow my > server to behave this way. In the list's Settings -> DMARC Mitigations set DMARC mitigation action to Replace From: with list address and set DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: How to run this script (attached) in the mailman shell (or withlist)?

by Mark Sapiro

On 8/5/25 13:56, Wikinaut wrote: > https://dpaste.com/39ZMH3M7S (Text below) > > The code works perfectly when pasted into the live shell of mailman. > But not when I start "(venv) mailman withlist -r set_member_pref". > > ... > module = import_module(module_path) > File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1030, in _gcd_import > File "<frozen importlib._bootstrap>", line 1007, in _find_and_load > File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked > ModuleNotFoundError: No module named 'set_members_prefs' > > What is wrong? > Please can anyone help? Please see my reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > Please can you add information in the documentation how exactly to run a script like that? See `mailman shell --details` -- 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: Syncing Real Name between user account and membership

by Mark Sapiro

On 12/31/20 2:52 AM, Andreas Barth wrote: > > I think it would be useful (for others who try it) to have just these > snippets somewhere (also as examples what could be achived by mailman > shell). I'm happy to add them myself if possible, but the > wiki seems to be mailman 2 centric? > > What would be the appropriate place then? The wiki <https://wiki.list.org/> is an appropriate place. It only seems to be Mailman 2 centric because it's been around in one form or another for over 20 years and during much of that time, there was no Mailman 3 at all. There is also a new FAQ section at <https://docs.mailman3.org/en/latest/faq.html>, the source for which is at <https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/faq.rst>. Merge requests to add to that are also welcome. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Setting up on ubuntu server 22.04

by Mark Sapiro

On 10/3/23 06:00, Kyriakos Terzopoulos wrote: > > However, I cannot find the mailman/setup.py anywhere in order to patch it, > since the installation was done through pip from here: > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > Maybe I can try upgrading python from 3.10 to 3.11 and re-install Upgrading Python won't help. There is currently an incompatibility issue when following https://docs.mailman3.org/en/latest/install/virtualenv.html because that doc is based on the head of the GitLab branch, but `pip install mailman3` installs the 3.3.8 released version of core and the latest 6.1.0 version of importlib_resources and these are incompatible. There are two ways to fix this. The easy way is to downgrade importlib_resources in your venv with ``` pip install importlib_resources\<6.0 ``` The slightly more complex way is to upgrade mailman core to 3.3.9b1 from GitLab with ``` pip install -U git+https://gitlab.com/mailman/mailman.git ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

Search results for query "sapiro"