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

[MM3-users] Re: duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Mark Sapiro

On 3/24/22 01:11, Stanisław Findeisen via Mailman-users wrote: > Hi > > I am having 4 different virtual domains (FILTER_VHOST = True). However on the domain list page in Postorius: https://.../postorius/domains/ I can see only 3 different SITE_IDs: 1,1,4,3. If I recall correctly, the "3" and "4" were created manually using the Postorius Web UI, whereas the two "1"s were created using the Mailman Client: > > client.create_domain(name) > > Is this a bug? Or did I mess something up? > What significance do those SITE_IDs have? The issue is client.create_domain doesn't support setting a Web Host. Web Hosts are the sites in the django_site table and SITE_ID is the id of the table entry. See `sites` in the Django admin UI. So when you create a domain with client.create_domain it gets arbitrarily assigned to a `site` > What I also noticed is that in the Postorius Web UI: https://.../postorius/lists/ both "1" domains display the lists contained in "3", whereas both "3" and "4" display correctly their lists. Except the "3", all domains are empty at the moment (no lists) (so "4" correctly displays no lists). Not sure if this is related?... FILTER_VHOST = True is imperfect. Lists have no Web Host attribute, only a Mail Host. Thus, with FILTER_VHOST = True, we get the Mail Host from the domains that have a Web Host matching the host in the http request. If that results in only one Mail Host, we limit the display to only those lists with that Mail Host, but otherwise we don't limit by domain. In other words, FILTER_VHOST = True only works if each Mail Host domain has a unique Web Host. If you have multiple Mail Host domains with the same Web Host (SITE_ID), FILTER_VHOST won't work for that Web Host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok I'll take a look at it Thanks El mar., 25 jul. 2017 a las 16:14, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 01:43 PM, Rafael Mora wrote: > > Ok, should I install the SASL authentication daemon saslauthd and start > it? > > > Probably not. > > If you are trying to configure Postfix to send via a remote server, see > <http://www.postfix.org/SOHO_README.html#client_sasl_enable>. > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 10 months

[MM3-users] Re: Receiving 8bit-clean mail

by Mark Sapiro

On 10/17/19 3:02 PM, Alyssa Ross wrote: > A subscriber to a mailing list I administer has been sending 8bit UTF-8 > encoded mail, with no further quoted-printable / base64 / > etc. encoding. This is handled fine by my MTA and MUA, but Mailman > seems to have trouble with it. When mail is sent out from Mailman, the > « character is replaced by ??. > > Is this a bug, or is there just a configuration option or something I > need to set? I couldn't find anything in the documentation. It works for me. I created this message > From: Mark <mark(a)example.net> > To: test(a)example.net > Date: Thu, 17 Oct 2019 22:02:04 +0000 > Message-ID: <87wod39gkj.fsf(a)alyssa.is> > MIME-Version: 1.0 > Subject: [MM3-users] Receiving 8bit-clean mail > Content-Type: text/plain; charset=utf-8 > Content-Transfer-Encoding: 8bit > > A subscriber to a mailing list I administer has been sending 8bit UTF-8 > encoded mail, with no further 8bit / base64 / > etc. encoding. This is handled fine by my MTA and MUA, but Mailman > seems to have trouble with it. When mail is sent out from Mailman, the > « character is replaced by ??. > > Is this a bug, or is there just a configuration option or something I > need to set? I couldn't find anything in the documentation. > and posted it to a test list. The message was delivered and archived. The delivered message had the list footer added and was base64 encoded, but in both the delivered and archived message, the « character was intact. In what other ways does Mailman modify the message. Does it add a msg_header and/or msg_footer, if so, are they added to a simple text/plain message body or is the message more complex so they are added as separate mime parts. Does content filtering remove anything? -- 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: Recipient address rejected: User unknown in local recipient table

by Mark Sapiro

On 4/17/20 11:24 AM, Mohsen Masoudfar wrote: > [mta] ... > configuration: python:mailman.config.postfix What's in this configuration file (mailman/config/postfix.cfg)? ... > in main.cf: > local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp > transport_maps = hash:/opt/mailman/var/data/postfix_lmtp > virtual_alias_maps = hash:/opt/mailman/var/data/postfix_vmap > > Bur for some reason the postfix_lmtp.db is older than postfix_lmtp, which means it does not get updated automated, I guess. This leads me to think that your mailman/config/postfix.cfg contains transport_file_type: regex in which case all of the Mailman mappings defined in main.cf should be regexp: tables rather than hash: tables. If you had transport_file_type: hash The .db files would be generated/updated whenever the corresponding text files are generated/updated. > I restarted the whole stack and added a new list. In postfix logs I see: > Apr 17 18:20:28 mailmandev01 postfix/smtpd[31399]: error: open database /opt/mailman/var/data/postfix_domains.db: No such file or directory Where are you even referencing that? Did you forget relay_domains = hash:/path-to-mailman/var/data/postfix_domains in the above list? ... > In addition, I found out this : > > On my old mailman2 I have a setting in postfix main.cf: > alias_maps = dbm:/usr/local/mailman/data/aliases > > the file /usr/local/mailman/data/aliases says in its first line: > # This file is generated by Mailman, and is kept in sync with the > # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE > > This makes a lot of sense to me. > > The point is I am missing any similar settings on postfix on mailman3. Mailman 2.1's data/aliases and data/virtual-mailman files have been replaced by the data/postfix* files in Mailman 3. I think your whole issue is you've configured Postfix with hash: tables but Mailman is generating regexp: tables. -- 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: Disable user registration

by Mark Sapiro

On 3/20/21 1:22 PM, mailman3(a)digicrime.com wrote: > I believe that your patch was for the web front end, but that would still allow people to join by sending email to listname-join(a)example.com. We wouldn't be running any web interface anyway. I wanted to disable all methods of users joining and only rely upon an administrative process to handle who joins. It's easy to imagine a corporate use case for this, such as "all people with offices in building 43" or "all employees with dependents on health insurance" where the definition of who is on a list is maintained in an external system. We're not actually a corporation - we're a professional society with different member classes in our membership database. In any case, the decision of who belongs on a list is not made by the user. I understand these scenarios, but unless there is a high volume of spurious subscriptions, can't this be handled by setting the subscription police to include moderator approval? > In the interim I discovered another problem with DMARC failures in gmail when mail is sent through mailman3. Mail sent directly from our exim instance doesn't have this problem, so perhaps it's a problem with SRS. I won't be investigating this further, but I'm sure that SPF hard fails will be causing more problems for mailing lists in the future. SPF always fails DMARC alignment on forwarded mail, whether from a mailing list or other forwarding mechanism because even though SPF may pass, the domain is that of the forwarding server, not the original sender. While it is possible for a domain to set a DMARC policy and to rely only on SPF for validation, any domain with a DMARC policy should also be DKIM signing the mail because DKIM signatures will survive simple forwarding such as via .forward files or MTA aliases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: MM3 templates

by Mark Sapiro

On 2/15/23 23:04, Odhiambo Washington wrote: > > The last time I referred to the link, I deliberately duplicated the <LC> > folder in two locations: > [09:51 ~ ]$ ls -al /opt/mailman/mm/var/templates/site/en/ > total 48 > drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . > drwxr-xr-x 3 mailman mailman 512 Feb 14 08:53 .. > -rw------- 1 mailman mailman 615 Jan 17 13:57 domain:admin:notice:new-list.txt > -rw------- 1 mailman mailman 341 Jan 17 13:54 list:admin:action:post.txt > -rw------- 1 mailman mailman 158 Dec 17 13:32 list:member:digest:footer.txt > -rw------- 1 mailman mailman 452 Jan 17 13:54 list:member:digest:masthead.txt > -rw------- 1 mailman mailman 137 Jan 17 13:55 list:member:generic:footer.txt > -rw------- 1 mailman mailman 1219 Dec 8 15:12 list:member:regular:footer.txt > -rw------- 1 mailman mailman 944 Jan 17 15:50 list:user:action:subscribe.txt > -rw------- 1 mailman mailman 247 Jan 17 13:56 list:user:notice:post.txt > -rw------- 1 mailman mailman 802 Jan 17 13:56 list:user:notice:probe.txt > -rw------- 1 mailman mailman 639 Jan 17 13:57 list:user:notice:welcome.txt > > Yet, it is NOT being picked. So definitely something is wrong somewhere. If you have the same list:* file in both /opt/mailman/mm/var/templates/site/en/ and /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ the ones in the lists directory will take precedence for that list over the ones in the site directory. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… for a discussion of the search order. >> >> Are the other templates such as list:member:regular:footer.txt used? >> > > I do see that in posts to the list, but I believe that is perhaps only > working because the list had that footer when it was imported from MM2. A template from import21 of the kictanet(a)lists.kictanet.or.ke list will be stored in the /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ directory. -- 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

[MM3-users] Re: how to administrate mailman3 in CLI ?

by Mark Sapiro

On 9/23/23 07:40, testeur via Mailman-users wrote: > > |# mailman shell -l testlist(a)domain.tld | It looks like you are running `mailman shell` as `root`. You should always run mailman commands including starting mailman as the Mailman user, never as root. Running thing as root can create things that later can't be read by the mailman user. > ||>>> from mailman.interfaces.action import Action >>> for mbr in > m.members.members: mbr.moderation_action = Action.defer |||commit()| > > |||>>> from mailman.interfaces.action import Action |||||||>>> english = > getUtility(ILanguageManager).get('en')| >>> for mbr in > m.members.members: || mbr.preferences.acknowledge_posts = False > mbr.preferences.delivery_mode = DeliveryMode.regular > mbr.preferences.delivery_status = DeliveryStatus.enabled > mbr.preferences.hide_address = False mbr.preferences.preferred_language > = english mbr.preferences.receive_list_copy = False > mbr.preferences.receive_own_postings = True|commit()|| I'm not sure what the above actually says. The interaction should look like ``` >>> from mailman.interfaces.action import Action >>> english = getUtility(ILanguageManager).get('en') >>> for mbr in m.members.members: ... mbr.preferences.acknowledge_posts = False ... mbr.preferences.delivery_mode = DeliveryMode.regular ... mbr.preferences.delivery_status = DeliveryStatus.enabled ... mbr.preferences.hide_address = False ... mbr.preferences.preferred_language = english ... mbr.preferences.receive_list_copy = False ... mbr.preferences.receive_own_postings = True ... >>> commit() ``` Actually, importing Action is not necessary as it is among the things defined by default in `mailman shell` in interactive mode. > Before the shell command, the web interface was with an other language > (i tested with italian one) and other options preferences, but after the > shell command, after a web interface refresh, it doesn't change. The above shell interaction sets the preferred_language for all list members to english. This has nothing to do with the language for the web UI. This is set by Django. See <https://docs.djangoproject.com/en/4.2/topics/i18n/translation/#how-django-d…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: rest api runner not running

by Mark Sapiro

On 3/27/21 5:13 AM, Christine wrote: > Hi, > I have been using mailman for about ten years, now I want to move the > lists to another server, I have installed mailman3 there, most of it > seems to be running, but the "rest api runner" is not. Nothing is > listening on port 8001. What have I missed? What do I do to start the > restapi runner? I checked the logs, I don't see anything suspicious. > > this is what systemctl status says: > > root@lists:~# systemctl status mailman3 > ● mailman3.service - Mailman3 server > Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; > vendor preset: enabled) > Active: failed (Result: timeout) since Sat 2021-03-27 12:04:06 UTC; > 6min ago > Docs: man:mailman(1) > https://mailman.readthedocs.io/ > Process: 173111 ExecStart=/usr/bin/mailman -C > /etc/mailman3/mailman.cfg start --force (code=killed, signal=TERM) > > Mar 27 12:02:36 lists systemd[1]: Starting Mailman3 server... > Mar 27 12:04:06 lists systemd[1]: mailman3.service: start operation > timed out. Terminating. > Mar 27 12:04:06 lists systemd[1]: mailman3.service: Failed with result > 'timeout'. > Mar 27 12:04:06 lists systemd[1]: Failed to start Mailman3 server. Nothing is listening on port 8001 because apparently Mailman core failed to start. > There is nothing in mailman.log, nor in smtp.log What Mailman package is installed? Perhaps you should contact the packager for support. Can you run the mailman command manually, e.g. ``` sudo -u xxx mailman -C /etc/mailman3/mailman.cfg ``` where `xxx` is the Mailman user which if I'm guessing correctly that this is a debian/ubuntu package, is `list`. Otherwise it might be `mailman`. That should just produce a list of `mailman` subcommands. If that works, try ``` sudo -u xxx mailman -C /etc/mailman3/mailman.cfg info ``` and ``` sudo -u xxx mailman -C /etc/mailman3/mailman.cfg start ``` and see what they produce. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: changeaddress command and nonmembers

by Mark Sapiro

On 2/2/23 09:28, Mike Wertheim wrote: > > Now that we're on Mailman 3 and the email list was migrated from MM2 to > MM3, we see that newaddress(a)gmail.com is a Member of the list, and we see > that oldaddress(a)hotmail.com is a NonMember of the list. That all makes > sense. > > But now, this person has decided that they actually want to go back to > using the old address. > > So I ran the command "mailman changeaddress newaddress(a)gmail.com > oldaddress(a)hotmail.com". But that gave me this output: > > Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS > Try 'mailman changeaddress -h' for help. > > Error: Address oldaddress(a)hotmail.com already exists; can't change. > > > Can anyone explain how I can do what I'm trying to accomplish? The user needs to create an account in the web UI for newaddress(a)gmail.com and once that is done and she is logged in, she can add oldaddress(a)hotmail.com to her account. There are alternatives that you as list owner can do such as mass subscribing oldaddress(a)hotmail.com to the list and then disabling delivery to newaddress(a)gmail.com. There are also things you can do in `mailman shell` such as ``` $ mailman shell -l list.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.example.com mailing list >>> mbr = m.nonmembers.get_member('oldaddress(a)hotmail.com') >>> mbr.role = MemberRole.member >>> commit() ``` > (Also, why is this error displaying the usage message? That seems odd, > since the number and type of arguments was correct.) That's the way the `mailman` command works. All errors start with the usage. -- 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

[MM3-users] Re: CSS Hyperkitty ERROR

by Johan Alsina

Mark Sapiro wrote: > On 3/18/25 3:39 PM, Johan Alsina via Mailman-users wrote: > > Like i said before, i think the problem comes with the css files in /static/CACHE.. because the ones that are in /static/hyperkitty are loading ok.. > > See this thread: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/7... > Some of that may be useful. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Hi Mark, i configured the paths to load all the files from /staticfiles/ but for some reason the .css files are loading but not showing again and i dont know why... https://freeimage.host/i/3ovaZgf https://freeimage.host/i/3ovaQ0G

3 months

Search results for query "sapiro"