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

[MM3-users] Re: Postorius not HTML-decoding < to "<" characters

by Mark Sapiro

On 11/9/24 17:09, Mark Sapiro wrote: > > Here's what's going on. In normal text, mistune disables HTML tags by > converting `<` to the html entity `<`, but your browser renders the > HTML entity `<` as `<` so you see what was written. > > The issue here is the text you quoted was originally in a markdown code > block, i.e. preceded and followed by lines of three backticks. Code > blocks are intended to be seen literally as written so they are wrapped > in <pre><code> ... </code></pre> tags in the HTML and also HTML escaped. > The problem is the tag disabling converts `<` to `<` but then the > HTML escaping converts `<` to `&lt;` which your browser then > renders as `<` rather than `<`. > > (aside, it will be interesting to see how that is rendered in the archive) The backtick quoting causes the < to be rendered as `<` Here are the above two paragraphs written in a way (removing the backticks from around <) that I hope will render as I intended. Here's what's going on. In normal text, mistune disables HTML tags by converting < to the html entity `<`, but your browser renders the HTML entity `<` as < so you see what was written. The issue here is the text you quoted was originally in a markdown code block, i.e. preceded and followed by lines of three backticks. Code blocks are intended to be seen literally as written so they are wrapped in <pre><code> ... </code></pre> tags in the HTML and also HTML escaped. The problem is the tag disabling converts < to `<` but then the HTML escaping converts `<` to `&lt;` which your browser then renders as `<` rather than <. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Mark Sapiro

On 11/18/24 19:19, mark(a)suburbia.org.au wrote: > Mark Sapiro wrote: >> This says it was held for moderation. Is there an X-Mailman-Approved-At: >> header which would say it was approved by a moderator? > > No "X-Mailman-Approved-At" in the header. All the X-Mailman headers in the mail sent to the list were included in my previous reply. The member moderation rule hit. This only happens if the `sender` is a member and the member's moderation action is other than None or Defer or the member's moderation action is None and the list's default_member_action is other than Defer. Once the rule has hit the message is accepted, held, discarded or rejected depending on the moderation action found above. One caveat here is how the `sender` is determined, The `sender` is the first address found in the From:, envelope sender, Reply-To: and Sender: headers that is a list member. If the From: address is the member whose moderation action is None than the list's default_member_action should apply, but if the From: is not a member, you have to look at those other addresses. One possible way to avoid this issue, although it doesn't solve the mystery, is to set Emergency Moderation to Yes which should hold all posts regardless of sender. To diagnose this further, can you create a test list, set Default action to take when a member posts to the list to Hold, mass subscribe an address and send a post from that address and see if it's held. It should be, and if it is, I think things are working as they should be and a test post to the original list from one of these mass subscribed members will be held. If that is true, I can only think that at the time of that post, settings weren't as they are now. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: Bounces address spammed

by Mark Sapiro

On 2/28/19 9:15 AM, Enrique Terrazas wrote: > Greetings, > I hope everyone is having a good day. We have a highly visible list that is being spammed with join requests from spoofed addresses. Web or email? > When the confirmation email is sent a bounce is received by the list owner. The count is in the 100’s of bounced emails/hour. We noticed they are all coming from one particular domain, this may help if we are able to filter/block the domain. What would be the best way to handle this? Is there a way to handle this granularly at the list level? If the requests are coming by email, you can block the domain in your MTA., E.g. with postfix in main.cf: header_checks = pcre:/etc/postfix/header_checks.pcre in /etc/postfix/header_checks.pcre: /^From:.*[@.]bad.domain\w/ DISCARD or /^From:.*[@.]bad.domain\w/ REJECT We don't accept mail from bad.domain. For web requests, adding a pattern like '^.*[@.]bad.domain$' to the lists "Banned addresses" might help. -- 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: [Mailman-Users] Web interface for users (not admins)?

by Mark Sapiro

On 5/7/21 6:21 AM, skip.montanaro(a)gmail.com wrote: > I am now signed up for the MM3 list. I'm trying out this posting interface. I like the basic interface, but others will want to attach images, tweak fonts, that sort of thing. Having the "email" button above makes that a reasonable (to me) alternative, but might not work for some tech-challenged people (odd, I know) who barely know how to get a picture out of their phone. Is there an "enhanced" editor? No, Posting from HyperKitty without using the "Use email software" button is plain text only. There is no plan to add any sort of rich text capability. Further, the HTML and image parts of archived messages containing them are just available in HyperKitty as links and not nicely rendered. See for example the signature links at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and 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

4 years, 1 month

[MM3-users] Re: Whitelist non subscriber

by Mark Sapiro

On 08/10/2017 07:12 AM, Mark Ziranski wrote: > > I want to whitelist an email address on all lists to bypass moderation. > The email address is not a subscriber. On google I > found accept_these_nonmembers but I do not know how to use it. > Please show me some examples how to whitelist someone(a)example.org. Since this is a Mailman 3 list, I assume you are asking about MM 3. Mailman 3 defines the list attribute accept_these_nonmembers, but it is not currently implemented to actually have any effect, nor is it exposed in Postorius. At the present, I think you would have to create a user record with the address and add that user to all lists with role nonmember and moderation_action 'defer' to apply subsequent tests or 'accept' to unconditionally accept posts from that address. (In MM 2.1, accept_these_nonmembers is a list of addresses and regexps matching addresses whose posts are to be accepted, subject to subsequent tests, and is exposed in the web admin UI) -- 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: integrating mm3 with postfix / lmtp

by Mark Sapiro

On 10/26/2017 06:16 PM, Fabian A. Santiago wrote: > > But in my testing, I replied to a subscription confirmation message and received back an undeliverable looping email error message from postfix. Any clues there you can offer? I can post to the list from any email added via the admin console. The test subscriber address was local to my server. From an outside address, same error. This usually means that postfic is trying to deliver to an address and the message already has a Delivered-To: header with that address. What are the headers of the "looping" message in the report? What are the Postfix log messages related to that message? > Once I registered the new email domain, I reverted my postfix config back to the default suggested by maxking's docker instructions. > > https://github.com/maxking/docker-mailman I have essentially no knowledge of the docker container images, so I can't be much help with issues specific to them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: hidden list is hidden even to the owner

by Mark Sapiro

On 7/1/20 2:05 PM, Abhilash Raj wrote: > > Which version of Postorius are you running? > > Newer version shows all the lists you are related to by default when you are logged-in. So, the ones you own, moderate, subscribe to. That's correct, but it's tricky. If as an owner of an unadvertised list, you go to a URL like https://www.example.com/postorius/lists/ you will see the unadvertised list(s) that you own as well as any that you are a member or moderator of. Likewise you will see the unadvertised list(s) you own at https://www.example.com/postorius/lists/?role=owner and if you are a member as well as owner of an unadvertised list, you will see it at https://www.example.com/postorius/lists/?role=member. But (here's the tricky part) if you go to https://www.example.com/postorius/lists/?all-lists, you will not see any unadvertised lists, not even ones you own. -- 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: Mailman3 not delivering list mail

by Mark Sapiro

On 10/2/20 4:53 AM, gordon(a)dickens.com wrote: > Hi Mark, > > BTW, as an aside, there is not any mention of admin users needing to be logged in as user=list instead of user=root in the documention here: > > https://docs.mailman3.org/en/latest/migration.html > > I highly recommend that the documentation be amended to clearly state that the admin users need to be logged in as user=list. The `list` user is a Debian/Ubuntu package thing. The Mailman user can actually be anything. I have added a note at <https://docs.mailman3.org/en/latest/migration.html#fn1> saying that these commands should be run as the Mailman user and not as root. The mailman command itself, if run as root, should probably set the effective user:group to the Mailman user:group. We don't know that from the Mailman config, but maybe use the owner and group of the mailman command file. This is now <https://gitlab.com/mailman/mailman/-/issues/776>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Problem user

by Mark Sapiro

On 5/18/23 04:33, Itay Malka wrote: > Hello everyone, > > I use mailman3 > And I have one user who every time receives reports on a mailing list that he is not the administrator of, he is only registered to it > How can I cancel it? > could not find > > This is the email > Message-ID: > <CABPnsAo5vT8YKXiaHk0E2qs8CRs8nP13B9T9n5x4Yc8n7iLV3Q(a)mail.gmail.com> > Content-Type: multipart/alternative; > boundary="00000000000069e01c05fbde1416" > > --00000000000069e01c05fbde1416 > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: base64 > > 16rXldeT15QNCg== > --00000000000069e01c05fbde1416 > Content-Type: text/html; charset="UTF-8" > Content-Transfer-Encoding: base64 > > PGRpdiBkaXI9ImF1dG8iPteq15XXk9eUPC9kaXY+DQo= > --00000000000069e01c05fbde1416-- The message above is not from Mailman. It is simply a message originally from Gmail that says :"Thank you" in hebrew. I can't say much more without seeing the entire raw email. > End of Dental-medicine-faculty-council Digest, Vol 1, Issue 1 > ************************************************************* This is the final part of a plain format digest. Was it part of what was received? -- 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: Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Mark Sapiro

On 10/30/19 12:52 AM, Franklin Weng wrote: > > If I use > > base_url: https://lists.slat.org/mailman3/hyperkitty/ > > The log became > > Oct 30 15:25:50 2019 (6256) HyperKitty failure on > https://lists.slat.org/mailman3/hyperkitty/api/mailman/urls: > <html><title>Auth required</title><body> > > <h1>Authorization Required</h1> > </body></html> (401) > > In my mailman-web.py: > > MAILMAN_ARCHIVER_KEY = 'my-key,same as in mailman-hyperkitty.cfg' > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') > > Not sure what to change here. There have been other reports of authorization failures even though the keys match. See the last few posts at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. The solution there was to change both the api_key setting in /etc/mailman3/mailman-hyperkitty.cfg and the MAILMAN_ARCHIVER_KEY setting in /etc/mailman3/mailman-web.py to new values. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

Search results for query "sapiro"