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

[MM3-users] Re: Subscription issue with ghost confirmations

by Brian Carpenter

On 10/29/20 12:21 PM, Mark Sapiro wrote: > On 10/29/20 8:51 AM, Brian Carpenter wrote: >> On 10/29/20 11:33 AM, Mark Sapiro wrote: >>> The real question is if a user has a subscription waiting confirmation >>> and the policy is changed to moderate, is a second request rejected >>> because of the request waiting confirmation. If so, I think this is a >>> bug which should be fixed. >>> >> Do you think this is a bug with Mailman core or my system? > > If the current policy is moderate and the user has a prior request > waiting confirmation and a new request is rejected because of the prior > request waiting confirmation, I think that is a bug in core, but I don't > know if that is the case or not. I think it is a bug in Mailman 3 core. I am seeing the same behavior on my Postorius server. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 6 months

[MM3-users] Re: slow restart time for mailmanweb

by David Newman

On 12/28/21 1:20 PM, Mark Sapiro wrote: > It looks to me like the timeout is in stopping, not starting. What > happens if you separately > > systemctl stop mailmanweb > > and > > systemctl start mailmanweb Confirmed: root@myhost:/etc/mailman3# time systemctl stop mailmanweb real 1m30.239s user 0m0.010s sys 0m0.004s root@myhost:/etc/mailman3# time systemctl start mailmanweb real 0m0.012s user 0m0.011s sys 0m0.001s On 12/28/21 3:01 PM, Mark Sapiro wrote: > Is your /etc/systemd/system/mailmanweb.service the recommended one at > https://docs.mailman3.org/en/latest/install/virtualenv.html#automatically-s… Yes, modulo the use of MariaDB instead of PostgreSQL. > If so, try adding > > KillSignal=SIGQUIT > > to the Service section and see if that fixes it. root@myhost:/etc/mailman3# time systemctl restart mailmanweb real 0m1.026s user 0m0.008s sys 0m0.004s My limited understanding of SIGQUIT is that it dumps core, but 'find / -type f -name '*.core' did not return any core dumps from this event. Still unsure why the service hung on stop, but thanks! dn

4 years, 4 months

[MM3-users] Re: Notifying owners of membership changes but not moderators

by Perry Kollmorgen

Thanks Mark, I will give it a shot. — Perry > > On Nov 28, 2024 at 9:12 AM, <Mark Sapiro (mailto:mark@msapiro.net)> wrote: > > > > On 11/26/24 9:30 PM, Perry Kollmorgen wrote: > > For the code for moderators it currently only adds them: > > mailing_list.add_moderator(moderator.email, display_name=moderator.display_name) > > Would I need to add something similar which sets a delivery_status for the moderator added ? I think something like this ``` mailing_list.add_moderator(moderator.email, display_name=moderator.display_name) moderator = mailing_list._get_membership(moderator.email, 'moderator') prefs = moderator.preferences prefs['delivery_status'] = 'by_moderator' prefs.save() ``` -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to pcjkollmorgen(a)hotmail.com > >

1 year, 5 months

[MM3-users] Re: moving lists to another server

by Mark Sapiro

On 11/17/23 00:51, Odhiambo Washington wrote: > I am scratching my head bald trying to figure out how to bring in this > other MM3 site and list into my existing server, especially with regard to > the DB backend. > > The list - let's call it users(a)domainX.name was using MySQL backend and > had a separate DB for Mailman core and Mailman web. > I believe combining these into one isn't a problem. But getting to merge > this DB into my current one is what I am not sure about. This is https://gitlab.com/mailman/postorius/-/issues/13 which is a real need, but doesn't yet exist. I think the easiest thing for the archives is to forget the Mailman web DB and just export the archive as a mbox from the other site (if it's large, exporting the entire archive will time out so you have to do it in pieces). Then you can use hyperkitty_import to import it. For the list data, it's probably easiest to just create the list manually and go through the settings in Postorius and make them match, although you could dump the mailinglist table entry where list_id = 'users(a)domainx.name' and load that, but you'd need to edit the id field in the dump to match the id on your server. That leaves the members. Doing this with a DB dump/load would be very complex because while the member table has a list_id field which is the id of the list's entry in the mailinglist table and can be used to select the relevant members, these records also link to entries in the address, preferences and user tables and matching them would be an issue. I think a custom script would be required. If I were doing this, I would make a separate database on my server with a copy of the data from the other server and then try to make a script that would extract data from the other database and add it to mine. Alternatively you could just dump the members from the other servers with the `mailman members` command perhaps separately for regular and the different digest types and then add them with the `mailman addmembers` command. This wouldn't get all their attributes, but it could work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Disable Sign-up per domain

by Mark Sapiro

On 7/31/25 17:54, Mark wrote: > > Thank you Mark. It's so close. After wrangling your solution a bit it's > working a treat on my test server (wrangled solution below) . > > When I add it to the production server (same OS, MM installation, etc) > I'm getting a "Bad gateway" error page and the log reports ... > > ... > raise self.model.DoesNotExist( > django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist. That error will occur when settings.py contains SITE_ID = 0 and the host in the http request is not one of the hosts in the django_site table in the database or in Sites in the Django admin web UI. Is that possibly the case here? In any case, if the change to /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py that you report below is the only thing that changed from a working installation, I don't see how that can affect this. Is there a complete traceback preceding the log snippet you report. If so, what is it? > I cannot for the life of me get my head around that. I suspect it's > something to do with what you said -- "whatever is proxying to Django > setting the appropriate HTTP_HOST header." -- which I don't understand. This is in the configuration of the web server. It should be configured to pass the host of the incoming request to the proxy target in the HTTP_HOST header. In nginx this is `proxy_set_header Host $host;`. In apache it is `ProxyPreserveHost On`, but again the change to user_adapter shouldn't affect this. > Any additional advice gratefully received. > > > ================================== > /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py > ================================== > COMMENT OUT THESE 2 LINES... > > # def is_open_for_signup(self, req): > # return False > > REPLACE WITH THE FOLLOWING... > > def is_open_for_signup(self, req): > if req.META['HTTP_HOST'] == 'lists.mydomain.com': I had if req.META.HTTP_HOST == 'lists.mydomain.com': which as you discovered is wrong. What you have is correct. > return False > else: > return True And here I had return super().is_open_for_signup(self, req) which should return the is_open_for_signup result from allauth.account.adapter.DefaultAccountAdapter but since that result is an unconditional True, what you have is OK too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: Migrating mailman3 to latest ubuntu lts

by Mark Sapiro

On 12/14/23 01:48, Helio Loureiro wrote: > > But it is failing to start displaying the domain name from the previous > machine. > > (venv) mailman@new-server ~ (v3.3.9)> mailman start > Starting Mailman's master runner > Generating MTA alias maps > Traceback (most recent call last): > File > "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", > line 1969, in _exec_single_context > self.dialect.do_execute( > File > "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", > line 922, in do_execute > cursor.execute(statement, parameters) > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/cursors.py", line > 153, in execute > result = self._query(query) > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/cursors.py", line > 322, in _query > conn.query(q) > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > line 558, in query > self._affected_rows = self._read_query_result(unbuffered=unbuffered) > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > line 822, in _read_query_result > result.read() > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > line 1200, in read > first_packet = self.connection._read_packet() > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > line 772, in _read_packet > packet.raise_for_error() > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/protocol.py", > line 221, in raise_for_error > err.raise_mysql_exception(self._data) > File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/err.py", > line 143, in raise_mysql_exception > raise errorclass(errno, errval) > pymysql.err.OperationalError: (1054, "Unknown column 'domain.alias_domain' > in 'field list'") The issue is your domains table and possibly others are not up to the current schema. This should be accomplished by Mailman core running all the necessary migrations in mailman/database/alembic/versions/. For some reason, alembic's MigrationContext thinks the migrations have been run, but they haven't. In the `mailman` database, the alembic_version table has the version_num of the putative current version. The migration that added alias_domain is dfe82cf73702_add_alias_domain.py. If there is no alias_domain column in the domain table, alembic_version.version_num should be a version older than 'dfe82cf73702'. I suggest querying the prior mailman database for the alembic_version.version_num value and setting that in the current database, assuming that that migration exists in mailman/database/alembic/versions/. This may be sufficient, but there may be other inconsistencies depending on exactly what you did. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Mailman Header Behavior

by Samir Faci

Perfect, Thanks. Is there a way to set this as a default for all new lists being created? Still working on the new styles, I imagine that can be set there during the selection of the list type. -- Samir Faci On Fri, May 15, 2020 at 9:44 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/15/20 9:31 AM, Samir Faci wrote: > > > > Is there a way to force mailman to ensure that the list name shows up in > > the from field? > > In Postorius Settings -> DMARC Mitigations set DMARC mitigation action > to Replace From with list address and set DMARC Mitigate unconditionally > to Yes. > > -- > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 11 months

[MM3-users] Re: Member Issue Discovered

by Mark Dadgar

On Oct 20, 2020, at 9:13 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/20/20 8:53 PM, Mark Dadgar wrote: >> On Oct 20, 2020, at 8:19 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> Even in mailman 2.1, while a list admin could go to a user's options >>> page for the list and change things, the "change globally" check boxes >>> only worked for the user, not for the list admin. >> >> That was by design!? >> >> As an admin, that was so irritating. > > Yes, it was by design. Do you really think that list owners should be > able to enable or disable mail delivery, set digest format, user's > password, etc. for a user's subscription on lists that they don't own? Yeah, that makes sense for very large installations. Good point. IIRC, mm2 had the concept of a site-admin. It would be nice if it had worked for them, though. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 6 months

[MM3-users] Re: Multiple domain problem

by Lars Bjørndal

Ah, so stupid error and so simple solution - thank you! Lars On Tue, Feb 14, 2023 at 12:42:16PM -0800, Mark Sapiro wrote: > On 2/14/23 12:08, Lars Bjørndal wrote: > > > > The domain that doesn't work: > > > > > > <VirtualHost *:80> > > ServerAdmin webmaster(a)list.punktskriftutvalget.no > > DocumentRoot /var/www/list.punktskriftutvalget/ > > ServerName list.punktskriftutvalget.no > > ErrorLog logs/list.punktskriftutvalget-error_log > > CustomLog logs/list.punktskriftutvalget-access_log common > > Redirect permanent / https://list.punktskriftutvalget.no > > </VirtualHost> > > Add a trailing slash > > Redirect permanent / https://list.punktskriftutvalget.no/ > > -- > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to lars(a)lamasti.net

3 years, 2 months

[MM3-users] Re: hello， Discussion on how to subscribe to the mailing list

by Mark Sapiro

On 1/16/23 18:55, 朱超 wrote: > Hi, When I subscribe the email list in Subscription Policy is confirm, Some problems happen in here： > 1.Some mail mua reject send the confirm the message, because the length of recipient is too long. for exmaple: requirements-confirm+9605556e0b35a5da280c1de0d34a3e6f770f8ea5@domain, and the mail mua reject to modify about this. The default English template says in part: Before you can start using GNU Mailman at this site, you must first confirm that this is your email address. You can do this by replying to this message. Or you should include the following line -- and only the following line -- in a message to $request_email: confirm $token I.e. It gives an alternative method if `reply` doesn't work. You can provide a custom version of this template with different wording if you think you can improve it. > 2.It is inconvenient for users to use. Many people will mistakenly think that after clicking the subscribe button, it will be successful, and they will not process the email. If you set Subscription Policy to Confirm, you are saying that the user must confirm that that is their email address. This requires sending an email requesting confirmation to that address. If you don't want that step, you can set Subscription Policy to Open, but then anyone can maliciously subscribe third parties to the list. > Regarding the discussion on the subscription method of the mailing list, should we consider optimizing the subscription method of the mailing list, for example: > 1. use the method of sending a verification code to subscribe by email，When you receive the verification code sent by the mailing list and fill it in again, you can subscribe successfully。 How is this different from the present method. If you want, you can make a custom template and include something like: Alternatively, you can confirm by going to the URL https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token We don't include that in the default template because Mailman core doesn't know if you even have a web UI or how to access it if you do. > 2. use the email to send a connection to confirm the subscription，People click the link to be redirected to a confirmation page to subscribe to the email。 See above. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

Search results for query "sapiro"