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

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Andy Smith

Hi Mark, On Fri, Sep 30, 2022 at 01:16:10PM -0700, Mark Sapiro wrote: > What is your version of flufl.bounce? I'm using Debian stable, and this is what is packaged: $ dpkg -l | grep flufl ii python3-flufl.bounce 3.0.1-1 all email bounce detectors (Python 3) > I suspect this is https://gitlab.com/warsaw/flufl.bounce/-/issues/12 which > was fixed in flufl.bounce 4.0 and upgrading to 4.0 will fix this. So that probably answers that then. Hmm, I wonder about the best way to proceed. The next stable release of Debian will have something that calls itself 4.0-2 and looks like it is fixed there: https://salsa.debian.org/python-team/packages/flufl.bounce/-/blob/master/fl… so maybe I can ask for that package to be put in stable-backports. I think the other option might be to remove system package python3-flufl.bounce, add it back with "equivbs" so that its system dependencies think it is present and then install the latest one from pip. I'll report the bug in Debian anyway. Thanks! Cheers, Andy

3 years, 6 months

[MM3-users] Re: Disable archives per list

by Bernd Wurst

Hello. Thank you for your answers. Am 25.02.21 um 22:01 schrieb Mark Sapiro: > Normally a list admin can select which of the enabled archivers is > active for that list via Postorius. To prevent this, you would have to > modify Postorius. It would be easy enough to just remove settings from > the relevant templates. This will take effect for all lists at once, I suppose. :( > I'm not sure what you mean by "custom archiver settings", but other than > enable/disable and public/private, probably not. Hyperkitty has a rather cool frontend but stores all messages from all lists together in one database table. Additionally, neither Mailman nor Hyperkitty seems to know or tell anything about archive sizes of a list. This is horribly for accounting. So I thought if I can have a separate hyperkitty installation per user without having to duplicate the whole mailman. Alternatively, I'd like to enable archiving only for some customers that buy a suitable plan. I did not really get into mailman plugins. Is is possible for plugins to hook into such settings? I could not really find examples for plugins. regards, Bernd

5 years, 1 month

[MM3-users] Re: ARC

by Marvin Gülker

Am 13. August 2019 um 05:42 Uhr -0700 schrieb Mark Sapiro: > The question is not whether they support ARC, but whether they will > trust you. Well. That's nothing new, given that GMail and Microsoft liberally reject e-mail from small providers for no reason anyway (I have experienced it myself). If this situation doesn't change with ARC, I can live with this (by paying for an SMTP relay provider that proxies my e-mail). However, I thought the entire point in ARC was fixing automatic rejections caused by DMARC invalidation by mailing lists, which are vital for so many open-source projects (including Mailman iself). If ARC falls short of solving that problem, because the large providers do not automatically trust ARC, then supporting ARC on my mailing list server is kind of void. Why should almighty Microsoft trust my small personal mailing list server? ARC can only achieve its goal with black-listing untrusted relays rather than white-listing known good ones, because it is simply unfeasable to manually maintain a list of all open-source project mailing lists in the entire world. I could set a new one up tomorrow, how should you know? -- Blog: https://mg.guelker.eu

6 years, 7 months

[MM3-users] Re: Maximum number of recipients Setting

by Brian Carpenter

On 4/3/21 5:04 PM, Mark Sapiro wrote: > On 4/3/21 1:45 PM, Brian Carpenter wrote: >> I have run several tests. It looks like on the 'Maximum number of >> recipients' setting, a 2 means 1. If I set it to 2, I can have the >> listname(a)listdomain.com only. If I have a CC, it comes to me for >> moderation. If I set it to a 3, I can send out to >> listname(a)listdomain.com plus a CC. If I set it to 3 and add 2 CC's plus >> the listname(a)listdomain.com address, it comes to me for moderation. > > I understand it's confusing, but it's been that way since the beginning > of Mailman 2.1. The docs at > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…> > say "For backward compatibility, the message must have fewer than the > maximum number of explicit recipients." > > I agree the description in Postorius could be clarified see > <https://gitlab.com/mailman/postorius/-/issues/515>. > That explains it. Thanks for solving this mystery. -- Brian Carpenter Harmonylists.com Emwd.com

5 years

[MM3-users] Re: hyperkitty threads by month question

by Bryan Fields

On 7/26/24 11:19 PM, Mark Sapiro wrote: > On 7/26/24 18:53, Bryan Fields wrote: >> On 7/26/24 4:01 PM, Mark Sapiro wrote: >> >>> If this returns just the one message_id, I would then >>> >>> DELETE FROM hyperkitty_thread WHERE id = 35670; >>> DELETE FROM hyperkitty_email WHERE id = 150555; >> >> It's giving an error due to a fk constraint on another table. I'm not >> familiar with the db structure enough to be certain how to clean/fix it. > > Yes, you need to do these first. > > DELETE FROM hyperkitty_favorite WHERE thread_id = 35670; > DELETE FROM hyperkitty_tagging WHERE thread_id = 35670; > DELETE FROM hyperkitty_lastview WHERE thread_id = 35670; > DELETE FROM hyperkitty_vote WHERE email_id = 150555; > > Not all those will exist, but then you should be able to > > DELETE FROM hyperkitty_thread WHERE id = 35670; > DELETE FROM hyperkitty_email WHERE id = 150555; Sill no go on it. mailmanweb=> DELETE FROM hyperkitty_favorite WHERE thread_id = 35670; DELETE 0 mailmanweb=> DELETE FROM hyperkitty_tagging WHERE thread_id = 35670; DELETE 0 mailmanweb=> DELETE FROM hyperkitty_lastview WHERE thread_id = 35670; DELETE 0 mailmanweb=> DELETE FROM hyperkitty_vote WHERE email_id = 150555; DELETE 0 mailmanweb=> DELETE FROM hyperkitty_thread WHERE id = 35670; ERROR: update or delete on table "hyperkitty_thread" violates foreign key constraint "hyperkitty_email_thread_id_038c9aee_fk_hyperkitty_thread_id" on table "hyperkitty_email" DETAIL: Key (id)=(35670) is still referenced from table "hyperkitty_email". mailmanweb=> DELETE FROM hyperkitty_email WHERE id = 150555; ERROR: update or delete on table "hyperkitty_email" violates foreign key constraint "hyperkitty_thread_starting_email_id_fa7c55f5_fk_hyperkitt" on table "hyperkitty_thread" DETAIL: Key (id)=(150555) is still referenced from table "hyperkitty_thread". >> I'm actually thinking I need to fix the archive mbox, then delete them and >> re-import them once they are cleaned. > > > Actually, that would be safest. Fix the mbox, delete the entire archive > and re-run the import. I'll attempt to clean this up tomorrow an clean it up/re-import. Is there a quick/easy way to drop the entire archive from the db or must I delete the entire list? >>> Also, FYI, assuming those messages with very old Date: headers had >>> reasonable unix from dates, the hyperkitty/contrib/cleanarch3 script >>> would fix them, except you have to get the script from >>> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… >>> or https://www.msapiro.net/scripts/cleanarch3 because the script in the >>> latest release has a bug. >> >> I tried the dry run option on your script and it gave a bunch of output >> for bad >> dates. This was absent on the one shipping with the source. What's >> interesting >> is that pipermail seems to have no issue with this, detecting the date >> correctly. > > If I recall correctly, pipermail checks date skew and 'fixes' the dates > in the archive, but they remain off in the mbox. I'll have to check that, but I've got at least some good leads now and tools to find suspected issues. It does seem like a bad design that importing a mailman2 mbox can cause the server to error 500. >> Is the archive tool in pipermail's import more robust in this manner? >> I'd argue >> it's common to have missing In-Reply-To: headers where the subject and time >> would need to be used to infer the likely thread. I'll agree this is a >> major >> violation of the relevant RFC's to be missing this, but many MUA's (M$) are >> famous for doing just this. > > > Yes, it's arguably a defect in HyperKitty to not implement Jamie > Zawinski's threading algorithm <https://www.jwz.org/doc/threading.html>, > but it doesn't. Well that kinda blows :-( I'm not going to take down the old archives, but I'd like at least one to be searchable, which is why we wanted to use mailman3/hyperkitty. Thank you, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 year, 8 months

[MM3-users] Re: Twitter OAuth2

by Stephen J. Turnbull

Mark Sapiro writes: > The last I looked into using Twitter as an OAuth2 provider, which was > some time ago, it would not work because Twitter would not provide the > user's email address via OAuth2. Possibly this could work if the user's > name was her Twitter handle. Yeah, but then I (@yasegumi@twitter) could log in as yasegumi(a)example.com and every other yasegumi in the world. There probably aren't any of those that aren't me, but of the 30 kids in my 6th grade class 5 were named something with the diminuative "Steve", and we also had one Stephanie. So I could log in as steve(a)turnbull.sk.tsukuba.ac.jp (that's me) or steve(a)xemacs.org (that's not me, I'm stephen(a)xemacs.org) or steve(a)any.old.com. Not good. Also, I wouldn't trust Musk's Twitter with no security staff left to give out only confirmed email addresses. If they give out any address you gave them, then anybody can spoof anybody. So I would advise not using Twitter as an idP under any conditions, unless it's to prove you own a Twitter handle. Steve

3 years, 3 months

[MM3-users] Re: mailman admin (django) interface does not work anymore after deleting website example.com

by Torge Riedel

Am 10.03.19 um 16:44 schrieb Mark Sapiro: > On 3/10/19 8:18 AM, Torge Riedel wrote: >> I deleted the existing "example.com" and added a new one >> "lists.mydomain.de". >> >> Now the admin (django) interface always gives "An error occurred while >> processing your request". After one of the first navigation clicks I saw >> a message that "site with id 1 is missing". > > In your Django settings your have > > SITE_ID = 1 > > which pointed to the example.com domain you deleted. > > You need to override this in settings_local.py. Probably > > SITE_ID = 2 > > but if that doesn't work, try '0' > Ah, thank you Mark. That makes a kind of sense. I changed the database directly to fix it. And renamed example.com to lists.mydomain.de. Now the error is gone. I'm wondering why the initial database set up of postorius (?) adds "example.com". Is there a way to directly add my domain instead? Somewhere in settings_local.py?

7 years

[MM3-users] Re: duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Stanisław Findeisen

On Thu, Mar 24, 2022 at 09:27:06PM -0700, Mark Sapiro wrote: > The issue is client.create_domain doesn't support setting a Web Host. Web Hosts are the sites in the django_site table and SITE_ID is the id of > the table entry. See `sites` in the Django admin UI. > > So when you create a domain with client.create_domain it gets arbitrarily assigned to a `site` Ok thanks, this is good to know. How about mailing list creation using Mailman Client, like this? domains = client.domains domains = list(filter(lambda x: (domain_name == x.mail_host), domains)) # .. check if domains is a singleton list .. domain1 = domains[0] domain1.create_list(list_name, style_name=style_name) Do you know of any quirks/deficiencies related to this kind of code? This code is taken from mailman3-utils: https://github.com/sfindeisen/mailman3-utils , a set of scripts I stitched together to facilitate common Mailman3 operations on the command-line. Most importantly this can apply the (currently hardcoded) set of list settings uniformly across the different lists (and different domains). (I realize part of this overlaps with the mailman command, especially in the local setting.) Thanks Stanisław

4 years

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Fri, Dec 23, 2022 at 2:02 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/22/22 13:57, Odhiambo Washington wrote: > > > > WSGIDaemonProcess mailman-web display-name=mailman-web > > maximum-requests=1000 umask=0002 user=mailman group=mailman > > > python-path=/opt/mailman/mm/venv/lib/python3.9/site-packages:/opt/mailman/mm/venv/lib/python3.9 > > python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > > WSGIRestrictSignal Off > > > Add /opt/mailman/mm to python_path. I.e. > > > > python-path=/opt/mailman/mm:/opt/mailman/mm/venv/lib/python3.9/site-packages:/opt/mailman/mm/venv/lib/python3.9 > Now working as expected. With this, my questions about running MM3 with either gunicorn or mod_wsgi are bound to get reduced to an acceptable level. There is just one more thing - I have this in settings.py: LOGGING['handlers']['file']['filename'] = '/opt/mailman/mm/var/logs/mailmanweb.log' However, the referenced file is ever empty. At what point is it supposed to record anything? Thank you very much and may you enjoy your festive season - the one we call Christmas. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 3 months

[MM3-users] User stories about topics, dynamic sublists, or sibling lists

by Stephen J. Turnbull

Mark Sapiro writes: > On 3/27/24 08:05, Markus Grandpre wrote: > > > > after I migrated a list from Mailman21 to Mailman3 I missed the > > Mailman21 setting "regular_include_lists" (or something similar) > > in Mailman3. How are sibling lists treated in Mailman3? > > The sibling list features do not exist in Mailman 3. Topics, dynamic lists, now sibling lists. All of these address a set of related problems, characterized by a large number of users who are divided into subgroups by interest, where the interests are pretty concrete and don't overlap much, each user may have several of those interests, and each subgroup considers the threads on other topics to be an interruption of their preferred workflow. I would be interested in hearing user stories about their sites' use cases for these features (and any similar features whether or not they were implemented in Mailman 2). Also horror stories, if any. (I can imagine that mixing rosters could leak personal information or result in annoying crosstalk.) Please keep it in this thread, or write me personally if you prefer. Steve

2 years

Search results for query "sapiro"