Search results for "Postorius" - Mailman-users

Re: Help request, almost got it going, but ....

by Abhilash Raj

Hi Claus, On Fri, 1 Sep 2017 23:33:56 +0200 Claus-Justus Heine via Mailman-users <mailman-users(a)mailman3.org> wrote: > First: thanks for all those development work, I am aware of the fact > that this is free software and most of the development probably happened > in someones spare-time. > > I have some problems: > > - I tried to install mailman v3. "Read the (non) docs" was of little > help, but I got to some partly success following the commands in the > scripts in the docker image at > > https://github.com/maxking/docker-mailman If you can point out what were the few things that you think were missing in the docs but you were able to figure out using the scripts in container image, it would help us improve the documentation. You can send them here or open an issue on Gitlab project[1]. [1]: https://gitlab.com/mailman/mailman-suite-doc/issues > > Things seemed to work out, I generated a test-list "Playground" and now > I am just in the progress to click through all the configuration options > in the the postorius Web-GUI. So far so good > > Now I read the "Message Acceptance" tab AND here is the problem: > > Seemingly, at some point in the deep dungeons of the source code the > "Acceptable aliases" Text-Box is not interpreted correctly. > > Specifically, at the start it contains the string > > [] > > When then changing something int the "Message Acceptance" tab, an error > shows up in the web-page (but no-where in the logs) > > "An error occured: []" > > and the bogus [] is restored. I tried to dig into the source code, and > well, the data source of the text-field is an array or list of > acceptable email-adresses. But seemingly finally at some point in the > source code an empty list is not converted to the empty string, but to > the string []. > > I can get rid of the error message "An error occured: []" by inserting > an email-at '@' at just some place in the input box, this yields > (clicking "Save changes" again and againg ...): > > [u"[u'@']"] > [u'[u\'[u"[u\\\'@\\\']"]\']'] > [u'[u\'[u\\\'[u\\\\\\\'[u"[u\\\\\\\\\\\\\\\'@\\\\\\\\\\\\\\\']"]\\\\\\\']\\\']\']'] > > and so on. > > Unfortunately, I did not find the location of this bug, although I was > finally able to add some "foobar" string to the already bogus web-output. > > Any help would be appreciated. > > BTW: > * where is the bug-tracker for mailman3? > * The documentation is really, well, close to non existent. Personally, > I think the name of the URL "read-the-docs" is almost cynical. > > Guess I give up on it, it just does not seem to be ready for production. > > > This was (following the docker stuff at githb) with > > Pythong3: > mailman==3.1.0 > mailman-hyperkitty==1.1.0 > > Python2: > mailmanclient==3.1.0 > postorius==1.1.0 > hyperkitty==1.1.1 > django-mailman3==1.1.0 > > Here I realize a slight version difference between the hyperkitty stuff. > But this is a bug in postorius. So what. > > Thanks for any help, cheers > > Claus > -- thanks, Abhilash Raj

8 years, 11 months

Re: Python 3.13 compatibility

by Thomas Krichel

4 months, 1 week

Re: [SOLVED] Re: Re: Help with Newbie error -- I think I deleted my server

by Mark Sapiro

On 12/25/21 7:13 AM, William Oliver wrote: > > Just out of curiosity, if I could not have guessed a valid ID number > and did not have the admin interface, how could I have figured out what > site IDs were available? If Postorius is working, recent versions show the SITE_ID in the domains view. I.e. after you added your domain you could have noted the SITE_ID and made the change in settings before deleting the example.com domain. In any case, the django_site table in Mailman's database has the information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

Re: Strange password problem

by Odhiambo Washington

On Thu, Jun 22, 2023 at 12:34 PM Eggert Ehmke via Mailman-users < mailman-users(a)mailman3.org> wrote: > This happened several times recently with Postorius Version 1.3.8: > -I try to log in as admin > -rejected because of wrong password (password is stored in browser) > -used forgotten password function > -reset password to the stored value from browser > -login works now. Works also when logged out/in again > -however, the next day this behaviour repeats. > > Any hints? 1. You have a bug in the browser cache. Try a different browser. 2. You can check also mailmanweb logs for clues?? -- 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]

3 years, 1 month

Re: howto reallow a banned email ?

by Mark Sapiro

On 6/18/19 9:12 PM, Nicolas Pettiaux wrote: > > By mistake a user has been banned to post to mailman list. How can I > allow him not only to post but also to become a member of a list ? > > I have not found any info on the web, or I have been unable to search > correctly. Do you have the Postorius web UI in your installation? If so go to the list's Ban List and remove the unwanted entry. Or is this perhaps a Mailman 2 question? If so you'll find the ban_list in the web admin UI at Privacy options... -> Subscription rules. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

Re: Another set of new releases

by Abhilash Raj

On Sat, Jan 18, 2020, at 6:18 AM, Torge Riedel wrote: > Am 13.01.20 um 03:42 schrieb Abhilash Raj: > > - Django-mailman3 1.3.2 > > Hi, > > are there somewhere release notes for Django-mailman3? Unfortunately, no. I've been meaning to create one, but mostly it is an internal library and any user facing changes are documented in the changelog for Postorius and Hyperkitty. If you look at the commits[1] since last release, there wasn't much changed except for new translations. https://gitlab.com/mailman/django-mailman3/compare/1.3.1...1.3.2 > > Thanks for your work and regards > Torge > _______________________________________________ > 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)

6 years, 6 months

Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Andrew Hodgson

Mark London wrote: >I added some email addresses manually to a mailing list and then removed them. But now I can't find how to totally remove them from mailman3. They show up in the Users list. You may find this script useful: https://www.msapiro.net/scripts/clean_users.py I have it running in a cronjob. Thread discussing the script can be found here: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… TLDR you end up with orphaned Django users both from when users subscribe/unsubscribe and due to spam signups using the Postorius form which never get confirmed. Thanks. Andrew.

3 years, 3 months

Re: How to authorise members visibility?

by Mark Sapiro

On 5/25/22 02:50, Pierre Malard via Mailman-users wrote: > Hello, > > My setup: > - Debian 11 > - Mailman3-full v 3.3.3-1 > > My Question: > How to configure the visibility of a list of subscribers to a list? > > I created a list and set "subscriber visibility" to subscribers only. When I log in as such and try to view the list information, I can't see anywhere how to display that list. > It's the same regardless of the setting used for this "subscriber visibility" field (only moderators, only subscribers or anyone). This is a bug in Postorius. See https://gitlab.com/mailman/postorius/-/issues/369 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

Re: Unable to remove non-member

by Mark Sapiro

On 9/28/20 6:43 AM, Brian Carpenter wrote: > Hi Everyone, > > I ran across a strange issue today. A client reported the inability to > remove a non-member in the following format: > > z_email/domain.org.za(a)domain.org.za > > The reported error from Postorius was: > > "The user could not be removed" Is that all it said? The code says it is The user could not be removed: <error message> Where <error message> is the relevant HTTP error. > I used https://verifalia.com/validate-email to validate the email > address and it is syntactically correct. Mailman core thinks it's OK too as does RFC5322. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Re: Help needed to create filters that were working in Mailman 2.

by Mark Sapiro

On 6/21/23 11:36 AM, mrl(a)psfc.mit.edu wrote: > I'm using version 1.3.8 Which I installed on Ubuntu 22 on April 18. I'm guessing this feature was installed in 1.3.9? The attached screenshot (which may not make it to the list but should be in your direct copy) is from Postorius 1.3.8 installed via pip. If you don't see this, possibly you have installed the Debian/Ubuntu package and this is a Debian issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Screen Shot 2023-06-21 at 1.07.49 PM.png

3 years, 1 month

Mailman-users search results for query "Postorius"