Search results for "Postorius" - Mailman-users

Re: Your Dashboard

by Mark Sapiro

On 2/11/20 1:27 PM, Allan Hansen wrote: > > Our site has over 50 lists and several moderators are responsible for multiple lists. In addition to a dashboard like described here I would like to have a ‘comment’ field next to each request, so tha the moderator can keep track of the status of each. Our approval process involves multiple steps. > > Time to visit gitlab? GitLab is the one place for feature requests for Mailman 3/Htperkitty/Postorius. Things requested in list posts get lost and forgotten. That said, the more specific you can be in a request, the better. I.e., if you want a dashboard, what do you want on it for, e.g., the site admin, a user who may or may not be an owner of a couple of lists, a moderator of a couple more and a member of still others. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

Re: Held messages page not rendering the message

by peter＠chubb.wattle.id.au

>>>>> "mike-mailman" == mike-mailman <mike-mailman(a)earth.li> writes: mike-mailman> Hi When the list moderator goes to the held_messages mike-mailman> page, they correctly get a list of the held messages and mike-mailman> can accept/reject/discard them mike-mailman> However, clicking on the individual message to read it mike-mailman> doesn't work - it does nothing visible at all. From mike-mailman> debug I can see it requests mike-mailman> /mailman3/postorius/api/list/<list>/held_message/1/ mike-mailman> which returns correctly (and the body includes the mike-mailman> message as expected) - but it never renders it If you installed from the Debain/Ubuntu packages, this is probably https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033072 The fix is to get your web server to pick the correct location for Jquery,js --- se the bug fix. To confirm, turn on the developer tools in your browser and look in the javascript console. Peter C

2 years, 7 months

Re: Installing mailman 3

by Rafael Mora

I did not run the createsuperuser command, have to do that. What about this: Don’t leave the console email backend configured and running once you get to the point where you want to send real emails, though! How do I change the setting to send the emails instead of printing them on the console???? On Fri, Jul 21, 2017, 21:16 Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/21/2017 06:59 PM, Rafael Mora wrote: > > Is there a ´default´ admin account?? > > > It's the user you create with > > python manage.py createsuperuser > > See > < > http://docs.list.org/en/latest/devsetup.html#run-the-mailman-suite-combined… > >. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 3 months

Re: Emergency moderation and clearing out a lot of held messages

by Caballero, Danny (Dan)

I don't understand. We have a single database configured for everything. I don't recall reading anything in the set-up documentation about using more than 1 database for Mailman3. Let me know if I'm missing something! -- Dan Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Friday, November 11, 2022, 7:01 AM To: Caballero, Danny (Dan) <dancab(a)caltech.edu> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Emergency moderation and clearing out a lot of held messages I don't have a helpful suggestion yet but would like to clarify: Dan Caballero writes: > "2022-11-09T18:37:49.106105Z 19100868 [Note] Aborted connection > 19100868 to db: 'mailman3_prod' user: 'mailman' host: '10.6.5.187' > (Got an error reading communication packets)" db: mailman3_prod is the core database, not the Django (Postorius and Hyperkitty, or mailman-web), is that correct?

2 years, 11 months

Re: pending subscriptions lost?

by IEM Network Operation Center (IOhannes m zmölnig)

On 3/14/22 17:03, Mark Sapiro wrote: > On 3/14/22 06:00, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > This is https://gitlab.com/mailman/mailman/-/issues/729 fixed in Mailman > 3.3.5. thanks for comfirming. > > >> - i (as administrator) do not see any "pending subscriptions" (the >> list is setup with a simple "Confirm" subscription policy > > The count badge only counts subscriptions waiting moderator approval. If > you pull down the Subscription requests tab and click Pending > Confirmation you should see them and be able to discard them. hmm. i'm not sure i can follow. my "Subscription requests" tab seems to not have any "Pending Confirmation" section (see attached screenshot). this is with "Postorius Version 1.2.4" (as installed by the mailman3 Debian package). fdsm< IOhannes ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Subscription requests.png

3 years, 7 months

Re: mailman-users archive search

by Abhilash Raj

On Mon, Sep 9, 2019, at 7:38 PM, Abhilash Raj wrote: > > > On Mon, Sep 9, 2019, at 7:19 PM, Mark Dale wrote: > > Is this list's search function kaput, or is it an issue with MM3, or is > > it me? > > > > *** > > https://lists.mailman3.org/archives/search?mlist=mailman-users%40mailman3.o… > > *** > > Mailman-users search results for query "Postorius" > > mailman-users(a)mailman3.org > > > > 0 messages > > > > Sorry no email could be found for this query. > > Elasticsearch server is down for now, I'll fix it. Should be working now. > > > > > > /Mark > > _______________________________________________ > > 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/ > > > > -- > thanks, > Abhilash Raj (maxking) -- thanks, Abhilash Raj (maxking)

6 years, 1 month

Re: Ann: Mailman Core 3.3.5 is out

by Eggert Ehmke

Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I would have to bypass the Debian installer. Or will there be Debian packages available? Same question for Postorius 1.3.6 Am Mittwoch, 29. September 2021, 05:26:47 CEST schrieb Abhilash Raj: > Hey Everyone, > > I just tagged and uploaded Mailman Core 3.3.5 release. > > This release includes both bug fixes and some new features. A full list of > changes is available here: > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS. > html#news-3-3-5 > > You can install this version using pip: > > $ pip install mailman==3.3.5 > > The release tarball is available on PyPI as well: > > https://pypi.org/project/mailman/3.3.5/#files > > Thanks to everyone who made this release possible! > > Abhilash > > > On Sep 19, 2021, at 11:02 AM, Abhilash Raj <maxking(a)asynchronous.in> > > wrote: > > > > Hey Everyone, > > > > I just tagged and released Mailman Core 3.3.5rc1 release. > > > > This is identical to 3.3.5b1 in code, the only changes that have been made > > are in utility scripts and testing configuration.> > > You can install this version using: > > $ pip install --pre mailman==3.3.5rc1 > > > > If you want to download a release tarball, you can do so from here: > > https://pypi.org/project/mailman/3.3.5rc1/#files > > > > This is the first (and only) planned release candidate for 3.3.5 release. > > The stable release is planned for next week. > > > > thanks, > > Abhilash > > > > On 9/7/21 12:39 AM, Abhilash Raj wrote: > >> Hello Everyone, > >> I am pleased to announce that Mailman Core 3.3.5b1 is now out. It is a > >> pre-release for 3.3.5, which is slated to come out in 3 weeks from now. > >> I am planning for a 2 week beta period, after which I'll release the > >> first RC and then stable a week after. Right now I am not planning to > >> release a second beta version, but if there are several changes in Core > >> in the next week or so, then I might. This release includes a lot of bug > >> fixes and some new features. It also includes a security enhancement > >> that improves the authentication of REST API by adding resistance to > >> some timing channel attacks. A full list of changes in this version can > >> be found here[1]. > >> [1]: > >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NE > >> WS.html#news-3-3-5 We have also made improvements in the i18n workflow > >> and now the email templates are updated from the translated messages in > >> the .po files that we get from Weblate. Documentation for translators is > >> available here[2] if you want to help translate Mailman into your native > >> language. [2]: https://docs.mailman3.org/en/latest/translation.html > >> > >> This is a pre-release version, if you want to test it with your setup, you can install it using: > >> $ pip install --pre mailman==3.3.5b1 > >> > >> If you want to download a release tarball, you can do so from here: > >> https://pypi.org/project/mailman/3.3.5b1/#files > >> > >> This release received a lot of contributions from community, which I am > >> really happy about! I'd like to thank everyone who made this release > >> possible!> > > -- > > thanks, > > Abhilash Raj (maxking) > > -- > thanks, > Abhilash Raj (maxking)

4 years, 1 month

upgraded Django & flufl.lock now do not receive own postings

by Stephen J. Turnbull

Christian via Mailman-users writes: > Now for some reason I'm not receiving my own postings to the list whereas > before I was. 'Receive own postings' is still set to yes. Is anybody receiving posts? Are you looking at your settings as a list subscriber, or for the address, or for your User? The first one in that list will decide what setting is applied. Most likely all of your settings are set in the User (called "global" in Postorius), but you should check to make sure. How about "receive list copies"? If you're Cc'd on the post as well as being a member of the list, setting that to "no" would prevent you from receiving the message via the list. The three levels of setting applies here too. Otherwise, we need to see logs, please. Also check your spam folder and local filters. Steve

3 years, 2 months

changing the main template for subscriptions and more

by Jens Günther

Hey there, in Mailman2 there was a simple link in the moderation-emails, with which I was able to open directly the "held-messages". I know how to manually integrate such a link with the variables of mailman (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) But: How can I change the template for all the lists (respectively maildomains/webdomains) so that I don't have to do this manually for all lists? I searched a bit for the corresponding template, but didn't find it. At the end it only says the following: "At your convenience, visit your dashboard to approve or deny the request." -> here I would like to add the following: "At your convenience, visit your dashboard to approve or deny the request: https://$domain/postorius/lists/$short_listname.$domain/held_messages" Or if someone sees another possibility to get us on the right track, it would be more than welcome, thank you! Kind regards, Jens.

4 years, 4 months

unique key violation because of case sensitivity of email address

by Jörg Schulz

After updating to the most recent version of mailman-web, the migrations script issued an error: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | Traceback (most recent call last): mailman-web | File "/usr/lib/python3.12/site-packages/django/db/backends/utils.py", line 89, in _execute mailman-web | return self.cursor.execute(sql, params) mailman-web | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mailman-web | psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "account_emailaddress_user_id_email_987c8728_uniq" mailman-web | DETAIL: Key (user_id, email)=(27, John.Doe(a)mynicedomain.de) already exists. mailman-web |(...) Digging into the db, I found the duplicate to result from a duplicate entry using john.doe(a)mynicedomain.de Obviously, the process that originally created the entry, took case sensitivity literally which doesn't seem to be the case any longer for the migration script. I fixed this by removing one of the duplicates hoping no further errors will come up.... What would have been the better approach?

1 year, 4 months