Search results for "Postorius" - Mailman-users

Re: best pratice - set default MM settings and make them update-save

by Stefan Bauer

Thank you very much. But this is a _new_ mailman behavior. In previous versions, there was no checkbox at all and mass-subscription was done without any confirmation. Stefan Am Mo., 16. Mai 2022 um 18:35 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 5/16/22 07:16, Stefan Bauer wrote: > > > > Is there also a way to have this box checked by default or do not > request a > > verifcation at all? > > Could not find any flag in base.py. > > To have the box checked by default would require a patch to Postorius > like this. > ``` > --- a/src/postorius/forms/list_forms.py > +++ b/src/postorius/forms/list_forms.py > @@ -1073,7 +1073,7 @@ class ListMassSubscription(forms.Form): > > pre_verified = forms.BooleanField( > label=_('Pre Verified'), > - initial=False, > + initial=True, > required=False, > help_text=_( > 'If checked, users will not have to verify that their ' > ``` > Not requiring verification at all would require patching Mailman core > but would be a bad idea as it could allow someone to subscribe anyone > without that person's consent. > > -- > 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/ >

4 years, 1 month

Re: mass invitation

by Mark Sapiro

On 6/20/19 9:07 AM, Abhilash Raj wrote: > > > On Thu, Jun 20, 2019, at 7:17 AM, mailman3(a)malevil.cc wrote: >> in postorius there is just the option to make a mass subscription, in >> mailman2 there was also the possibility to just invite users, so they >> need to click a link when they really want to join the list. Is this >> also available in mailman3/postorius? > > > No, not yet. There is an open issue that I can't dig out right now. The issue is <https://gitlab.com/mailman/mailman/issues/510> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Re: Mailman3 on Debian 10

by Mark Sapiro

On 1/30/20 9:22 AM, Bala Mutyam wrote: > Sorry one more issue, > > Mailman settings page giving me below error. > > Server error > An error occurred while processing your request. > > Error logs: > > ERROR 2020-01-30 17:20:11,331 16285 django.request Internal Server Error: /postorius/accounts/subscriptions/ > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 41, in inner > response = get_response(request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 187, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 185, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py", line 23, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python3/dist-packages/postorius/views/user.py", line 306, in user_subscriptions > mm_user = MailmanUser.objects.get_or_create_from_django(request.user) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 164, in get_or_create_from_django > return self.get(address=user.email) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 86, in get > return method(*args, **kwargs) > File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 322, in get_user > return User(self._connection, content['self_link'], content) > KeyError: 'self_link' Just prior to this is a call to the REST API to GET /users/user(a)example.com (or whatever the user's address is). It appears that that user doesn't exist in core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

Re: Postorius is not working (throws "Error 500" suddenly after changing POSTORIUS_TEMPLATE_BASE_URL and changing back)

by Odhiambo Washington

On Sun, Oct 1, 2023 at 10:46 AM Wikinaut <mail(a)tgries.de> wrote: > I could not fix the problem, apparently there is a mismatch somewhere now. > > sudo pip uninstall django-q > Found existing installation: django-q 1.3.9 > Uninstalling django-q-1.3.9: > Would remove: > /usr/local/lib/python3.9/dist-packages/CHANGELOG.md > /usr/local/lib/python3.9/dist-packages/django_q-1.3.9.dist-info/* > /usr/local/lib/python3.9/dist-packages/django_q/* > Proceed (y/n)? n > > whereas > dpkg -l | grep django-q: > > ii python3-django-q 1.2.1-1 > > /usr/lib/python3/dist-info: > 4 drwxr-xr-x 8 root root 4096 21. Jun 2022 django_q > 4 drwxr-xr-x 2 root root 4096 21. Jun 2022 django_q-1.2.1.egg-info > > sudo apt remove python3-django-q > the following packet will be REMOVED: > mailman3-full mailman3-web python3-django-hyperkitty python3-django-q > Continue [Y/n] n > > What to do? I don't want to remove mailman3, I just want to bring the > 1.2.1-1 to 1.3.9... > Maybe you can make your life a little more bearable by abandoning the use of Debian packages and embracing the virtualenv install documented at https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install and we'll find it easier to help you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 8 months

Re: The Use of Hyperkitty as a Forum and Archiver

by Allan Hansen

I can echo Mark’s responses exactly, as well as the sentiment that it’s WAY WAY WAY better. One additional item of praise: The ability to post/respond to messages from within HK(I guess what you refer to as the ‘forum’ feature) is way cool. While I’m at it here are also some small and not so small gripes: a. The link for visit ’the archives’ is embedded in a sentence. It should be an icon like ’Unsubscribe’. While we’re on that page, the same goes for ‘your list options page.’ b. On entering HK, when listing ‘Recent’, etc, the author is not listed. c. Why is ‘Manage subscription’ an option on this page? The ‘Manage this list’ in the header already has this link. And it appears in the list of options on which threads to show. ????? d. When listing ’Threads by month’ and ‘All threads’, the left panel is taken over. e. When I log in as admin, I get a ‘Delete’ button on this page as well. There is no mention of what it does. Does it delete the list, the archive or the shown threads (I assume the list, but why is this button here???). f. The activity summary here is irrelevant to most users and should be just an optional display. g. Sometimes the lists are listed by Postorius and at other times (at login) by HK. The displays by Postorius are much better and cleaner. The listings by HK use too much real estate for the ‘Activity in the past 30 days’ graphs, which really are just fluff. The difference in presentation between Postorius and HK is confusing and confounding. Thank you for the reminder, Brian. I’ll send out a note to my lists’ members to remind them of this very improved tool. Yours, Allan Hansen hansen(a)rc.org > On Jul 14, 2020, at 8:48 , Mark Dadgar <mark(a)pdc-racing.net> wrote: > > On Jul 14, 2020, at 6:51 AM, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: >> - Has the forum feature (Hyperkitty) of MM3 been received well by your list members or is it mostly ignored? > > Pretty sure no one even knows its there, even though I told them when we migrated to MM3 originally. > >> >> - Do you see an increase in the use of HK as a forum from your list members? > > No. > >> - What kind of feedback have you received from your list members considering the forum function of MM3? Positive or negative? > > None. > >> - Do you think HK is received well by your list members as an archiver and do you think it provides a better user experience for viewing/searching archives vs Pipermail of MM2? >> > > WAY WAY WAY better experience than Pipermail. The single most common feedback about the archives under MM2 was “the archives are broken - search can’t find anything.” htdig was not a great indexer. > > - Mark > ----- > mark(a)pdc-racing.net | 408-348-2878 > > > _______________________________________________ > 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/

5 years, 11 months

Re: Emergency Moderation

by Brian Carpenter

On 5/21/20 6:30 PM, Mark Sapiro wrote: > On 5/21/20 3:23 PM, Brian Carpenter wrote: >> Is there an Emergency Moderation function (similar to the one that Mailman 2 had) with Mailman 3 core/Postorius? > > It's in core and it's just recently been exposed in REST > https://gitlab.com/mailman/mailman/-/merge_requests/643 but it's not in > Postorius yet. > Can I add this through a mailman core update via pip? Thank you for the information. It is very helpful. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

6 years, 1 month

Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Mark Sapiro

On 6/8/19 4:33 PM, Andrew Bernard wrote: > Hi Mark, > > Thanks for your great help. But despite decades of UNIX experience, my area > is not Django (yet). The nub of my question is that I thought you have to > have a manage.py file for Django to be able to set up the various affairs, > such as making the database migrations and so on. It is that that is > eluding me. Apologies for this hopelessly newbie question. The equivalent of manage.py in what I suggested is /opt/mailman/bin/django-admin. > I was impressed with your method of installation in the page referenced, > and I have foolwed that closely. But I am puzzled about the build script. > If I run as user mailman, not root, it wanted to install under /usr. which > of course results in permission denied. I had to modify the script to say > this: > > python setup.py install --prefix /opt/mailman/mm/venv If you want to install in the virtualenv, you should just activate the virtualenv and it should work. Perhaps the issue is that the build script at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> assumes the virtualenv is at /opt/mailman/mm/venv. You need to insure that the '. ../mm/venv/bin/activate' line is actually pointing to your 'venv/bin/activate' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Question after upgrade to mm 3.2.3 and latest postorius

by David Krantz

Hi all, I have just upgraded to mailman 3.2.3. My installation is from the git sources and I use two different venv:s, one for the web part as I did not want to compile the web server plugin to a newer python version than 3.5, and one venv for the rest running python 3.7. Apart from some missing dependencies and some changes that affected the django config I just have two issues with postorius: 1. The index page with all lists is not sorted in any useful way although it is based on something as the order seems to be stable. Prior to the upgrade the lists were sorted in alphabetical order after list name which is a lot more usable for me as admin. If I click the link at the bottom with "click to view all lists" I get the old behaviour. 2. The template menu simply does not work, it seems as if some database table is missing even after running migrations. Django logs the following: ERROR 2019-08-11 20:58:55,038 exception 11837 139756347221760 Internal Server Error: /mailman3/lists/TESTLIST/templates Traceback (most recent call last): File "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", line 85, in _execute return self.cursor.execute(sql, params) psycopg2.errors.UndefinedTable: relation "postorius_emailtemplate" does not exist LINE 1: ...ext", "postorius_emailtemplate"."identifier" FROM "postorius.. The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/exception.py", line 35, in inner response = get_response(request) File "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/base.py", line 158, in _get_response response = self.process_exception_by_middleware(e, request) File "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/base.py", line 156, in _get_response response = response.render() File "/...VENV3.5/lib/python3.5/site-packages/django/template/response.py", line 106, in render self.content = self.rendered_content File "/...VENV3.5/lib/python3.5/site-packages/django/template/response.py", line 83, in rendered_content content = template.render(context, self._request) File "/...VENV3.5/lib/python3.5/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 175, in render return self._render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 943, in render bit = node.render_annotated(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 910, in render_annotated return self.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/loader_tags.py", line 155, in render return compiled_parent._render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 943, in render bit = node.render_annotated(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 910, in render_annotated return self.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/loader_tags.py", line 67, in render result = block.nodelist.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 943, in render bit = node.render_annotated(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 910, in render_annotated return self.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/defaulttags.py", line 313, in render if match: File "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", line 276, in __bool__ self._fetch_all() File "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", line 1179, in _fetch_all self._result_cache = list(self._iterable_class(self)) File "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", line 54, in __iter__ results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size) File "/...VENV3.5/lib/python3.5/site-packages/django/db/models/sql/compiler.py", line 1063, in execute_sql cursor.execute(sql, params) File "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", line 68, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", line 77, in _execute_with_wrappers return executor(sql, params, many, context) File "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", line 85, in _execute return self.cursor.execute(sql, params) File "/...VENV3.5/lib/python3.5/site-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", line 85, in _execute return self.cursor.execute(sql, params) django.db.utils.ProgrammingError: relation "postorius_emailtemplate" does not exist LINE 1: ...ext", "postorius_emailtemplate"."identifier" FROM "postorius... Cheers // David

6 years, 10 months

Re: error changed after restart

by Abhilash Raj

On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > On 6/2/21 18:08, Abhilash Raj wrote: >> >> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via >> Mailman-users wrote: >>> I restarted de server and the error changed. Now the log shows >>> "KeyError: 'subscription_mode'": >> Did you also restart Mailman Core after the upgrade? > > Yes, indeed: > > I stopped mailman core and all the processes related. Did the > upgrades. > Started all again. Find the errors in the web user interface. Stopped > all again. Looked for errors in the log. Restarted the complete > server. > > Found the second error that this second mail is about to. It happens > when, in the main page that shows all the lists you click to see one > of > them. It seems to me that it has been database structure changes in > django that the upgrade is not aware... but it's a very long shot from > my side. `subscription_mode` was added in Mailman Core 3.3.2 and it is actually a derived atrribute and not stored in Database. Mailman's API should be returning this attribute for each Member, but for some reason it seems to me like it isn't doing that even though do have Mailman 3.3.3 running like you said. If you have Curl installed, can you send me the output of: $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1 It should ideally return an output that looks something like shown here[1]. You can put the username/password of Core's API server in the above command. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… Abhilash > > I'm using sqlite as django database and mysql for mailman. > >> >>> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server >>> Error: /mailman3/mailman3/lists/name_and_domain.of.the.list >>> Traceback (most recent call last): >>> File >>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>> line 119, in __getattr__ >>> return self._get(name) >>> File >>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>> line 86, in _get >>> raise KeyError(key) >>> KeyError: 'subscription_mode' >>> >>> During handling of the above exception, another exception occurred: >>> >>> Traceback (most recent call last): >>> File >>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", >>> line 34, in inner >>> response = get_response(request) >>> File >>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >>> line 115, in _get_response >>> response = self.process_exception_by_middleware(e, request) >>> File >>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >>> line 113, in _get_response >>> response = wrapped_callback(request, *callback_args, >>> **callback_kwargs) >>> File >>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >>> line 71, in view >>> return self.dispatch(request, *args, **kwargs) >>> File >>> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", >>> line 74, in dispatch >>> return super(MailingListView, self).dispatch(request, *args, >>> **kwargs) >>> File >>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >>> line 97, in dispatch >>> return handler(request, *args, **kwargs) >>> File >>> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", >>> line >>> 295, in get >>> member.subscription_mode == >>> File >>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>> line 124, in __getattr__ >>> self.__class__.__name__, name)) >>> AttributeError: 'Member' object has no attribute 'subscription_mode' >>> *********************** >>> some info about the installed versions via pip list: >>> pip list | grep django >>> django-allauth 0.44.0 >>> django-appconf 1.0.4 >>> django-compressor 2.4 >>> django-extensions 3.1.0 >>> django-gravatar2 1.4.4 >>> django-haystack 3.0 >>> django-mailman3 1.3.5 >>> django-picklefield 3.0.1 >>> django-q 1.3.4 >>> djangorestframework 3.12.2 >>> >>> pip list | grep mailman >>> django-mailman3 1.3.5 >>> mailman 3.3.3 >>> mailman-hyperkitty 1.1.0 >>> mailmanclient 3.3.2 >>> >>> pip list | grep postorius >>> postorius 1.3.4 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users >>> wrote: >>>> I've just upgrade mailman 3 installation following Mr. Sapiro >>>> advice: >>>> did a >>>> >>>> pip install --upgrade django-mailman3 hyperkitty mailman >>>> mailmanclient >>>> mailman-hyperkitty postorius >>>> >>>> I did a "python3 manage.py migrate" after, too. >>>> >>>> And all seemed to run well. >>>> >>>> All the lists showed in postorius via web, but when I try to >>>> accesss >>>> into one of them the browser shows an error. >>>> >>>> In the log you can see: >>>> >>>> *-*-*-*-*-*-* >>>> >>>> Traceback (most recent call last): >>>> File >>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>> line 119, in __getattr__ >>>> return self._get(name) >>>> File >>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>> line 86, in _get >>>> raise KeyError(key) >>>> KeyError: 'get_requests_count' >>>> >>>> ... (And after all the traceback lines) >>>> >>>> AttributeError: 'MailingList' object has no attribute >>>> 'get_requests_count' >>>> >>>> *-*-*-*-*-*-*-* >>>> >>>> The lists seem to be distributing messeages well.. but I cannot >>>> acces >>>> via web administration (django/postorius) >>>> >>>> Can anyone point me in the right direction to solve this, please? >>>> >>>> _______________________________________________ >>>> Mailman-users mailing list -- mailman-users(a)mailman3.org >>>> <mailto:mailman-users@mailman3.org> >>>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >>>> <mailto:mailman-users-leave@mailman3.org> >>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> >>>> >>> _______________________________________________ >>> Mailman-users mailing list -- mailman-users(a)mailman3.org >>> <mailto:mailman-users@mailman3.org> >>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >>> <mailto:mailman-users-leave@mailman3.org> >>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> >>> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

5 years, 4 months

Re: django fake users

by Stephen J. Turnbull

Andrew Hodgson writes: > >Require moderator approval for subscribing. > > I don't think this would help the issue. What I am seeing here is > users signing up through Postorius using the sign up option which > then creates an account in Django (but not Mailman). Ah, so "fake" == "account in Django but no user in Mailman"? I don't have time to look at it, so take this with a grain of salt, but I don't think they are passing the email confirmation. If they were, they would show up in Mailman. > I don't know whether they pass email confirmation or not (I don't > see this in Django admin), however they don't get added as users in > Mailman and they don't attempt to subscribe to any list. I think this would be simple enough to deal with (not trivial, so I'm not making any promises except to try adding it to the GSoC ideas page -- that should be enough to clarify whether there are any "annoyance to 'real' users" issues, and we move forward from there if there aren't). Basically, Postorius should notify Mailman that there is a *pending* user in Django, and if there's no confirmation by a deadline, remove that user. This requires a bunch of infrastructure like a table of "pending" users, callbacks for the deletion, etc, but I don't see why it would be conceptually difficult. (This combination is why I think it would be a good GSoC task) Steve

5 years, 5 months

Mailman-users search results for query "Postorius"