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

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 5/24/24 2:18 AM, marcus--- via Mailman-users wrote: > > The problem, however, is that it does not send out any mails, nor do they appear in the archive. > > When I look in the Mailman-Log I find: > > May 16 01:44:55 2024 (6833) Cannot connect to SMTP server localhost on port 25 This is a misleading error message. It can occur when Mailman's out runner can't read a template. You need to check ownership and permissions on mailman/templates in the code tree and Mailman's var/templates directory which probably has permissions errors from running inport21 as root. Also, if you've set any templates in Postorius, they may not be accessable if your setting for POSTORIUS_TEMPLATE_BASE_URL is not good. > May 16 01:48:15 2024 (61252) error opening connection to nntp_host: localhost > [Errno 111] Connection refused > May 16 01:48:15 2024 (61252) NNTP error for list vereinsmitglieder(a)ludothek.de: > [Errno 111] Connection refused Are you gating messages to/from usenet for this list? If so, you have to set host: and port: and maybe user: and password in the nntp section of mailman.cfg -- 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: Database permission problem?

by Mark Sapiro

On 10/15/24 15:24, Bill Oliver wrote: > > Yeah, I saw that, too. The double db files are created by postmap. I > haven't worried about it too much yet, since the permissions are the > same. I don't know why postmap does this, but it's next on my list of > things to fix. You should not be running postmap manually and never on a *.db file in any case. Mailman should be creating postfix_domains, postfix_lmtp and postfix_vmap and calling postmap on those to create the .db files. > In my main.cf postfix_lmtp is mentioned four times: > > virtual_mailbox_maps = > proxy:mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf, > > proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_mailbox_maps.cf > #added 20241009 for mailman > hash:/opt/mailman/mm/var/data/postfix_lmtp ${dovecot} > > virtual_alias_maps = > proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf, > proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf, > > proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.c > f > #added 20241009 for mailman > hash:/opt/mailman/mm/var/data/postfix_vmap > > #Mailman transport stuff > transport_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp ${dovecot} Are you adding ${dovecot} to the local_recipient_maps and virtual_mailbox_maps mailman entries or was that there before? -- 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: Outgoing messages fro Mailman fails DMARC

by Mark Sapiro

On 04/19/2018 03:22 AM, Henrik Rasmussen wrote: > > Thanks you for the links. According to https://wiki.list.org/DEV/DMARC the MM3 list setting "DMARC mitigation action" (which actually say "Replace From: with list address" in Postorius) should change the From: header. This doesn't seem to work if I don't also set "DMARC Mitigate unconditionally" to Yes, but does if I do. If DMARC Mitigate unconditionally is No, DMARC mitigation action will only be applied if the original From: domain publishes a DMARC policy of quarantine or reject. If the action is not being applied in this case, there is some issue in looking up the DMARC policy for the domain. Possibly, dnspython is not available or there is some other issue with this. In any case, errors should be logged in Mailman's log. > Where do I change defaults for all lists, instead of a per list change in settings/dmarc_mitigations ? You need to do this with list styles. See <http://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html>. At present, Postorius doesn't allow specifying a style when creating a list, so you may need to modify mailman/src/mailman/styles/base.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: Adding / manipulating users

by Mark Sapiro

On 11/18/19 6:15 AM, Seth Seeger wrote: > > My next question - I have two lists from Yahoo to import. I’ve migrated them through groups.io and have a convenient export. I now have all the data in formats I can handle. (json file for members, mbox for archives.) What’s the best way to import hundreds of users, setting their mail delivery status and moderation status at the same time? (There doesn’t seem to be a command line option for adding members anymore where you can also set their delivery status.) I’ve looked at the documentation, but couldn’t figure out what to do. You are correct that there is no existing command line tool or Postorius way to do this. If you have facility with Python, you can look at the mailman import21 command which is actually processed by mailman/utilities/importer.py. It shouldn't be too difficult to adapt the part that imports the list members to use your data and create a script to do what you want. Alternatively, you could create a script that would post the appropriate transactions to add a member and set moderation and delivery status to Mailman's REST API and use that to process your members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Hyperkitty: Error when rebuilding Index

by Mark Sapiro

On 11/26/21 4:35 AM, M4tze wrote: > Dear list members, > > if there is any Hyperkitty expert here, I have issues in Hyperkitty > (just updated Maxkings Docker images) when rebuilding the Index. > > Unfortunately, there are more than 25,000 mails and I do not know which > one is/might be broken. Does the error mean that the rebuilding process > is incomplete or does it simply skip the erroneous message? It means the process is incomplete. > Traceback (most recent call last): ... > return self._result.fetch_row(size, self._fetch_type) > UnicodeDecodeError: 'utf-8' codec can't decode byte 0xed in position > 3209: invalid continuation byte I'm not sure what's going on here. I suspect the issue is withe the `content` of some message in the hyperkitty_email table in the database. You could try a database query like ``` SELECT * FROM hyperkitty_email WHERE LEN(content) >= 3209; ``` If you're lucky, that may just return a few messages and enable you to find the problem one. Otherwise, you could try first running `mailman-web clear_index` and then run `mailman-web update_index` with --start and --end options to specify a date range and zero in on the offending message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Mailman3-web/Postorius behind Lighttpd

by Mark Sapiro

On 2/16/22 10:00, Élodie BOSSIER via Mailman-users wrote: > > I'm using Mailman 3.3.3 (Tom Sawyer) on Debian Bullseye 11.2 from > packages : When you install Debian packages, your primary support resource is Debian. ... > I can access from localhost to http://127.0.0.1:8000/ which move me > correctly to http://127.0.0.1:8000/postorius/lists/ and all seem to be > correct. > > But 127.0.0.1:8000 listen only in localhost : > #netstat -tanpu | grep 8000 > tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN > 626175/python3 Which is as it should be. > So I try to use my lighttpd as proxy as recommanded with this config : > > >> scgi.protocol = "uwsgi" >> scgi.server = ( >> "/" => (( "host" => "127.0.0.1", "port" => 8000, "check-local" => >> "disable" )), >> ) > > but it's return me a "502 Bad Gateway". I don't know anything about lighttpd, but the fact that you can access http://127.0.0.1:8000/ from localhost and that seems to work suggests that you shouldn't be using uwsgi protocol, but just a straight http proxy. See https://redmine.lighttpd.net/projects/lighttpd/wiki/HowToPythonWSGI#lighttp… and https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModProxy -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Mark Sapiro

On 1/28/23 09:39, Odhiambo Washington wrote: > Now that you have mentioned > https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v…,, > please show me how to import it, edit. Then I can submit a diff. > Alternatively, I'd love to be given access to edit that document (and the > edit can be reviewed before getting published) to make it easy to follow by > someone with zero python background. > I am willing to invest some time in improving it for laymen. There are multiple ways to proceed. The simplest is to just download https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v… (there's a download button on that page), edit that and post the edited file somewhere where we can get it to look at. The better way is more complex. That way is for you to create a personal project space at https://gitlab.com/users/sign_up and clone the mailman/mailman-suite-doc project into your personal space and edit it there and then create a merge request to merge your edits into the mailman/mailman-suite-doc project. GitLab documentation is at https://gitlab.com/help -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: configuring postfix local recipient table

by Mark Sapiro

On 4/23/25 9:25 AM, Stephen J. Turnbull wrote: > Alexander Inzinger-Zrock via Mailman-users writes: > > and then i just found out that my postfix_lmpt file was empty > > 1. What database are you using?[1] Is it running? If not, yes, that > file is going to be empty. > 2. Do you have any lists configured for your Mailman 3 instance? If > not, that file will be empty. > 3. Is Mailman running? (This probably isn't necessary, just > checking.) > 4. Is there a postfix_lmtp.db file in the same place? (Postfix will > not read the plaintext version, it must be a .db file.) If you haven't set `incoming` in the `mta` section of mailman.cfg to other than the default `mailman.mta.postfix.LMTP`, the `mailman aliases` command will at least write ``` # AUTOMATICALLY GENERATED BY MAILMAN ON {} # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. ``` to the postfix_lmtp file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Separating Lists by Domain

by Mark Sapiro

On 1/3/19 2:34 PM, Abhilash Raj wrote: > > > On Thu, Jan 3, 2019, at 2:27 PM, brian(a)emwd.com wrote: >> So who manages Postorius? Is that a whole separate application from >> Mailman 3? Is there a way we can get whoever the developer is to update >> it where we can separate lists by domain the way Hyperkitty does? Mark >> Sapiro refers to this in the following post: >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > You can file an issue at https://gitlab.com/mailman/postorius/issues Yes, filing a GitLab issue is the best way to get things on the record. It's no guarantee that things will be addressed immediately, but they are there, and merge/pull requests are always welcome. As far as your question goes, Mailman Core, Postorius and HyperKitty are separate entities and they were mostly developed by separate people/groups and some important players have either overtly or implicitly retired from the project. Not long ago I write in another context > MM3 is much more complex than MM2.1 and there's a lot that I don't fully > understand myself. > > There is a basic core engine which does all the work of > creating/managing lists and users and receiving and sending mail. It has > no web UI per se. It exposes a RESTful API on the host server. > > The web management UI is Postorius and it is based on the Django web > framework and communicates with core via the REST API. The Archiver is > HyperKitty and it is fairly independent. It is also based on the Django > web framework. Account creation and web login is via django-allauth. > > Postorius, HyperKitty and the core were all developed separately by > different people and no one understands all of it. That said, Abhilash is currently the lead developer for all of Mailman 3 and he's doing a great job. I and a few others are also involved (I'd be more involved if I didn't have Mailman 2.1 to distract me), but we are a small group and things take time. And as I said, merge/pull requests for GitLab issues are always welcome. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users]Re: Installation issues

by Mark Sapiro

On 04/19/2016 11:40 AM, Andrew Hodgson wrote: > > I have often wondered if there was a howto on how this specific mailman3.org server was built, so it gives us a production-like template to follow? Sort of, but it's not (yet) public. The process I followed is very convoluted and not what I would recommend anyone follow. Part of the issue is I started with mailman-bundler not using a venv, but bundler still installs a lot of stuff in Python 2 and Python 3 venvs. I then proceeded to install the git master branches of mailman, mailmanclient, mailman-hyperkitty, hyperkitty and postorius and their dependencies system wide and ripped out most of the venv stuff. Then there were issues because I'm running django 1.9 only and that's not compatible with django_haystack 2.4.1, so I upgraded that to 2.5.dev0 from GitHub, but that now has a compatibility issue with HyperKitty which I have worked around. As you can see this is not a clean process. If I were starting over with what I've learned, I'd probably let bundler install it all in venvs and then upgrade the venvs to the git master branches. There would still be issues, but it would be cleaner. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 4 months

Search results for query "sapiro"