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

[Test] Re: What now -reply from web

by Mark Sapiro

On 03/20/2016 07:22 PM, mailman(a)mailman3.org wrote: > The last post with SSL = True and latest core still hits the same > underlying exception both in trying to get the archive URL and in > trying to archive the message. The core now handles these exceptions > and continues so the message goes to the list, but isn't archived and > has no archive headers. > > This is a post from hyperkitty which will probably be handled the > same, so we have to go back to SSL = False until we can fix the > certificate issue. Yes. Bottom line. With USE_SSL = True, core connects to hyperkitty via SSL to 127.0.0.1 and the certificates I installed don't include 127.0.0.1 in their domains, so urllib3 or requests (depending on where we're coming from) throws SSLError: hostname '127.0.0.1' doesn't match either of 'lists.mailman3.org', 'mirror.list.org', 'mirror.mailman3.org'. The core now handles the exceptions and the message is ultimately delivered but not archived. regardless of where it originated. We're back to USE_SSL = False now so this post should be archived, albeit the archive URLs will have 127.0.0.1 ast the host and not lists.mailman3.org. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 11 months

[MM3-users] Re: WEB UI fail to reply and create new thread

by Mark Sapiro

On 12/19/20 3:02 AM, Carlo Landmeter wrote: > We are not running in debug mode, we simply set the loggers to log DEBUG or else we don't see much info. > I also doubt the shown error is the problem as I see more template errors. > I have also tried to run the official docker images mailman-docker but im having the same issue. > > When I post via the online form, i can see uwsgi requests with http status 200 from the ajax call, so i would expect it to work, but it does not leave a message in hyperkitty nor sends an email. > > PS emails are send just fine via smtp posting. The error reported from hyperkitty/ajax/temp_message.html in the OP has nothing to do with the replies not being sent or archived. hyperkitty/templates/hyperkitty/ajax/temp_message.html is called to build the HTML response sent to the web browser after the reply has been sent to Mailman core. Abhilash's fix at <https://gitlab.com/mailman/hyperkitty/-/merge_requests/299> will get rid of that error, but I would be very surprised if it fixes the problem. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Mixing Mailman 3 with AWS SES

by Mark Sapiro

On 3/24/21 7:58 AM, Brian Carpenter wrote: > On 3/24/21 9:54 AM, Ralph Weber wrote: >> Comments received directly from one of the people who developed the >> AWS Marketplace kits for Mailman 3 and Mailman 4 have definitively >> established that AWS Mailman is *not* intended to interact with AWS >> SES when receiving email messages > > I don't think there is a Mailman 4 and the person who is marketing his > services under that name is sending a confusing message to the public. Danil Smirnov owns both the mailman3.com and mailman4.com domains. Mailman 4 is apparently his branding of "Mailman 3 in AWS Marketplace". In response to our request, the following is included at the bottom of <https://mailman3.com/>: Mailman3.com (this site) is unaffiliated with Mailman3.org, the domain used to coordinate development of the Mailman 3 free software suite. The Mailman 3 core developers are not involved with Mailman3.com, and cannot answer any questions or provide any support related to its operations. If you are looking for resources for development of the Mailman 3 free software suite, please see mailman3.org. Yes, this is all ripe for confusion ... -- 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: Upgrading mailman 3 venv installation

by Mark Sapiro

On 9/29/21 10:52 AM, Morris Jones wrote: > > In my virtual environment, I ran `pip list -o` and got a significant > list. I noticed that all of the mailman packages seemed to be "Type > sdist" and the framework packages "Type wheel". (Dunno what "Type" means > in this context.) Type is the package type. sdist is a source distribution. wheel is a form of binary distribution. Older forms are egg and bdist. > So I tried `pip list -o | grep sdist` and got a smaller list: > > (venv) mailman@mail:~$ pip list -o | grep sdist > atpublic 2.1.1 2.3 sdist > django-allauth 0.43.0 0.45.0 sdist > django-mailman3 1.3.4 1.3.7 sdist > flufl.i18n 3.1.3 3.2 sdist > flufl.lock 5.0.3 6.0 sdist > HyperKitty 1.3.3 1.3.4 sdist > lazr.config 2.2.2 2.2.3 sdist > mailman 3.3.2 3.3.5 sdist > mailmanclient 3.3.1 3.3.3 sdist > mysqlclient 2.0.1 2.0.3 sdist > postorius 1.3.3 1.3.6 sdist > > Is this a reasonable list of the packages that I should update? Several of those are dependencies. The packages you should upgrade are mailman, postorius, hyperkitty, django-mailman3 and mailmanclient. Dependencies will be upgraded as required. If a dependency is not upgraded, the older version should work. -- 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

[MM3-users] Re: Multiple server replicas

by Mark Sapiro

On 5/23/23 19:33, Dave Hall via Mailman-users wrote: > > With Mailman 3 we would like to keep the same kind of setup. However, > things have changed quite a bit. Having both mailman and mailman-web > instances all share their respective MySql/MariaDB databases is the easy > part. For /var/lib/mailman3 it is a little less clear. So far I have > symlinked messages, archives, lists, data, and templates onto the NFS > share. I'm wondering about cache, locks, queue, and web/fulltext_index. cache is used to store the contents of templates which are retrieved by URI other than mailman:// URIs. I.e. mailman:// URIs refer to templates in the templates directory or in the Mailman installation itself so are cheap to retrieve. Other URIs can refer to possibly remote servers and may be expensive to retrieve so the contents are cached. In short, this should be shared. locks contains the master lock and others locking things used by this instance. This should not be shared. queue is the queues for this instance and should not be shared. In your installation, web/fulltext_index is the search index for whoosh which is apparently the hyperkitty configured search engine. This should be shared. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[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

1 year, 9 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, 4 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

7 years, 10 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, 3 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, 3 months

Search results for query "sapiro"