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

[MM3-users] Re: Confirmation emails to Users has wrong domain name (example.com!)

by Odhiambo Washington

On Wed, Sep 29, 2021 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/29/21 9:50 AM, Odhiambo Washington wrote: > > 1. Confirmation emails to Users has wrong domain name (example.com!) > > <https://docs.mailman3.org/en/latest/faq.html#id1> > > < > https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h… > > > > > > This happens when your reverse (SSL) proxy isn’t setting up the correct > > headers when proxying requests. Fix this by setting the right > > proxy_set_header directives: > ... > > How is this supposed to be mitigated in Apache when using WSGI? > > > > My config: > > > > WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman > > user=mailman group=mailman > > WSGIPythonHome "/usr/local" > > WSGIProcessGroup hyperkitty > > > You are using mod_wsgi and not proxying at all, so this is not relevant > in your case. > > Are you actually seeing this issue? If so, it might be related to > > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > My issue is related to this, but the documentation referred to is not for the faint-hearted! I can't make head or tails of it. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

4 years, 11 months

[MM3-users] Re: search this list searches more then just this list

by Marco van Tol

Op 24 jan 2024, om 12:24 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: > Op 23 jan 2024, om 19:09 heeft Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> het volgende geschreven: >> >> On 1/23/24 05:49, Marco van Tol wrote: >>> Small unfortunate twist, this leads to: >>> --- >>> [ERROR/MainProcess] Failed indexing 204001 - 205000 (retry 5/5): Term too long (> 245): ... >>> --- >>> I have seen comments on that from back in 2020, but what’s the latest advise on how to deal with this? >> >> This issue is discussed at <https://github.com/notanumber/xapian-haystack/pull/181>. >> There are two patches for this issue. They are somewhat different approaches, but either one is OK. One patch is the one in the above PR <https://github.com/notanumber/xapian-haystack/pull/181/files>. The other is at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…>. >> >> I use the one from the PR, but it requires a substitution `s/force_text/str/`. > > Hi, thanks! Just to double check, do you mean `str` or `force_str` in the substitution? > > I found a comment on this topic regarding django-4 where they advice to use force_str. > https://stackoverflow.com/questions/70382084/import-error-force-text-from-d… Hm, never mind, sorry. I now see the current file already has str() rather than force_text() in it. Marco

2 years, 7 months

[MM3-users] Re: Can disabled users enable themself?

by Flo

On 7/2/26 11:06 PM, Mark Sapiro wrote: > > What are your list settings for bounce processing? With a list that > apparently only gets one post in a few months, the default settings > > Bounce score threshold = 5 > Bounce info stale after = 7d > > will not disable delivery for any one as disabling would require 5 > bounces with no more than 7 days between any two bounces. > > For your above scenario, you might want something like > > Bounce score threshold = 4 > Bounce info stale after = 60d > To make it more clear: This list is promoting events, 2-3 in spring and 2 in fall and two towards the end of the year. For each event one (or maybe two) emails are sent. I thought I will use the following settings: Bounce score threshold 2 Bounce info stale after 60d Bounce disabled warnings interval 60d Bounce disable warnings 5 If there are bounces at two events the account will be disabled. Afterwards mailman should check every 60d if this continues. In this case it is done by sending out emails. Then I'd wish that the user is enabled if email doesn't bounce anymore. But since this is not the way it works, the user needs to take action and email the owner of the list to be enabled again. If this is not done (IE: mails are still bouncing), the user is to be removed. That's my plan. Flo

2 months, 1 week

[MM3-users] Re: Mailman shell tutorial

by Andrew Bernard

Thanks Mark, The omission of the code to make the examples work seems to need correction. Perhaps I can submit an update to the project. Had me scratching my head for a long time. Obviously I knew there were imports etc missing, but what to put? I have this going, and it is great. But I recall seeing something called mmclient or similar which has simple commands like show user, show lists, and so on. Is that still available? Now knowing how mailman shell works, anybody could write their own commands, but I don't want to reinvent wheels. Andrew > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, 11 June 2019 1:26 PM > To: mailman-users(a)mailman3.org > > Perhaps you saw the `command('mailman shell --details')` line in the docs at > <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/s > hell.html#getting-detailed-help> > in any case, that requires two things to precede it. The first is part of the > doctest infrastructure and is not evident in the docs. that step is > > from mailman.testing.documentation import cli > > The second step is in the docs and is > > command = cli('mailman.commands.cli_withlist.shell') > > If you do those two steps within `mailman shell`, then the step > > command('mailman shell --details') > > will work, but as I said, this is just the same as doing `mailman shell --details` > at a command prompt.

7 years, 3 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/24/21 9:40 AM, David Newman wrote: > > > > IMO post-installation docs for list admins would be a big help in > > Mailman3 adoption. I'm willing to help with this. > > > Thank you for being willing to contribute. +1 > I think the place for list admin docs would be in the > https://gitlab.com/mailman/mailman-suite-doc project which is the > source for https://docs.mailman3.org/en/latest/. +1 > Here are the steps to migrate a 2.1 list named `alist(a)example.com` and > its archives. This is documented at https://docs.list.org/en/latest/ (prominent link in sidebar). This appears to be completely different from https://docs.mailman3.org/ (and https://mailman.readthedocs.io/ which I guess is just a redirect). But it looks like the sources are in the some gitlab repo?! > > And I don't know where to add list members. I guess it would be a good idea to provide an image of the menu tree for Postorius. > Did you specify the list's fqdn as in > https://www.example.com/archives/list/list@example.com/ That's not an FQDN, though. "example.com" might be one, but that whole thing is the URL to the archive. Pedantry aside, I think we should probably have a Mailman-specific glossary for many terms, including the tests we use for validation. In this case, FQDN appears to be "sequence of characters not containing '@' or '/'." Steve

4 years, 9 months

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

by kisner＠live.com

Mark Sapiro wrote: > On 7/8/22 8:28 AM, kisner(a)live.com wrote: > > I tried to follow that guide ( https://docs.mailman3.org/en/latest/install/virtualenv.html ), but I couldn't get it to work. I'd have to try it again to see where it broke. One thing that I got past was I had to change: > > (venv)$ pip install wheel mailman psycopg2-binary<2.9 > > to > > (venv)$ pip install wheel mailman psycopg2-binary==2.8.6 > > and that got me past that part, > > I don't understand why that would make a difference since the latest > psycopg2-binary<2.9 is 2.8.6 > > but hyperkitty/mailman-web pip install has components that failed to install. I'm not sure why, someone smarter than me could probably have figured it out, but as written it wasn't working for me. > > If you do try again, post the specific issues/error messages and we will > try to help. Just out of curiosity and to try to improve the doc I can do this a little later. But I can tell you for sure the pip install psycopg2-binary<2.9 command failed for me on Ubuntu 22.04 and Debian 11.3. I'm not saying it's *not* me, and I don't know when the last time that doc was updated but I couldn't get it to work on a few different distros.

4 years, 2 months

[MM3-users] Re: Trouble importing a Mailman 3 Postgres database into a new Mailman 3 instance (Docker)

by skenny＠scss.tcd.ie

Mark Sapiro wrote: > > My point was after you remove the newly minted mailmandb database and > then create a new blank one, and import into that, you should then run > manage.py migrate to apply any new migrations to the imported database. Ah, right ... ok, I've done that now, and all's good. Actually, I've noticed something related. It looks like the mailman-web container runs manage.py as part of its startup procedure in any event. After the import completes, I start up the mailman-web container and, its logs say this: mailman-web | Operations to perform: mailman-web | Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | Applying auth.0012_alter_user_first_name_max_length... OK mailman-web | Applying django_q.0014_schedule_cluster... OK mailman-web | Applying hyperkitty.0022_mailinglist_archive_rendering_mode... OK mailman-web | Applying postorius.0014_auto_20210329_2248... OK mailman-web | Applying postorius.0015_auto_20210619_0509... OK mailman-web | Applying postorius.0016_auto_20210810_2157... OK If the container is restarted again, it shows that there's nothing to do this time: mailman-web | Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | No migrations to apply. These latter diagnostics are also what I see if, at this point, I enter the mailman-web container and run "manage.py migrate" explicitly. I really appreciate the help, thanks so much.

4 years, 1 month

[MM3-users] Re: Add an extra option for "Delivery status" for users?

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/19/25 12:50 PM, Thomas Ward via Mailman-users wrote: > > We have a unique case where we have a user we want to disable for mail > > receiving, etc. for the reason "Disabled by IT Security Team" but I > > don't even know if it's possible to add a delivery status that is that > > custom. > At a minimum, you would need to add that choice to the > DeliveryStatus(Enum) in mailman/interfaces/member.py and the choice and > its description to the DELIVERY_STATUS_CHOICES tuples in > postorius/forms/fields.py. I don't know offhand if that would be > sufficient, or if more would be required. In postorius/views/user.py, you also need to add it to `UserPreferencesView,delivery_status_disabled_fields`. Otherwise users will be able to reenable from a security disable. In Mailman core, it's not absolutely necessary, but I think you should handle it the same as `by_moderator` in mailman/commands/cli_members.py, mailman/commands/cli_addmembers.py, and mailman/commands/cli_syncmembers.py. The mention of `by_moderator` in mailman/utilities/importer.py is irrelevant since the new `by_security` (or whatever you call it) doesn't exist in Mailman 2. In mailmanclient, you *may* want to update docstrings in mailmanclient/asynclient.py and mailmanclient/restobjects/mailinglist.py. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

9 months, 3 weeks

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by tokyoprogressive＠mailbox.org

Thank you Mark. I will need to find time tomorrow to create two totally new email accounts that I can use in tests so I do not inadvertently sign up again with the same address. Also will double check my settings. Best regards Paul Sent from my iPhone > On Sep 17, 2019, at 14:39, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/16/19 9:22 PM, Paul Arenson wrote: >> In my test of the two forms of signup, I am getting these unexpected results. Is it my settings or is something weird within the program itself? >> >> 1) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… >> >> 2) Choose "You can also subscribe without creating an account. If you wish to do so, please use the form below" >> >> 3) Then I have to approve it. They get "Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org > > > You have to approve it or the user has to confirm her email address? > Maybe you have to approve it because the lists Subscription Policy is > Moderate. > >> 4) But I have to approve it.I assume this is because they do not yet have a real account. And they should be listed as a NON MEMBER? > > > No. They will be a member, they just will not have a Django account that > they can log in to. > > >> 5) But even when they sign up here: https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… they get an email from my provider (NOT MY LIST????) as follows: >> >> "Hello from mailman3.emwd.com! You're receiving this e-mail because user iCloud has given yours as an e-mail address to connect their account. >> To confirm this is correct, go to https://list.tokyoprogressive.org/accounts/confirm-email/MTE3:1iA44k:E7w7xh… Thank you from mailman3.emwd.com! mailman3.emwd.com" > > > Because when you create a Django account, you have to confirm your email > address. > > >> 6) And this is where it gets weird. If they send from their email program and get the welcome (Welcome to the "Discuss" mailing list! >> To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You can unsubscribe or make adjustments to your options via email by >> sending a message to....... I then get a notice: >> >> "Your mail to 'discuss(a)list.tokyoprogressive.org' with the subject test notice Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member" > > > What is Message Acceptance -> Default action to take when a member posts > to the list ? > > You get the notice or the user gets the notice? > > >> 7) While if they send FROM THE interface it goes through. >> >> 8) What I am confused about. >> >> Signing up for an account should make them a member, right? Subscribing should make them a non member, no? > > Signing up for an account is just signing up for a Django account. You > can sign up for an account and log in and then subscribe to the list. > > Subscribing makes one a member whether or not you subscribe from a > logged in account or subscribe without creating an account. > > >> But here it seems that both make them a non member. > > If an address which is not a member posts to the list, that address > becomes a non-member. This is the only way other than being explicitly > added by an admin that an address becomes a non-member. > > >> And worse, someone with an account sending from the Interface has their message get through while the same person sending from an email program has me get a notice that a non member is trying to post. > > > If by sending from the interface, you mean posting via hyperkitty, the > user must have an account and be logged in to do that. > > Your "same person" may have multiple entities within Mailman, possibly > subtly different email addresses, one of which is a member and one of > which isn't. > > > -- > 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/

6 years, 11 months

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-05-01 13:35, Mark Sapiro wrote: > On 4/30/24 17:54, Mark wrote: >> >> In the new installation, are the template.uri (in the mailman DB) >> records written as http://localhost:8000/... ? > No. In both the installation that worked and the one that didn't, they > were https://msapiro.net/..., but I don't think it would have > mattered. > > When I reinstalled, I kept the same database, I only rebuilt the venv. > > As I have said at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, > this is all strange. My logs from the failure show the web server > getting the request and serving the template with a 200 status and > then after 5 seconds which is the specified timeout a > requests.exceptions.ReadTimeout error is logged in mailman.log. > > The exact same code is executed whether by a rest runner gunicorn > worker or via some other Mailman core runner, but only the rest runner > fails. Further, a reinstalled venv on the failing server has no error, > and another server which has a venv identical to the failing one > except for Python micro version also has no error. > > I can't begin to understand what the underlying cause might be. Thank you Mark. I'll give rebuilding venv a crack. In the meantime I've cobbled together a script -- https://postmark.io/scripts/ -- and it's got things going for the moment. .

2 years, 4 months

Search results for query "sapiro"