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

[MM3-users] Re: Setup Question: Disk-Layout (Migrating from Mailman 2.1)

by Mark Sapiro

On 4/17/25 11:35 AM, Mihai Moldovan wrote: > > New incoming messages will have the correct data, of course, but > imported ones wouldn't, so I'll have to use a more sophisticated > approach to handle them, probably by going through mailman's email > wrapper, figuring out how to generate a msgdata object for a message, > using RFC2369.process and maybe more. Here's an example script. You need to run this with /opt/mailman/mm/venv/bin/python to get access to the mailman imports. ``` from mailbox import Maildir, mbox from mailman.email.message import Message from mailman.handlers.rfc2369 import process from mailman.interfaces.listmanager import IListManager from mailman.utilities.email import add_message_hash from zope.component import getUtility mb = mbox('path/to/mbox', factory=Message, create=False) md = Maildir('path/to/maildir', create=False) mlist = getUtility(IListManager).get_by_list_id('your.list.id') for msg in mb: add_message_hash(msg) process(mlist, msg, {}) md.add(msg) mb.close() md.close() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 4 weeks

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Mark Sapiro

On 9/19/19 2:22 AM, Manos Pitsidianakis wrote: > Thank you again for your reply, Mark. > > Στις 2019-09-18 21:53, Mark Sapiro έγραψε: >> What are these entries? > > > I have these log entries, are these what you were referring to? > > https://paste.debian.net/hidden/37d863f6/ No. You referred to "shunted" mails. I assumed that mail was winding up in the shunt queue, but this is apparently not the case. >> The "Cannot connect to SMTP server" log message should not occur >> immediately on startup unless there are queued messages. That log >> message should only occur on an attempt to actually send a message. > > I think the problematic e-mails that cause this issue are stuck on the > outgoing queue. Right now there are 2 pck files and one .bak in > var/queue/out changing filenames repeatedly. What is happening is you have three messages in the out queue which are problematic. When Mailman or the out runner is restarted, for some reason the attempt to send these triggers the "Cannot connect to SMTP server" issue which is logged only once. Here's what happens: The oldest .pck file in the out queue gets picked up by the out runner and renamed to a .bak. The runner attempts to send the message and gets a socket.error exception so it requeues the message to be tried again. This removes the .bak and creates a new .pck. This process continues so the files keep getting renamed. I suggest you stop Mailman, and move the three files out of the out/ queue, and then restart Mailman. This should stop the out runner from "spinning" on these messages. Then you can examine the files with Mailman's 'bin/mailman qfile' command and see if you can identify something in the recipients list or other metadata that might be causing this. -- 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: How to Increase outgoing mail volume for Mailman 3

by Mark Sapiro

On 11/10/20 1:22 PM, Mark Dadgar wrote: > > Brian specified: > > verp_personalized_deliveries: no > > Doesn’t that default back to regular mass delivery, as opposed to individualized VERPed envelopes, which mandates individual deliveries? That depends on the setting of verp_delivery_interval. If verp_delivery_interval = 1, every message will be VERPed regardless of verp_personalized_deliveries. If verp_delivery_interval = 0 and verp_personalized_deliveries = no, deliveries won't be VERPed as you note. If verp_delivery_interval = 0 and verp_personalized_deliveries = yes, only personalized deliveries (i.e. individual messages, not digests, from lists with Personalization enabled) will be VERPed. The theory is VERPing has a cost because it requires a separate message sent to each recipient rather than a single message with multiple recipients, but personalization also requires a separate message sent to each recipient, so those can be VERPed at no extra cost. But to be clear, automated bounce processing does not require VERP. It just works a tiny bit more reliably with VERP. -- 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 mails blocked from GMX - web.de > Spamfolder

by Mark Sapiro

On 7/19/23 05:31, itservice--- via Mailman-users wrote: > How can I configure Mailman3 so that Mails from the list will not be blocked by gmx.net > I tried to send with the same user (mailman.cf) at my mail server, which will not be blocked by gmx. > unfortunately, I get no bounce back message. They do just not appear in the mail folder of gmx. Unfortunately, there are some ESPs that will silently discard mail without giving any clue as to the reason. I think this is wrong, but there's nothing we can do about it. > At web.de they go to the SPAM folder. Is your mail server properly configured with a fixed IP and full circle DNS? Is it on any block lists (check at http://mxtoolbox.com/blacklists.aspx)? Are you DKIM signing your outgoing mail? Are you applying DMARC mitigations to your list mail? All these things are important. -- 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: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Mark Sapiro

On 4/25/23 2:14 PM, Andrew Hodgson wrote: > Mark Sapiro wrote: > >> The script at https://www.msapiro.net/scripts/clean_users.py has been updated. As before, it has settings to control whether Django users are deleted if there is a corresponding Mailman user with no memberships or only if there is no corresponding Mailman user, and whether or not Mailman users with no >memberships are deleted. > > Thanks, I ran this script and it did delete a load of Mailman users, I got output similar to this: > <User "" (47600399411039288509336192576257642185) at 0x7fb17a6a35e0> deleted from Mailman > > Why aren't we seeing the actual address here? That was a choice I made. you could change ``` with transaction(): user_manager.delete_user(mm_user) print(f'{mm_user} deleted from Mailman') ``` to ``` with transaction(): try: email = user.preferred_address.email except AttributeError: email = 'no_preferred_address' user_manager.delete_user(mm_user) print(f'{email} deleted from Mailman') ``` to display the email address from the user's preferred_address if the user has one. All users should have one, but I've seen cases where there isn't one. It could also be ``` email = user.addresses[0].email ``` which might be better. In the above case, the empty string, "", is the user's display_name which in this case is empty, and the number in parentheses is the UUID of the user expressed as a decimal integer which isn't really useful. My thought was the display_name was as useful as anything, but obviously not if it's empty. I actually started with the preferred_address.email code above, but in testing, I got the 'no_preferred_address' result with the one deleted user so I, perhaps erroneously, went with the representation of the user. I'll probably update the script again. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[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

1 year, 1 month

[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

1 year

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

[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

8 years, 4 months

Search results for query "sapiro"