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

[MM3-users] Re: Displaying addresses in emails from a Mailman 3 installation

by Mark Sapiro

On 7/4/25 11:08, Steve Brown via Mailman-users wrote: > Yes, I intended to post to the list. I now see that if I use the archives > to post (as I'm doing now), I have to use "reply all". On my Outlook, it's > the other way around. If I want to reply off-list, I have to click on > reply all and then remove the list address. Sorry. I only use the Gmail > address for a few limited purposes. I don't understand. When I reply from HyperKitty, the reply just goes to the list whether I enter the reply in the web UI or "Use email software". There is no "reply all" option and no way to reply to the poster other than using the "Use email software" method and manually adjusting the recipient addresses. Is this not the case with you? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Handling of Mail from non-subscribers

by Mark Sapiro

On 5/8/20 4:42 PM, Peter Adebahr via Mailman-users wrote: > > I have a fresh setup of MM3 on Ubuntu 20, installed by apt-get. It seems > to be running fine so far, except for some (to me) strange behaviour: > > When posting to the list as a non-subscriber, I see the mail coming in > on mailman's smtp.log, then it vanishes. No notice of this mail being > hold is sent to the sender, no notice to the moderator, and logging into > Postorius as owner of the list, it is not showing up in "Held messages" > > "Hold for moderation" has been set. Set in "Default action to take when a non-member posts to the list"? If that is the case, find the non-member in Users -> Non-Members and look at the Non-member Options link. What is the "Administration options Moderation" setting? for that non-member? -- 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: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Mark Sapiro

On 2/27/21 4:36 AM, Stephen J. Turnbull wrote: > > As far as I know the "emoji" problem (MySQL doesn't handle Unicode > characters outside of the Basic Multilingual Plane by default) is > still present. Given that emoji are now in use by pretty much > everybody and easily accessible on most platforms, this default is > unfortunate. However, I believe this is a server-wide setting, so I > am dubious that Mailman should force the "full Unicode" setting on. > (Anybody who knows feel free to correct me.) As far as I know, the `OPTIONS {'charset': 'utf8mb4}` setting in the `DATABASES` definition for mysql (see <https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec…>) will fix this issue. Although, one user may be currently having this issue where the `OPTIONS` setting doesn't fix it <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Username being set to givenname for socialaccount login

by Mark Sapiro

On 9/22/21 11:22 AM, cfarley(a)iastate.edu wrote: > I have a new mailman3 install setup with Okta as a social application. This is working well for logins and data comes through as expected, but for some reason the username is being set at to a lowercase version of the given_name. The Extra data on the social users in the admin interface looks good, so I don’t think it’s a problem with the attributes coming from Okta. > > We have tried a number of variations on the below setting, but that all of them other than the default of “username” end up with the username being empty. > ACCOUNT_USER_MODEL_USERNAME_FIELD = “email” > > Any direction would be welcome. This is an issue for Django allauth <https://django-allauth.readthedocs.io/en/latest/index.html>. Mailman has no control over this. The username is part of Django's login and is not used by Mailman at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[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, 5 months

[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, 9 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, 5 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, 4 months

[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

6 years, 2 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, 4 months

Search results for query "sapiro"