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

[MM3-users] Re: eccentric setup question

by Mark Sapiro

On 3/21/23 02:05, Jeff Berry wrote: > > The problem we're having is that if the mailman domain of the list is listserver.domain.com then spamfilters start to flag the mail since it looks like spoofing/malformed headers and so on. If the mailman domain is just domain.com then postfix rejects it with an unknown local recipient error. I though I might be able to just tweak the incoming mail headers in postfix via header_checks but that's not working, either because I've got the wrong check or it's the wrong approach, or both. > > postfix relay_domains might do it, I think, but if it maps listserver.domain.com to domain.com that would break the listserver domain mailing lists (I think). Is Postfix on the mailman server set up per https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… and did you run `mailman aliases` to regenerate mappings after changing Exchange to relay to list(a)domain.com? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Mailman3-Web lots of database queries

by Mark Sapiro

On 11/17/18 8:36 AM, Stefan Tatschner wrote: > Hey! > > I recently set up a mailman3 instance and it works quite nice. I use > the debian packages from buster. After running the thing for a few > days, I realized an unexpected network load (my postgres database is on > a separate machine). Turning the postgres log on revealed that mailman3 > constantly queries the database: > > [...] > 2018-11-17 16:33:15.417 UTC [8304] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:15.385901+00:00'::timestamptz) LIMIT 1 ... > > Is this behaviour intended? No. This is not normal. This is apparently coming from Django qcluster. At least it is qcluster that uses the django_q_ormq table, but these repeated queries are not normal, at least I don't see them in the sites I administer. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 2/25/21 6:32 AM, David Partain via Mailman-users wrote: > > In /etc/mailman3/mailman.cfg I see: > > > class: mailman.database.mysql.MySQLDatabase > > url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8&use_unicode=1 > > > Should I change the latter to be something like: > > > url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8mb4&use_unicode=1 Yes, either make it charset=utf8mb4 or I think dropping the charset= option altogether will use the database default, however I'm not clear why this would be the issue as this only controls how Mailman core accesses the database, and your issue is with HyperKitty/Django and its access is controlled by the DATABASES setting in Django's settings which you say do specify 'charset': 'utf8mb4' in OPTIONS. Also, it seems Mailman core is not even using the same database - i.e. `mailman3` whereas Django's is `mailman3web`. -- 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: Hyperkitty on Debian 12

by Mark Sapiro

On 3/25/24 07:58, Markus Grandpre wrote: > Dear list members, > > when following the instructions to migrate list archives from Mailman21 > to Mailman3 (see [1]), I face the following problem: > > # python3 manage.py hyperkitty_import -l mailman21-migration-test-04 > /var/mailman21/testlist.mbox > python3: can't open file '/var/mailman21/manage.py': [Errno 2] No such > file or directory > > and have no clue, where to find the right <manage.py> file. The command This depends on how you installed Mailman 3. You may or may not want `python3 manage.py` at all. The required command could be something like `django-admin` or `mailman-web`. Also the `#` prompt indicates you may be running as root. Mailman related commands should be run as the Mailman user (could be `mailman` or `list` or ... depending again on how you installed Mailman). Running as root can create files owned by root that later can't be read by the Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Mark Sapiro

It turns out this error is caused by a non-ascii character in a prologue section of the email. When the message gets parsed into a mailman.email.message.Message objectand then flattened to a string, the non-ascii in the prologue gets converted to unicode surrogates which causes problems in subsequent processing. The bug report has moved twice in the process of diagnosing and fixing this - from https://gitlab.com/mailman/hyperkitty/-/issues/301 to https://gitlab.com/mailman/mailman-hyperkitty/-/issues/25 to https://gitlab.com/mailman/mailman/-/issues/732 The fix is in core and is quite simple. ``` --- a/src/mailman/email/message.py +++ b/src/mailman/email/message.py @@ -55,7 +55,8 @@ class Message(email.message.Message): except (KeyError, LookupError, UnicodeEncodeError): value = email.message.Message.as_bytes(self).decode( 'ascii', 'replace') - return value + # Also ensure no unicode surrogates in the returned string. + return email.utils._sanitize(value) @property def sender(self): ``` See https://gitlab.com/mailman/mailman/-/merge_requests/665 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Rejection Reason for refusing a subscription request

by Mark Sapiro

On 3/27/21 2:08 PM, Brian Carpenter wrote: > I was testing out the process of rejecting an incoming subscription > request. Choosing the reject option for a moderated subscription request > does send out a rejection notice but it gives no reason for the > rejection. ... > Is there a place somewhere in Postorius to provide a rejection reasons > for moderated subscription requests? Does Mailman 3 core provide this > via its REST api but it is just not revealed in Postorius yet? It's in Postorius since 1.3.3. If in the held message view, you click the subject of a held message, you get a popup dialog the shows the message with options to also show headers or the raw message. There is also a dropdown t=o set the poster's moderation action and a box for a reject reason if you click the reject button in the dialog. Do you not see this? -- 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: List Migration from MM2.1 -> MM3

by Mark Sapiro

On 8/15/22 00:32, Odhiambo Washington wrote: > > Apparently so, because: > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman lists > No matching mailing lists found > mailman@lists:~$ > > Which is surprising, given this: https://imgur.com/a/LPrh42K Postfix is talking to a different Mailman core. > root@lists:/home/wash# su - mailman > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman create > skunkworks(a)lists.my.co.ke > sh: 1: /usr/sbin/postmap: not found > sh: 1: /usr/sbin/postmap: not found > Traceback (most recent call last): ... > RuntimeError: command failure: /usr/sbin/postmap > /opt/mailman/var/data/postfix_lmtp, 127, Key has expired > command failure: /usr/sbin/postmap /opt/mailman/var/data/postfix_domains, > 127, Key has expired > > Now that wants Postfix, while I don't use Postfix, but Exim as the MTA. In the [mta] section of mailman.cfg, put ``` incoming: mailman.mta.exim4.LMTP configuration: python:mailman.config.exim4 ``` See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: MM attaches mime-attachments to mail as text file since update to 3.3.8

by Mark Sapiro

On 1/23/23 22:50, Stefan Bauer wrote: > Dear Mark, > > thank you for your time. > > Here are the lists settings and an example mail attached. > > Filter content: NO > Filter types: EMPTY > Pass types: EMPTY > Pass extensions: EMPTY > Collapse alterantives: YES > Convert html to plaintext: NO > > Thunderbird is showing the mail "correct". Outlook does show the > attachments as attachments. So Filter content is NO so Mailman isn't doing any content filtering. All it is doing is adding headers and footers if any, and if the original message is other than a single text/plain part, these will be added as separate MIME text/plain parts. For a discussion on why this is done, see https://wiki.list.org/x/4030707 which is written for MM 2.1, but which applies at least generally to MM 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Held messages not delivered after approval

by Mark Sapiro

On 7/30/25 07:27, Stephan Krinetzki wrote: > Hi all, > > I'm running into an issue with Mailman 3. Mails sent to a list are being held due to moderation settings — which is expected — but after approving them, they are not delivered to list members. Are there any regular members with delivery enabled? ``` mailman members --regular --nomail enabled LISTSPEC ``` > The message does not end up in the shunt queue, and nothing is delivered. > > Here's what I see in the Mailman log: > > Jul 30 16:12:23 2025 (213300) HOLD: mm(a)lists.example.com post from sender(a)sub.example.com held, message-id=<20250730141221.5VVrn%sender(a)sub.example.com>: The message is not from a list member > Jul 30 16:12:39 2025 (213338) held message approved, message-id: <20250730141221.5VVrn%sender(a)sub.example.com> This is expected. Is there anything relevant in Mailman's smtp.log? Do any posts to this list get delivered, e.g., posts which aren't held. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: messages with attachments, without text discarded silently

by Mark Sapiro

On 1/31/25 17:38, Mark Sapiro wrote: > On 1/31/25 12:14, Schulz wrote: >> ---- >> these are the first lines of the .eml: >> >> MIME-Version: 1.0 >> Date: Tue, 28 Jan 2025 19:31:15 +0000 >> Content-Type: multipart/mixed; >> boundary="6efe513a-b2f8-47e5-ace0-b3b6aa5a056c-1" >> From: "J. Schulz" <js(a)jslz.de> >> Message-ID: <17def72e63ed443458a88ec892a17fe01b8a287c(a)jslz.de> >> TLS-Required: No >> Subject: empty, but another att >> To: it(a)freie-dorfschule.de >> >> --6efe513a-b2f8-47e5-ace0-b3b6aa5a056c-1 >> Content-Type: text/plain; charset="utf-8" >> Content-Transfer-Encoding: quoted-printable >> >> >> --6efe513a-b2f8-47e5-ace0-b3b6aa5a056c-1 >> Content-Type: application/pdf; name="someExample.pdf" >> Content-Disposition: attachment; filename="someExample.pdf" >> Content-Transfer-Encoding: base64 >> >> JVBERi0xLjcKJcOkw7zDtsOfCjIgMCBvYmoKPDwvTGVuZ3RoIDMgMCBSL0ZpbHRlci9GbGF0 >> ZURlY29kZT4+CnN0cmVhbQp4nC2NTQvCMBiD7++vCHjz0L7t1q2DMXAfgoeBg4Ln4TpRULEU >> 9OdbRB4SCISEhcKb5C7E6zqfI9qxoxcYLFhbmMoIXRrYXAlbKARPpy0eNKSWPAa/PsN9jtEv >> G83Of2Jdy7E79OCmafv/UCJcqHVkCmFRlsmzCm6B3CsohltrVqw545wNF0llSjZRNe5Gg6Pp >> 9zfhC14SKM4KZW5kc3RyZWFtCmVuZG9iagoKMyAwIG9iagoxNTMKZW5kb2JqCgo3IDAgb2Jq >> Cjw8L0xlbmd0aCA4IDAgUi9GaWx0ZXIvRmxhdGVEZWNvZGUvTGVuZ3RoMSA5MDc2Pj4Kc3Ry >> ZWFtCnic5Vh9dFPHlb/zniTLH1iSP4RtGd4zwh9gW7ItTIAa/LAtYbDBso1BAgJ6lmQkYkta >> SbZj0haTJoGYzyaEtEnOhuajTQgJz5AcTEqBLbs9yTZp04/ddje00G6a3Z4mkO02Pd3TYO+d >> 0bP5aJKes2f/2yfPmzv3zr33N/feGWmcjA8GIQtGgQfJPyDH5s3K1APAWwAkxz+UFPsiGgfS >> VwG4V/pi2weeOLPlDwCawwBpr27vH+n7k+ZkC0AWNm0sFJQD8rtQCWB6FW0sDiHjyRvHdTj+ >> AMfzQwPJe/+Fe00DkGPEsbk/6pdbtKMoz6mg4wH53lhCU8/jWMKxGJEHgu+9/ I see the issue. Mailman's content filtering sees this multipart message as having two parts, the first of which is empty, so it tries to recast the message as a single part message containing only the second part. The problem is this code only works if the second part is a text/* part. Here it decodes the base64 encoded pdf and tries to recast it as unicode text which works for text/* parts with a declared charset, but not for non-text parts. This patch is untested, but I think it will fix the issue. ``` --- a/src/mailman/handlers/mime_delete.py +++ b/src/mailman/handlers/mime_delete.py @@ -221,7 +221,7 @@ Replaced multipart/alternative part with first alternative. def reset_payload(msg, subpart): # Reset payload of msg to contents of subpart, and fix up content headers - if subpart.is_multipart(): + if subpart.is_multipart() or subpart.get_content_maintype() != 'text': msg.set_payload(subpart.get_payload()) else: cset = subpart.get_content_charset() or 'us-ascii' ``` -- 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

Search results for query "sapiro"