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

[MM3-users] Re: Documentation for transferiering a list between mm3 and mm3

by Johannes Winter

Am Fri, 26 Feb 2021 11:21:25 -0800 schrieb Mark Sapiro <mark(a)msapiro.net>: > On 2/26/21 11:03 AM, Morris Jones wrote: > > On 2/26/2021 10:55 AM, Mark Sapiro wrote: > > > Would it be unreasonable to do a database dump on the old instance > > and a restore on the new one? > > > The question is transferring a `list`. I took that to mean > transferring one of multiple lists to another installation which may > also have other lists. Yes, indeed, that was the question. Thank you for the answers!

4 years, 6 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by Mark Sapiro

I just tested this with the heads of the GitLab branches for Postorius and Mailman core, and I don't see this issue. I did see an issue in that if the footer template did not end with a newline, the footer wasn't added, but I didn't see any looping behavior. With a Postorius template, what do you get from ``` curl -o - https://example.com/postorius/api/templates/list/listname.example.com/list:… ```

4 years, 6 months

[MM3-users] Re: postfix malformed address with confirm replies

by Mark Sapiro

Just to complete this thread, the GitLab issue is https://gitlab.com/mailman/mailman/-/issues/836. The issue is fixed in aiosmtpd 1.4.1 and the solution for Mailman is to upgrade aiosmtpd to 1.4.1 or later.

4 years, 6 months

[MM3-users] Re: [EXTERNAL] [Mailman-Users] Re: Help with 'The message has no valid senders'

by Mark Sapiro

It turns out that there were two bugs involved: https://gitlab.com/mailman/mailman/-/issues/903 and https://gitlab.com/mailman/mailman/-/issues/904, both now fixed for the next release of Mailman 3.

4 years, 3 months

[MM3-users] Re: New messages not being archived

by Mark Sapiro

Sarah H wrote: > The site is behind a proxy, yes. apache serves the client site redirecting 80 to 443 and serving SSL for the site then proxying to Nginx for postorius/hyperkitty at 8080. I've also tried going straight to 8080 bypassing the proxy internally using localhost or loopback to the same end result. But then Nginx then proxies to Django (via uWsgi or Gunicorn or ?) at probably port 8000. Have you tried setting base_url to `http://127.0.0.1:8000/hyperkitty/`?

4 years, 1 month

[MM3-users] Re: Problems with signed messages from Apple Mail

by Mark Sapiro

We have done some more investigation on this. The message defect is `InvalidMultipartContentTransferEncodingDefect()` This is caused by the presence of a Content-Transfer-Encoding: header in the headers of the multipart/signed part. This has been observed with macOS 12.0.1, Mail.app Version 15.0 (3693.20.0.1.32), and GPG Mail 6.0. We don't know if this applies to all PGP signed mail from Apple Mail 15.0 (3693.20.0.1.32) or only mail signed by GPG Mail 6.0. The issue affects more than Mailman. In my case Thunderbird won't display the message body of such messages. I have reported this to Apple, but have gotten no response so far.

3 years, 9 months

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

Actually, I misspoke. There is one more step from mailman-post-update that is important. You need to run ``` /opt/mailman/mm/bin/django-admin migrate ``` to run all the django migrations. This may also avoid the ``` django.db.utils.ProgrammingError: relation "hyperkitty_email" does not exist LINE 1: SELECT COUNT(*) AS "__count" FROM "hyperkitty_email" ``` error.

3 years, 8 months

[MM3-users] Re: Issues with international characters (replaced by ?) when mail is send as text/html

by Michal Soltys

On 22/01/12 00:59, Mark Sapiro wrote: > On 1/11/22 2:08 PM, Mark Sapiro wrote: >> >> No, this is a bug. It has to do with message decoration (adding of >> headers and footers). You can probably avoid this issue by setting the >> list's filter_content and convert_html_to_plaintext to True. I am >> looking at why this occurs and fixing it. > > > > See https://gitlab.com/mailman/mailman/-/issues/967 which I just filed. > > Thanks for looking into it, meanwhile I'll try suggested workarounds.

3 years, 8 months

[MM3-users] Re: Problems with shunted Mails

by Stephan Krinetzki

Mark Sapiro wrote: > On 4/20/22 02:00, Stephan Krinetzki wrote: > > Mark Sapiro wrote: > > You might be able to fix this with something like > > for mbr in m.regular_members.members: > > ... if mbr.address is None: > > ... mbr.address = mbr.user.preferred_address or > > member.user.addresses[0] > > ... > > commit() > > This fix didn't worked. It returned a "Index out of bounds" exception. > > Apparently these Users have no associated Addresses at all. Do you have > any idea how these Users got created/subscribed to the list? Unfortunately not. We only see the result.

3 years, 4 months

[MM3-users] Re: Social signup?

by Mark Sapiro

Duane Raymond wrote: > Wow - thanks for the redirection on where to patch it and the first-cut > code. I'll look into this in 2 weeks when I am able to focus on it. I have submitted https://gitlab.com/mailman/django-mailman3/-/merge_requests/198 for this. It is currently a draft because I'm looking for feedback on the specific wording.

2 years, 5 months

Search results for query "sapiro"