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

[MM3-users] Re: update_index

by Mark Sapiro

On 04/03/2018 09:59 AM, Darren Smith wrote: > OK - next issue...here's the warning that I'm receiving when I run that: > > /__init__.py:1451: RuntimeWarning: DateTimeField Email.archived_date > received a naive datetime (2018-04-03 07:51:25) while time zone support is > active. > RuntimeWarning) That warning comes from dateutil.parsedate, and I think it's just a warning and shouldn't affect processing. > I'm not sure that anything else occurred. The indexing took 2 seconds, and > there have been tens of thousands of emails imported since the last index. > Thoughts? I'm unsure about what happens when 'runjob update_index' runs after an import. I.e. it adds messages added since the last run, but is this based on when the message was added or on some date in the added message, so if the added messages are old, do they get indexed by 'runjob update_index'. You could easily check by doing some searches that should find them and see if they're found. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Setting moderation_action when approving a message from a non-member fails

by Mark Sapiro

On 6/13/23 05:15, Tom Smyth wrote: > > When a message is held due to it being from a non-member, I notice that > Mailman creates a non-member record for the sender automatically. This is > great! > > But if I try to set their moderation action while approving the message in > Postorius, I get: > > Failed to set moderation action: xxx(a)gmail.com is not a member address of > xxx(a)xxx.org > > Is this expected? I would like to be able to set the moderation action for > the non-member that has already been created. > > I am on Postorius v1.3.2. This is <https://gitlab.com/mailman/postorius/-/issues/448>, apparently filed by you, fixed in Postorius 1.3.4 by <https://gitlab.com/mailman/postorius/-/merge_requests/558>. Until you upgrade, you will have to set the non-member's moderation action separately from handling the held message. -- 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: Dealing with hyperkitty spool files (was Re: Re: Fwd: [Django] ...)

by Mark Sapiro

On 3/4/21 2:09 AM, David Partain via Mailman-users wrote: >> On Wed, 2021-03-03 at 08:29 -0800, Mark Sapiro wrote: >>> 1. Am I correct in assuming that I can just use my favorite editor >>> (vi) to remove the offending characters from the file? > >> No. The file is a Python pickle and you can't edit it. You would need >> to get the message and the metadata from the pickle (you could at > least >> view it with the `mailman qfile` command), edit the message and then >> re-pickle the message and metadata. > > And, in my impatience, I tried it before receiving your response and > now I seem to have done silliness in my database :( New error in > mailman-web.log: > > AttributeError: 'NoneType' object has no attribute 'subject' > > Sigh. Stupid me. If you have suggestions on fixing that... Is the file you edited still in the spool directory or is it gone? If it's still there, move it aside and see if that fixes the issue. What is the full traceback accompanying that AttributeError message from the log? > Right now, my plan is simply to remove the first message in the queue > (since I assume it'll be the "broken" one) and it'll just not be in > the archive. Life's hard. Even if I unpack 'em to edit, I'll find > mail in, for example, in base64, and I'm not going to fix the mail > by decoding, editing, re-encoding, ... Nope. Examine the messages in the spool with `mailman qfile var/archive/hyperkitty/spool/filename`. If any files throw exceptions on that, move them aside. Also, if you can see any 4-byte utf-8 encodings in the output, move that aside as well. Then see what happens after that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Mark Sapiro

On 10/27/20 11:08 PM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > All the mentioned versions of all the components are taken from my > currently running system only in which I am facing the issue. Did you run $ cd mailmanclient $ python setup.py develop as it says at <https://docs.mailman3.org/en/latest/devsetup.html> I do not understand exactly how the various components are installed in your installation, so I can't tell you what is wrong, but the version of mailmanclient that gives you the AttributeError: 'MailingList' object has no attribute 'get_requests_count' is not the one whose latest commit is ### Mailmanclient Version ### commit aaa529808e2d61899f90509da4ea802a70d2c8ff Merge: ff39dd8 8670751 Author: Abhilash Raj <maxking(a)asynchronous.in maxking(a)asynchronous.in> Date: Thu Oct 15 01:09:32 2020 +0000 Merge branch 'fix-ci' into 'master'* Use GHCR for the CI image* See merge request mailman/mailmanclient!130* because that one won't have this error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Migrating archives from mailman2 to mailman3 with attachments

by Mark Sapiro

On 2/28/22 10:14, bob B via Mailman-users wrote: > So I see the process for migrating an archive from mailman2 to mailman3 > https://docs.mailman3.org/en/latest/migration.html.................. i.e python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox > > but does the migration handle attachments?? attachments are in > ..../archives/private/foo-list/attachments. You do not need those files. They were extracted from the messages in the foo-list.mbox file which is all you need. > I am migrating to a new server and my plan is to follow these steps but copy the config.pck. and .mbox files to the new server and import them, but then it looks like I need to copy the attachment directory? if so how do I import the attachments to mailman3? No. You do not need the attachments directory or any of the .html files. All this information is in the .mbox. -- 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: How to promote non-members to members?

by Mark Sapiro

On 3/16/22 12:56, Quanah Gibson-Mount wrote: > > Thanks for the response. Unfortunately I'm currently stuck with the > junk shipped by Debian. Yet another reason to move to a standalone > install and avoid their broken packages. In the mean time, you can handle these issues via REST or via `mailman shell`. For example: ``` $ mailman shell -l list(a)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. >>> pendings = getUtility(IPendings) >>> sub_mgr = ISubscriptionManager(m) >>> for token, data in pendings.find(pend_type='subscription'): ... if data['token_owner'] != 'subscriber': ... continue ... if data['email'] != 'user(a)example.com': ... continue ... sub_mgr.confirm(token) ... >>> commit() ``` The above will find the pending confirmation for user(a)example.com on the list list(a)example.com and confirm it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: About the sender of the mailing list receiving an auto-reply email

by Mark Sapiro

On 1/12/23 17:48, 朱超 wrote: > Hi, When I use the mailing list to send emails, I receive an automatic reply email, Is there a better way to block similar automatic reply emails? From: Tom I don't really understand what you mean by a better way to block similar automatic reply emails. If you are saying you get an acknowledgement of your post, there are two possibilities. Each user has an `Acknowledge posts` setting. If you are getting that, you can turn it off. Also, lists have an `Autorespond postings` setting to send an autoresponse to posts from anyone. If that's what you are seeing, a list owner can turn that off too. If you mean you don't want to receive a copy of your own post from the list, there's also a user setting to `Receive own postings` which you can turn off. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question

by Mark Sapiro

On 6/24/23 9:44 PM, Ken Alker wrote: > How did you join the split thread? using HyperKitty's "Reattach this thread". > The order of the first two emails is flipped; the original email from 6/23 is showing after the second email on 6/24. Do you know how that happened? Do you have a way to fix that too? That was my mistake. There were two choices. I could open the reply thread containing only https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and reattach it to the original message thread now containing several messages or vice versa. I did the latter, i.e. with the result you see with the reply out of sequence at the top. Had I done the former the reply would have been out of sequence at the bottom. This would have been better, but it's now too late to change it. -- 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: Is there a way of recording bounce messages?

by Mark Sapiro

Stephen J. Turnbull wrote: > This is almost certainly due to a recent policy change at Gmail, where > they are requiring "from alignment"[1] but only for Gmail authors. > That is, Gmail does not publish a p=reject policy, but the effect on > Gmail recipients (only) is the same as if they did -- they all bounce > every time a Gmail user posts. Another way to prevent gmail users from having delivery disabled and being unsubscribed because of this is to enable VERP probes (set `verp_probes: yes` in the [mta] section of mailman.cfg). Since the probes are not sent from a gmail user, they won't bounce and the user's delivery won't be disabled. This is not a fix for the issue as the gmail users will still not receive posts from other gmail users, but they will receive other posts and won't get their delivery disabled by bounce. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Errors while importing mm2 list archives

by Mark Sapiro

On 12/8/22 07:23, Odhiambo Washington wrote: > MM3-3.3.7, Hyperkitty-1.3.6 > > While importing, I encountered several of this error: > > <CUT> > MySQLdb.OperationalError: (1366, "Incorrect string value: > '\\xF0\\x9F\\x98\\x8A, ...' for column 'content' at row 1") > The above exception was the direct cause of the following exception: ... > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/backends/mysql/base.py", That's a 4-byte utf-8 encoding for an emoji. MySQL and MariaDB have to be told to accept 4-byte encodings. In the DATABASES['default'] definition, you need to set `'OPTIONS': {'charset': 'utf8mb4'}` Also, although it doesn't affect this, see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/datab… You might also need to modify the tables, particularly hyperkitty_email with something like ``` ALTER TABLE hyperkitty_email DEFAULT CHARACTER SET utf8mb4, MODIFY subject varchar(512) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci, MODIFY content CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ``` -- 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: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 2/24/23 01:18, zoltan(a)circle-interactive.co.uk wrote: > Hi Everyone, > > we have mailman 3.3.8 venv test installation which in general works fine however > our mysql error log is filled up with messages below because they are so frequent. > > 2023-02-24 0:31:30 199567 [Warning] Aborted connection 199567 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) > 2023-02-24 0:36:30 201063 [Warning] Aborted connection 201063 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) > 2023-02-24 0:41:31 202559 [Warning] Aborted connection 202559 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) > 2023-02-24 0:46:31 204056 [Warning] Aborted connection 204056 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) See https://dev.mysql.com/doc/refman/8.0/en/communication-errors.html for information on debugging this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[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

5 years, 10 months

[MM3-users] Re: Set Postorius interface locale

by Mark Sapiro

On 3/2/21 7:55 AM, Duane Raymond wrote: > > The problems I've encountered so far are: > 1) Where do I set the local of the Postorius interface? > 2) Individual lists have a language setting, but it doesn't seem to reflect what the Postorius locales are as the only english option is "English (USA)" and none of the other English speaking locales and on the file system there is no en-us PO files....so I suspect I'm looking in the wrong place. Multiple things are required. In order to be able to set the list's preferred_language via Postorius, the language must be included in the LANGUAGES definition in postorius/utils.py. However, you can set the list's preferred_language in Mailman core via `REST` or `mailman shell` or direct update of the database. Then there must be message catalogs for the language in postorius/locale, django_mailman3/locale and hyperkitty/locale and these must be compiled by the Django management command `compilemessages`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Missing Base64 encoding from control message reply

by Mark Sapiro

I have now seen a similar instance on one of my servers. I was able to get the raw garbled response from the user. I have asked to get the raw message that was sent, but unfortunately, I haven't gotten it and I suspect I won't. I think it was an attempted post sent by mistake to the LIST-confirm address. I have tried, so far without success, to duplicate this, but I will keep at it. The raw message is attached. This one is worse than the one in the OP in that the Content-Transfer-Encoding is base64, but the content is unreadable in the raw message. It is clearly not a valid base64 encoding. I'm guessing that the original message looked similar to the one in the OP, but Microsoft Exchange garbled it by doing some attempt at base64 decoding the unencoded plain text and placing that result in the message body -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: "From address" for list moderation notification

by Mark Sapiro

On 12/29/23 10:58 AM, ronn.ramirez(a)pge.com wrote: > Hi Mailman Group, > > I noticed that the from address for list moderation notifications are coming from a certain user address. > May you please help me figure out where to change this? > > In this example, I would like to change the From address "listadmin(a)domain.com" > > ================================================================ > -----Original Message----- > From: Admin <listadmin(a)domain.com> > Sent: Thursday, December 28, 2023 12:00 AM > To: dummy-list <dummy-list(a)domainx.com> > Subject: The dummy-list(a)domainx.com list has 2 moderation requests waiting. > > The dummy-list(a)domainx.com list has 2 moderation requests waiting. > ... I do not understand "certain user address". I also don't undersatnd the above example. These notices are sent both From: and To: the list owner address. In the above example it would be From: dummy-list-owner(a)domainx.com To: dummy-list-owner(a)domainx.com Is this not what you see? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[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

3 months, 2 weeks

[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

4 years, 8 months

[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

[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, 3 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

8 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

8 months, 2 weeks

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

7 years, 11 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, 9 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

5 years, 1 month

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

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

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/9/21 12:59 PM, Duane Raymond wrote: >> What is the full error including traceback from Mailman's mailman.log >> for the shunted messages? > > My test just now raised the following error: > ...> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/member.py", line 174, in _lookup > pref = getattr(self.address.preferences, preference) > AttributeError: 'NoneType' object has no attribute 'preferences' > Mar 09 20:52:56 2021 (26271) SHUNTING: 1615323176.8137882+cd8501dd322d0ca6b4a3a187d57bc691cd0ec343 > > and running the following command raised the result below > root@mail:~# mailman qfile var/queue/shunt/1615323176.8137882+cd8501dd322d0ca6b4a3a187d57bc691cd0ec343.pck That result is as expected. It isn't the message that causes the problem. We are now back to <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> As I said there, Mailman is going through the roster of regular (non-digest) list members to find those with delivery enabled and it finds a member that has no associated address. Can you view the members of this list? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Default Setting for 'Results per Page' and other Web Pull-downs

by Mark Sapiro

On 5/5/23 14:25, Dave Hall via Mailman-users wrote: > > My question: when I go to any page that has a list (of lists, of members, > or archives), there are pulldowns like 'Results per page' that seem to > reset to the minimum number when I refresh the page. There are others like > 'Hide inactive' on the Archives page. What I'm looking for is a per-user > way to customize these values so I don't have to keep on setting them to > the value I prefer. > > If that is available in a later release then I have something to look > forward to. If not, it sure would be nice to have. No, it is not available. You can submit a wishlist issue at https://gitlab.com/mailman/postorius/-/issues/new for Postorius and https://gitlab.com/mailman/hyperkitty/-/issues/new for HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Alleviating confusion regarding"Subscription options" that are left unselected.

by Mark Sapiro

On 5/31/23 15:41, Mark London wrote: > > So instead I added the following line to the web page. Which is > displayed on other options setting web pages, but is not displayed when > you click "Manage Options" for a specific mailing list. I added this, > to the file list_options.html: > > <p>{% trans 'Any options displayed as not set here, inherit at runtime > from your global preferences (viewable on other tab)' %}</p> > <hr /> More correctly it should say "Any options showing as not set inherit at runtime from your global or address specific preferences (viewable on other tabs)" as it says, e.g., at https://lists.mailman3.org/mailman3/accounts/per-subscription-preferences/. > Although I had to fix the wording, as elsewhere it says: "Any options > showing as not set here have inherit at runtime.." That's been fixed. See https://gitlab.com/mailman/postorius/-/merge_requests/810 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: RDS CA changes

by Mark Sapiro

On 8/12/24 10:23, Hirayama, Pat wrote: > > As near as I can tell from reading the Mailman 3 docs, and looking at my mailman.cfg and settings_local.py ... I don't know that Mailman 3 is using certificate verification for the PostgreSQL connection. At least, I can't see anything in those configuration files that suggest this. Does anyone know if this is the case – or which configuration file I should look at to verify? Will my Mailman 3 be ok if the DBAs go ahead and update the certificates on their end? There are two places where the database access is defined. They are the [database] section in mailman.cfg and the DATABASES definition in Django's settings. I don't see a way in either of these to specify TLS for the connection, possibly it is set on the PostgreSQL side. In any case, I don't think there'd be any issue if the DBAs go ahead and update the certificates on their end. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

[MM3-users] Re: adding personalized email header/content in mailman 3

by Mark Sapiro

On 10/16/24 08:42, Alex I wrote: > > I tried creating a custom Handler (custom_header.py) in 3.3.19, adding outgoing_pipeline = custom_header in config [mta] section but it doesn't seem to be activating. First, can you accomplish what you want with a custom list:member:regular:header template? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… If not and you need a custom handler, you have a couple of choices. You can patch the default_posting_pipeline at mailman/pipelines/builtin.py to add your handler to the _default_handlers after installing it in mailman/handlers/. This will require you to reapply the patch after any upgrade. You can create a plugin which defines a new pipeline which includes your new handler and set the posting_pipeline attribute of your list(s) to the name of your new pipeline. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do… for some documentation and https://gitlab.com/mailman/example-mailman-plugin/-/tree/master for an example. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

[MM3-users] Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 4/20/19 8:55 AM, Kevin Hurtley wrote: > > It sounded on Github that some opinion was that it wasn't necessary to see these pending requests, but as "users will be users" I think would be useful to see what is in queue for subscription requests, it would be better yet to be able to either clear them out or accept them there. But at very least seeing them there would go a long way helping out my moderators troubleshoot. The issue with the way Postorius displayed all the subscription requests was that it wasn't possible for the moderator to distinguish request waiting moderator approval from those waiting user confirmation, and in general a moderator shouldn't approve a request waiting user confirmation, but this thread shows there is sometimes a need for a moderator to be able to deal with these. I have reopened <https://gitlab.com/mailman/postorius/issues/314>, and will look at fixing 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, 3 months

[MM3-users] Re: Hyperkitty fulltext search performances

by Mark Sapiro

On 10/4/20 8:07 AM, Brian Carpenter wrote: > > On 10/4/20 8:59 AM, Loïc Dachary wrote: >> After a little digging it turns out the mailman3-web Debian GNU/Linux >> package I'm using is configured to use Woosh as a haystack backend. >> And it is not fit for volumes greater than a few hundred mega bytes. I >> should switch to something else from the list of supported >> backendshttps://django-haystack.readthedocs.io/en/master/backend_support.html >> > For our servers running Postorius/Hyperkitty, we use Xapian. I believe > the mailman-users (MM3) list also uses Xapian. It is a lot quicker. For > our Affinity/Empathy servers, we use Elasticsearch which we are very > happy with. Elasticsearch does have a higher memory requirement I > believe than Xapian. Brian is correct about this list. We started with Whoosh, then went to Elasticsearch and ultimately to Xapian. Each step gave better performance and a smaller footprint than the one before. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: mailman2 import not working

by Mark Sapiro

On 7/29/20 9:33 AM, Abhijith PA via Mailman-users wrote: > > ------------------------------------------- > mailman create -o <foo(a)example.com> foo-bar(a)lists.example.com > mailman import 21 foo-bar(a)lists.example.com path/to/config.pck > ------------------------------------------- You don't need to specify an owner for `mailman create`. The owners will be imported. > After everything done tried a test mail, but didn't reach any of the > inbox though mail is archived. mailman.log says message is accepted > > ACCEPT: <FEE2E515-C054-41E6-9853-744D3312A137(a)xxxxxx.org> > Nothing after this. It is surprising that no exception/traceback/SHUNTING message(s) are logged. That would seem to say that Mailman's `out` runner is not running. I think Mailman's var/ directory in the Debian package is /var/lib/mailman3/, so what does `ls -aR /var/lib/mailman3/queue` show? Is there a .pck file either in shunt/ or in out/? what does `ps -fwwu list` show? There should be a lot of runner processes. Is there one with argument --runner=out:0:1? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: New messages not being archived

by Mark Sapiro

On 7/22/21 11:41 AM, Sarah H wrote: > here is the full error message. Nginx proxies on http. > > https://pastebin.com/raw/TUf5dYi8 Thanks for the log. It is basically just confirming what we see with this. > the curl commands above result in. > ... > (venv) [mailman@sysname sarah]$ curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive > curl: (52) Empty reply from server I am at a loss to understand why HyperKitty isn't responding. Are you able to access HyperKitty normally from a web browser? Do you get a response from ``` curl http://127.0.0.1:8000/hyperkitty/ ``` If so, what? What you should get from ``` curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive ``` is ``` <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct. </p></body></html> ``` You should get the same response as a web page if you go to https://example.com/hyperkitty/api/mailman/urls. Do you? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Mailman 3 questions (purge archives, list metrics, and auto discard held messages)

by Mark Sapiro

On 8/2/22 08:53, bob B via Mailman-users wrote: > Mark, > > Thanks, I know you are not a docker guy, but any idea on how to run this in the maxking docker environment? Or maxking any thoughts? > > Not sure if the docker environment has all the components or can get them all to run this script, but I have been trying to figure it out. > I assume it should be run in the mailman-web container? we are using an external database, but I don't think that should matter. Yes, it would run in the mailman-web container in the same way the `manage.py` command is run for example. Looking at https://asynchronous.in/docker-mailman/web/#django-management-commands, I think this would be something like ``` $ docker exec -it mailman-web python3 prune_arch3 yyyy-mm-dd ``` after saving the prune_arch3 file in the same place as manage.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Mark Sapiro

On 11/25/23 6:35 AM, Jered Floyd wrote: > > OK -- my turn to ask a question... > > I created a new domain and lists in my (functioning) Mailman 3 install. > > Messages to these new lists are successfully delivered via LMTP to Mailman and then disappear. They are in the shunt queue, with a source queue of "in". There are no exceptions logged in my mailman.log. When Mailman shunts a message, it always attempts to log the exception to its error.log which by default is written to mailman.log. If you can't find these messages, either you aren't looking in the right place or Mailman doesn't have permission to write the log. > Unshunting the message has no effect, and no logs are generated. Actually, the message is moved back to the `in` queue and shunted again. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Adding Mass Subscribe custom template error

by Mark Sapiro

On 1/29/25 11:20, Arte Chambers via Mailman-users wrote: > Ok I did install using the > https://docs.mailman3.org/en/latest/install/virtualenv.html > > I added > ``` > POSTORIUS_TEMPLATE_BASE_URL='https://www.example.com/' > ``` I hope you didn't add the above literally without replacing www.example.com with your actual host name. It should be ``` POSTORIUS_TEMPLATE_BASE_URL = 'list.louisvillecommunitygrocery.com' ``` > to /etc/mailman3/settings.py and restarted mailman services > > However I'm still getting the same error from mailman.log > > requests.exceptions.ReadTimeout: HTTPConnectionPool(host='localhost', > port=8000): Read timed out. (read timeout=5) I don't understand why it should still be trying to connect to localhost:8000. Also, I don't understand why localhost:8000 times out. What is your setting for localhost in /etc/hosts? it should be `127.0.0.1`. If it is `::1` that could be the issue. > Not sure if I'm editing the correct config file. /etc/mailman3/settings.py should be correct. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Mark Sapiro

On 1/18/20 6:58 AM, Torge Riedel wrote: > Am 16.01.20 um 21:43 schrieb Mark Sapiro: >> >> This won't work for posts from members because the header checks are >> done between member moderation checks and non-member moderation checks, >> but if you create a Header Filter for header 'x-spam' and pattern 'yes' >> with action hold, a message from a non-member which has an X-Spam: Yes >> header should be held for that reason. >> >> > Hi Mark, > > thank you for your answer. Just to understand that right: In case a > posting with an "X-Spam: Yes" header comes from a member, it will not be > held? It will be directly forwarded to the list? No. I apologize for being unclear. A post from a member will first be handled according to that member's moderation action which may be the list's default action for posts from members or a specific action for that member. If that moderation action is reject, discard or hold, the post will be rejected, discarded or held as a moderated member post regardless of any header filters. If the action is accept, the post will be accepted without any further checks including the header checks. If the action is defer (default processing) the message will be held for matching the X-Spam: Yes header. What I meant was if the member's (or default) action was hold, the post would be held, but the reason would be moderated member, not header match. The bottom line here is the moderation action of accept should only be used in cases of a highly trusted member (such as a list owner) because it bypasses other checks, but the address is still subject to spoofing. In the normal case where a moderation hold is not desired, use the defer (default processing) action. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 9/10/22 22:22, Stephen J. Turnbull wrote: > > Will let you know if I find anything. Mark will be back soon, too. Yes, I'm back and am looking at this. I'm looking at the traceback at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and I would like to get a copy of the shunted 1662376669.3194733+25b74de3b7cd8a28d0c3cf5b6cc6fc582726efec.pck file. If that is not available, any of the shunted files from the same `Uncaught runner exception: 'list' object has no attribute 'encode'` will do. Also, the same post contains a traceback from mailman_hyperkitty indicating the message has no Message-ID header. This is possibly related to the fact this is an anonymous list. For anonymous lists, the original Message-ID is removed because it can reveal the sender's domain, but it should always be replaced by a generated one. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/clean… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users]Re: [Mailman-Users] Mailman3 administration

by Mark Sapiro

On 6/24/16 8:18 AM, John Griessen wrote: > On 06/18/2016 02:10 PM, Mark Sapiro wrote: >> I think in the >> long run, you'd be better off with Mailman 3. > > > Is it time to install version 3? > > Is that going to work with different rewrite rules behind nginx? > > Will it cure my problem with moderation and nginx and https? If you are going to post to mailman-users(a)mailman3.org, please join the list. That way you will see replies to your posts such as the one at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. You can join at <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/>. The reply addresses your first question. With respect to your other questions, I think you have resolved your http/https issues in MM 2.1. MM 3 works similarly, but perhaps more obviously. When you create a domain in MM3 you specify a web URL for the domain's web UI. If this is an https URL, you won't have the issues you saw. There is another way to address this, and that's in the web server (nginx in your case) when you configure the web server to redirect http to https with a 301 Moved Permanently status (or maybe a 302), this tells the browser to issue a GET for the new URI, even if the original request was a POST. Thus the POST data is lost. That is the underlying issue. If instead, you configure the web server to issue a 308 Permanent Redirect instead, this tells the browser to issue a request for the new URI using the original GET/POST/whatever method, so the browser SHOULD reissue the original POST to the new URI. This will work provided the browser recognizes 308 and acts appropriately. Thus, fixing the scheme in Mailman is the more reliable solution as it doesn't depend on the browser knowing what to do. See, e.g., <https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#3xx_Redirection>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] Re: Customizing Look and Feel?

by Mark Sapiro

On 12/27/18 7:42 PM, Joel Lord wrote: > Is it possible to customize the look at feel of the web interface at > all? I have some lists that really require that subscription requests > include full name, to make the workload on the moderators, well, > workable in keeping a closed list tight. I've found where the "Your > name (optional)" text is in list_forms.py, but modifying that strikes me > as a poor plan. > > Changing that text would be lovely. Actually making that field required > would be seriously awesome. > > Is this possible in the current code base (3.2.0) without doing > ill-advised things modifying source code? None of this is really possible in Postorius without modifying source code. However, Postorius is just an example of a web list management UI. While it is non-trivial, it is possible to build your own web UI that either communicates directly with Mailman core's REST API or communicates via MailmanClient. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Disabling max_message_size and send_welcome/goodbye_msg globally or by API

by Mark Sapiro

On 10/10/2017 12:04 PM, Peter Mueller wrote: > > is it possible to turn off max_message_size and send_welcome_msg / > send_goodbye_msg globally? Not for existing lists, but for new lists you can create a style with these settings and make it the default style. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> for how you might do that. > If there are no global options, how can I turn off these feature using the > REST API? > In python you can do it with >>> mlist.max_message_size = 0. > If I send a PATCH request to lists/some@list/config with body > max_message_size=0, I get "Unknown attribute". Same for send_welcome_msg > and send_goodbye_msg. max_message_size and send_goodbye_msg are not currently exposed in REST. See the definition of ATTRIBUTES in mailman/rest/listconf.py for what is. You should be able to PATCH send_welcome_msg via REST. I don't know why that didn't work for you? -- 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: SUBSCRIBE_FORM_SECRET in MM3?

by Mark Sapiro

On 1/30/20 1:50 AM, Gila Halpern wrote: > I've been looking into ways to prevent spam on my company's list, and one thing I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman configuration, which embeds a CSRF token into the form, and prevents it from being submitted until five seconds after it renders, to keep bots from subscribing. Unfortunately, the information I found pertained to Mailman 2. Does this option exist in MM3 as well, or is there a similar option? This feature in MM 2.1 is not very effective. On mail.python.org, this feature as well as reCAPTCHA is enabled (e.g. <https://mail.python.org/mailman/listinfo/mailman-users>) and we still get periodic attacks of robotic subscribes that get around these measures. To answer your question, no, this does not exist in Postorius which is an entirely different, Django based web UI. Django may have some protections built in; I'm not sure about that, but there's nothing in Postorius itself like this MM 2.1 feature. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Installation Wooes

by Mark Sapiro

On 5/2/20 12:51 AM, Samir Faci wrote: > A few questions about an Ubuntu install. > > I managed to add my domain to hyperkitty, created a new list and now i'm > getting this behavior: > AttributeError: module 'time' has no attribute 'clock' > I'm on python 3.8.2 It time.clock() went away in Python 3.8. Mailman versions older than 3.3.0 are not compatible with Python 3.8. You need to upgrade Mailman core. > Question #2. I'm setting up mailman 3 on sqlite for simplicity's sake. Do > people find the performance of mysql / postgres worth the upgrade? It depends on the size of your installation - how many lists, how many list members, frequency of posts and so on. You may find <https://www.digitalocean.com/community/tutorials/sqlite-vs-mysql-vs-postgre…> of interest. > 2B. Is there a migration path if I want to switch to mysql at a later date? The migration path mostly consists of migrating the data from the SQLite database. -- 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: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Mark Sapiro

On 6/15/20 12:37 PM, Gilles Filippini wrote: > > There are 4 emails stored into this folder. 3 of them are spam, and the > last one is a legitimate email. This is annoying that such emails could > accumulate and stay into var/archives/hyperkitty/spool/ forever, causing > more and more hyperkitty errors. > > Any idea how to make their processing more error proof? Change the offending .encode() method to add errors='replace'. The traceback from the error should tell you where it is. You could also open an issue at <https://gitlab.com/mailman/hyperkitty/-/issues> for us to look at. If you do that, please include an error traceback if possible. If there is not a traceback in mailman.log associated with the error, there might be one in HyperKitty's log (configured in Django's settings). Also, including enough of a message to duplicate the issue is very helpful. -- 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: The doubled entries issue

by Mark Sapiro

On 11/11/23 23:56, Lars Bjørndal wrote: > > Thank you. The script I try to run, is found here: https://gitlab.com/mailman/mailman/-/issues/657 > > I named the script fix-doubled-entries.py. When I try > > `mailman shell --run ./fix-doubled-entries.py` I get: This is not the way to run a script with `mailman shell`. See ``` mailman shell --details ``` for info. However, that script cannot be run as is by `mailman shell --run`. It can be run by invoking `mailman shell` interactively and copying and pasting it, or if your Mailman is installed in a venv it can be run with the venv active by `python ./fix-doubled-entries.py`. However, that script will not fix your issue because you don't have multiple mhonarc entries for a list. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and as it says, Tell us more about the "duplicate entries" error, and if possible copy it exactly from where you found it originally, including any traceback. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: add / remove / set moderation bit of non-members via mailman shell

by Mark Sapiro

On 2/7/24 02:37, Zaheer Abbas wrote: > > I do the above via postorius because I couldn't find a way to do this via > mailman shell. Something like ``` mark@msapiro:~$ mailman shell -l list(a)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(a)example.com mailing list >>> NEW_NONMEMBERS = [('First User', 'user1(a)example.com'), ... ('Second User', 'user2(a)example.com'), ... ('Third User', 'user3(a)example.com'), ... ] >>> from mailman.app.membership import add_member >>> from mailman.interfaces.subscriptions import RequestRecord >>> for display_name, email in NEW_NONMEMBERS: ... record = RequestRecord(email, ... display_name=display_name, ... delivery_mode=None, ... ) ... member = add_member(m, record, role=MemberRole.nonmember) ... member.moderation_action = Action.accept ... >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: No resend after delivery bouned

by Mark Sapiro

On 1/31/22 06:47, Axel Rau wrote: > My listserver has been blocked with 550 and I received > bounce score on <list_add> has been incremented. > notifications. > After resolving the block issue, I'm now waiting for mailman to resend > the mails. > Now, after 3 hours, nothing has happened so far. And nothing will. Mailman sent the message originally and when it was done sending it, it discarded the outgoing message. The message may have been archived depending on the list's archiving settings, but that's it. No version of Mailman 2.1 or Mailman 3 has ever automatically resent bounced messages. If the failures are temporary, the MTA should keep the message queued and retry up to a limit before reporting a bounce, but that's it. The best you can do is get the messages from the archive (you can export a mbox from Hyperkitty or get the messages from Mailman's var/archives/prototype/LIST_ADDRESS/new/ directory) and manually resend them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 1/30/23 10:32, Jeremy Stanley wrote: > > I'm not having any luck finding an API or CLI which I > can use to create sites and domains rather than manually doing it in > the Django admin WebUI. Does such a thing exist, or an I going to > need to resort to directly performing database inserts (which I'd > rather avoid since it could break if the schema changes). It appears > there's a foreign key relationship involved, which could make DB > manipulation like this even more fragile. Domains can be created via Postorius or via the Mailman Core REST API that postorius uses or implicitly by the `mailman create` command when creating a list in a new domain. However, none of this can create a new site. You can do this through the Django admin site at sites/site/add/. See https://docs.djangoproject.com/en/4.1/ref/contrib/sites/ for methods you can use to do this programmatically. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Mark Sapiro

On 8/5/24 12:45, Odhiambo Washington via Mailman-users wrote: > > Yes, those are Cloudflare IPs and I don't know why 2! > All I know is that in DNS, I created an A record for the hostname and chose > the "proxy" option in the cloudflare DNS management interface. OK, I know nothing about how cloudflare proxying works, so ignoring that and assuming it's OK, ... ... > I don't know. However, those IPs you see in the Nginx logs, none belong to > me! I have two possible IPs - one domiciled in KE and another domiciled in > the US (when I use VPN). I think I've misunderstood. Is it the case that the messages you report like /opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css" failed (2: No such file or directory) ... are in the nginx log on the mailman server. If so, see https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura…. Is that what you have? If not, post your nginx configuration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: RHEL 7 + Mailman 3 : Need help and guidance

by Mark Sapiro

On 7/15/19 8:27 AM, vgandhi(a)fdu.edu wrote: > Thank you so much for the guidance. We ended up installing version 2.1.15 on RHEL7 using yum. We don't want mailing lists' email addresses with the same domain as the server has. For example: server is example1.fdu.edu . We would like to have email addresses of the mailing lists to end with @fdu.edu so that someone sends email to list1(a)fdu.edu and the subscribers of the the mailing list list1 will receive it. Can you please provide us some guidance on how can we accomplish this? This is not the list for Mailman 2.1 questions. Please join the mailman-users(a)python.org list at <https://mail.python.org/mailman/listinfo/mailman-users> and post your request there. Also note that while the RHEL7 package for Mailman may be 2.1.15, that version is 7 years old and the current release is 2.1.29. You may wish to install from source - <https://www.list.org/mailman-install/>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Running mailman3 on AWS and dealing with SES email verification

by Mark Sapiro

On 5/1/20 6:54 AM, Mohsen Masoudfar wrote: > Thank you Mark, this is really very helpful. I am going to work on the details. It would be breat, if there were a way to set some of this options as default, like DMARC mitigation is default to no, I changed it to unconditionally and replace From to with list address and got good results, but the default is no. How may I changed the default, do that the list owner/creator does not need to update these fields. There are two ways to do this. Both require some code modification. The simplest is just to change the lines at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py…> to: mlist.dmarc_mitigate_action = DMARCMitigateAction.munge_from mlist.dmarc_mitigate_unconditionally = True The other way is to create a new list style that has these settings and chose it when creating a list. See <https://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: spanish localization

by Mark Sapiro

On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > I contributed in january to translate to spanish all the items left in > Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I > thought they will be used in the next upgrade, but I cannot see any > improvement and there are many words untranslated. The Spanish translations for Mailman core and HyperKitty are currently completely up to date with weblate. django-mailman3 differs in one string that was translated on Feb 10 and hasn't yet been merged. Postorius also differs in a few places from the Feb 10 version that hasn't yet been merged. Other than that, the translations should be good. > Is there any way to upgrade the .po files in order to get the last > translation? For the web UI you need to run the django management `compilemessages` command. For Mailman core you need to run ``` cd mailman/messages/es/LC_MESSAGES msgfmt -o mailman.mo mailman.po ``` to compile the mailman.po file for gettext. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: [EXTERNAL] [Mailman-Users] Re: Help with 'The message has no valid senders'

by Mark Sapiro

On 5/19/21 10:37 AM, McGuire, Tommy M. (MSFC-IS90)[EAST2] wrote: > > Here are (what I think are :-)) the anonymized relevant parts of the smtp.log. > > May 19 08:52:29 2021 (126270) _handle_client readline: b'MAIL FROM:<aaaaaaaaaa.a.aaaaa-1(a)nasa.gov> SIZE=11726\r\n' > May 19 08:52:29 2021 (126270) ('127.0.0.1', 52130) >> b'MAIL FROM:<aaaaaaaaaa.a.aaaaa-1(a)nasa.gov> SIZE=11726' > May 19 08:52:29 2021 (126270) ('127.0.0.1', 52130) sender: aaaaaaaaaa.a.aaaaa-1(a)nasa.gov > May 19 08:52:29 2021 (126270) ('127.0.0.1', 52130) << b'250 OK' > ... > May 19 08:52:29 2021 (126270) DATA readline: b'From: "Aaaaa, Aaaaaaaaaa A. (location)[employer,\r\n' > May 19 08:52:29 2021 (126270) DATA readline: b' Inc.]" <aaaaaaaaaa.a.aaaaa-1(a)nasa.gov>\r\n' That all looks good. I don't understand what's wrong. Can you apply the attached patch to mailman/rules/no_senders.py and see what you get in Mailman's debug.log. -- 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: Upgrading packages

by Mark Sapiro

On 10/13/22 10:55, Eggert Ehmke wrote: >> >> It shouldn't have been necessary to apply any patch. The head of the >> GitLab hyperkitty master branch is already compatible with mistune 2.0.4 > > strange, I still had the line with the (not working) > from mistune.scanner import escape_html, escape_url > > maybe because the migration step was not working at that time? It should have nothing to do with migrations. The command ``` pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master ``` run as the mailman user with your venv active should have set the content of venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py to be the same as https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/renderer…, but it didn't. I wonder what else didn't get upgraded? Clearly it did do something because mistune was upgraded. If you run `pip freeze` in your active venv,, what versions do you see for the things you upgraded? Do they look for example like ``` HyperKitty @ git+https://gitlab.com/mailman/hyperkitty@cf585a6588a176e714ec32bbcfe52e8a2… ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Mark Sapiro

On 4/25/24 14:01, Thomas Stein wrote: > Am 2024-04-25 22:03, schrieb Mark Sapiro: >> >> I don't know how things are arranged in the Debian/Ubuntu package, but >> you may have a settings.py which at the end does something like >> ``` >> try: >> from settings_local import * >> except ImportError: >> pass >> ``` >> If that is the case, adding the above snippet to the end of >> settings_local.py should work. > > Yes, that's the case. I added the snippet in question to > settings_local.py but this leads to another error: > > File "/usr/share/mailman3-web/settings.py", line 503, in <module> > from settings_local import * > File "/usr/share/mailman3-web/settings_local.py", line 194, in <module> > x = list(MIDDLEWARE) > ^^^^^^^^^^ > NameError: name 'MIDDLEWARE' is not defined > dpkg: error processing package mailman3-web (--configure): Yes. I understand. In your case, MIDDLEWARE is only defined in settings.py and not in settings_local.py. As I understand it originally you added ``` x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` to settings.py and you say it didn't help. I don't know why that wouldn't work as long as there is no setting for MIDDLEWARE in settings_local.py and you added that after the MIDDLEWARE setting in settings.py. When you say it didn't help, do you mean you still get the django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE message or something else? I note that the original post in this thread refers to /etc/mailman3/mailman-web.py which is presumably where the package ultimately puts the Django settings, and I don't know what `dpkg --configure` is doing. One thing you could try is in settings_local.py, put ``` from settings import MIDDLEWARE x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` to work around the NameError. -- 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

[MM3-users] Re: update_index

by Mark Sapiro

On 04/03/2018 09:02 AM, Darren Smith wrote: > Hello, > > If I'm reading the docs correctly, when we run manage.py update_index, it > should be an incremental index of new emails that have been added since the > last time update_index was run - can anyone confirm that this is the > expected behavior? Or is there another command line option that I am > missing? There are two ways to run update_index. Hyperkitty's update_index is incremental and is run by manage.py runjob update_index Running manage.py update_index runs haystack's update_index which with no options does a full update. Run manage.py update_index --help to see the options. The incremental 'manage.py runjob update_index' should be run every minute by 'manage.py runjobs minutely' assuming cron is running the periodic Django jobs, so running either update_index job manually shouldn't be necessary ... > So...can anyone help with how to get the update_index to do only emails > added since the last time the update_index was run? manage.py runjob update_index -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Avoiding reply to list when User does "Reply To All"

by Mark Sapiro

On 06/19/2018 05:06 AM, Asaf Ohayon wrote: > hello > > I've played with explicit reply-to address, and "Reply goes to list" -> > "Explicit Reply-to headers set", > And it works fine when user does "Reply" in the client (e.g: gmail), > But when she presses Reply To All, still it sends also to the list, > > Is there some way to avoid this ? The short answer is No. Even with Full Personalization where Mailman puts the recipient address in the To: header, it will still put the list address in Cc: to facilitate replying to the list. If you want a list that members can't post to, the article at <https://wiki.list.org/x/4030685>, while aimed at Mailman 2.1 and older, has some information that is relevant and in Mailman 3, creating a list with the "Announce only mailing list style" is at least a start. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: Bug - if you change primary email address, you're "semi-subscribed"

by Mark Sapiro

On 5/24/19 5:38 AM, roger(a)reasonal.com wrote: > For what it's worth, I subscribed with my work address, sent a couple of posts to the list, then because of the annoying auto-adding of our corporate email branding, I added a new email address, verified it, made it primary and then deleted the old address. I think there are two issues in this thread. The one we're discussing here is that following the above changes, you received a list welcome message at the new address, but not until you posted from that address. Is that correct? The other issue you've mentioned is posts via email disappearing. My questions regarding that are: Have you tried posting via email from this address? Please try replying to this post by email and see if that works. From what address and when as best as you can recall did you post the messages that disappeared? -- 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: Mailman 3 installation from latest Debian packages

by Mark Sapiro

On 2/12/21 4:49 AM, Matthew Blissett wrote: > Hi, > > I've installed mailman3-full 3.3.3-1 from Debian bullseye (Debian testing). > > The dropdown controls on the UI for Postorius (e.g. "Subscription > requests", "Mass operations" and the username button to log out) and the > similar controls on Hyperkitty (e.g. "Threads by month") do not work. > You can see the latter at > http://newlistszm.gbif.org/mailman3/hyperkitty/list/test@newlistszm.gbif.or… Everything works as expected at <https://lists.mailman3.org/mailman3/> and <https://mail.python.org/mailman3> which are installed from source. > Could this be a problem with the Debian packaging, or perhaps my > configuration -- which is very close to the defaults (i.e. Mailman and > Apache configuration generated by dpkg). I can't speak to the Debian package possibility, but it might possibly be related to the way your browser handles the javascript. I don't know anything in configuration that would cause this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Configure administrative users via command line?

by Mark Sapiro

On 7/18/23 11:38, kjohnson(a)eclypse.org wrote: > > How can I configure administrative users via command line? I need to process a moderation request. I have root access on the server. A pointer to the appropriate documentation would be more than welcome. Thank you to anyone who can provide help. I'm not sure what you want. If you are an owner or moderator of a list or a superuser, you can handle moderation requests via Postorius. If you are a list owner or a superuser, you can manage owners and moderators via Postorius. You can add superusers via the command line django admin `createsuperuser` command. It might be good if the command line `mailman addmembers` and `mailman delmembers` commands accepted a `role`, but they don't. You can manage owners and moderators via the REST API which you can access via curl. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. You can also do this via `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Post-installation documentation?

by Mark Sapiro

On 11/26/21 9:49 AM, David Newman wrote: > On 11/25/21 1:16 PM, Mark Sapiro wrote: >> >> What django admin command are you running? > > As the mailman user, with venv activated: > > (venv) mailman@lists:~$ hyperkitty_import -l testlist(a)lists.domain.com > /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox hyperkitty_import is not a command. it is a subcommand to the django administration command. You need to run ``` mailman-web hyperkitty_import -l testlist(a)lists.domain.com /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox ``` ... >> If you don't set DJANGO_SETTINGS_MODULE in the environment and you >> have activated your virtualenv and run `mailman-web` as the django >> admin command it will set /etc/mailman3/settings.py as the settings. > > I'd run these two environment commands as the mailman user with > virtualenv activated: > > export DJANGO_SETTINGS_MODULE=settings > export PYTHONPATH=/etc/mailman3/settings.py That should be ``` export PYTHONPATH=/etc/mailman3/ ``` but you don't need these. > Am I being overly literal here with 'settings' in that first command? > Asking because 'mailman-web check' runs clean before running these > commands and returns this error afterward: > > ModuleNotFoundError: No module named 'settings' Yes, the mailman-web command sets these up correctly if they aren't set, but if they are, it believes what you set which was wrong for PYTHONPATH. Don't set those environment variables and let mailman-web do it for you. > Either way, the hyperkitty_import command still isn't found. Again because it's not a command but a `mailman-web` subcommand. >> By default, only lists that you are owner, moderator or subscriber for >> are shown. What if you click Filter by Role and select All? > > Same result. In this case, the ID of the admin and list owner are the same. Have you set FILTER_VHOST = True in your settings.py. If so, that could possibly explain it. Can you access these lists at something like https://example.com/mailman3/lists/listname@example.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, 8 months

[MM3-users] Re: Query on how to change moderator message to non-members

by Mark Sapiro

On 7/4/18 2:36 PM, robert.kydd(a)gmail.com wrote: > Hi Mark, my apologies it is version 2.1.26 This list is really for Mailman 3. The list for Mailman 2.1 is mailman-users(a)python.org <https://mail.python.org/mailman/listinfo/mailman-users>. > 1. Do I find Mailman's file system using cPanel ? In cPanel Mailman, Mailman's file system is at /usr/local/cpanel/3rdparty/mailman. > 2. Your quote: > with the various UPPERCASE things replaced appropriately and then > 'compile' it via > ... > msgfmt -o messages/en/LC_MESSAGES/mailman.mo > messages/en/LC_MESSAGES/mailman.po > > Does the compiling happen when I use mailman or do I have to have a compiler for this to happen ? The compiler is msgfmt. There may be a msgfmt installed with cPanel, but in any case, there is a Mailman version so you should be able to do cd /usr/local/cpanel/3rdparty/mailman bin/msgfmt.py -o messages/en/LC_MESSAGES/mailman.mo \ messages/en/LC_MESSAGES/mailman.po -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/2/22 4:03 AM, Michael Heseltine wrote: > > I have no idea whatsoever what this HAYSTACK_CONNECTIONS thing is, nor have I found anything in the HowTo. The HowTo you are following under `Setup Directories and Files for Mailman 3` includes # touch /opt/mailman/mm/settings.py (copy of the mailman-suite settings.py file but with DEBUG = False) While I would have written this section differently to emphasize you actually need to copy the content and not just `touch` (i.e. create) the file, `mailman-suite settings.py` is a link to https://gitlab.com/mailman/mailman-suite/blob/master/mailman-suite_project/… and that in turn contains: ``` # # Full-text search engine # HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), # You can also use the Xapian engine, it's faster and more accurate, # but requires another library. # http://django-haystack.readthedocs.io/en/v2.4.1/installing_search_engines.h… # Example configuration for Xapian: #'ENGINE': 'xapian_backend.XapianEngine' }, } ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 7/9/22 9:00 AM, kisner(a)live.com wrote: > So I went and created /opt/mailman/web/logs, did chown -R mailman.mailman /opt/mailman, ran it again and got this (and this is probably where I stopped last time): > > (venv) mailman@lists:~/web$ mailman-web migrate ...> ImportError: cannot import name 'escape_html' from 'mistune.scanner' (/opt/mailman/venv/lib/python3.9/site-packages/mistune/scanner.py) ... > django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'hyperkitty.templatetags.decorate': cannot import name 'escape_html' from 'mistune.scanner' (/opt/mailman/venv/lib/python3.9/site-packages/mistune/scanner.py) This is https://gitlab.com/mailman/hyperkitty/-/issues/431, fixed by https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 but not yet released. The easiest fix is to apply this patch ``` --- a/hyperkitty/lib/renderer.py +++ b/hyperkitty/lib/renderer.py @@ -4,7 +4,7 @@ from django.conf import settings import mistune from mistune.plugins.extra import plugin_url -from mistune.scanner import escape_html, escape_url +from mistune.util import escape_html, escape_url class MyRenderer(mistune.HTMLRenderer): ``` -- 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: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Mark Sapiro

On 5/6/23 16:02, volkmar(a)grote-family.com wrote: > > My urls.py: >> (venv) mailman@me:/opt/mailman/mm$ grep -v "^#" urls.py >> from django.contrib import admin >> from django.urls import include, reverse_lazy, re_path >> from django.views.generic import RedirectView >> >> urlpatterns = [ >> re_path(r'^$', RedirectView.as_view( >> url=reverse_lazy('list_index'), >> permanent=True)), >> re_path(r'^postorius/', include('postorius.urls')), >> re_path(r'^hyperkitty/', include('hyperkitty.urls')), >> re_path(r'', include('django_mailman3.urls')), >> re_path(r'^accounts/', include('allauth.urls')), >> # Django admin >> re_path(r'^admin/', admin.site.urls), >> ] We and the various docs are inconsistent about 'postorius' vs 'mailman3' and 'hyperkitty' vs 'archives' in urls. Add these re_path(r'^mailman3/', include('postorius.urls')), re_path(r'^archives/', include('hyperkitty.urls')), to your urlpatterns list in urls.py to cover both variants. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Link in the top-left corner of Hyperkitty

by Mark Sapiro

On 5/8/20 10:36 AM, Seth Seeger wrote: > > I believe this is what I’m seeing. I was able to change the displayed name by changing the original entry in Django. That name displays no matter what the URL hostname is. This is strictly a Django thing. The HyperKitty template, hyperkitty/templates/hyperkitty/navbar-brand.html, contains this: <a class="navbar-brand" href="{% url 'hk_root' %}">{{ site_name }}</a> {{ site_name }} is provided by Django when the template is rendered. In my case in my test installation, I have three sites in django.Sites: Domain name Display name example.com example.com msapiro.net msapiro.net msg1.msapiro.net msg1 example.com is a dummy, and it is also referenced in my settings by SITE_ID = 0 which may have something to do with my success, but if I go to HyperKitty via https://msapiro.net/, I see the site name msapiro.net, and if I go via https://msg1.msapiro.net/ I see the site name msg1. -- 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: Is there a "global" max_message_size?

by Mark Sapiro

On 6/19/20 4:03 AM, skenny(a)scss.tcd.ie wrote: > > Jun 19 11:44:50 venus postfix/lmtp[17630]: C0C7928564: to=<mj(a)lists.scss.tcd.ie>, relay=172.19.199.2[172.19.199.2]:8024, delay=109, delays=2.2/0.04/0.01/107, dsn=5.0.0, status=bounced (host 172.19.199.2[172.19.199.2] said: 552 Error: Too much mail data (in reply to end of DATA command)) > > So 172.19.199.2 is complaining about "Too much mail data". That's the IP address of the mailman-core container. I'm wondering why this is happening, and where the decision is being made, as it seems at odds with the fact that the mailing list has no limit on message size. Mailman's lmtp runner which implements the server that receives mail via LMTP uses the aiosmtpd.lmtp.LMTP class to implement the server. This has a default size limit of 33554432 bytes (32 MB) and that's where the "552 Error: Too much mail data" comes from. There is also the message_size_limit setting in postfix. Presumably you've changed that because it defaults to 10240000 bytes (about 10 MB). -- 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: Moderation for nested mailing lists

by Mark Sapiro

On 11/18/20 8:48 AM, peterbw(a)gmail.com wrote: > Hi Everyone, > > I have a list that has other mailing lists as members. When a non-member posts to this list I receive a moderation message. After approving the moderation message I then receive a lot of other moderation messages for the sub-lists that are members of the "top-most" list (since the non-member is not a member of any of the sub-lists). Is there any way to approve a message for moderation once and have all sub-lists automatically approve the message? That capability doesn't exist. If the poster were a member of the top-most list this issue <https://gitlab.com/mailman/mailman/-/issues/794>, currently not fixed, would apply, but for non-members, even that wouldn't do. If the same nonmembers post repeatedly, you could set the moderation action for their various non-member records to defer to accept their posts without moderator intervention, but for one-offs, this doesn't save any effort. -- 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: HyperKitty failure

by Mark Sapiro

On 1/1/22 2:31 AM, horvath.arpad.szfvar(a)gmail.com wrote: > In the /var/log/mailman3/smtp.log I have at the same time: > > Jan 01 10:54:37 2022 (126980) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > Jan 01 10:54:37 2022 (126980) Peer: ('127.0.0.1', 54816) > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) handling connection > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) Data: b'LHLO yyy.hu' > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) Data: b'MAIL FROM:<horvath.arpad.szfvar.nospam(a)gmail.com>' > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) sender: horvath.arpad.szfvar.nospam(a)gmail.com > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) Data: b'RCPT TO:<test(a)lists.xxx.hu>' > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) recip: test(a)lists.xxx.hu > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) Data: b'DATA' > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) Data: b'QUIT' > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) connection lost > Jan 01 10:54:37 2022 (126980) Connection lost during _handle_client() This is all normal and expected for a post from horvath.arpad.szfvar.nospam(a)gmail.com to test(a)lists.xxx.hu. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Virtual alias + shell

by Mark Sapiro

On 5/26/23 9:51 AM, alopez(a)ac.upc.edu wrote: > Now I have created the mailing list with 'mailman create' but I get this error: > > postmap: warning: /etc/postfix/main.cf, line 65: overriding earlier entry: virtual_alias_maps=hash:/etc/postfix/virtual_alias/example.edu, hash:/etc/postfix/virtual_alias/example.org > > in my postfix file I have the following code: > > virtual_alias_maps = hash:/etc/postfix/virtual_alias/example.edu, > hash:/etc/postfix/virtual_alias/example.org, > hash:/var/lib/mailman3/data/postfix_vmap > > Should I remove hash:/etc/postfix/virtual_alias/example.edu, and hash:/etc/postfix/virtual_alias/example.org, ? In that case how I create alias not related to mailman? Without seeing the contents of those files, I can't say, but something in /var/lib/mailman3/data/postfix_vmap is conflicting with and overriding something in the other two files. Since the only things in /var/lib/mailman3/data/postfix_vmap are specific list addresses, they are probably what you want, and you could just ignore the warning, but you probably do want to examine and remove conflicts from the other two files. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 10/1/24 13:17, jkoral(a)luc.edu wrote: > Here is my plan for forwarding. Let me know if this looks correct. First off, I deleted the list off of the old server, so I am assuming that removed the alias as well. > > -Create new alias file in /var/lib/mailman/data/ called migratedaliases (this directory is where the aliases file is currently located, but under the aliases file). > -Edit /etc/postfix/main.cf and add the path to migratedaliases to alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases. After editing, it will look like this: alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases, hash:/var/lib/mailman/data/migratedaliases. > -Run newaliases command to update the aliases db. > -Then add the alias for the the migratedaliases file the way you posted above. > > Does that make sense? Yes On 10/1/24 13:19, jkoral(a)luc.edu wrote: > Or can I just put the forwarding alias in /etc/aliases? Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months

[MM3-users] Re: List description as sender

by Mark Sapiro

On 09/14/2018 05:35 AM, Henrik Rasmussen wrote: > When receiving a mail from Mailman 3, the From: User name is the description of the list, like From: Long desription of the list for all members of certain project <project(a)lists.example.com>. > > Starting to get old, I recall something about a discussion we once had on http://mail.python.org/pipermail/mailman-users/, but I don't recall the reason for this and I can't find the discussion, so it might be something I dreamed. Specifically what messages are you talking about? The only case I see offhand where the From: is as you describe is in posts from an anonymous list. In any case, the list description is described in Postorius as "This description is used when the mailing list is listed with other mailing lists, or in headers, and so forth. It should be as succinct as you can get it, while still identifying what the list is." I.e., it shouldn't be a long description. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Emergency Moderation

by Mark Sapiro

On 5/25/20 8:21 PM, Allan Hansen wrote: > > Not sure what is the difference between ‘emergency moderation’ and ‘Hold for moderation.’ It appears redundant. `emergency` moderation is meant for emergencies such as flame wars on and otherwise open list. It trumps essentially everything else except pre-approval with and Approved: <password> header. It is not really intended as a "normal" list setting, although it can be used that way if you want to hold all posts. The default action "Hold for moderation" for members and non-members only applies to those whose individual moderation is set to "List default". To fully understand the difference, you have to know the order in which the various checks are applied. This is defined at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/builtin…>. You will see for example that emergency with a hold action comes before banned-address with a discard action. This means that if emergency is True, a post from a banned address will be held and not discarded, at least initially. -- 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: MM3 to MM3 migration

by Mark Sapiro

On 1/31/23 13:34, David Newman wrote: > > Is this really as simple as building the new server, creating the same > lists on the new server, and rsync’ing the archives from the old server? > If not, how to do the migration? If you want to mirror the entire installation, you can dump the databases off the old server and import them to the new server. Depending on the installation, everything may be in one database or there may be separate ones for mailman core and mailman web. This is a little tricky because some of the tables have to do with Django stuff. To do only selected lists is much more difficult and there are no scripts that I am aware of. HyperKitty can dump a list's archive as a mbox which could then be used as input to hyperkitty_import on the new server to move archives, but there are no similar scripts to dump list settings, users, memberships, etc. in a format that can be imported. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Moderated unsub requests are not provided by mailman3 service

by Mark Sapiro

On 11/29/24 4:47 PM, Joachim Schrod wrote: > > The unsubscriptions requests are not shown in the web interface. I > suppose they should appear in the UI section "Subscription requests", > either as "Pending Approval" or "Pending Confirmation". (Frankly, I > don't understand the difference between these two options at all.) Subscriptions pending confirmation are those waiting for the user to confirm. Those pending approval are waiting for moderator approval. Unsubscription requests not being shown is https://gitlab.com/mailman/postorius/-/issues/332 which was fixed in Postorius 1,3.6 released over 3 years ago. Current release is 1.3.13. > System information: mailman3 3.3.3; Postorius (mailman3-web) 1.3.4; > both on Debian 11 (bullseye). > > I know that this is out of date; thus a definitive info "this is fixed > by now" is quite OK for me. (Debian upgrade is planned as the next > action after getting Mailman3 to work for that use case.) Yes, this is fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months

[MM3-users] Re: Errors in MM3

by Mark Sapiro

On 4/7/25 04:08, Odhiambo Washington via Mailman-users wrote: > I am using uwsgi+APache2. > I am suddenly seeing hundreds of errors in my mailmanweb and uwsgi logfiles: > > 1. mailmanweb.log has hundreds of such lines: > [WARNING] [2025-04-07 13:01:50,162] [log] 317562 139768548886080 Method Not > Allowed (GET): /archives/list/ > kictanet@lists.kictanet.or.ke/message/YOPKCEWPHX4BV7U5MOTCVCNSWR2J2JOZ/vote ... > [WARNING] [2025-04-07 13:02:37,567] [log] 317562 139768548886080 Method Not > Allowed (GET): /archives/list/ > kictanet@lists.kictanet.or.ke/thread/MICNFIHVLOETVE4PXEDO5MBYWG7SN57H/favorite ... > > Any clues as to what needs to be done to mitigate the above? A web crawler is issuing GETs for those URLs which only allow POST. If you look in your web server logs, you can find the IPs they are coming from. If it's only a few, you can block them with a firewall or using access controls in your web server. If its a compliant web crawler, you may be able to use robots.txt to stop it. Also see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: Hyperkitty archive: date format in thread overview of list does not honor DATETIME_FORMAT of settings.py

by Mark Sapiro

On 5/24/25 5:04 AM, Stephen J. Turnbull wrote: > Christian Schneider writes: > > > In settings.py I set DATETIME_FORMAT to 'd-m-Y H:i:s' but the > > format did not change. > > I'm not sure what DATETIME_FORMAT is used for in Django 3.x. I doubt the OP is using Django 3.2. I suspect the URL <https://docs.djangoproject.com/en/3.1/ref/settings/#std:setting-DATETIME_FO…> came from a search result and the OP actually has Django 4.2 or 5.0 (django_mailman3 >= 1.3.12 requires django>=4.2,<5.1). Note that the doc for DATETIME_FORMAT for Django >=5.0 removes the note about USE_L10N = True and says "Note that the locale-dictated format has higher precedence and will be applied instead." Thus, with Django >= 5.0 I think the setting for DATETIME_FORMAT is ignored for output and the locale's format is used in all cases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 1 week

[MM3-users] Re: MM3 on debian - redirect problem

by Mark Sapiro

On 4/27/20 8:17 AM, Gelpi Andrea wrote: > Hi, > on a debian10 I have mm3 installed via apt-get > > apt-get install mailman3-full > dpkg-reconfigure mailman3 > dpkg-reconfigure mailman3-web > > I have this minor issue > > https://webserver/mailman3 redirects to > http://webserver/mailman/postorius/lists/ > > that doesn't exist. > > The same problem form django admin page to return to lists > > https://website/mailman3/admin/sites/site > > In the upper right corner I have a link to https://webserver/mailman3 > that redirects to https://mailman/postorius/lists/ > > I searched for a redirect but without success. The redirection must be a web server issue. There is a urls.py file probably in the same directory as your django settings - probably /usr/share/mailman3-web/urls.py in your case. You can make a URL like http://webserver/mailman/postorius/lists/ work by adding url(r'^mailman/postorius/', include('postorius.urls')), to the urlpatterns list in the urls.py file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Errors while importing mm2 list archives - SOLVED

by Mark Sapiro

On 12/20/22 06:48, Odhiambo Washington wrote: > > There is a WARNING on > https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install > which says one must create the config file as /etc/mailman3/mailman.cfg > How to force mailman to read that file is something I haven't understood, > but turns out to be what has taken me days trying to get things right. If you run the `mailman` command without any -C option, it will look for a config in /etc/mailman3/mailman.cfg > Ultimately, when I did the import, there was only one email from the > archives that failed to be imported - which I honestly don't mind, but > maybe there is a solution for this > "'utf-8' codec can't encode character '\udcae' in position 331: surrogates > not allowed" ?? If you provide a copy of that message from the mbox, either on the list or to me directly, I'll investigate. -- 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: Change delivery_status of a member by using the rest api

by Mark Sapiro

On 5/4/23 12:30, Michael Schaarschmidt wrote: > Hello, > > I would like to set or change the delivery_status of a list member by > using the rest api. The curl request looks like > > curl \ > -X PATCH \ > -H "Content-Type: application/json“ \ > -H "Accept: application/json“ \ > -u restadmin:secret_password \ > -d "@./foo_patch.json“ \ > "http://127.0.0.1:8001/3.1/members/ebcdd09bb8d84758a135c3449023701e“ > > With the json-file: > > { „delivery_status“: „by_user“ } I assume those fancy quotes are an artifact of your mail client. > I get an error message: > > {"title": "400 Bad Request", "description": "Unexpected parameters: > delivery_status“} > > > Is there a way to change the attribute `delivery_status` of an existing > member by using the rest api? You can't set a memnber's delivery status directly. It is an attribute of the member's preferences. The correct endpoint is "http://127.0.0.1:8001/3.1/members/ebcdd09bb8d84758a135c3449023701e/preferen…" -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Problems with mailman core translation and other details

by Mark Sapiro

On 2/6/24 2:41 PM, celi--- via Mailman-users wrote: > It´s the case below: the pair msgid/msgstr seems to be OK, but this particular sentence is not being translated. > > #: templates/postorius/lists/summary.html:88 > #, python-format > msgid "" > "\n" > " To subscribe you can send an email with 'subscribe' in the" > "subject to\n" > " <a href=\"mailto:%(address)s?subject=Subscribe\">" > "%(address)s</a>\n" > " or use the form below:\n" > "" > msgstr "" > "\n" > " Para se inscrever você pode enviar um e-mail com o assunto" > "'subscribe' para\n" > " <a href=\"mailto:%(address)s?subject=Subscribe\">" > "%(address)s</a>\n" > " ou use o formulário abaixo:\n" > > What am I doing wrong? Or what can I do to make things suitable? Is the rest of that page translated appropriately? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Moderation of held emails vs. spam

by Mark Sapiro

On 3/11/25 7:09 AM, ricola(a)poivron.org wrote: > > The problem is when spam is held for moderation and forwarded to the list owner, the mail provider of the list owner sometimes flags the moderation request as spam because it includes the original spam message. > > Sounds much safer to only forward a summary of the subject line, sender and size to the list owners and not the full message. This is https://gitlab.com/mailman/mailman/-/issues/670. https://gitlab.com/mailman/mailman/-/merge_requests/1332 and https://gitlab.com/mailman/mailman/-/merge_requests/1334 introduce a new admin_notify_held_with_attachment list attribute which if set False will not include the message in the admin notice. This will be in the next release. In the mean time, you can set the list's `Admin immed notify` setting to No to not send the immediate notice and only send the daily summary, but this doesn't completely solve the issue as sometimes the Subject: of the held message contains things that will trigger spam/malware filters. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: content filtering in version 3.1

by Mark Sapiro

On 12/12/19 6:36 AM, Dieter Leupold via Mailman-users wrote: > Hi, > > I'm new to MM3. I installed version 3.1.1 on Ubuntu 18.04. All looks > fine. But i miss the setting "pass_mime_types" at content filtering. The settings are there in Mailman core but not exposed in Postorius. You can set them via `mailman shell`. MM 2.1 settings map to MM 3 as: filter_mime_types -> filter_types pass_mime_types -> pass_types filter_filename_extensions -> filter_extensions pass_filename_extensions -> pass_extensions collapse_alternatives -> collapse_alternatives * convert_html_to_plaintext -> convert_html_to_plaintext * filter_action -> filter_action * in Postorius Settings -> Alter Messages The mailman import21 command will properly import these settings when importing a Mailman 2.1 list. > Also i don't find the settings for bounce processing. Are these features > no longer supported at version 3.1.1? Bounce processing is not yet implemented in MM 2.1. See <https://gitlab.com/mailman/mailman/issues/343>. There was a recent GSOC project to address this. See <https://gitlab.com/mailman/mailman/merge_requests/538>. I don't know how close this is to being ready. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: HyperKitty failure

by Mark Sapiro

On 12/30/21 1:30 PM, William Oliver wrote: > On Thu, 2021-12-30 at 21:19 +0000, horvath.arpad.szfvar(a)gmail.com > wrote: >> Hi, >> >> I try to connect mailman3 to hyperkitty, but there is no success so >> far. You can see the details below. How can I solve the problem? >> >> As I have several domain name (like lists.xxx.hu, xxx.hu, yyy.hu) on >> the same server, so I guess localhost won't work. >> >> In mailman-hyperkitty.cfg there is a line: >> >> base_url: http://lists.xxx.hu/hyperkitty/ As noted in the thread that William references and also the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… the issue is probably that the above http url is being redirected to https and losing POST data. Set the above to base_url: https://lists.xxx.hu/hyperkitty/ > [snip] > > I'm no expert, but here's a previous discussion I found: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Request for help with configuring "from" headers in mailman3 list

by Mark Sapiro

On 1/6/22 12:52 PM, Stephen Daniel wrote: > > Sendgrid requires that the "From:" address on any email reference an > authenticated domain. > > In the old mailman2 implementation, emails sent by mailman are listed as > > From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org > > Reply-to: <human name> sender(a)senderdomain.com (the original email's sender) > > Sendgrid would be happy with this, because LISTDOMAIN.org is a > validated domain. > > However, in my mailman3 implementation, the From: header lists the original > email's sender. Sendgrid rejects this because the original email's > sender's address is not one of the validated domains. > > How do I configure mailman3 to generate headers in the same style as the > old mailman2 implementation? In the list's Settings -> DMARC mitigations, set DMARC mitigation action to Rrplace From: with list address and DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Lost posting in archives

by Mark Sapiro

On 1/21/22 3:06 PM, Axel Rau wrote: > I created a list, did migration from 2.1 and run update_index_one_list. > Then I posted a test mail to the list and it got distributed and was seen in the archive. > Now 2 days later it does no longer show up in the archive. > > What is going on here? > May this have to do with > HYPERKITTY_RENDER_INLINE_IMAGE > which I have turned on meanwhile. It may. Is there anything in Django's log about this? If you have the original message from the list, can you go to the URL in the Archived-At: header? is the message in the hyperkitty_email table in the database? E.g., SELECT * FROM hyperkitty_email WHERE message_id_hash ='xxx'; (xxx is the value of the Message-ID-Hash: header from the message) If the prototype archiver is enabled for the list, the message should be in Mailman's var/archives/prototype/list(a)example.com/new directory and that message will have the Archived-At: and Message-ID-Hash: headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

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

by Mark Sapiro

On 11/18/24 04:12, mark(a)suburbia.org.au wrote: > > For the list I am talking about: > - Default action to take when a member posts to the list is set to "Hold for moderation" > - Default action to take when a non-member posts to the list is set to "Hold for moderation" > - When I am viewing all users, the migrated ones are set to Moderation Action: "Hold for moderation". The mass-added ones post-migration are set to Moderation Action: "None" > - When a mass-added post-migration user sent an email to the list it passed through without being held. This should not happen. In the message as delivered to the list what do you see in the X-Mailman-Rule-Misses: header and the X-Mailman-Rule-Hits: header if any? > Happy to check any logs if there might be something to hunt for. What if anything is in the lists Accept these non-members setting? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Patch/kludge suggestion and a question on adding accepted addresses

by Mark Sapiro

On 04/24/2017 07:07 AM, David Krantz wrote: > On Sun, Apr 23, 2017 at 11:04 PM, Barry Warsaw <barry(a)list.org> wrote: >> On Apr 23, 2017, at 10:33 PM, David Krantz wrote: > >>> I have another question: In the old mailman you could add accepted >>> senders without adding them to the list. Is that possible in Mailman >>> 3/Postorius? >> >> You do this by creating a "nonmember" subscription for the sender, and then >> setting that member's moderation_action to Action.accept. > > Okay. I see no way of doing that in my instance of Postorius but in > this case it is okay to do it in the command prompt. Yes. There are still quite a few things that aren't yet exposed in Postorius and probably some not yet exposed in the rest API. In these cases you have to resort to mailman shell (aka mailman withlist). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 3 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Installing mailman-suite for web ui. I did this: (env) [mailman@localhost ~]$ git clone https://gitlab.com/mailman/mailman-suite/ Cloning into 'mailman-suite'... error: RPC failed; result=22, HTTP code = 404 fatal: The remote end hung up unexpectedly but it returned an error, what should I do?? Thanks El vie., 21 jul. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 10:29 AM, Rafael Mora wrote: > > Can we modify the docs? > > > > El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > >> > >> However, that said, the doc is wrong. The lines should be added to > >> main.cf, not master.cf. See > >> <https://gitlab.com/mailman/mailman-suite-doc/issues/14>. > > > That's what the above issue and associated MR are for. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: LMTP not listening

by Mark Sapiro

On 11/24/2017 04:40 AM, Bartosz Sawicki wrote: > > But messages send to the list address are not delivered to the list :( I've > started to investigate whats happening and realize that Postfix can not > connect to mailman using LMTP. It seems that mailman is not listening on > port 8024. > > Nov 24 13:12:31 lists postfix/lmtp[2737]: connect to > 127.0.0.1[127.0.0.1]:8024: Connection refused > > I've checked log files, but haven't realize anything unusual . Any ideas > where I could try to find cause of the problem ? Is Mailman, particularly the lmtp runner, running? $ ps -fwwu mailman|grep lmtp mailman 19107 19085 0 Nov16 ? 00:00:44 /usr/local/bin/python3 /usr/local/bin/runner -C /opt/mailman/mailman-bundler/deployment/mailman.cfg --runner=lmtp:0:1 If so, where is it listening $ sudo netstat -lntp|grep 19107 tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 19107/python3 where the 19107 in the grep is the PIP of the lmtp runner. If that's all OK, is there a firewall (iptables or ??) thats not allowing access to localhost:8024? -- 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: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/13/21 2:27 PM, Odhiambo Washington wrote: > On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> Hey Everyone, >> >> I am pleased to announce new stable releases for Mailman Core, Postorius, >> Hyperkitty. >> >> These include both new features and bug fixes. Complete change log for >> each components: >> >> Mailman Core 3.3.3: >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > > > May I ask if this is a typo? > I am asking because Mailman Core 3.3.4 was announced on Marc 22nd. > So is this new one version 3.3.3 or 3.3.5? The text you are quoting is from the Feb 2 announcement <https://mail.python.org/archives/list/mailman-announce@python.org/message/N…> of the release of Mailman core 3.3.3. Mailman 3.3.4 was released and announced at https://mail.python.org/archives/list/mailman-announce@python.org/message/H… on March 21 and is the current release. There is no "new one". -- 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: templates

by Mark Sapiro

On 5/4/23 11:15, Christian via Mailman-users wrote: > In March when I started troubleshooting my lists, you stated: > > "Also, one other thing you might check. Do these non-working lists have > templates defined in postorius, in particular, one for > list:member:regular:footer, and if not, are there any in Mailman's > var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that > Mailman doesn't have permission to find and read?" > > There are no other templates listed in either Postorius nor in Mailman's > var/templates (as I stated, I do not even lave a 'lists' subdirectory under > Mailman's var/templates). My subscribers are not receiving message > distributions from my lists, even while some of them are listed in the > archives. See the original thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… (which you hijacked about 4 messages in) and particularly the message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Without further information, I can't say more than that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Database permission problem?

by Mark Sapiro

On 10/15/24 14:45, Bill Oliver wrote: > > In any case, here it is changed back: > > ls -l > total 68 > -rw-rw-r-- 1 mailman mailman 0 Oct 15 12:53 postfic_vmap.db > -rw-rw-r-- 1 mailman mailman 12288 Oct 15 12:53 postfic_vmap.db.db Were these created manually? They should not be there. Likewise the .db.db files below. > -rw-rw---- 1 mailman mailman 353 Oct 15 13:37 postfix_domains > -rw-r----- 1 mailman mailman 12288 Oct 15 13:37 postfix_domains.db > -rw-rw-r-- 1 mailman mailman 12288 Oct 15 12:53 postfix_domains.db.db > -rw-rw---- 1 mailman mailman 1155 Oct 15 13:37 postfix_lmtp > -rw-r----- 1 mailman mailman 12288 Oct 15 13:37 postfix_lmtp.db > -rw-rw-r-- 1 mailman mailman 12288 Oct 15 12:53 postfix_lmtp.db.db > -rw-rw---- 1 mailman mailman 1118 Oct 15 13:37 postfix_vmap > -rw-r----- 1 mailman mailman 12288 Oct 15 13:37 postfix_vmap.db Does Postfix have read and search ('x') on all of /opt, /opt/mailman, /opt/mailman/mm, /opt/mailman/mm/var and /opt/mailman/mm/var/data? Perhaps there is a SELinux issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

[MM3-users] Re: Message getting held due to max number of recipients and maximum message size

by Mark Sapiro

On 9/22/23 14:56, Wong, Wesley wrote: > I can confirm that the list was set to 0 for max recipients and message size. In addition, I checked the base.py and the defaults are the ones in the message. If I went ahead and modified the settings in base.py, would this immediately to all existing lists in Mailman? No. It would only affect lists created after you did that. I suggest the following mailman shell interaction ``` $ ./mailman shell 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. >>> for mlist in getUtility(IListManager): ... if (mlist.max_num_recipients == 10 and ... mlist.max_message_size == 40): ... print(mlist.list_id) ... ``` This will print the list ids of all lists with max_num_recipients = 10 and max_message_size = 40 Your held message notice is for one of those lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/18/23 12:18 PM, eboltz(a)lhtservices.com wrote: > Mark, > > I don't think the setup will work, as the client uses O365 for the emails and doesn't appear to like the virtual lists domain on the MM3 server. I've tried both using the O365 email connector as well Smtp2Go, both have the same issue with headers. > > real email domain = example.org > MM3 virtual domain = lists.example.org Actually, lists.example.org is a real email domain. > The FROM: header is always what's causing the issue, plus it doesn't like any external emails as it can't send held messages or posts to users outside of the example.org domain. If you want to use these 3rd party smtp relays, you have to configure them to accept mail from the lists.example.org domain. It should not be difficult, but it is not a Mailman issue. It is strictly an issue with configuring the 3rd party relay to accept the mail. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Mark Sapiro

On 8/5/24 10:30, Odhiambo Washington via Mailman-users wrote: > > Actually, what I mean is that CF is proxying requests to the host named > m3-lists.kictanet.or.ke. > I do not have any configuration other than DNS proxying at CF. ``` dig a mm3-lists.kictanet.or.ke ... mm3-lists.kictanet.or.ke. 300 IN A 172.67.167.73 mm3-lists.kictanet.or.ke. 300 IN A 104.21.11.217 ``` Both of those are cloudflare IPs, and why 2? > So when you talk to m3-lists.kictanet.or.ke via a browser, it's CF IP who > you talk to and it in turn talks to the host directly. And how is that configured? > So the IP address you see in the logs is CF's IP address, not yours, not > mine and CF are doing some caching. That's why > they are requesting for expired files. Why is cloudfare trying to access /opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css locally if all it is doing is proxying the request to the actual mailman server? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: Login confusion

by Mark Sapiro

On 2/11/25 01:26, Stephen J. Turnbull wrote: > > That will work in the short run, but I'm not sure that's a long-term > solution. It's not clear to me that allauth won't do the same thing > again. Allauth since 0.62.0 and better since 0.63.0 no longer does this. See https://codeberg.org/allauth/django-allauth/src/branch/main/ChangeLog.rst#s… > > Could I have achieved the same deletion using the REST interface? > > I don't know. I would think not. That's correct. The issue is in the account_emailaddress database table which is an allauth table that Mailman core and hence the REST api know nothing about. Our latest recommendation is django-allauth>=65.4, but that requires changes, see https://gitlab.com/mailman/django-mailman3/-/merge_requests/316 and https://gitlab.com/mailman/mailman-web/-/merge_requests/58 although the changes only affect testing and a deprecation warning. Also, installing that django-allauth version may result in upgrading Django to a version which doesn't support django-haystack<3.3.0 and may also require manually upgrading django-haystack. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

[MM3-users] Re: How to separate bans for sending emails to lists and subscribing to them

by Mark Sapiro

On 5/29/19 9:29 AM, Nathan Dixon wrote: > Hi, > Our requirements for using Mailman are that we can have non-members send an > email to a list from any domain name, but only people who's email addresses > match a list of specific domains should be able to actually subscribe to > those lists. > > I can't seem to find any way of doing this. Any ideas? > > I have tried using the bans (global and on each list) but these appear to > stop all subscriptions and emails being sent to or from a list if the > address matches a ban. Right. The default posting rules chain includes 'banned-address' which discards posts from banned addresses. You can work around this by creating a new chain based on mailman/chains/builtin.py but without the 'banned-address' rule and setting the list's posting_chain to use it. -- 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: If you delete a list but not the HyperKitty archive

by Mark Sapiro

On 1/4/22 6:45 AM, Philip Colmer wrote: > > So ... should the archive be deleted when the list is deleted and it is a > bug that it isn't? Or is it expected that access to the archive is "frozen" > once a list is deleted? It is often desired to have a public archive available after the corresponding list has been deleted. Even for a private archive, it may be desirable for site admins to have access. Furthermore, a list might not even have a HyperKitty archive in the first place. Thus, what to do about a HyperKitty archive (or prototype archive or ...) when a list is deleted is an administrative decision and is best left up to the site admins to do it or not. As you note with a private archive, former members no longer have access when the list is gone, but unless an attempt throws some uncaught exception, that is not a bug. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Apache+mod_wsgi issue

by Mark Sapiro

On 12/26/22 07:08, Odhiambo Washington wrote: > > So it seems your WSGIDaemonProcess is defined somewhere outside the VHOST, > right? Or it wasn't necessary? > And what does your urls.py look like? Eggert's configuration is for uWSGI. This is completely different from Apache mod_wsgi. Background: Python PEP 333 defines the Python Web Server Gateway Interface (WSGI) which is a protocol for communication between web servers and applications. Django is one such WSGI application. Basic web servers typically do not support WSGI directly but need some kind of intermediary. Apache mod_wsgi is an Apache module that extends Apache to communicate with WSGI applications. Both uWSGI and gunicorn are separate applications that can receive http requests via proxy from a web server and communicate them to a WSGI application and receive responses from the application and return them to the web server. Thus Apache mod_wsgi, uWSGI ang gunicorn are three separate ways of providing the connection between the web server and Django (or other WSGI applications), each with their own separate configuration requirements. -- 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: Archive search failing on one list

by Mark Sapiro

On 9/23/23 19:19, Mark wrote: > > Yes, the query returns a result and the case in "name" matches that in > the query ... > > select * from hyperkitty_mailinglist where name like 'listname(a)domain.com' > > id | 91 > name | listname(a)domain.com > display_name | Listname > description | ... > subject_prefix | [Listname] > archive_policy | 1 > created_at | 2023-09-21 08:55:36.385239+2 > list_id | listname(a)domain.com Is that really what you get for list_id? It should have a dot, not at as listname.domain.com. What if you do something like the following where django-admin is whatever command you use for the Django admin command. ``` $ django-admin shell Python 3.9.16 (main, Dec 11 2022, 12:49:23) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models.mailinglist import MailingList >>> mlist_name = 'listname(a)domain.com' >>> mlist = MailingList.objects.get(name=mlist_name) >>> mlist <MailingList listname(a)domain.com (listname.domain.com)> >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: out queue backlog and delivery rate

by Mark Sapiro

On 4/8/22 09:47, dancab(a)caltech.edu wrote: > For anyone coming across this thread. It seems increasing the runners did the job for us. The smtp.log is now showing smaller lists being completely processed while larger lists are still in progress of sending out to members. > > We edited the mailman.cfg to include the following and the mailman stop; mailman start > > [runner.in] > class: mailman.runners.incoming.IncomingRunner > instances: 2 There's probably no issue that would be helped by increasing in runner instances. > [runner.out] > class: mailman.runners.outgoing.OutgoingRunner > instances: 2 I would suggest larger, 4 or even 8. This is not a single queue/multiple server setup. It is multiple queue/multiple server. I.e. The queue entries are named based on a hash of the message and each instance processes its own slice of the hash space. So, with 2 slices and a large recipient message being processed, there's a 50% chance that the next message will wind up waiting. -- 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: FYI: Django security releases issued: 4.0.6 and 3.2.14

by Mark Sapiro

On 7/8/22 6:34 AM, Stephen J. Turnbull wrote: > David Newman writes: > > > Interesting -- that does produce two directories with names starting > > with a tilde: > > > > /opt/mailman/venv/lib/python3.9/site-packages/~jango: > > /opt/mailman/venv/lib/python3.9/site-packages/~jango-3.0.14.dist-info: > > I would guess that those are the previous versions before the upgrade, > moved out of the way in case a revert-to-previous was needed. Again, > guessing, they should have been removed by the upgrade process once > the new package was fully installed. Was there an interrupted or > partially successful upgrade in the past? When pip is doing an upgrade of the xyz package, it renames the existing package as ~yz and then ultimately deletes the old ~yz package after successfully installing the new xyz. In this case, the upgrade was aborted because of the Django<3.1 constraint in mailman-web and apparently pip then installed Django<3.1 and left the ~jango* directories behind. -- 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: Where to configure 'hostname' used in 'From:'-header?

by Mark Sapiro

On 3/10/23 01:55, Dmitri Heerdegen wrote: > > I've recently installed MM3 with Exim4 on, say, subdomain.myhost.tld > and configured MM3 to use lists.someotherdomain.tld as web host and mail > host. > Thus, the mailman.cfg contains: > > [mta] > smtp_host: lists.someotherdomain.tld > > When I send a message to test(a)lists.someotherdomain.tld it gets > delivered, however the 'From:'-header becomes "test(a)subdomain.myhost.tld". The From: should be unchanged from the incoming post unless the list is anonymous or DMARC mitigations are applied. In the case of anonymous lists, the From should be the list's address and in the case of DMARC mitigations it should be something like User Name via listname <list-address>. In either case, the list address should be list-name@list-domain where list-domain is the list's email domain. If the address is being rewritten as test(a)subdomain.myhost.tld it is probably Exim doing it. -- 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: A poll: "Delete this thread"

by Mark Sapiro

On 6/21/24 07:45, Sam Darwin via Mailman-users wrote: > Thanks for the replies. Not yet a close match to what I have installed. Jeremy is using Dockerfiles. Marc is running mailman3-web from 4 years ago "20200530". I may need to dig into the code and attempt to debug, line by line. "Oh, of course, in your settings refresh_cache needs to be set to 1, you have it set to 0", or something obscure like that. Or who knows. I manage 3 production mailman 3 servers and a development server. All 4 are running the current (as of today) heads of the GitLab branches installed in a venv. The versions of some dependencies probably vary, but all use django_q2-1.6.2 one uses Django-4.2.11, two use Django-4.2.6 and one uses Django-4.1.13. They all use memcached as the cache backend. I don't know what you mean by the refresh_cache setting as I have no information about such setting. All 4 servers are able to delete threads in HyperKitty with no issues. -- 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: Installation -- error on mailman-web migrate

by Mark Sapiro

On 9/16/21 7:27 PM, Mark Dale via Mailman-users wrote: > > I note that in the sample "settings.py" file, there are lines that have the directory "web" in the file paths ... > > STATIC_ROOT = '/opt/mailman/web/static' > > LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' > > > ... but as yet there is no directory "web". This appears to be an error in the docs. With ``` [paths.here] var_dir: /opt/mailman/mm/var [mailman] layout: here ``` The logs are in `/opt/mailman/mm/var/logs/`, not `/opt/mailman/web/logs/` and `STATIC_ROOT` should probably be `/opt/mailman/mm/static`, but it could also be `/opt/mailman/mm/var/static`. > Was I meant to create the directories "web/logs/" and the "mailmanweb.log" file at some point, or were they meant to get created during the mailman-web install process? They should be created automatically, but in `var_dir` which is `/opt/mailman/mm/var`, not `/opt/mailman/web` > Should the owner/group be "mailman"? Yes -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: REST API authorization failed

by Mark Sapiro

On 1/8/22 10:40 AM, Axel Rau wrote: > Hi all, > > I’m going to do a mailman2->3 migration in a FreeBSD jail. > I installed mailman3 in an venv from pypi, along with nginx, uwsgi and exim. > The above error happens when I try to open the base url of my server with a browser > (is redirected to postorius/lists/) > (no errors on admin/ and hyperkitty urls) > > Same passwords and users in mailman.cfg: > > [webservice] > hostname: localhost > port: 8001 > use_https: no > admin_user: restadmin > admin_pass: ??? > > and in settings.py: > > MAILMAN_REST_API_URL = 'http://localhost:8001' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = ??? > > Its a long password, created as secret key by manage.py Is the password unquoted in mailman.cfg as admin_pass: ??? and quoted in settings.py as MAILMAN_REST_API_PASS = '???' Does the `mailman info` command report what you think for REST credentials? To you get an appropriate JSON response from wget -O- --user restadmin --password ??? http://localhost:8001/3.1/lists -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Digests not working correctly

by Mark Sapiro

On 6/13/23 09:42, Joel Lord wrote: > Now I'm on one of the lists in digest mode and I can see that it's a > mess. Periodic digests are definitely NOT working, so I'll lay that out > here. > ... > root@host2:/# grep digests /var/log/cron.log > Jun 11 23:00:01 host2 CRON[1632765]: (lists) CMD (/usr/local/bin/mailman > digests --periodic) > Jun 12 23:00:01 host2 CRON[2177286]: (lists) CMD (/usr/local/bin/mailman > digests --periodic) OK. > root@host2:/home/members/directory# su - lists > lists@host2:~$ /usr/local/bin/mailman digests --periodic > lists@host2:~$ ls var/lists/<list>/ > digest.mmdf If there is nothing in Mailman's mailman.log, I don't know what the issue is unless the list's digest_send_periodic flag is False. > How can I try and track this down? Try manually running ``` /usr/local/bin/mailman digests --periodic --verbose ``` to get more info. Also try ``` /usr/local/bin/mailman digests --send --verbose ``` to see what it reports and whether it sends the digest. -- 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: Execution of msgfmt failed when performing post upgrade steps

by Mark Sapiro

On 9/15/19 5:19 AM, Torge Riedel wrote: > > When runnin the post-upgrade-script I get the following error message: > > Execution of msgfmt failed: > /opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/locale/nb_NO/LC_MESSAGES/django.po:630: > duplicate message definition... > /opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/locale/nb_NO/LC_MESSAGES/django.po:273: > ...this is the location of the first definition > msgfmt: found 1 fatal error > > Not sure whether this is an error of MM3 or one of its dependency packages. The file hyperkitty/locale/nb_NO/LC_MESSAGES/django.po does contain a duplicate definition. This is a bug. lines 270,273 are: #: templates/hyperkitty/fragments/month_list.html:78 #: templates/hyperkitty/overview.html:75 msgid "All Threads" msgstr "" and lines 629,631 are: #: templates/hyperkitty/overview.html:75 msgid "All Threads" msgstr "Alle tråder" You can just delete lines 272,273 but if you want to be really fussy, you can delete lines 629,631 and change line 273 to msgstr "Alle tråder" See <https://gitlab.com/mailman/hyperkitty/merge_requests/185> -- 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: Cron of Mailman notify is not working

by Mark Sapiro

On 1/28/20 3:03 AM, Shashikanth Komandoor wrote: > Hello, > > With your help, I was able to setup mailman 3.3 on my RHEL 7.5 > machine and running well and good. > > For daily notification I have added the below line in the crontab: > > 00 08 * * * /var/lib/mailman/venv3/bin/mailman notify > > But this cron job is not working while I was able to run the same > command manually at my CLI. Into exactly what crontab did you put it? That is the correct line if you put it in the mailman user's crontab, but if you put it in a system crontag, e.g./etc/cron.d/mailman, it needs a 'user_name' argument between the date/time fields and the commands. E.g., 00 08 * * * mailman /var/lib/mailman/venv3/bin/mailman notify although the Mailman user may not be 'mailman' in your case. You should see some errors from cron in /var/log/syslog at 08:00 that would give you a hint. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/23/20 7:02 AM, Brian Carpenter wrote: > On 9/23/20 7:33 AM, r.woithe(a)callassoftware.com wrote: >> Thank u for the hint ! >> The only one is that Ubuntu uses uWSGI and not gunicorn. >> I set the para socket-timeout = XXX. >> I hope thats the right parameter. >> _________________________________________ > > I think Mailman 3 core still has its own gunicorn process that it runs. > Brian is correct. The REST API does not use the web server and uWSGI is not involved. Since Mailman core 3.3.0, the REST API is served by Gunicorn processes that have nothing to do with the web server. The time limit for these processes needs to be set as described at <https://wiki.list.org/x/17892072>. Prior to 3.3.0, the REST API used the standard library wsgiref module which doesn't have timeouts. Since you said you have Mailman core 3.2.2, this may not be a REST timeout 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: MIMEDefang to fix footers

by Mark Sapiro

On 11/13/20 9:51 AM, Ryan Morash wrote: > Does anyone know how to use MIMEDefang to fix the footer as attachment issue when using Mailman3? I've seen several guides/scripts referring to its use with Mailman2, but I'm unsure of how they would match with Mailman 3. I don't use MIMEDefang and don't specifically recommend it, but I have looked at <https://stuff.mit.edu/~jik/software/mailman_mimedefang/>, and it seems that the only Mailman specific things involved in the installation and configuration of this script are the addition of the "MAILMAN_MIMEDEFANG" lines as the first and last lines of the footer template. The only thing Mailman 3 specific in that is how to edit the footer template. This can be done on a per-list basis via Postorius since 1.2.0 or more directly in Mailman core by setting URIs, see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> or by creating templates in Mailman's var/templates directory, see <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n…>. -- 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: mailman3-web language preference and translation settings

by Mark Sapiro

On 12/6/23 15:54, Nils wrote: > Thanks for your help, Mark. I've already tried that and it gave me this > message: > > # sudo -u www-data python3 /usr/bin/django-admin compilemessages > --pythonpath /usr/share/mailman3-web --settings settings > CommandError: This script should be run from the Django Git checkout or > your project or app tree, or with the settings module specified. > > I'm working on ubuntu and I don't have (venv)$ The other commands (migrate, collectstatic and compress) worked fine. Kind regards I don't know why this fails like that, particularly since the same thing works for migrate, collectstatic and compress. The only thing I can think of is you may need to cd to the directory containing django/ django_mailman3/ postorius/ and /hyperkitty before doing the above. This may be something like /usr/lib/python3.x/site-packages. If that doesn't work, since I think you are using the Debian/Ubuntu package, I suggest you try Debian for help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Wrong info in moderation mail when held due to match of a header rule

by Mark Sapiro

On 10/18/20 4:15 AM, tlhackque via Mailman-users wrote: >> > I considered including the regex in each message, but that seemed > redundant - and potentially long. Thus the pointer. Perhaps number the > rules for each list, and use that index? The ROWID would seem to be a > candidate for the number. The number would be the `position` value from the headermatch table for the matched rule, but that's unreliable as the rules can be reordered (or the particular rule even deleted) between the rule being applied to a message and subsequently looking for the rule. ... > I may have some details wrong - I found mm3 not ready for my needs and > am thus out of date - but I hope the high level approach that I outlined > is useful. It seems to me that this is a great deal of additional implementation to solve a non-existent problem. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: MM2 to MM3 Archives Loading

by Mark Sapiro

On 11/22/24 13:46, Joshua Bushe wrote: > Both "Hide Inactive" and "Hide Private" are unchecked. I can view the lists without any issues, but when I click on a specific list, I see three loading icons. On the left side, there's an "All Threads" option, which lets me view all the archives for the list. > > My question is: why don’t the list appear in the "list overview"? I'm still confused. You say "I can view the lists without any issues", but then you say 'why don’t the list appear in the "list overview"?' By "list overview" I thought you meant a page like https://lists.mailman3.org/archives/, but now I think you see your lists on that page and the page you call "list overview" is one like https://lists.mailman3.org/archives/list/dummy@mailman3.org/. If your question is why don't you see a list of threads on that page, it only shows threads with posts in the last 30 days. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 1 week

[MM3-users] Re: Hyperkitty performance problem

by Mark Sapiro

On 12/31/24 06:07, monochromec via Mailman-users wrote: > Further RCA reveals the fact that the archiver runner tries to archive the same message over and over again - hence the overhead during pipeline processing. The total # of attempts reaches well into five digits for a single message. This is not directly related to the pipeline runner issues but they may have the same underlying cause. All the pipeline runner does is put the message in the archive queue. It's the archive runner that is doing all these retries. However, the pipeline runner in processing the rfc_2369.py handler is also communicating with hyperkitty to get the values for the List-Archive: and Archived-At: headers. You need to focus on the communication between mailman_hyperkitty and HyperKitty. If there are significant delays there, it could explain your pipeline runner issue. Btw, I see https://gitlab.com/mailman/mailman/-/issues/1189 is also from you. I wondered at the time why you were trying to increase the number of pipeline runners which is not something that would normally be required. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months

[MM3-users] Re: Linking to a forum thread from a (news) website.

by Mark Sapiro

On 9/25/19 2:29 AM, Paul Arenson wrote: > SOLUTION > I figured out that all replies are listed under Re:, so if the first comment does not have the Re:, then it gets cut off. ... > QUESTION > Am I correct that if I want to create a thread and link to it, but make sure the first note is included, I need to make the thread title: Re: Something? Re: has nothing to do with it. Replies are not threaded by subject. Replies are threaded by In-Reply-To: and References: headers in the reply. These headers are generated by the sending MUA (mail client) when replying to a message. If you send a 'new' message without those headers, it will be a new thread regardless of whether or not the Subject: matches with or without the Re:. Also, there are broken MUAs that don't properly generate In-Reply-To: and References: headers and replies from these MUAs will never be properly threaded. -- 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: Cannot start lmtp runner due to error while attempting to bind on address ('127.0.0.1', 8024): address already in use

by Mark Sapiro

On 12/2/19 5:04 AM, actionmystique(a)gmail.com wrote: > > Of course the port is already in use: it is used by dovecot. > ``` > tcp6 0 0 ::1:8024 :::* LISTEN 0 1317360 129620/dovecot > tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 0 1316324 129620/dovecot > ``` > I must be missing something. What is Dovecot listening for on the lmtp port? If this is Postfix communicating with Dovecot as the LDA or for address verification and using TCP port 8024, you have at least two choices. You can have Postfix/Dovecot communicate via a unix socket instead or you can configure Mailman to use a different port. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html> which says in part: lmtp_port is fairly arbitrary (there is no standard port for LMTP). Use any port convenient for your site. “8024” is as good as any, unless another service is using it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 1/30/24 10:46, andrea.janna.unipd(a)gmail.com wrote: > Same issue at my site. > I'm using mailman3 3.3.8 shipped with Debian 12. Then your first line of support should be Debian. See <https://wiki.list.org/x/12812344> > To debug the problem I stopped apache, cron, postfix and mailman3-web services. > But I still get the mariadb aborted connection warnings every 5 minutes. The only thing that runs every 5 minutes is `mailman gatenews`. The issue may be with that. You could try running it manually via ``` _MAILMAN_GATENEWS_NNTP=yes;sudo -u list mailman gatenews ``` ... > The regular mailman log doesn't show anything and I'm not sure about how to enable an appropriate debug log for mailman. Mailman has a number of virtual logs, most of which are written to the file mailman.log. You can enable debug level for those with ``` [logging.template] level:debug ``` See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> for more info on logging. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Trouble Installing Mailman3

by Mark Sapiro

On 6/3/25 08:22, Henry Hartley via Mailman-users wrote: > > (venv) mailman@wz-prd-tpmd-1:~$ pip -v --trusted-host pypi.org install wheel mailman psycopg2-binary > Using pip 24.0 from /opt/mailman/venv/lib/python3.12/site-packages/pip (python 3.12) > ERROR: Could not find a version that satisfies the requirement wheel (from versions: none) > ERROR: No matching distribution found for wheel > > The same error shows up if I try to install just mailman or psycopg2-binary, except the word "wheel" is replace with whichever package I've requested. I don't understand why this is occurring. All those packages exist in pypi.org https://pypi.org/project/wheel/ https://pypi.org/project/mailman/ https://pypi.org/project/psycopg2-binary/ Also, pypi.org has a valid ssl certificate signed by GlobalSign nv-sa If I create and activate a new virtualenv named zzz, and do ``` (zzz) mark@msapiro:~$ pip -v install wheel mailman psycopg2-binary ``` I get a successful installation. I am guessing that there is something in your local network that's redirecting connects to pypi.org to somewhere else. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 4 weeks

[MM3-users] Re: Unknown templates being used

by Mark Sapiro

On 2/14/21 1:47 PM, Tom Stoddard wrote: > > On 2/14/2021 1:31 PM, Mark Sapiro wrote: >> >> I.e., we know it should be a template, but it currently isn't. > > That's fine but it doesn't explain why I have received messages that > were built by a template for some subscription requests. In other words, > why is there a template being used in some instances and on others a > "mailman notify command" is being used? The notice sent at the time the request is generated is built from a template. The `mailman notify` command is intended to be run periodically via cron set up by the site admins to send a summary of then outstanding requests to the list admins. You should receive the initial notice built from a template of each request as it is generated as long as the list is sent to send immediate notices. The notice sent by `mailman notify` is a summary of all requests outstanding at that time. If all the requests have been handled by the time `mailman notify` is run, it won't send you anything. > Are there different methods for people to use to request a subscription? Yes, but that's not the explanation for your question. Subscription can be requested via a web UI or via email to the list-join or list-subscribe address or via a join or subscribe command sent to the list-request address, but all methods result in the same notices to the admin. > By the way, Brian at EMWD has been extremely helpful to me already and, > as he stated, he informed me that this is an issue with Mailman 3 so I > thought I'd try getting the answer directly from this group. I agree and appreciate that Brian is very supportive. In my initial reply, it was not clear to me that Brian had referred you here which is the only reason I pointed out that he was your primary line of support. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Mark Sapiro

On 7/24/20 10:34 AM, Shashikanth Komandoor wrote: > Hi Team, > > Today, I found an error message like "Multiple rows were found > for one_or_none()" when a hold message is approved for a list. Until > yesterday the mails were accepted and delivered fine. We have seen this issue before. See <https://gitlab.com/mailman/mailman/-/issues/657>. There are also multiple threads on it in the archive, e.g., <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. We don't know how it happens, but the issue is that the `listarchiver` table in the database has multiple `mhonarc` entries for the same `mailing_list_id`. You can see the problem with the query select * from listarchiver where name = 'mhonarc'; There will be two entries with the same `mailing_list_id` and deleting one of them will fix this and you can run `mailman unshunt` to reprocess the shunted messages. The above referenced issue contains a script that can be run to remove the extra entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by Mark Sapiro

On 12/9/20 6:39 PM, matthew(a)alberti.us wrote: > > For core, the connection string seems to accept a tailing > "?charset=utf8&use_unicode=1" per > https://mailman.readthedocs.io/en/stable/src/mailman/docs/database.html So > for core, maybe just updating the connection string to include > "?charset=utfmb4&use_unicode=1" will just work? The link lists utf8 as the > recommend encoding... maybe that should be updated? I'm in the process of doing that update. > Seems the takeaway is that, for mysql databases only, the use of utf8mb4 is > recommended, and it needs to be explicitly identified in the database > settings for BOTH core and web, and probably somehow at database creation > time? It's not as critical for core because barring things like 4-byte utf-8 unicode graphics in list configurations, core doesn't store anything like that in its tables. The major issue is with HyperKitty where messages have emojis and other 4-byte utf-8 encodings in message subjects and bodies. -- 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: Is there a way of recording bounce messages?

by Mark Sapiro

On 9/21/23 17:30, Thomas Ward wrote: > > MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). > > If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: General question mailman3: message sender acceptance "always"

by Mark Sapiro

On 10/23/23 09:08, Wikinaut wrote: >>> In the Postorius held messages view, click on the message's subject to >> open a dialog showing the messages content > > Dear Mark, sorry: > How should I know this? Well, the subject of the message in the held messages view looks like a link. Maybe click it once to see what it does. > I'd rather prefer to have these both changes: > > i) relabel the existing one od three buttons from "accept" to "accept once" ; and > ii) add a fourth button "accept all messages from this sender (i.e. add to white list)" That wouldn't include options like "discard further posts from this user", "reject further posts from this user" and perhaps other possibilities. If I were going to do anything, it would probably be adding a line above the list of held messages saying something like "Click the message's subject for more options." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Mailman web interface / uwsgi

by Mark Sapiro

On 11/26/22 21:29, Jan Eden via Mailman-users wrote: > > Replicating this setup on the server solved the KeyError problem, > everything works now! I just wonder why these uwsgi parameters need to > be passed explicitly when using a file socket, but not with a http > socket. You are doing more than just switching from a tcp socket to a unix socket. You are also switching from communicating with uwsgi via http protocol to uwsgi protocol. > Another (unrelated) question: Why is mailman_hyperkitty.cfg placed in > /opt/mailman/mm and not in /etc/mailman3 with the other configuration > files when using the virtualenv installation instructions > (https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… mailman_hyperkitty and its mailman-hyperkitty.cfg are part of mailman core, not mailman-web. If you want, you could put mailman-hyperkitty.cfg in /etc/mailman3/ by putting ``` configuration: /etc/mailman3/mailman-hyperkitty.cfg ``` in the `[archiver.hyperkitty]` section of mailman.cfg, but as it really belongs to core and not mailman-web we choose to put it in /opt/mailman/mm/. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Unusual behavior: Standard discussion lists with prefix are sometimes having prefix *dropped*

by Mark Sapiro

On 10/19/23 10:02, Thomas Ward via Mailman-users wrote: > I noticed some unusual behavior in Mailman3 stable release on PyPI and > such. Namely, there are instances where replies are being processed and > the prefix tags are simply being **lost** and dropped by Mailman3, > instead of being properly prepended where they're supposed to go. > > Is this a known bug or does it need its own bug in the gitlab tracker? Are you sure you are looking at messages from the list and not messages received by direct To:, CC: or BCC:? I have never seen an issue where list posts would sometimes have the subject prefix prepended and sometimes not. If you are seeing this, we would ideally like to see a thread in the hyperkitty archive where some of the messages have the prefix in the message view and some don't, or at least see some of the raw Subject: headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Template for Password Reset Email

by Mark Sapiro

On 11/17/24 16:57, Mark wrote: > > I can see the French text for the "Password Reset Email" in the > django.po file. And running the compilemessages command reports the > "django.po" for French is okay and up to date. Should I be recompiling > the ".mo" file? No, It's fine. The issue is the language context for this message has nothing to do with any Mailman list's preferred language. Again, see https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… If all the lists on your server are French, you could set LANGUAGE_CODE = 'fr' in your Django settings. Otherwise, the user's browser has to include an Accept-Language: header specifying French as the most preferred language in it's request. Also note the ordering of SessionMiddleware, LocaleMiddleware and CommonMiddleware in the above doc. I have recently updated the various places where we suggest or supply MIDDLEWARE settings, but you may find that your settings have LocaleMiddleware after CommonMiddleware and you should fix that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Migrate from mysql to postgresql

by Mark Sapiro

On 03/17/2018 01:44 PM, Bjoern Franke wrote: > Hi, > > is it possible to migrate a mailman3-mysql-database to a > postgresql-database? > > I tried to convert it with pgloader, but some identifiers had to be cut off: > _address_id); > 2018-03-17T21:33:39.087000+01:00 WARNING PostgreSQL warning: Bezeichner > idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_account_e > wird auf idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac > gekrzt I suspect the issue is due to the way Mailman supports different databases via SQLAlchemy. The bottom line is the table and column specifications are based on the Mailman database models, but are database specific. If I were doing this, I would dump the data from MySQL, but rather than using the CREATE TABLE queries from the dump, I would let Mailman create a new PostgreSQL database and then just load the existing tables from the MySQL dump. However, that may all be irrelevant. I don't know which table/column that specific item comes from, but it appears just visually that idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_account_e is already truncated so further truncating it to idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac may not be a problem. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Various patches for mm3 stable 3.3.1

by Mark Sapiro

On 9/30/20 6:57 AM, Ruth Ivimey-Cook wrote: > > 1. If I do not set up 'individual' or 'full' personalisation, all is > well and the default footer templates are expanded as expected. However > setting up personalisation causes template expansion to fail > completely, and messages get sent with a blank expansion. Your mailman-debug.patch makes changes to mailman/handlers/decorate.py including wrapping all the relevant code in a try:/except: that logs any exception. If you set the level for logging.error to debug, what do you get in the log? This issue doesn't occur in the unpatched code on my servers - personalized footers work fine - so I think the problem must be something in your patch. > 2. I would find the postorius UI much easier to cope with if the > default template was 'populated' into the UI wherever it was non-blank, > rather than the UI starting off as if no templates were defined at all. This is <https://gitlab.com/mailman/postorius/-/issues/366>. -- 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: mailman-suite: Error 500 on Lists /setting/ pages

by Mark Sapiro

On 11/18/20 8:43 AM, ljsbw-it(a)riseup.net wrote: > I just installed Mailman3 (mailman-suite) on my Server following these instructions: https://lab.uberspace.de/guide_mailman-3.html Please see <https://wiki.list.org/x/12812344> > and everything works fine so far. I can create lists, subscribe people and send mails through lists but when I click the settings button and get redirected to /postorius/lists/listname/settings/ i get an Error 500 message. I couldn't find anything in the logs except the uwsgi log: > [pid: 20568|app: 0|req: 62/62] 100.64.115.1 () {48 vars in 1052 bytes} [Wed Nov 18 16:27:59 2020] GET /postorius/lists/listname/settings/ => generated 1102 bytes in 1438 msecs (HTTP/1.1 500) 6 headers in 209 bytes (1 switches on core 0) I think that uwsgi log message just refers to the delivery of the error page to your browser. What other logs are you looking at? There should be something in Mailman core's mailman.log or the Django log whose location is defined in settings(-local).py, probably mailman-suite/logs/mailmansuite.log. -- 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: messages with attachments, without text discarded silently

by Mark Sapiro

On 1/27/25 12:35, Schulz via Mailman-users wrote: > Using the current mailman version, I can reproduce the following: > - send a text-formatted email with attachment but without text body to a list. > - the msg will be received by mailman > - the msg shows up in shunt, the log shows: > ile "/usr/lib/python3.12/email/message.py", line 343, in set_payload > payload = payload.encode(charset.output_charset, 'surrogateescape') > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > UnicodeEncodeError: 'ascii' codec can't encode characters in position 10-17: ordinal not in range(128) Please provide the full traceback and the MIME structure of the message. > an attempt to unpickle the file leads to the same error. > I know it's uncommon to send emails without txt but with attachments - but it may happen; at least we would welcome an error message. Without more of the traceback I can't be sure which handler is doing this and without the MIME structure I can't be sure what's going on. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/29/2017 03:46 PM, Barry Warsaw wrote: > On Mar 30, 2017, at 12:34 AM, David Krantz wrote: > >> When starting this as the recipe seems reasonable I find that I have >> no reliable source for git links for the parts. Some of the git links >> I find are marked with "do not use" so it is a bit hard having >> confidence in selecting one of the others. > > All the Mailman 3 suite subprojects are listed here: > > https://gitlab.com/mailman > > Those project links will take you to the active git repositories. The only > one you should not use is mailman-bundler. To be more specific, the projects that are required for a fully functioning Mailman installation with Postorius and Hyperkitty are Mailman (the core) Hyperkitty (the archiver) Postorius (the web list management UI) django-mailman3 (common django things used by Postorius and Hyperkitty) MailmanClient (python bindings for the core REST API used by Postorius and Hyperkitty) HyperKitty - Mailman plugin (plugin for the core to communicate with Hyperkitty) -- 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

[MM3-users] Re: configure Mysql and postfix on mailman3

by Mark Sapiro

On 02/20/2018 10:01 AM, Abhilash Raj wrote: > > One _hack_ that I can think of is that when using maps for postfix, Core calls the "postmap" command to generate the maps from the files that it generates. You can potentially provide a script that updates the MySQL database with the same configuration instead of generating maps and specify that script in configuration to be called by Core instead of "postmap". More information on how to do this. On mail.python.org we want to do some manipulations to the various maps, so we have a script to do this. The first step is in your mailman.cfg file, add an [mta] section if there isn't one and in that section add configuration: /path/to/your/postfix.cfg That file is a copy of mailman/config/postfix.cfg except you change the line postmap_command: /usr/sbin/postmap to postmap_command: /path/to/your/script While you could just edit mailman/config/postfix.cfg directly, this is not advisable as your edits will be lost in an upgrade. -- 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: Mailman core: basic internationalization howto?

by Mark Sapiro

On 10/04/2017 12:33 PM, thor.rustad(a)gmail.com wrote: > I finally got around to testing this setup. First I verified that the template in /var/templates/site/no was picked up when subscribing. Then I changed the text, and it stopped working. If I add one of these three Norwegian letters to list:user:action:subscribe.txt, I get the following in logs/mailman.log: > > UnicodeEncodeError: 'ascii' codec can't encode character '\xe5' in position 153: ordinal not in range(128) > Oct 04 19:18:41 2017 (29) Uncaught runner exception: 'ascii' codec can't encode character '\xe5' in position 153: ordinal not in range(128) ... > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 576, in _handle_confirmation_needed_events > msg = UserNotification(email_address, confirm_address, subject, text) > File "/usr/local/lib/python3.6/site-packages/mailman/email/message.py", line 124, in __init__ > @public ??? > UnicodeEncodeError: 'ascii' codec can't encode character '\xe5' in position 153: ordinal not in range(128) > Oct 04 19:18:41 2017 (29) SHUNTING: 1507144721.896973+35dc93aa969a0934bf717ca07965b09924eca59d See my comment at <https://gitlab.com/mailman/mailman/issues/413#note_42453740>. -- 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: Understanding of members, accounts

by Mark Sapiro

On 5/11/20 5:15 PM, Peter Adebahr via Mailman-users wrote: > Is the solution to "sign up", using one's very e-mail address already in > the system? Yes. The address is in the Mailman Core part of the systen, but not in the web UI part. > I would like to understand why there is a difference between being > (only) a subscribed member and a member having an account - or, what > might be the advantage of being a member without an account? Being a mailing list member is a Mailman core concept. It usually says you receive posts from the list based on your delivery status and you can post based on your moderation status. Logging in to the web UI to access HyperKitty and Postorius is a Django concept and requires a Django account. If all you want is to post by email and receive messages from the list, you don't need a Django account, but to manage your user settings via Postorius and to visit private archives, you do. -- 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: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 2/12/25 12:05, Christian via Mailman-users wrote: > That worked. > > Now on > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman > -automatically it says > > "Pay attention to the config file output above and make sure that you see > /etc/mailman3/mailman.cfg there. If the config path is different, you should > make sure to create a new config file at /etc/mailman3/mailman.cfg and > re-run the command." > > Well...mailman info yields > > GNU Mailman 3.3.5 (Tom Sawyer) > Python 3.7.3 (default, Mar 23 2024, 16:12:05) > [GCC 8.3.0] > config file: /opt/mailman/mm/mailman.cfg > db url: postgres://mailman:5DqTHnv8hUQSdd@localhost/mailman > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass > > Should I create a new config file at /etc/mailman3/mailman.cfg ? You can, but the easiest thing is just replace the line Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" in /etc/systemd/system/mailman3.service with Environment="MAILMAN_CONFIG_FILE=/opt/mailman/mm/mailman.cfg" -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: Issue with Held Messages

by Mark Sapiro

On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: > > No matter what action I set for member posts (Hold for moderator, > Reject) they are always delivered. I don't know why this would be. Perhaps the member's moderation is set to Accept immediately - you can see this on ther member's options page in Postorius when logged in as a list owner. When the message is delivered, what are the X-Mailman-Rule-Hits: and X-Mailman-Rule-Misses: headers? > When I tried from a non-member email address, the message got held but > when I try to see it I get a Server Error (500) page. The log files shows: > > ERROR 2016-08-18 01:04:30,231 base 21026 34722993152 Internal Server > Error: /mailman3/lists/test.mydomain.com/held_messages > Traceback (most recent call last): ... > File > "/usr/local/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", > line 443, in held > moderation_reasons=entry['moderation_reasons'], > KeyError: u'moderation_reasons' This is apparently <https://gitlab.com/mailman/mailmanclient/issues/10> fixed by <https://gitlab.com/mailman/mailmanclient/merge_requests/16> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

[MM3-users] dkim failing

by Mark Sapiro

On 10/15/18 8:37 PM, Abhijith PA via Mailman-users wrote: > > I am seeing dkim fail in mail that people send to lists > /dkim=fail reason="signature verification failed"/ > but it is not happening when the list solely sending mail to subscribers > (like digest, or subscribe/unsubscribe messages etc). I recently added a > new domain to the mailman3. After this I started noticing this issue. > Any help ? Are you saying the DKIM signature on the incoming post fails to validate in the post as sent from the list, or are you saying that a DKIM signature added by your MTA to the outgoing post fails to validate. If the former, this is probably expected. If your list does any content filtering, adds a subject prefix or adds a list header or footer, these transformations will break the incoming DKIM signature. This is why we offer DMARC mitigations. If the latter, you may be doing your own DKIM signing before Mailman applies transformations to the message. You need to sign the message on the way out, not before. -- 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: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Mark Sapiro

On 10/25/21 1:45 AM, Stefan Bauer wrote: > Dear Users, > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > web-interface via > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > I receive > > Not Found: /mailman//postorius/lists/ > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core > 1) > > Where does the wrong path come from (mailman vs. mailman3) See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ... > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> Others have found that removing the trailing slash from ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ to make it ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost fixes the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: mass subscribers disablement!?

by Mark Sapiro

On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote: > Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. Is > there a way to see via the web GUI which subscribers were disabled? > Correspondingly, can I re-enable delivery for them via the web GUI? Only one at a time. You could modify the shell session I posted previously to just display the members. ``` $ bin/mailman shell 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. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print('Delivery disabled by bounce for member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> exit() ``` Alternatively you can script some mailman commands as in ``` #!/bin/bash for list in `bin/mailman lists|sed '1d'`; do echo $list bin/mailman members --nomail bybounces $list done ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: How to delete non-users

by Mark Sapiro

On 9/17/22 10:03, Allan Hansen wrote: > Hi Mike, > > Yes, the users can be subscribed, but they think that they can't because it seems they are until the moderator accepts them. > > I tried your script again, with nothing happening. So I tried this: > >>>> >>>> a = 1 >>>> b = 1 >>>> for l in lm: > ... print(a) > ... a = a+1 > ... for nm in l.nonmembers.members: > ... print(b) > ... b = b + 1 > ... nm.unsubscribe() > ... >>>> commit() >>>> print(a) > 1 >>>> print(b) > 1 > > > It appears that lm can't see the lists (I have 50+ of them). Did you start with lm = getUtility(IListManager) ? What if you do ``` >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... ``` That should print the posting address for all the lists. What does `mailman info` show? In particular, for `config file:` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Fresh installation mailman3-suite via "pipx" - any experiences yet?

by Mark Sapiro

On 1/26/24 07:06, Stephen J. Turnbull wrote: > > I'm pretty sure it will install dependencies. I think (everything I > say below is based on reading the README.md from pipx's pypa.io repo, > so caveat installer) that the complexity that will arise is that (for > example) a naive approach like > > $ pipx install mailman > $ pipx install mailmanweb > $ pipx install postorius > $ pipx install hyperkitty > > will create 4 separate venvs with 3 copies of mailmanclient, 3 copies > of django-mailman3, and two copies of Django. But postorius and hyperkitty are dependencies of mailmanweb so only $ pipx install mailman $ pipx install mailmanweb should be required. This should put core in one venv and everything else in another without redundancy. > Besides the space > waste, there's also the small problem that mailmanweb won't have copies > of postorius and hyperkitty in its venv. But it will because they are dependencies of mailmanweb. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Recipient address rejected: User unknown in local recipient table

by Mark Sapiro

On 8/19/24 16:24, eyoelz--- via Mailman-users wrote: > Error: > Aug 19 15:06:10 xxx-rocky9 postfix/smtpd[153746]: NOQUEUE: reject: RCPT from xxxx.xxxxxx-xx.iphmx.com[xx.x.xx.xxx]: 550 5.1.1 <devops(a)xxx.xxx.edu>: Recipient address rejected: User unknown in local recipient table; from=<xxx(a)xxxx.edu> to=<xxx(a)xx.xx.edu> proto=ESMTP helo=<xx.xx-xx.iphmx.com> Is xx.xx.edu in to=<xxx(a)xx.xx.edu> The same as > main.cf > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination > myhostname = xxx.xxx.edu xxx.xxx.edu in myhostname? > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases > mydestination = $myhostname, mailman, localhost.localdomain, , localhost > relayhost = [xx.xx.xx.xx] > mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 > recipient_delimiter = + > inet_interfaces = all > inet_protocols = all > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp What is the content of postfix_lmtp? In particular is there an entry for xxx(a)xx.xx.edu? > local_recipient_maps =$alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains Is this the complete main.cf? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 3 weeks

[MM3-users] Re: Domain in welcome message

by Mark Sapiro

On 02/19/2017 02:05 PM, Maadix wrote: > Hi, > I'm having problems with customizing welcome message > > It's working fine for > var/templates/site/en/welcome.txt > > but not for domains or lists , so maybe I'm doing something worng > > I'm using a subdomain as mail_host which is different from the URL Host. > > I've been trying all these combination, with no success: > > var/templates/domains/sub.example.com/en/welcome.txt > var/templates/lists/listname.sub.example.com/en/welcome.txt > var/templates/lists/listname(a)sub.example.com/en/welcome.txt > > I'm running mailman-bundler version 3.0.0 Templating has changed for MM 3.1, and I don't have a 3.0 platform available for testing, but as far as I can recall, the paths var/templates/domains/sub.example.com/en/welcome.txt and var/templates/lists/listname.sub.example.com/en/welcome.txt should be valid for domain and list specific templates and the precedence should be (high to low) list, domain, site, default. I don't know why it isn't working for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 5 months

[MM3-users] Re: leaving Sympa for MM3

by Mark Sapiro

On 2/20/20 3:12 PM, rance.hall(a)esu10.org wrote: > > Now for the question/hard part. Migrating list archives. > > In Sympa the list archive is just a maildir format directory structure reflecting month/year. In MM3 the Archive is stored in the db with attributes that are likely only available as the message is processed. > > I'd really rather not loose the archive data if I can help it. Does anyone have any thoughts on how I could perhaps import this? It shouldn't be hard. HyperKitty has a function to import archive mbox files. It would be a simple matter to use Python's mailbox module to convert your archive. Something like import mailbox md = mailbox.Maildir('path/to/maildir/directory', create=False) mb = mailbox.mbox('path/to/mbox', create=True) for msg in md: mb.add(msg) mb.close() md.close() Then just run hyperkitty_import to import the mbox. run something like django-admin hyperkitty_import --help for details. Note that if there are already archived messages you need to specify --since to import older messages. -- 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: New releases

by Mark Sapiro

On 9/11/20 8:19 PM, brylon(a)oit.rutgers.edu wrote: > I already have ruby-sass installed and the compress command used to work as expected prior to my upgrading to the latest core, postorius, hyperkitty versions using pip in my venv. > > Does It matter at all when performing the Django-admin commands whether I've activated the venv or not? I think I've tried running them both activated and deactivated to no avail, but any other suggestions? I don't think that's the issue here, but the venv should be active when you run the Django-admin commands. Looking more closely at the error, I see it says ``` File "/opt/mailman/mm/venv/lib/python3.6/site-packages/compressor/base.py", line 282, in precompile mod = import_module(mod_name) ... ModuleNotFoundError: No module named 'sass -t compressed {infile} {outfile}' ``` Thus it appears that compressor is trying to import 'sass -t compressed {infile} {outfile}' as a module instead of executing it as a command. What version of compressor is this? It is working for me on 4 sites with django_compressor-2.4, django_compressor-2.3 and django_compressor-2.2. -- 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: spanish localization

by Mark Sapiro

On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > But... here is a thing that I can not understand: If the source (the .po > file) is from november 7th, it doesn't matter how many times you > recompile it: the result will be the same. Correct, but the point is if you download the latest gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 file in the distribution, you will find they are identical, so it it appears that the weblate translation hasn't changed since that time. If there are issues in this mailman.po, they exist in weblate too and need to be fixed there. Also note that the translations on weblate only affect strings in the core code. The Mailman core templates are not currently translated in weblate and there are currently no Spanish language templates. One would need to create Spanish translations of all the templates in <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> and submit a merge request to add them to a mailman/templates/es/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Problem with redirection when entering alias without a / at the end

by Mark Sapiro

On 3/19/21 2:55 PM, Jens Günther wrote: > > When I want to get to Mailman Starting Page now I need to Enter the > following URL: https://mailman.xyz.de/mailman3/ to be directly > redirected as expected to > https://mailman.xyz.de/mailman3/postorius/lists/ -> works. > > Problem: When leave out the slash at the end and I ONLY enter the > following URL: https://mailman.xyz.de/mailman3 -> then I'm wrongly > redirected to a page, taht does not exist: > https://mailman.xyz.de/mailman/postorius/lists/ -> 404 Huh? that is the same URL as the one above that you say works. Do you mean https://mailman.xyz.de/mailman/postorius/lists without the slash or what. > Where can I change this misbehaviour? In Apache-conf everything seems as > it'S in the docs, for the vHost I do not have any other custom settings. What is the exact content of your RedirectMatch or ReweriteRule or whatebver you are using? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/7/21 11:54 PM, Kimmo L wrote: > Hi! > > Thanks for the support and help! > But so far i havent been successful with upgrading my postorius, hyperkitty and django pip packages from python2.7 to python3.5 or higher. As i understand, it was installed 2018 and has not been updated (because it has been working without any problem). Perhaps we can help with that. How are these installed now? What issues are you having when trying to upgrade. > Maybe the easiest way is to create a new deployment and somehow transfer data from old server to new one ? It's up to you which way to go. If you create a new deployment, I recommend following https://docs.mailman3.org/en/latest/install/virtualenv.html. You might also consider Xapian as the search engine - see https://docs.mailman3.org/en/latest/config-web.html#enable-full-text-search… and https://github.com/notanumber/xapian-haystack/tree/master Transferring the data is easy as long as the database is compatible - just dump and load, plus copy some files from Mailman's var/ directory. -- 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: multiple sites on a mailman3 server question

by Mark Sapiro

On 12/29/21 8:48 AM, William Oliver wrote: > > What I'm trying to figure out is where uwsgi yanks control from nginx > and does the rewriting. Pulling that proxypass stuff out will stop > mailman3 from coming up, and adding it allows mailman3 to show its > interface, but the address gets referred regardless. > > Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow tell > nginx not to push it to port 8000. But I don't see where nginx is > getting told to go to 8000 in the www.domain.com section. If you are following https://docs.mailman3.org/en/latest/install/virtualenv.html you have ``` location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } ``` in your nginx config and everything goes to uwsgi. What you want is to put those proxy directives in only the mailman locations as at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and then configure your document root so other locations are served from there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: anyway to change/set options for a bunch of users?

by Mark Sapiro

On 3/22/22 06:19, bob B via Mailman-users wrote: > We just migrated to mailman 3 and one of my admins asked is there a way to change their digest options, when adding a bunch of users via mas subscription? Not yet at least. You could submit a feature request at https://gitlab.com/mailman/postorius/-/issues/new to be able to set Delivery mode when mass subscribing. > I was looking for an option to say all new users are set to digest, but I can't find it. Also, is there a way to select multiple users in list and change their digest options? I believe could do this in mailman2 but I am trying to figure out if this is possible for the GUI in mailman3? No, it's not, and in MM 2.1 you could check the digest option for multiple users in the Membership Management... -> Membership List, but if the list was paginated, you'd still need to go page by page. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Function "Mass subscription" does not allow any more the format `"Givenname Familyname" <mailaddress>`

by Mark Sapiro

On 12/22/23 10:34 AM, Wikinaut wrote: > Wheras my older lists handled these format apparently correctly, I now cannot add any more > > "Givenname Familyname" <mailaddress> ; or > Givenname Familyname <mailaddress> > > In any of these cases, only the part <mailaddress> is added. > > Is this strange behaviour know? > What can be done to have the correct function back to working again? There haven't been any changes to this. The issue is almost certainly that when subscribing "Givenname Familyname" <mailaddress> ; or Givenname Familyname <mailaddress> if there is no Mailman user/address for <mailaddress>, one will be created with display name `Givenname Familyname`, but if there is an existing user/address for <mailaddress>, its display name won't be changed. In this case, you can find the user at https://www.example.com/mailman3/users, click the user's Manage button and update its display name. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Legit login attempts yield, "An error occurred while processing your request."

by Mark Sapiro

On 8/14/24 3:18 PM, Greg Newby wrote: > > My primary question is: *How can I find out what's causing this*? > > I've looked in all the MM and web logfiles, by "tail -f" while generating > the error, and nothing is logged there. Apache logs shows something like > this: > > x.x.y.y- - [13/Aug/2024:21:46:41 -0700] "POST /accounts/password/reset/ > HTTP/1.1" 500 1448 "https://lists.pglaf.org/accounts/password/reset/" > "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/127.0.0.0 Safari/537.36 Edg/127.0.0.0" This is django-allauth. Errors should be logged in Django's log which, if yoiu followed our virtual env install doc is /opt/mailman/web/logs/mailmanweb.log. > I've come across this error while trying to do authentication-related > activities that worked before the reboot: Did django-allauth get upgraded to >=64.0. There are currently issues with that. It should be >=0.63,<64.0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

[MM3-users] Re: API privileges question for mailman3

by Mark Sapiro

On 10/14/21 12:41 PM, bob B wrote: > In mailman3 documentation it says: > "Because the REST server has full administrative access, it should never be exposed to the public internet. By default it only listens to connections on localhost." > > So I just wanted to confirm there is no way to limit API access? For example I have a group that wants to use API access to mange their mail lists, but from what I can gather, if I give them access to the API they would have access to ALL the mail lists etc.. I would suspect this is even true if I give them their own domain? > > Is there anyway to limit access via the API to certain lists etc..... No, there isn't. If Postorius is not suitable for some reason, you would need to implement an application on the host to provide a user interface to the API with appropriate authentication and controls. There are some ideas but no actual code at <https://gitlab.com/mailman/lemme>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: What's the difference between (purpose of) reject and ignore

by Mark Sapiro

On 6/26/22 08:07, Andy Smith wrote: > > On Sun, Jun 26, 2022 at 12:37:05PM -0000, denis.bitouze(a)univ-littoral.fr wrote: > >> Just to be sure: for this feature, is it necessary to click on the >> subject and to choose in the drop-down list “Discard (no >> notification)”, or is it enough, on the .../held_messages page, to >> select the messages and click on “Discard”? > > Doing it from the held messages page will be a one-time thing; it is > only by clicking on the individual message that you can choose an action > for future messages from that address. In case the above is not clear, selecting the message and clicking Discard will only discard that message. To automatically discard all future messages from that sender, you need to set that (non-)member's moderation action to Discard which you can do by clicking on the subject and selecting the Discard moderation action from the dropdown list. -- 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: Mailman 3 Hyperkitty indexes not being built

by Mark Sapiro

On 10/18/22 05:27, tom(a)gather.coop wrote: > My config looks like this: > > HAYSTACK_CONNECTIONS = { > 'default': { > 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > 'PATH': os.path.join(BASE_DIR, "fulltext_index"), > ... > I have whoosh 2.7.4 installed. But my fulltext_index directory contains only one file, _MAIN_0.toc, which hasn't been updated in two years. > > What could be going on here? Presumably Hyperkitty should be indexing new messages as they are archived. I could run update_index to fix the index now but then it would just go out of date again. > > Also asked on SO: https://stackoverflow.com/questions/74055901/mailman-3-hyperkitty-indexes-n… And answered there. You need to be running several things periodically via cron. For Mailman core, see https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs and for Django, see https://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required. The particular job which updates the search index is the hyperkitty update_index job which in current HyperKitty is one of the hourly jobs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: bounces with empty message-id

by Mark Sapiro

On 01/31/2018 11:57 AM, Peter Münster wrote: > On Wed, Jan 31 2018, Mark Sapiro wrote: > >>> I have verp_delivery_interval = 10 ... >> >> Which says only every 10th message will be VERPed. You want >> verp_delivery_interval = 1 to VERP every message. > > Hi, > > Why? The smtp relay host would get much more outgoing messages. With > verp_delivery_interval = 10, only 10% of the messages would be > personalized. Shouldn't this be enough to detect sooner or later, that a > recipient address is no more valid? Or is it important, to detect such > failure immediately? Yes, VERP does increase the number of SMTP transactions to deliver the mail from mailman to the outgoing MTA, but in general it has mush less effect on deliveries from the outgoing MTA to the recipient MXs, but with modern hardware, most people seem to find the added overhead of VERP to be minimal. Also, it is possible to have the MTA do the VERPing rather than Mailman. See <https://bugs.launchpad.net/mailman/+bug/558067> for a way to do this in Mailman 2.1. There's nothing for Mailman 3, but all that's needed is to configure Postfix to do it and add an appropriate mail_options= to the smtplib.SMTP.sendmail() calls to enable it. In any case, consider (assuming automated bounce processing is working, which it currently isn't) a list with bounce_info_stale_after = 7 days that gets even a post per day and has a member who is bouncing with a DSN that can't be successfully parsed for the member address (maybe because the bounce is from a forward to a different address) so only a VERPed bounce will be successfully scored. At some point a VERPed post bounces for this member and the member gets a bounce score of 1. Now, the next 9 posts to this list will not be VERPed and by the time the 10th post bounces it's more than a week since the first bounce and the score is reset so this member's delivery is never disabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/6/21 2:00 AM, marcus.granath(a)gmail.com wrote: > > BUT I don't really follow you when you say that those 3 allowed users to send on the list should also have set to "Moderation: List default"? > How will they then be able to send messages, or what do I misunderstand here? My fault. Sorry for the confusion. I wrote: > Now, no one can post. To allow your set of users to post, you have > choices. The easy way but not secure against spoofing is to set the > Maderation Action for the three allowed members to List Default and toi > create a non-member for no-reply(a)abc.com and set it's moderation action > to List Default. That should have said "set the Moderation Action for the three allowed members to Defer or Default Processing (again two names for the same thing) and to create a non-member for no-reply(a)abc.com and set it's moderation action also to Defer or Default Processing." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/22/21 2:10 PM, Marco Marinello wrote: > Dear Mark, > > configuration needed much troubleshooting so I'm sure I always restarted mailman core along apache2 but since it's still a testing environment, I took the liberty to test it again for you. > > # pip install https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip > # pip install https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… It appears that https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… is the latest mailman-hyperkitty, but https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip is missing some commits. It has https://gitlab.com/mailman/hyperkitty/-/commit/79b22a23d3390db741a8233fa1ff… but is missing https://gitlab.com/mailman/hyperkitty/-/commit/ec9c8ed18798cf8f7e89dfaba001… which is very strange because it does seem to have https://gitlab.com/mailman/hyperkitty/-/commit/705bdbb2fb27be60d17ada7cba84… I Suggest you do pip install -U HyperKitty pip install -U mailman-hyperkitty which will get the latest packages from PyPI or if you want the heads from gitlab, pip install git+https://gitlab.com/mailman/HyperKitty.git pip install git+https://gitlab.com/mailman/mailman-hyperkitty.git -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Mark Sapiro

On 1/31/23 23:33, Odhiambo Washington wrote: > Is this a race condition? > > <CUT> > ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) > Traceback (most recent call last): > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django_extensions/management/commands/runjobs.py", > line 40, in runjobs > job().execute() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/jobs/update_and_clean_index.py", > line 37, in execute > run_with_lock(update_index, remove=True) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/lib/utils.py", > line 181, in run_with_lock > log.exception("Failed to update the fulltext index: %s", e) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/flufl/lock/_lockfile.py", > line 470, in __exit__ > self.unlock() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/flufl/lock/_lockfile.py", > line 420, in unlock > raise NotLockedError('Already unlocked') > flufl.lock._lockfile.NotLockedError: Already unlocked > <CUT> Yes, it is a race between the monthly hyperkitty update_and_clean_index job and the hourly hyperkitty update_index job -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: cannot import name 'parse_header' from 'django.http.multipartparser

by Mark Sapiro

On 2/26/25 07:40, Stefan Bauer via Mailman-users wrote: > Dear Users, > > i recently tried to upgrade to latest MM3 and followed this[1] steps. > > However > > (venv) $ mailman-web migrate > > fails with: > > from rest_framework import mixins, views > File "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/views.py", > line 15, in <module> > from rest_framework.request import Request > File "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/request.py", > line 17, in <module> > from django.http.multipartparser import parse_header > ImportError: cannot import name 'parse_header' from > 'django.http.multipartparser' > (/opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py) > (venv) mailman@edmmal03$ vi > /opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py > > Could this be a broken dependency? You have an incompatible configuration. django.http.multipartparser.parse_header was removed in Django 4.2. See https://docs.djangoproject.com/en/5.1/releases/4.2/#miscellaneous Your version of djangorestframework is incompatible with Django>=4.2. Try in your venv ``` pip install --upgrade djangorestframework ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months

[MM3-users] Re: Which crontab?

by Mark Sapiro

On 11/03/2017 11:43 AM, Pierre Abbat wrote: > According to http://docs.mailman3.org/en/latest/config-core.html, I have to > add "@daily mailman digests --send" to the crontab. Which crontab does it go > in? In the system crontab, the thing after the time is the username, and > there's no user named "mailman" in /etc/passwd. Or should I put a script in / > etc/cron.daily/? The partucular "@daily mailman digests --send" would have to go in the user crontab for the Mailman user. If this is not 'mailman' it is what ever user "owns" Mailman. Further it would require that the path to Mailman's bin/mailman command be in that users $PATH. If it were to go in the system /etc/crontab it would need to be something like @daily user /path/to/bin/mailman digests --send where 'user' is the Mailman user as above. That could also go in a file in /etc/cron.d/ Or you could put an executable script to run '/path/to/bin/mailman digests --send' in /etc/cron.daily Your choice. -- 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: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Mark Sapiro

On 10/13/21 3:53 PM, Christian Stalberg via Mailman-users wrote: > Is this anything to be concerned about? It seems like an attempted break-in as I have no user named alekos.pantazis. First, this is a Django user, not a Mailman user. > -----Original Message----- > From: noreply(a)lists.ccalternatives.org <noreply(a)lists.ccalternatives.org> > Sent: Tuesday, October 12, 2021 7:55 AM > To: csa(a)web-analysts.net > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ > > Internal Server Error: /user-profile/ > > TemplateSyntaxError at /user-profile/ > 'd_gravatar' is not a registered tag library. Must be one of: The d_gravatar template tag was introduced by https://gitlab.com/mailman/django-mailman3/-/merge_requests/114 to support the `HYPERKITTY_ENABLE_GRAVATAR = False` setting for the user profile page. It should be OK. The error you see seems to say that django_mailman3/templates/django_mailman3/profile/profile.py contains {% load gravatar %} at line 3 but there is no django_mailman3/templatetags/d_gravatar.py file. Do you have the django_mailman3/templatetags/d_gravatar.py file in your installation? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: spf/dkim/dmarc

by Mark Sapiro

On 5/19/23 09:10, Christian via Mailman-users wrote: > > May 18 12:53:11 lists postfix/smtp[28104]: C9D7A1005DA: > to=<billb6951(a)gmail.com>, > relay=gmail-smtp-in.l.google.com[142.250.138.27]:25, delay=0.69, > delays=0.01/0.01/0.14/0.53, dsn=5.7.26, status=bounced (host > gmail-smtp-in.l.google.com[142.250.138.27] said: 550-5.7.26 The MAIL FROM > domain [lists.ccalternatives.org] has an SPF record 550-5.7.26 with a hard > fail policy (-all) but it fails to pass SPF checks with 550-5.7.26 the ip: > [192.46.218.224]. To best protect our users from spam and 550-5.7.26 > phishing, the message has been blocked. Please visit 550-5.7.26 > https://support.google.com/mail/answer/81126#authentication for more 550 > 5.7.26 information. p3-20020a056870868300b001926c1449a6si1393979oam.240 - > gsmtp (in reply to end of DATA command)) `dig txt lists.ccalternatives.org` reports "v=spf1 a mx ip4=192.46.218.224 -all" It should be "v=spf1 a mx ip4:192.46.218.224 -all" i.e. :, not = > Could the hard fail policy be implicated in the gmail rejection? Yes but only because the ip4 is not effective due to the syntax error. ~all could help, but I suspect replacing the = with : will do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: List mails blocked from GMX - web.de > Spamfolder

by Mark Sapiro

On 7/19/23 10:45, Stephen J. Turnbull wrote: > > % host -t TXT _dmarc.gmx.net > _dmarc.gmx.net descriptive text "v=DMARC1; p=none; sp=quarantine; rua=mailto:dmarcreport@gmx.net" > % host -t TXT _dmarc.web.de > _dmarc.web.de descriptive text "v=DMARC1; p=none; sp=quarantine; rua=mailto:dmarcreport@web.de" > > The important part is "p=none", which says that GMX does not reject or > quarantine *solely* because of a DMARC fail.[1] Not exactly. These DMARC records specify policies suggested to be applied by any recipient server to mail From: addresses in these domains. They don't say anything about mail To: addresses in these domains From: addresses in other domains. > Footnotes: > [1] IIRC, the "sp=quarantine" means that some fraction of DMARC > failing mail should be quarantined for testing purposes, but the > default fraction is 0 so that is ignored. Actually "sp" is subdomain policy and specifies the policy to be applied to mail From: sub-domains of the main domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Mark Sapiro

On 07/18/2018 02:07 AM, Sebastian Hagedorn wrote: > > I have only now started playing around with Mailman 3.2, because I never > managed to get the earlier releases to work, and reading through the > documentation I thought that such situations could be handled with > Alembic, as described here under "Database Migrations": > > <http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html> > > Is that not the case, and if not, in what cases can or should it be used? Alembic is used by Mailman core to migrate changes in Mailman's data models (database schema). It interfaces with SQLAlchemy <https://www.sqlalchemy.org/> which is used by Mailman core to interface with the underlying SQL database. Alembic is used by mailman developers to create migrations when table and column definitions are modified for some reason. It is not used by end users unless they are actually modifying Mailman's code and database schema. Alembic does not do migrations based on a change in the underlying database engine, e.g. SQLite -> PostgreSQL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Hyperkitty performance problem

by Mark Sapiro

On 11/22/24 00:37, Odhiambo Washington via Mailman-users wrote: > On Fri, Nov 22, 2024 at 9:59 AM Tobias Diekershoff <tobiasd(a)fsfe.org> wrote: >> >> Are Mailman3/Postorius and Hyperkitty supposed to run in separated >> databases, or are they supposed to use the same database? ... > > The official documentation specifies two DBs - one for Mailman Core and the > other for Mailmanweb. > As far as I know, there are no conflicts in the tables so you could use the > same DB for both. And the mailmanweb DB is for HyperKitty and Postorius. I know of no doc suggesting separate databases for HyperKitty and Postorius and in fact accomplishing that would require separate Django instances for HyperKitty and Postorius. I.e., Postorius, HyperKitty and django-mailman3 are all Django applications and use the database configured in Django's settings. Mailman core is separate and uses the database configured in mailman.cfg. As Odhiambo says, there are no table conflicts between these databases so they can be either the same database or separate databases as you wish. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 1 week

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 6:11 PM, David Newman wrote: > On 1/14/22 4:54 PM, Mark Sapiro wrote: >> >> It should work. I suspect you need to go to the list's Settings -> >> Automatic Responses and set `Admin immed notify` to Yes. > > > It's enabled. I think this triggers notifications only for new > subscription requests, not pending ones. Yes. That will send a single notification at the time of the request using the `list:admin:action:subscribe.txt` template. Notices of pending requests are sent by the `mailman notify` command using the `list:admin:notice:pending.txt` template. ... >> You can test `mailman notify` at any time by running it by hand. > > > Thanks. This still isn't working as intended. I took these steps: > > 1. Created the file > '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' The template name is `list:admin:notice:pending.txt`, not `list:admin:action:pending.txt`. Thats why it didn't work. ... > 2. Restarted the mailman3 and mailmanweb services You only needed to restart Mailman core. ... > What I'm trying to do here is replicate a feature from MM2.1, where > pending notifications had URLs embedded in the message. That's not > available out of the box in MM3, and if there's a place for feature > requests I'd be glad to ask that this be made the default. The place for feature requests for Mailman core (which this is) is https://gitlab.com/mailman/mailman/-/issues, however, this is not straightforward as Mailman core doesn't know if you even have Postorius or some other web management UI installed or what the URL to access it might be. Thus it's not just a simple matter of editing templates. It would also require a configuration setting for the base URL for the web admin UI and changes in logic to provide an appropriate replacement depending on whether or not the base URL was configured. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 6/16/22 15:46, Dan Caballero wrote: > Which database table contains these pending subscriptions? I checked the "members" and "address" tables but no luck yet. > > I'm trying to help someone clear a few hundred of these. I can try writing a Python script to use the "hex_token" values in the Python dict. But maybe doing something via MySQL would be easier. The tables are `pended`, `pendedkeyvalue` and `workflowstate`, but don't do it via MySQL. A `mailman shell` interaction like this is better. ``` $ ./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 >>> util = getUtility(IPendings) >>> for token, data in util.find(mlist=m, pend_type='subscription'): ... if data.token_owner == 'subscriber': ... util.confirm(token, expunge=True) ... >>> commit() >>> ``` -- 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: Cannot connect to SMTP server

by Mark Sapiro

On 8/13/22 15:14, mkummini(a)cmi.ac.in wrote: > > However, I get the following line each time I do a restart > Aug 14 03:19:57 2022 (4096859) Cannot connect to SMTP server localhost on port 587 > I tried to specify the name of the postfix server, though it runs on the same machine as mailman3, and the different ports : 25, 465 and 587; they all raise the same error. You only see this message once at startup because it is only issued once until there is a successful delivery. This error can occur for reasons other than an inability to connect to the smtp server. In particular, if there are errors in decorating the message with a header and/or a footer because of permissions or other problems in retrieving a list:member:regular:header or list:member:regular:footer template, this will occur. Have you put templates in Mailman's var/templates directory (possibly named /var/lib/mailman/templates in the debian package). If so, can the Mailman user (I think `list` in a debian package) find and read them? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Mailman shutting down Hyperkitty: Request too large

by Mark Sapiro

On 1/31/25 21:44, Stephen J. Turnbull wrote: > > I don't think that's the best we can do, though. Especially if > Convert HTML to plain is also yes, we want to preserve the HTML part > and convert it, don't we? Not if we're collapsing alternatives. If we're collapsing a multipart/alternative part with text/plain and text/html alternatives to just the first alternative we don't keep the text/html part. The only html parts we keep and possibly convert to plain text are ones that aren't a second or later alternative in a multipart/alternative part. > I think a better (or additional) strategy > would be to check the selected alternative for blank, and if so, drop > it and try again for an appropriate type. The collapsing of a two part multipart message with an empty first part into a single part message with just the second part is the last thing that's done after all other content filtering. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Good choice of defaults for content filtering?

by Mark Sapiro

On 7/30/20 5:00 PM, hansen(a)rc.org wrote: > Hi all, > > I had MM2 set to the default filtering that I think came OOTB. MM3 has none such and I was wondering: > a. What were those MM2 defaults (My MM2 server is long gone now). You will find the content filtering defaults beginning at <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman…>. These have been the defaults for new lists since Mailman 2.1.21. Prior th that, the the default for pass_mime_types was ['multipart/mixed', 'multipart/alternative', 'text/plain'] > b. Is there a better set today. I know that MIME types can be faked, but they have worked. I want to avoid anything that can contain malicious code while also allowing simple text to go through. If you go with the current defaults, except of course for setting filter content on, you can add text/html to pass_types and any html parts that aren't collapsed out by collapse alternatives will be kept and converted to plain text. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Internal Server Error on installing Mailman 3 using PIP

by Mark Sapiro

On 10/28/20 11:04 AM, Shashikanth Komandoor wrote: > Dear Mark, > > As you have suggested in my earlier issue, I have implemented > the latest stable version of mailman 3 through the URL > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > . > > But after the installation through the above URL, when I > tried running the command *elinks http://localhost:8000/postorius/lists > <http://localhost:8000/postorius/lists>* or *elinks > http://localhost:8000/admin <http://localhost:8000/admin>*, I got the error > as *Internal Server Error*. > > I don't find any specific log in mailman.log or in > mailmansuite.log. > > Is there any way to solve this issue ? > You need to hire a consultant who understands Mailman 3 installation to help you with this. The help you need is beyond the scope of this list. I am not available as a paid consultant. I do not do that work. See <https://wiki.list.org/x/4489296> for a partial list of people who do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Mark Sapiro

On 1/14/21 3:43 PM, Eric Broens via Mailman-users wrote: > Hi Mark, > The link that shows the subscription request pending approval is as follows: 'https://<host_url>/postorius/lists/<listname>.<domain>/subscription_requests' > > The link behind the accept button is as follows. 'https://<host_url>/postorius/lists/<listname>.<domain>/handle_subscription_request/4d6b4b11266c7332684c5a492eb3f92c531f761b/accept' > > I have checked if there is already a subscription with that email address, but that's not the case. I don't know why that would 404 unless the token 4d6b4b11266c7332684c5a492eb3f92c531f761b didn't exist, but since it came from a "current" view, it should be good. I have seen occasional issues where two moderators attempt to handle the same request in close succession - i.e. both get the pending request and try to handle it and the second fails because the request is gone, but that appears not to be the case here. You might check the web server logs, the Django log and Mailman's logs to see if there is any more of a clue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Mark Sapiro

On 3/15/22 12:22, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > hmm. > the list-url (e.g. where you can subscribe to the list) for my instance > looks like https://$domain/postorius/lists/$list_id/ (that is: it spells > "postorius" rather than "mailman3"). > so i guess the URL should be > https://$domain/postorius/lists/$list_id/confirm/?token=$token, which > unfortunately returns 404. > > also, my postorius/urls.py does not contain an url-pattern for > "confirm", unlike the current one as found on > <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/urls.py#L83> > > > > so i guess this was not possible yet with postorius 1.2.4 Yes, This was added in Postorius 1.3.4 (over a year ago) > yes. > the *current* template. > but not the template that came with mailman3 3.2.1 Which is over 3 years old. You should really be taking up these issues with Debian. Maybe if they got enough pressure from users, they would update their package. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] {Spam?} Re: Monthly mailman-web job using a lot of memory

by Mark Sapiro

On 7/1/22 1:40 AM, Andy Smith wrote: > > In the job list I see: > > appname - jobname - when - help > -------------------------------------------------------------------------------- > hyperkitty - update_and_clean_index - monthly - Update the full-text index and clean old entries > > so I'm guessing it's that, but there is also: > > hyperkitty - update_index - hourly - Update the full-text index > > which hasn't been noitceably a problem so I wonder why the "and > clean old entries" bit is so much more heavyweight, what exactly it > dopes and if there's any way to make it lighter on resources? The difference is the update_and_clean_index job calls hyperkitty.search_indexes.update_index() with remove=True See https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/search_index…. The comments say "Setting remove to True is extremely slow, it needs to scan the entire index and database." I second Mark Dadgar's comment to replace whoosh with xapian. It will help, although it requires rebuilding the entire search index. -- 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: migrate MM3 list from an old server to a new one

by Mark Sapiro

On 8/6/24 01:43, noc(a)iem.at wrote: > > there *is* documentation about migrating MM2 to MM3; and my understanding is that `mailman-web migrate` can be used to upgrade a given MM3 instance to a new version. No. the mailman-web migrate command will apply relevant migrations for various django projects. You do need to rin it after upgrading things like hyperkitty, postorius and django-mailman3 and other dependencies which may have defined migrations for various database schema changes, but this will do nothing for your data. For that, you need to dump the mailman and mailmanweb databases on the old server and import them on the new server. > but how can i export an entire MM3 list (including 20 years of archives) to some serialization format, and import it again in another instance? With the dump and other utilities from your database manager. Almost everything is in the database. There are some things in Mailman's var/ directory, but those can simply be moved. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: MTA setup

by Mark Sapiro

On 12/24/24 09:31, Arte Chambers via Mailman-users wrote: > Looks like the from header is the email address I am using for testing: From: > Arte Chambers <paul.m.robey(a)gmail.com> I'm not sure what's going on. Previously, I said > Presumably it has previously requested and received the list_url and > the permalink to put in the message headers. This can be confirmed by > the presence of List-Archive: and Archived-At: headers with values > in the messages from the list. but they aren't there. ... > Archived-At: <> > List-Archive: <> I was able to add that message to a test list with no problem, so now it looks like the issue is possibly mailman_hyperkitty not able to communicate with hyperkitty, although the log messages aren't consistent with that. Possibly the issue is not with the message you sent, but with the first message in var/archives/hyperkitty/spool/. Is /1734973370.5060537+806f73d2a296b0293228a9489b81129740d7afea.pck the first file in a listing of var/archives/hyperkitty/spool/? If not, what does `mailman qfile` show for the first one? -- 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: Implementing threading [was: hyperkitty failed to create a thread]

by Mark Sapiro

On 2/12/19 8:09 AM, Stephen J. Turnbull wrote: > > I suppose HyperKitty uses References (it works for messages that have > proper Message-IDs ;-), but I don't know what algorithm it uses. > Might be worth looking into, as well as considering a more Postelian > parsing of Message-IDs. Specifically, take the field body, unfold it, > strip leading and trailing whitespace and leading "<" and trailing > ">", and whatever's left is the message ID. Hyperkitty uses In-Reply-To: and if absent falls back to the last item in References: to determine a message's parent. I haven't looked at what happens if the parent is not in the archive but arrives later. We could look at earlier References: items to try to find one we know, but this could result in bad threading if a later reference arrives after we think we've determined the parent. The unfolding of Message-ID: is now correct. See <https://gitlab.com/mailman/hyperkitty/merge_requests/125>. -- 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: bounces with empty message-id

by Mark Sapiro

On 01/30/2018 11:38 PM, Peter Münster wrote: > On Tue, Jan 30 2018, Mark Sapiro wrote: > >> The underlying issue is the orange.fr domain is sending DSNs without a >> Message-ID: header. > > Yes. Is a Message-ID header required in a DSN by any RFC? It's not a MUST, just a SHOULD, but RFC 5322, sec 3.6.4 says Though listed as optional in the table in section 3.6, every message SHOULD have a "Message-ID:" field. >> If you used VERP (i.e. set verp_delivery_interval = 1 in the [mta] >> section of your config), this log message > > I have verp_delivery_interval = 10 ... Which says only every 10th message will be VERPed. You want verp_delivery_interval = 1 to VERP every message. >> would contain to=<test-bounces+user=example.com(a)my-domain.org> and you >> could identify the bouncing address (user(a)example.com in this case) that >> way. > > Yes, that's my intention, but first of all, mailman must receive the DSN. The message does appear in the mail log, but until the issues below are fixed, even if Mailman receives it, you won't see it. >> Beyond that, there are still other issues, the biggest of which is >> currently, Mailman is not processing bounces other than storing them in >> the database. See <https://gitlab.com/mailman/mailman/issues/343>. > > Shouldn't the DSNs be forwarded to the owner of the list? They should be processed by Mailman and scored as bounces for the recipient if recognized and forwarded if not (depending on settings), but they currently are only stored. >> if a recipient MTA can't create a DSN that has a Message-ID:, would >> you trust what else it does? > > I don't know. The question for me is: does the remote MTA needs a fix > (i.e. the Message-ID is required by some RFC), or mailman (i.e. a DSN > without Message-ID should be acceptable)? I have filed <https://gitlab.com/mailman/mailman/issues/448> for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Migration advice

by Mark Sapiro

On 08/28/2018 06:42 PM, Quanah Gibson-Mount wrote: > Hi, > > I'm looking at migrating from an old server running mailman 2.1.15 > (Debian wheezy) to a new Ubuntu 18.04 LTS system. I'd like to upgrade > to mailman3 as a part of this migration. I was reading the migration > docs (<http://docs.mailman3.org/en/latest/migration.html>), which seem > to require both mailman2 and mailman3 be installed concurrently on the > same system. Is that correct, or can I rsync the mailman2 list > information onto the new server without mailman2 itself being present, > and import from there? Short answer - Yes. You need only a Mailman 3 installation. You also need a copy of the Mailman 2 lists/LISTNAME/config.pck file for input to 'mailman import21' and a copy of the Mailman 2 archives/private/LISTNAME.mbox/LISTNAME.mbox file for input to the Django management hyperkitty_import command. It would be good to check the archives/private/LISTNAME.mbox/LISTNAME.mbox file with the Mailman 2 bin/cleanarch command, but you can do that on the Mailman 2 system before copying the mbox. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Using REST with CLI using curl .... help needed

by Mark Sapiro

On 12/8/20 2:01 AM, Krešimir Mihalj wrote: > Hi ! > I need simple add/delete member to list using rest ..... but all documentation is for python and not helpfull for me, .... and I need these in CLI using curl command .... Have you seen <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > To add member using CLI i tried this command: > > curl -d "{'list_id' : 'list.domain.com', 'subscriber' : 'user(a)email.com'}" -H 'Content-Type: application/json' --user restadmin:restpass http://localhost:8001/3.0/members Try this: > curl --user restadmin:restpass --data-raw 'list_id=list.domain.com&subscriber=user(a)email.com' http://localhost:8001/3.0/members > Also, if someone is willing to give example: delete user: user(a)email.com from list: list(a)domain.com First find the member_id with something like > curl -urestadmin:restpass http://localhost:8001/3.0/lists/list.domain/member/user@email.com which will return json including the value of member_id Then you can do > curl -urestadmin:restpass -X DELETE http://localhost:8001/3.0/members/xxxx where xxx is the member_id. -- 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: Problem with redirection when entering alias without a / at the end

by Mark Sapiro

On 3/19/21 3:12 PM, Jens Günther wrote: > > > -> the first one works and leeds to > https://mailman.xyz.de/mailman3/postorius/lists > -> the second one redirects to > https://mailman.xyz.de/mailman/postorius/lists > -> which does not exist, since Apache-alias is only for mailman3 Sorry, I missed that it was mailman vs mailman3. > > I only use the apache-conf given in the documentation: > > <code> > Alias /mailman3/favicon.ico > /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 > unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > </code> I don't use uwsgi so I can't advise on its configuration, but do you have USE_X_FORWARDED_HOST = True SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') in your Django settings? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Turned on archiving and it is not working

by Mark Sapiro

On 6/9/22 12:09, bob B via Mailman-users wrote: > > Jun 09 18:49:10 2022 (28) Exception in the HyperKitty archiver: <html><title>Auth required</title><body> > <h1>Authorization Required</h1><p>The archiver key is now > File "/usr/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > <h1>Authorization Required</h1><p>The archiver key is now > <h1>Authorization Required</h1><p>The archiver key is now The full message is <h1>Authorization Required</h1><p>The archiver key is now required to be sent over the Authorization HTTP header. You need to upgrade the mailman-hyperkitty package to 1.2.0 or newer. > HyperKitty version 1.3.5. As indicated in the above message, HyperKitty >= 1.3.5 requires mailman-hyperkitty >= 1.2.0 If your mailman-hyperkitty is < 1.2.0, you need to upgrade it. If it is 1.2.0, there is some issue with the http headers being dropped in the request from mailman-hyperkitty to HyperKitty. See the last two posts in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- 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: hyperkitty failed to create a thread

by Mark Sapiro

On 2/17/19 2:13 AM, Danil Smirnov wrote: > > Could you advise how to rebuild the failing threads please? I've done index > update with 'django-admin update_index' command but it seems irrelevant to > the issue, I still have all those messages separated: > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/2019/2/ I've not tried it and have no idea if it will work, but the query select message_id, message_id_hash, in_reply_to from hyperkitty_email; will show those things. You will see some (most) entries have a message_id of the form 'left-part@right-part' with no angle brackets, but some are of form ' <left-part@right-part>'. In those cases where 'left-part@right-part' of in_reply_to is in a message_id of form ' <left-part@right-part>', you could try altering that in_reply_to to ' <left-part@right-part>' After doing this, you probably need to run 'django-admin runjob thread_order_depth'. Obviously, make backups before you start. An alternative might be to 'fix' the message_id which may or may not require recomputing message_id_hash. -- 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: mailman3 vs postfix

by Mark Sapiro

On 4/29/20 7:35 AM, Ralf Wiegand wrote: > hey Mark, that worked. Thank YOU. Got one step ahead. So after > creating a admin account and logging in via the GUI, I get this error > message: > > > IntegrityError at /accounts/login/ > > UNIQUE constraint failed: account_emailaddress.email > > Request Method: POST > Request URL: http://192.168.0.27:8000/accounts/login/ > Django Version: 2.2.12 > Exception Type: IntegrityError > Exception Value: > > UNIQUE constraint failed: account_emailaddress.email > > Exception Location: > /opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/sqlite3/base.py > in execute, line 383 > Python Executable: /opt/mailman/venv-3.6/bin/python > Python Version: 3.6.8 > > What does this mean? I think it means you have more than one Django account with the same email address. If you can log in to your django admin interface as the superuser, you may be abl to go to 'Users' and delete one. If you can't log in to your django admin interface as the superuser for this reason, you will probably need to create another superuser. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: How to Unshunt Specific Message ?

by Mark Sapiro

On 8/11/20 9:55 PM, Shashikanth Komandoor wrote: > Hahahaha. > > Looks like a work around. Yes, it's a workaround. > I understood "moving out of the shunt queue" means "Moving the files from > /var/lib/mailman/mailman/var/shunt directory to any other directory say > /opt/...." in my environment. Because I installed mailman software inside > /var/lib/mailman only. It means first understand why the messages were shunted and fix whatever the underlying issue is or they will just be shunted again. You should look at each message in the shunt queue with `mailman qfile` and determine which ones you don't want at all, which ones you want to save for later and which ones you want to unshunt now. Just remove the ones you don't want at all. For the ones you want to save for later, move them to any other directory at all. Then run `mailman unshunt` for the remaining ones after which you can move the saved ones back or leave them where you moved them to. -- 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: only show mail domains from web host on web-host-url

by Mark Sapiro

On 3/19/21 6:38 AM, Jens Günther wrote: > Thank you for your answer. I should have seen that in the Docs, but > somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html > > I set it in the corresponding file, but unfortunately it doesn't work > :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS > works, changed here from '*' to 'localhost' and my example-domains, this > works). It seems to be the same as this user describes (a while ago): > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… FILTER_VHOST is problematic. It works fairly well for HyperKitty, but not so well for Postorius. In particular with Postorius it doesn't work if there is more than one mail host domain with the current web host. See these issues and MRs for more detail. https://gitlab.com/mailman/hyperkitty/-/issues/254 https://gitlab.com/mailman/hyperkitty/-/merge_requests/243/diffs https://gitlab.com/mailman/hyperkitty/-/merge_requests/244/diffs https://gitlab.com/mailman/postorius/-/issues/394 https://gitlab.com/mailman/postorius/-/merge_requests/500/diffs -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Auto discard after max_days_to_hold not working.

by Hitashi mancho

Thank you so much, Mark and Stephen, for the quick action and response. Waiting for the next release. On Tue, Apr 29, 2025 at 10:52 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/28/25 10:55, Mark Sapiro wrote: > > > > `mailman import21` will import the setting, but per the above comment, > > it doesn't yet work. The setting exists and is exposed in REST, but it > > appears it is not actually implemented. > > > This is now implemented for the next release. See > https://gitlab.com/mailman/mailman/-/issues/1215 and > https://gitlab.com/mailman/mailman/-/merge_requests/1346 for Mailman > core and https://gitlab.com/mailman/postorius/-/issues/628 and > https://gitlab.com/mailman/postorius/-/merge_requests/1001 for Postorius. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to huhamails(a)gmail.com >

3 months

[MM3-users] Re: Full-text searching: why Haystack instead of PostgreSQL?

by Mark Sapiro

On 6/10/25 02:33, admin(a)bclug.ca wrote: > I've been asked to give a presentation on a recent migration from MMv2 to MMv3 and one of the items in my notes is the question about why Haystack is used for full-text searching instead of PostgreSQL? > > Can someone shed some light on that decision? The people who developed HyperKitty are no longer actively involved with Mailman and I can't speak with any authority about their design decisions. That said, both Django and Mailman core support multiple databases including PostgreSQL, MariaDB, MySQL, Oracle and SQLite whereas Django's full text search relies on PostgreSQL specific features and without some custom implementation, which may not even be possible, would not allow other DBMs. Haystack on the other hand provides a unified API that works with multiple backends. As far as I know, no one has developed a Haystack backend for PostgreSQL full text search, but as Sam notes in another reply, there are supported backends for Solr, ElasticSearch, Whoosh and Xapian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

[MM3-users] Re: Strange problem in user lists

by Mark Sapiro

On 12/16/21 2:25 AM, Gelpi Andrea wrote: > > I cant' understand why, but I have two members with the wrong name. > > "A B" <C(a)dom.tld> > "D E" <F(a)dom.tld> > > My problem is that A and B must be associated with F(a)dom.tld and vice-versa. > > I tried to delete the user member and recreate it, but it has always the > wrong name. Because the display name is associated with the Mailman user and unsubscribing the user from the list doesn't change the user. > Is it possible to correct those errors? How? The user can log in to the web UI and go to the Account link in the dropdown at the username at the upper right and change the first and last name there. If you have a recent enough Postorius, a site admin can go to the Users link at the top of a page find the user, click Manage and change the Display Name. Otherwise, you can do this in `mailman shell` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Error 500 on held_messages page

by Mark Sapiro

On 2/4/22 04:57, Stephan Krinetzki wrote: > > we have fixed the issue now: Good. > mailman shell -l list(a)lists.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. > Die Variable 'm' ist die list(a)lists.example.com Mailingliste > >>> lr = IListRequests(m) > >>> for req in lr.held_requests: > ... if lr.get_request(req.id) is None: > ... print(req.id) > ... > 32598 > 22449 > 66937 > 68261 > 92927 > >>> > > With this IDs > > DELETE FROM _request WHERE id IN (32598, 22449, 66937, 68261, 92927); > > And the 500 error is gone. I'm glad you were able to fix it. Do you happen to have the content of those rows in the db before you deleted them? It would be interesting to know what that was to try to determine how that situation happened in the first place. -- 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: Verification emails 'helo' rejected

by Mark Sapiro

On 10/14/24 12:42, Greg Newby via Mailman-users wrote: > > Here are the corresponding logfile entries from mailmanweb.log: > smtplib.SMTPRecipientsRefused: {'redacted(a)gmail.com': (504, b'5.5.2 <mail>: > Helo command rejected: need fully-qualified hostname')} > > and from mail.log: > Oct 14 12:06:26 domain postfix/smtpd[722764]: NOQUEUE: reject: RCPT from > localhost[127.0.0.1]: 504 5.5.2 <mail>: Helo command rejected: need > fully-qualified hostname; from=<root(a)lists.domain.tld> to=<root@localhost> > proto=ESMTP helo=<mail> > > lists.domain.tld is the domain for Mailman3. I don't know why it's trying > to send email from root@. I think the mail.log entry is for the DSN for the failure. The issue is the HELO/EHLO command. Try the following in your venv ``` (venv) ...:~$ python Python 3... Type "help", "copyright", "credits" or "license" for more information. >>> import socket >>> socket.getfqdn() ``` If that returns `localhost`, that's the issue. I think you can fix it by putting a fully qualified domain name in /etc/hostname. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

[MM3-users] Re: Relaying email from external SMTP server (office365 or Exchange)

by Mark Sapiro

On 6/23/20 10:14 AM, Waqas Ahmed Khan wrote: > > Could you Please confirm, what should be hardware configuration (ram, > processor, disk) to run mailman3 server for medium size organization? This > server will have 10-15 lists and some lists having 10k to 20k members. Also > what should be DISK SPACE of the server for Archiving emails? We really don't have hard requirements and a lot depends on what else besides Mailman the server does. First of all, it appears from some reports that 2GB RAM is not enough, but for Mailman 3 alone, 4GB is ample and I suspect that would do for what you describe. For disk, consider mail.python.org This server currently supports 139 Mailman 3 lists. There are a total of over 36,000 known Mailman 3 users. There are archives going back in some cases, decades, with currently a total of over 673,000 archived messages. The Mailman 3 database with all the archived messages and user info is 8.7 GB. The Xapian archive search index is 18 GB. -- 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

Search results for query "sapiro"