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

[MM3-users] Re: Auth question

by David Krantz

On Thu, Mar 30, 2017 at 1:06 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > 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) > I tried to upgrade today. The result is a broken install which fails when trying to upgrade the database. $> ./bin/mailman-post-update [...] File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", line 236, in _commit return self.connection.commit() File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", line 236, in _commit return self.connection.commit() django.db.utils.IntegrityError: update or delete on table "auth_user" violates foreign key constraint "social_auth_usersocial_user_id_193b2d80880502b2_fk_auth_user_id" on table "social_auth_usersocialauth" DETAIL: Key (id)=(3) is still referenced from table "social_auth_usersocialauth". I have tried to drop and recreate the databases but I get the above result anyway. The description in https://wiki.list.org/DOC/Mailman%203%20installation%20experience is very hazy. The process of symlinking in libraries is fiddly to say the least. I get mailman to start but not any web interface. I have not tested mailman so if it works rather than just start I do not know. There is a description for a clean install for development at http://docs.mailman3.org/en/latest/devsetup.html, but I suspect that it isn't usable for anything other than development. I have read it parallell to try to interpret the installation experience description which in turn describes more of what I am trying to do. No luck though. regards // David

9 years, 7 months

[MM3-users] Re: mailman-cli tools

by Dmitry Makovey

On 09/27/2017 10:20 AM, Abhilash Raj wrote: > On Wed, Sep 27, 2017, at 08:44 AM, Mark Sapiro wrote: >> On 09/27/2017 08:26 AM, Dmitry Makovey wrote: >>> On 09/27/2017 08:25 AM, Dmitry Makovey wrote: >>>> I've come across mailman-cli docs: >>>> >>>> http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… >>>> > > This is basically one of our GSoC projects which hasn't yet been merged > with MailmanClient. It uses the REST API to to provide a command line > client for Mailman, while there hasn't been any in-compatible changes in > API since this project was finished, I am not sure about the current > status of it. > >>>> yet I cannot figure out what's the official source for the installation. > > Official source for MailmanClient is at gitlab.com/mailman/mailmanclient > and it doesn't have a CLI, the Github project you linked to says right > on the top that it is not official project (Thanks for that Rajeev!). I did see that, thus I was asking the question here. > Also, I would say not to use this client to remotely access Mailman, the > REST API is not meant to be exposed over internet (unless you have a VPN > or other sort of setup to securely access the box remotely). > in my case - I need to use REST API since we're deploying with docker and pieces that need to integrate with mailman commands now live in a different container (and very likely on a different machine). I do need to be able to execute commands remotely - I can handle securing of that connection, but it is not an option for me to run "fat" docker containers thus the only interconnect is via sockets (either UNIX or TCP). -- Sr System and DevOps Engineer SoM IRT

9 years, 1 month

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-30 16:25, Mark Sapiro wrote: > Jan Eden wrote: > > I tried setting permissions on /opt/mailman/fulltext_index to 777 > > temporarily, but the issue remained (as expected). It occurs in the > > Whoosh backend of Haystack (whoosh_backend.py, line 132-133): > > > if self.use_file_storage and not os.path.exists(self.path): > > > > > > os.makedirs(self.path) > > > > > > where self.path is referenced, which is defined in line 110 (as part of > > the __init__ function): > > > def __init__(self, connection_alias, **connection_options): > > > super().__init__(connection_alias, **connection_options) > > > self.setup_complete = False > > > self.use_file_storage = True > > > self.post_limit = getattr(connection_options, "POST_LIMIT", 128 * 1024 * 1024) > > > self.path = connection_options.get("PATH") > > > > > > Unfortunately, I cannot see where the PATH key for connection_options is > > defined. > > > It is defined in the HAYSTACK_CONNECTIONS dictionary in your Django settings. The dictionary contains the following: > HAYSTACK_CONNECTIONS = { > 'default': { > 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > 'PATH': "fulltext_index", > }, > } Changing the PATH value to a full path (/opt/mailman/fulltext_index) and restarting mailman-web generates a different error: > ERROR 2022-11-30 16:38:37,953 1028315 django.request Internal Server Error: /archives/list/testing@lists.eden.one/thread/T6MCILAVQYV5QIOGHJB3JNJ26Z7E2Z35/reattach-suggest > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 55, in inner > response = get_response(request) > File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 197, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/view_helpers.py", line 137, in inner > return func(request, *args, **kwargs) > File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/views/thread.py", line 454, in reattach_suggest > sugg_thread = msg.object.thread > AttributeError: 'NoneType' object has no attribute 'thread' - Jan

3 years, 11 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 7., H, 0:44): > On 4/6/25 14:40, via Mailman-users wrote: > >> Is your login a member of the list? > > > > It's supposed to be – when I click „Manage subscription” in the very > same thread, it reveals that I'm subscribed. This is why I can't subscribe > again. Yet I still can't post from HyperKitty, however I can by e-mail. > > > > However, when I checked the member list, I also found my address as a > „nonmember” (besides being listed as „member” too). I removed myself as > „nonmember”, but I still can't post to the list from HyperKitty. > > > What response do you get when you click `reply` on a message? and what > when you click `Start a new thread`. Do you get an error immediately or > do you get a composition dialog and only get an error when you click > `Send`. What do the errors look like? > I get a composition dialog and can type my message, but when I click send, I get the error message: „This list is moderated, please subscribe to it before posting.”. Upon reply, a red rectangle appears to enclose this message. Upon trying to create a new thread, a white page loads which only contains this error message. What do you see in Django's logs when you do this? > I don't know where to look – I don't see anything outstanding, only a few HTTP requests appear in mailman.log on mailman side and uwsgi.log on web side. None of these indicate any error. What HyperKitty version is this and is it installed from PyPI or is it a > downstream package? Version 1.3.12. It is installed through pip with the virtualenv method.

1 year, 6 months

[MM3-users] Re: Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Franklin Weng

Hi Mark, Great thanks to you and everyone in this discussion. Mark Sapiro <mark(a)msapiro.net> 於 2019年10月30日週三 23:13 寫道： > 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. > I didn't change the key. When I follow the thread and print the keys getting from web and in the settings I found that one with single quote and the other not. In the mailman-web.py the value of MAILMAN_ARCHIVER_KEY should be single quoted, **but** the api_key in [general] SHOULD NOT single quoted. Therefore I set my hyperkitty base URL to https://lists.slat.org/mailman's/hyperkitty/ and removed the quote in mailman-hyperkitty.cfg it finally works. Maybe adding a comment to explain it a bit more would help later people not to step on the mine again. Thanks for your help! Regards, Franklin

7 years

[MM3-users] Re: Using MySQL via unix socket

by Torge Riedel

Am 02.02.19 um 19:06 schrieb Mark Sapiro: > On 2/2/19 5:31 AM, Torge Riedel wrote: >> A call to >> >> mysql -umailman -p >> >> successfully uses the socket on the machine and logs in. > > Yet you haven't specified -S or --socket > > >> I tried >> >> mysql+pymysql://mailman:mailmanpass@127.0.0.1/mailman3?charset=utf8&use_unicode=1&unix_socket=/var/run/mysqld/mysqld.sock >> >> >> as the connection string but it says that mysql server is not available. >> Which is the same if remove the "unix_socket" parameter. I have found >> this parameter when searching the net, but I'm not sure if it is supported. > > I think it should be, but the actual connection is via the the > sqlalchemy create_engine() function. It appears this should be passed to > the pymysql Connection() function per > <https://docs.sqlalchemy.org/en/rel_1_2/core/engines.html#custom-dbapi-args> > > What happens if in a Python 3 session, you do > > from pymysql import connect > conn = connect('127.0.0.1', > user='mailman', > password='mailmanpass', > database='mailman3', > charset='utf8', > use_unicode=1, > unix_socket='/var/run/mysqld/mysqld.sock') > > As I understand it, that's what sqlalchemy should be doing with your > database url. In my testing, the above works with or without the > unix_socket= argument, so I suspect something else is wrong in your case. > Hi, thanks a lot for your answer. Yes, sounds valid that something else is (or was) wrong in my environment. I'm new to docker containers and might have overseen something. I now managed it a different way: I used rinetd on the host to redirect connections from docker host ip of a bridged network to 127.0.0.1 to make MySQL accessible in the docker container. This works and avoids mapping the mysqld.sock file into the container. Thanks again Torge

7 years, 8 months

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sun, 2021-12-26 at 16:47 -0800, Mark Sapiro wrote: > On 12/26/21 3:06 PM, William Oliver wrote: > > > > When running mailman3, do I need to set up a completely different > > virtual domain for it to run in? > > No. > > > > My "real" domain name is > > libertyfp.org, and I'm trying to make mailman work on that domain, > > e.g. > > "testlist(a)libertyfp.org." I'm starting to get the idea that I need > > to > > stick a completely different domain in there for the mailinglist. > > No. > > DNS or anywhere outside your server. > > Have you actually set an alias domain in Postorius for the > libertyfp.org > domain. It doesn't matter what name it is as long as it isn't > a real domain. A good choice is x.libertyfp.org. Have you set that > or > things like > > testlist(a)libertyfp.org testlist(a)x.libertyfp.org > testlist-bounces(a)libertyfp.org testlist-bounces(a)x.libertyfp.org > testlist-confirm(a)libertyfp.org testlist-confirm(a)x.libertyfp.org > ... [snip] Ah. I misunderstood you. I thought you meant that I had to tweak *postfix* to get this done. It's not that you weren't clear, it's that when I read the mailman3 instructions, I got the impression that *mailman* would set the alias domain automatically, so I was dead set on munging postfix. This makes more sense, and I can back out of some of the changes I made in postfix, which for the last couple of rounds was mostly flailing about randomly -- I've heard that's often not a good admin strategy. So.. if I need to do it myself, can you point me to what file I need to create/modify in the /opt/mailman/mm tree to set up the alias? Thanks! billo

4 years, 10 months

[MM3-users] Re: Subscription Request asking for Confirmation instead of Moderation

by Henry Hartley

> -----Original Message----- > From: Stephen J. Turnbull <steve(a)turnbull.jp> > Sent: Friday, August 29, 2025 03:36 > > Last I looked, *moderators* don't have access to Mass Subscribe, only > *owners* do. Has that changed? I don't think this would have any effect on the > misqueueing issue, however. Our moderators are also owners so that's not a problem. > Hm. Do you have a reason for sending email from Drupal to Mailman through > Microsoft servers? Note: "yes" is a sufficient answer, I have no need to know > more. If it's just an accident, you can ensure that Drupal's mail will reach > Mailman by configuring it for local delivery, which you can make safe from > spam filters and DMARC processing. > > I don't think this would resolve the misqueueing issue, though. The reason for the Microsoft server being involved is that's the way our Systems folks insisted we set it up. So, main to our particular domain goes through that and is routed to our server. In other words, "yes". > > We definitely could rewrite our code to use the REST API[...]. But > maybe we > need to do that sooner rather than later. > > This should resolve the misqueueing issue. It's not that hard. In fact, it might be > easier that doing it by email (except that of course you already have the code for > doing it by email). The reason we didn't use the REST API is that we had code that worked (or at least that we thought worked). I've recommended to the site maintainers that they update their code to use the API and we'll deal with these things manually until that's done. Thank you and Mark Sapiro for your responses. -- Henry Hartley Westat RB 2151

1 year, 2 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > On 7/4/26 6:13 AM, Stephen J. Turnbull wrote: > > On the other hand, if Mailman sends mail to your user for > > any reason, and it does *not* bounce, they will be re-enabled > > automatically. > > I don't think this is correct unless you have some local > modification to do this. Thank you for the correction. Likely I misremembered that it would be re-enabled. I guess the stock process is the bounce count gets reset to zero after a time period with no bounces, but this isn't immediate and doesn't reenable. When the bounce count is reset, if it's "disabled by bounce", we could then re-enable. That's like a two-line change. Perhaps with a more complex algorithm (eg, store an indicator of that Address's recent bounce history in the database, and re-disable more quickly if it has a history of bouncing recently). A complex algorithm would be more invasive (database schema addition) and I'm not suggesting that yet. > Even then, how would it work? A bounce might come from downstream > MTA and possibly not for days. Nothing that depends on bounce by DSN is reliable though. Heck, you can't even be sure that that status "250 OK" isn't somebody treating you like a spammer and eating your mail. And if you're heavy on Gmail and Yahoo users, most bounces are likely to come very quickly and reliably. It might work pretty well for some lists and horribly for others. I guess we'd have to do more parsing of the local MTA's DSNs in that case, though. Hmmm. At least we know the stock behavior of the four we support. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 3 weeks

[MM3-users] Re: Moderate mails from owner

by Malcolm Austen

On Thu, 21 Mar 2019 16:58:45 -0000, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Thu, Mar 21, 2019, at 8:47 AM, Malcolm Austen wrote: >> On Wed, 20 Mar 2019 18:42:10 -0000, Mark Sapiro <mark(a)msapiro.net> >> wrote: >> >> > However, this is apparently not relevant because both the Member and >> > Non-Member actions are Hold. Thus, the post should be held unless it >> has >> > an Approved: header with the list's moderator_password attribute if >> > there is one, or it matches a Header filter rule with an accept >> action. >> >> At the risk of getting this really wrong - I have only limited MM3 >> knowledge - I will ask what is, I fancy, a closely related question ... >> >> My only experience of MM3 is with Ancestry's 'RootsWeb' installation. >> From >> the emails I can see a header "X-Mailman-Version: 3.1.0" but I can't >> find >> anything to identify Postorius which is the only interface I have to the >> system. >> >> From symptoms seen and described by others, I have deduced that the >> Postorius admin-per-user moderation options of "Default processing" and >> "List default" mean that a user may be set (by default on the rootsweb >> system!) to use the system default moderation settings rather than the >> list default settings. > > "Default Processing" means the default pipeline defined in Thanks, I will do some (more!) reading. > List > Settings > Alter Messages > 'Pipeline' ( in the bottom). This > pipeline is > system wide and is defined in source code, so it can't be customized by > site administrator. Unfortunately, that is not available to list-owners on the system concerned. Ancestry must have removed it. Malcolm. -- Malcolm Austen <malcolm.austen(a)weald.org.uk>

7 years, 7 months

Search results for query "sapiro"