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

[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, 1 month

[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, 6 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?

6 years, 11 months

[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

3 years, 10 months

[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, 1 month

[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

1 year, 10 months

[MM3-users] Re: SpamAssassin header confusion

by skenny＠scss.tcd.ie

Mark Sapiro wrote: > On 4/8/21 3:18 PM, skenny(a)scss.tcd.ie wrote: > > On the face of it, it looks like Mailman has removed the X-Spam-* headers. > > This should not be the case. Mailman removes some headers from posts to > anonymous lists, but not X-Spam- headers even there. Are you sure you > are looking at the raw message headers and not some MUAs rendition of them? > I can think of no reason why Mailman would remove those headers. I think I may have been misreading what's going on. The spam email is first received by Postfix and rinsed by SpamAssassin. In the copy that gets retained as a gzipped file under /var/lib/amavis/virusmails, there's a header present near the top that says "Delivered-To: spam-quarantine" - as well as all the X-Spam-* headers. So Postfix must consider the message "delivered" in that sense. My guess is that it then hands off the original email - minus all the X-Spam-* and other headers, but with the amended Subject: line (***SPAM*****) - to Mailman. Thus Mailman never sees those spam-related headers in the first place (?) Stephen

4 years, 10 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Stephan Krinetzki

Stephen J. Turnbull wrote: > Mark Sapiro writes: > > mailmancore/API ->database > > that seems to have an issue and only with this one > > DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > > query. However, like you, I have no idea as to what you could do further > > to debug this. > > I have an idea, but it seems so obvious that presumably it's already > been tried: log in to the database as mailman with pgsql and try > deleting something. If that works immediately, try with mailmanclient > and the mailman command line utility. > Steve Well, we didn't try this. Since we don't know what the query for deleting a held message in the database needs to look like, we left that out for now. If someone can help me there, it would be great. Over the mailman shell it hangs as long as on the web ui (using mailman shell -l list@host and iterating over the held messages). So it is the communication Mailman API <-> Database.

4 years

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

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/27/22 00:19, Jan Eden via Mailman-users wrote: > > > > I see. But the mailman.cfg is placed in /etc/mailman3, and this file > > also belongs to the core, doesn't it? In any case, I changed the > > configuration parameter for [archiver.hyperkitty] as you suggested and > > all settings are in one place now. > > In that case, it's probably just an oversight. Yes, I think that's what's going on. There's been quite a bit of simplification and unification of the Django configuration over time, which is ongoing and not 100% reflected in all documentation. Because of the way most Linux distros work (and I think it's probably true for *BSD and other POSIX systems), it makes sense to put users' site configurations in /etc. I don't see a particular reason why with the current relatively small set of config files we'd want to put HyperKitty or Postorius files elsewhere than /etc/mailman3 (although it might make sense to have more separation given the existence of EMWD's Affinity etc). Steve

3 years, 2 months

[MM3-users] Re: Moving from forum to Mailman 3

by Stephen J. Turnbull

Mark Sapiro writes: > On 10/9/20 4:39 PM, jonathan.mailing.lists(a)gmail.com wrote: > > > > Thanks for this. I’m sure I could turn that basic information > > (from, date, subject) into an mbox file somehow. What else does > > Mailman need, eg to work out which messages are in reply to > > which? > > To properly thread messages, each message should have a unique > Message-ID: header and all replies should have an In-Reply-To: header > with the Massage-ID: of the message to which it's a reply. [example thread omitted] > The angle brackets around the strings are required and every Message-ID: > in the entire archive for a list must be unique. This is harder to do well (or even "well enough") than you might think. I recommend using some software targeting RFC 4122: https://tools.ietf.org/html/rfc4122. RFC 4122 is implemented in the Python standard library (the uuid module), so if you have Mailman, you have it. The command line utility uuidgen is also good, and you probably have that too if you prefer CLI scripting to Python. Steve

5 years, 4 months

Search results for query "sapiro"