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

[MM3-users] Re: Header Filter madness

by Mark Sapiro

On 1/14/21 9:54 AM, Brian Carpenter wrote: > Mark Sapiro wrote: >>> What's in the X-Mailman-Rule-* headers of the post that should be >> but >> isn't held? >> Are there other header filter rules besides the one that doesn't work? > > This is what the client provided me: > > X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-listname.listdomain.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header So header-match-listname.listdomain.org-0 and no other header-match rule misses and no rule hits says there is only one header match rule and it missed. Since it hits in your test, I can only guess that the regexp in your test or the specific header in your test was not identical to what was in your test. I assume you have access to the list settings. Does the offending regexp have trailing white space or something else different from your test? Or perhaps the offending header or regexp has some character which is ascii in one and a visually similar but different unicode in the other. Also, I think but am not sure that we don't always properly decode RFC2047 encoded headers for header match rules. This would be a bug. -- 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: Held for notification - runner exception: 'ascii' codec can't encode character

by Mark Sapiro

On 1/2/22 11:18 AM, Mark Sapiro wrote: > > Please do send me the shunted .pck. what is going on is this is an > English language list which has character set `ascii` and the notice for > some reason has non-ascii, possbbly the Subject: or the user's display > name has non-ascii. But possibly the message itself is defective. > > In any case, I'd like to get the shunted message to see if there's > something we should fix. Thanks for sending me the shunted .pck. It turns out I didn't need it. Had I looked more closely at the Traceback, I would have realized that the issue is that the list's list:admin:action:post template contains non-ascii. In particular, the character in position 5 is ’ which is a unicode right_single_quote, not an ascii apostrophe. There may be other unicode fancy quotes ad well. You can fix the template to contain only ascii or you can set the character set for English to utf-8 by adding ``` [language.en] charset: utf-8 ``` to mailman.cfg. The downside of the latter is that outgoing message bodies will always be base64 encoded which generally precludes grepping mailboxes to find things. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Problem with debian uipgrade

by Mark Sapiro

On 3/8/22 11:40, Mark Sapiro wrote: > On 3/8/22 10:10, Lars Schimmer wrote: >> Hi! >> >> Today I tried a mailman3 upgrade of the debian packages and I got this >> error: >> >> django.db.migrations.exceptions.NodeNotFoundError: Migration >> hyperkitty.0007_allauth_20160808_1604 dependencies reference >> nonexistent parent node ('socialaccount', '0003_extra_data_default_dict') >> >> Anyone has a idea howto fix those? > > This is a reference to a migration in django-allauth. is django-allauth > installed. If so, what version? > > What does the database query > ``` > SELECT app, name FROM django_migrations WHERE app = 'socialaccount'; > ``` > show. It should be > ``` > app | name > ---------------+------------------------------ > socialaccount | 0001_initial > socialaccount | 0002_token_max_lengths > socialaccount | 0003_extra_data_default_dict > (3 rows) > ``` Possibly one way to fix this is to run ``` django-abmin migrate socialaccount ``` where django-admin is the name of your django management command. Then running `django-abmin migrate` should succeed. The issue appears to be due to the face that `django-admin migrate` runs the migrations in alphabetical order by app. This is fine if migrations were run during the period after socialaccount.0003_extra_data_default_dict was created and before hyperkitty.0007_allauth_20160808_1604 was created, but it's an issue in an installation that wants to migrate hyperkitty.0007_allauth_20160808_1604 without having previously migrated socialaccount.0003_extra_data_default_dict. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Weird hourly indexing error

by Mark Sapiro

On 5/5/20 2:39 PM, Mark Dadgar wrote: > On May 5, 2020, at 2:27 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> This is how less >> displays it >> >>> XSUBJECT9<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>5<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>2<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>5<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>1<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>4<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>1<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>3<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B> >> >> >> Each of those <U+200B> represents a unicode zero width space. > > > That’s gnarly. > > BTW, the patch did not fix it. I haven’t had a chance to look more deeply into it yet. Actually, if I take the above as a unicode string and encode it as utf-8, each of the <U+200B> unicodes becomes three hex bytes \xe2\x80\x88 and the length of the result is 247 bytes, so I suspect that the 'word' in the error message has been truncated. As to the patch not working, there is a different patch at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…> which may work. There is one issue with this patch. Namely it calls force_str() in the section > + # https://trac.xapian.org/wiki/FAQ/UniqueIds#Workingroundthetermlengthlimit > + # Working round the term length limit > + word = force_str(word) > + word_length = len(word) but xapian_backend.py imports force_text <https://github.com/notanumber/xapian-haystack/blob/master/xapian_backend.py…>. They are actually synonymous <https://docs.djangoproject.com/en/3.0/ref/utils/#module-django.utils.encodi…>, but just appliing the patch without changinf force_str to force_text won't work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Multiple domain problem

by Mark Sapiro

On 2/10/23 01:43, Lars Bjørndal wrote: > On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: >> On 2/9/23 13:21, Lars Bjørndal wrote: >>> >>> If I connect to example2.com, the title is example2.com, without the >>> preceding List index. And the body says Page not found. >> >> >> What's in the browser's address bar for that page? > > It's https://example2.com/mailman3/lists/ And when you get the Page not found, is it a browser 404 error or a Postorius error page? > >> What's in Postorius domains view? > > I realized that I have to change SIT_ID to 1 to be able to connect to http://localhost:8000/. Then, when checking Domains, I have both domains with different SIT_ID value (1 and 2). Why are you going to http://localhost:8000/? You should be able to see the domain's view at https://example1.com/mailman3/domains/ or https://example1.com/mailman3/domains/ or by just clicking Domains in Postorius top nav bar. > Going to http://localhost:8000/admin and choosing Sites, I have both domains listed. Again you should be able to go to https://example1.com/admin or https://example2.com/admin. If these don't work, you need to add directives in your web server to proxy them to http://localhost:8000/admin -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Mark Sapiro

On 5/13/16 5:05 PM, Simon Hanna wrote: > On 05/12/2016 09:26 PM, Barry Warsaw wrote: >> On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: >> >>> It is the intent that Postorius will eventually expose all these >>> settings. We're not there yet. At present you could possibly do this by >>> interacting with mailmanclient, although I'm not certain the settings are >>> exposed there. >> >> I'm not sure if they're exposed in mailmanclient, but they are exposed in the >> core's REST API, on the member resource. It's the `delivery_mode` attribute >> and it takes as legal values one of 'regular', 'plaintext_digests', >> 'mime_digests', and 'summary_digests' (IOW, the enum item names for the >> DeliveryMode enum). > They are exposed in mailmanclient and are used in postorius. They can be > found in the users personal subscription settings > https://lists.mailman3.org/mailman3/accounts/mailmansettings/ You are correct. When I checked this before my initial reply, I never pulled down the Delivery Mode list to see all the options. My bad. However, please correct me if I'm wrong, but there does not appear to be a way in Postorius to set a list's mime_is_default_digest attribute. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 9 months

[MM3-users] Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 12:06 AM, Paul Arenson wrote: > Mark Sapiro wrote: > >> If by "read only" you mean the "Announce only mailing list style" as >> opposed to the "Ordinary discussion mailing list style" the only >> difference is that for the Announce only style the list attribute >> allow_list_posts is False and for the Discussion style, it's True. >> >> This is the setting in Postorius -> Settings -> Alter Messages -> >> Include the list post header an all it does is include or not include >> the List-Post: header in mail from the list. > > Ok...there is no specific setting I see "allow_list_posts" but you wrote "Include the list post header " later on. So i set THAT one to NO? allow_list_posts is the name of the attribute in Mailman core. It is exposed in Postorius as "Include the list post header". I.e., they are the same thing. Note however that unless your users are using MUAs to reply by email and their MUAs offer a "reply-list" function for replies to mailing list posts, this setting will make no difference. It is the presence of the List-Post: header in the message that allows the MUA to offer/process the "reply-list" function. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Footer variables

by Mark Sapiro

On 3/2/26 11:03, Mark Sapiro wrote: > > Are there `Exception in "hyperkitty" archiver` messages in mailman.log, > or if you have set a path: in the [logging.archiver] section of > mailman.cfg, in that file? Actually, there won't be those messages. The code in question is <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/decor…> The fact the ${hyperkitty_url} is replaced with an empty string indicates that line 79 does not raise an exception but rather sets archive_url to the empty string. This is the only way that the replacement dictionary would contain the key `hyperkitty_url` and if it didn't contain that key, the resultant footer would contain literally `${hyperkitty_url}` You could try in `mailman shell` ``` $ mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> from mailman.email.message import Message >>> msg = Message() >>> msg['Message-ID'] = '<xxx(a)example.com>' >>> for archiver in IListArchiverSet(m).archivers: ... if archiver.system_archiver.name == 'hyperkitty': ... print(f'URL: {archiver.system_archiver.permalink(m, msg)}') ... ``` This should print something like URL: https://example.com/archives/list/list@example.com/message/FMB3KJSE74FUTZBV… Does it? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 days, 3 hours

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Mark Sapiro

On 9/19/19 12:02 AM, Henrik Rasmussen wrote: > Abhilash Raj wrote: >> On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro wrote: >>> each other, but Postfix is trying to deliver mail via lmtp to >>> [172.19.199.2]:8024. Mailman's lmtp runner should be running and >>> listening on port 8024. Either that is not the case or that port is not >>> exposed to Postfix on IP 172.19.199.2. >>> Right, that is what I was wondering, you verify that by using telnet >> on the specified IP and Port (172.19.199.2:8024). > > Yes, the postfix container listens on 172.19.199.2:8024 > ``` > [root@postfix /]# nc -v 172.19.199.2 8024 > Ncat: Version 7.50 ( https://nmap.org/ncat ) > Ncat: Connected to 172.19.199.2:8024. > 220 mailman-core GNU Mailman LMTP runner 2.0 > ``` This seems to say that the Postfix container can connect to 172.19.199.2:8024 and receive the greeting from Mailman's lmtp runner. So, why can't Postfix send to 172.19.199.2:8024? The only log entry you postes just says "Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: mail for [172.19.199.2]:8024 is using up 7844 of 7844 active queue entries". What other log entries relate to attempts to send to 172.19.199.2:8024? You may have to go back to when this first started to see them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: required cron entries?

by Mark Sapiro

On 1/1/21 12:37 AM, Andreas Barth wrote: > * Mark Sapiro (mark(a)msapiro.net) [201231 19:28]: >> On 12/31/20 2:49 AM, Andreas Barth wrote: >>> Looking in the source code, there is a ./cron/crontab.in.in however >>> references to scripts in port_me/ directory. >> >> That's all old Mailman 2.1 stuff. ignore it. > > Can we replace that by a mailman3 cron tab? (I'm happy to write that > as merge request if useful, but I assume that should be done rather by > opening a bug report and using gitlabs features and not inline per > mail) Yes, the ideal workflow is to open an issue on GitLab and then open a merge request to fix it. However, I don't think we need a sample crontab as we have <https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs> which should be enough. I think the real solution is to just remove the mailman/cron directory and at least some of the mailman/port_me/ files. The cron/crontab.in.in file is just a distraction. For the port_me files, we have: checkdbs.py - this function is handled by `mailman notify` disabled.py - handled by core's bounce processing show_config.py - handled by `mailman conf` and these for which no MM 3 equivalent exists and which could be helpful in implementing a corresponding `mailman` subcommand: config_list.py export.py find_member.py -- 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

Search results for query "sapiro"