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

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

by Andy Smith

Hi, On Fri, Jul 01, 2022 at 12:57:41PM -0700, Mark Sapiro wrote: > I second Mark Dadgar's comment to replace whoosh with xapian. It > will help, although it requires rebuilding the entire search > index. Thanks both. Yes I am currently using whoosh which is the Debian packages' default. I decided to dramatically reduce the number of messages in our archives, as the vast majority of them are for lists that had never actually been looked at ever when under Mailman2, and external archives of them already exist. For ~6k messages it still took approx 16 hours to run that monthly job, and during that time spewed out thousands of these errors: Failed to remove document 'hyperkitty.email.29351' from Whoosh: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py", line 309, in remove self.index.delete_by_query(q=self.parser.parse('%s:"%s"' % (ID, whoosh_id))) File "/usr/lib/python3/dist-packages/whoosh/index.py", line 365, in delete_by_query w = self.writer() File "/usr/lib/python3/dist-packages/whoosh/index.py", line 464, in writer return SegmentWriter(self, **kwargs) File "/usr/lib/python3/dist-packages/whoosh/writing.py", line 515, in __init__ raise LockError whoosh.index.LockError …so I'm not even sure if it worked. I will definitely have to look in to switching to Xapian. Thanks, Andy

3 years, 3 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

Hi Mark, 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25. This is weird because other mails have been distributed. The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id > Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25 webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0" <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0" This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too). 2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there. 3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these? mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings Best Regards,Eric On Sunday, December 13, 2020, 06:29:19 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 7:40 PM, Eric Broens via Mailman-users wrote: > There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail. I'm not sure what is causing the repeated access of /archives/api/mailman/urls... This call comes from Mailman core in order to request the URL at which a message will be archived. It is called from mailman/src/mailman/handlers/rfc_2369.py when adding the Archived-At: header and from mailman/src/mailman/handlers/decorate.py in order to get the hyperkitty_url replacement value. I don't understand why it would be called repeatedly for the same message. Are there any clues in mailman.log. > I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)." What if you look at "threads by month" and select the current month? > Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list. I think the basic issue is when you see no messages, HyperKitty, for whatever reason thinks there are no current messages. I'm not sure, but if there are recent posts, are they all in threads started more than 30 days ago? As far as all the participants/discussions counts being zero, I think one of the periodic jobs will fix that (possibly the daily recent_threads_cache job) -- 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/

4 years, 10 months

[MM3-users] Re: Enable delivery

by Hirayama, Pat

Apologies, I should've said my "Mailman 3" server, not listserv. MTA logs do not show messages being sent to the member(s) in question, even though other members are being sent messages. Nothing out of the mailman server, and nothing received by our outbound Postfix MTAs. As for the CLI commands, I keep getting Attribute Error when I try them, like: /opt/mailman # mailman shell -l listname(a)mailman.tld 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 listname(a)mailman.tld mailing list >>> from mailman.core.constants import system_preferences >>> mbr = m.members.get_member('user(a)domain.com.') >>> print(mbr.delivery_status) Traceback (most recent call last): File "<console>", line 1, in <module> AttributeError: 'NoneType' object has no attribute 'delivery_status' >>> Thanks, -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, December 9, 2024 18:38 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Enable delivery CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 12/9/24 17:35, Hirayama, Pat wrote: > Greetings, > > I'm finding something a bit odd with our listserv. Please see https://urldefense.com/v3/__https://wiki.list.org/DOC/Mailman*20is*20not*20… > Some of the members of some of the lists are reporting that they aren't receiving messages sent to the list. When I review the member options for the person in question, I see that Delivery Status shows nothing selected (i.e. neither radio button is selected for Enabled or Disabled). If you look in the MTA logs is mail being sent to them. As far as the Delivery Status showing nothing, that means the member's delivery_status is None. The ultimate delivery status is determined by checking first the member's delivery_status, then the address's delivery_status, then the user's delivery_status and finally Mailman's global preferences. The first non-None value is what's used. See https://urldefense.com/v3/__https://gitlab.com/mailman/mailman/-/blob/maste… Also see the various tabs at https://urldefense.com/v3/__https://www.example.com/mailman3/accounts/subsc… > If I select Enabled and Save, then delivery starts working for that user. This should only happen if the users address or user based preference or the global preference is Disabled. > There are other members of the list that have neither Enabled or Disabled selected, but they are working. Which also seems to mean that when I run: > > mailman members --nomail any listname@listserv > > Nothing is returned. Because all members ultimately have delivery enabled. > If anyone has any ideas about why this might be the case, or how I might proactively identify other members who aren't receiving mail, that would be appreciated. Alternately, any thoughts on how I might force all members to Delivery Status Enabled, that would also be great. It shouldn't be necessary to do that. For one of these members, e.g. user(a)example.com, that isn't getting mail, do this in mailman shell ``` 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 >>> from mailman.core.constants import system_preferences >>> mbr = m.members.get_member('user(a)example.com') >>> print(mbr.delivery_status) (this will print the ultimate delivery_status, for the components do) >>> print(mbr.preferences.delivery_status) (output) >>> print(mbr.address.preferences.delivery_status) (output) >>> print(mbr.address.user.preferences.delivery_status) (output) >>> print(system_preferences.delivery_status) (output) >>> ``` The first of the (output) lines which is not None should be the same as the output from print(mbr.delivery_status). -- 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://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailm… Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma… This message sent to phirayam(a)fredhutch.org

10 months, 1 week

[MM3-users] Re: configuring postfix local recipient table

by Alexander Inzinger-Zrock

Am 29.04.25 um 18:27 schrieb Mark Sapiro: >> Last idea before that would be to >> >> 1. delete the files: >> >> -rw-r--r-- 1 mailman mailman 0 Mar 21 11:58 postfix_domains >> -rw-r--r-- 1 mailman mailman 12K Mar 24 11:44 postfix_domains.db >> -rw-r--r-- 1 mailman mailman 0 Mar 21 11:58 postfix_lmtp >> -rw-r--r-- 1 mailman mailman 12K Mar 24 11:44 postfix_lmtp.db >> >> 2. restart services >> >> 3. test if programms make new files >> >> 4. report to mailinglist >> >> Would that be of interest to someone? > > Yes. + [X] deactivate services + mailman3.service + mailmanweb.service + postfix.service + postfix(a)-.service + [X] deleting files under /opt/mailman/mm/var/data + postfix_domains + postfix_domains.db + postfix_lmtp + postfix_lmtp.db + [X] restart services + mailman3.service + mailmanweb.service + postfix.service + postfix(a)-.service LEARNINGS: + no new files made (expected). + despite mailman3.service reports: + 'Apr 30 14:37:40 mlist01-prod mailman[533171]: Generating MTA alias maps' + postfix warns about the deleted files (expected): Apr 30 14:41:02 mlist01-prod postfix/error[533928]: warning: hash:/opt/mailman/mm/var/data/postfix_domains is unavailable. open database /opt/mailman/mm/var/data/postfix_domains.db: No such file or directory Apr 30 14:42:02 mlist01-prod postfix/error[533928]: warning: fast_flush_domains: hash:/opt/mailman/mm/var/data/postfix_domains: table lookup problem Apr 30 14:42:02 mlist01-prod postfix/error[533928]: warning: C5B821C00E5: flush service failure

5 months, 3 weeks

[MM3-users] Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Andrew Bernard

Hi Mark, Thanks for your great help. But despite decades of UNIX experience, my area is not Django (yet). The nub of my question is that I thought you have to have a manage.py file for Django to be able to set up the various affairs, such as making the database migrations and so on. It is that that is eluding me. Apologies for this hopelessly newbie question. I was impressed with your method of installation in the page referenced, and I have foolwed that closely. But I am puzzled about the build script. If I run as user mailman, not root, it wanted to install under /usr. which of course results in permission denied. I had to modify the script to say this: python setup.py install --prefix /opt/mailman/mm/venv I am concerned that I have also misunderstood something here. A On Sun, 9 Jun 2019 at 00:57, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/8/19 4:04 AM, Andrew Bernard wrote: > > > > Where is the Django config area for the > > pip installed modules? It is this that I find obscure. > > The short answer is wherever you put it. If you look at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> > which Abhilash mentioned, you'll see what I do. > > >

6 years, 4 months

[MM3-users] Re: How to promote non-members to members?

by Quanah Gibson-Mount

--On Thursday, March 17, 2022 12:06 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > This says that there is no Address object with the email > xxxxxxxx(a)xxxxx.org > > What do you get in `mailman shell` for > ``` > >>> um = getUtility(IUserManager) > >>> um.get_address('xxxxxxxx(a)xxxxx.org') > >>> um.get_user('xxxxxxxx(a)xxxxx.org') > ``` > These should return an Address and a User respectively. If they don't, > did you perhaps run some process to delete the user? I've done nothing in regard to this user. Neither command returns anything. I see it return my user object if I test with my own email address. > If the user is gone, you should be able to replace > ``` > ... sub_mgr.confirm(token) > ``` > in the above with > ``` > ... wfm = getUtility(IWorkflowStateManager) > ... pendings.confirm(token, expunge=True) > ... wfm.discard(token) > ``` > to clear the pending subscription and workflow and then be able to mass > subscribe the user. I did this, and can confirm that they no longer show up in the list of pending subscriptions via the mailman shell interface for that list. However, if I go to mass subscribe them via the interface, I get: HTTP Error 409: b'Subscription request already pending' Regards, Quanah

3 years, 7 months

[MM3-users] Re: message awaits moderator approval

by Eggert Ehmke

Yes, the templates did have URL's of the old lists. I changed them to refer to the new lists. Am Mittwoch, 21. Dezember 2022, 21:33:26 CET schrieb Mark Sapiro: > On 12/21/22 08:53, Eggert Ehmke via Mailman-users wrote: > > Now it turned out that there were several relicts of the old list in the > > database, in particular in the template table. I removed them using direct > > SQL commands. > > > > Now my new mailing lists work as expected. > > > > Is this a bug in postorius? I think when I delete a mailing list, all > > relicts should be deleted from the database. > > Were there Postorius custom templates for that list?, I.e. did the > template table entries have Postorius URLs. If so, this is probably a > Postorius issue. I haven't actually looked, but when Postorius deletes a > list, it should delete any of it's templates from the > postorius_emailtemplate table and revert the template table entries. > > Beyond that, Postorius is just telling Mailman core to delete the list, > and when Mailman core does that it should probably also remove any > var/templates/lists/<list_id> directory and any entries from the > template table with context = the list_id. If it doesn't, this is a core > issue.

2 years, 10 months

[MM3-users] Re: mail loops back to myself

by Florian Sukup

On 6/12/25 19:48, Mark Sapiro wrote: > > That is not correct. Postfix should receive the initial connect and smtp > for the list and then transport_maps should tell it to relay the message > via lmtp to the configured lmtp_host and lmtp_port (127.0.0.1:8024 per > your previously posted mailman.cfg). You have also posted that Postfix > main.cf contains > > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > > What is the content of that file? In particular does it contain > > mylists(a)lists.yyy.com lmtp:[127.0.0.1]:8024 > Yes, that's exactly the case. > and is the timestamp of /var/lib/mailman3/data/postfix_lmtp.db >= that > of /var/lib/mailman3/data/postfix_lmtp, and have you restarted/reloaded > Postfix since updating main.cf? And, is Mailman core running and > listening on port 8024? > # ls -rtl total 296 -rw-rw---- 1 list list 270336 Jun 8 21:58 mailman.db -rw-rw---- 1 list list 1123 Jun 12 08:43 postfix_lmtp -rw-rw---- 1 list list 367 Jun 12 08:43 postfix_domains -rw-r----- 1 list list 12288 Jun 12 08:43 postfix_lmtp.db -rw-r----- 1 list list 12288 Jun 12 08:43 postfix_domains.db # lsof -i :8024 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python3 1146914 list 23u IPv4 78503106 0t0 TCP localhost:8024 (LISTEN) I always restart mailman3 after changing main.cf if there is any interest, postfix_domains contains this line: lists.yyy.com lists.yyy.com Florian.

4 months, 1 week

[MM3-users] Re: auto-away notices as bounces

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210830 04:30]: > On 8/24/21 11:17 AM, Andreas Barth wrote: > > > >Well, the mail adress got disabled, and the user got warning mails > >("Your subscription for list mailing list has been disabled"). As none > >of the list owners did that, I don't think there is any other > >explanation. Please note that individualsation was enabled, so all > >mails are sent out with per-subscriber mail envelope address, which > >then makes bounce detection quite straight-forward. > > > If by 'individualsation was enabled' you mean messages were VERPed, > there could be a bug here. Yes, that's what happens. > There are a couple of considerations. First the vacation responder > should not respond to list messages. See > <https://www.rfc-editor.org/rfc/rfc5230.html#section-4.6>. I fully agree with you, and already responded with the same remark to the user before sending my initial mail here. > That said, bounce processing should treat even a VERPed message as > unrecognized if it doesn't look like some kind of DSN. This may not > be the case in MM 3. Thanks, that's what I also think. Looking at the returned mail, they definitly don't look like DSNs / bounces to me. Anything I should be doing re this topic? Thanks, Andi

4 years, 1 month

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

by Allan Hansen

That worked, Mark. Thank you. Now I just have to figure out how to put it all in a script for the cron utility, so I can run it daily (or hourly, for that matter). But for now I have no more non-members. Yours, Allan As for non-members, the list settings for 'Message Acceptance' has a number of options to accept, hold, reject or discard messages for a list of addresses (entered using regexps, even) of non-members. Under 'Users' there is an option to add non-members. Given this, the notion that non-members are being automatically created in the database, has been a source of confusion to me, let alone my users/moderators. On 9/17/22, 11:18 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 9/17/22 11:01 AM, Allan Hansen wrote: > Sure: > >>>> lm = getUtility(IListManager) >>>> for l in lm: > ... print(l.posting_address) > ... >>>> > > Nothing here, either. So your `mailman shell` command is not pointing at your productiom mailman.cfg. Try `mailman -C /path/to/production/mailman.cfg shell` -- 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/

3 years, 1 month

Search results for query "sapiro"