Search results for "Postorius" - Mailman-users

Re: Docker mailman3 delete social logins, did something change?

by bob B

Got, Per someones advice I waiting and the bad gateway error cleared. I was being impatient. But I looked at the variables using (docker exec -it mailman-web python3 manage.py print_settings) and INSTALLED_APPS = ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google'] so in /opt/mailman/web/settings_local.py. I added a modified version INSTALLED_APPS = ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount'] And the social are gone!!!!!!!

3 years, 11 months

Re: Digest Formatting

by mailman＠manygoodideas.com

mailman＠manygoodideas.com wrote: > I have 2 more digest questions, which I'm hoping to get insight on: > 1) Is there a way to trigger a digest for a user (for testing purposes)? Specifically, > is there a function that can be revealed via the REST api to an interface like Postorius > and Affinity? > 2) I have customized list:member:digest:header, but am not seeing the custom text where > I thought it should be. The documentation seems to imply that both > list:member:digest:header and list:member:digest:footer surround each message in the > digest, with the digest starting with list:member:digest:masthead. What I'm seeing is > list:member:digest:masthead, which is followed by list:member:digest:header, then the TOC, > then all the digest entries. I also have a feature request (I didn't see it in the docs), consider creating list:member:digest:mastfoot – a chunk of text that could be at the end of the digest. Thanks.

4 years, 9 months

Re: Welcome Message

by Abhilash Raj

On Tue, Apr 16, 2019, at 7:40 AM, brian(a)emwd.com wrote: > So I create a template with just one line of text and I save it. When I > go subscribe to the list, Postorius throws this error message: > > "A server error occurred. Please contact the administrator." > > The core mailman.log records a whole bunch of exemptions: > <snip> > requests.exceptions.ReadTimeout: HTTPConnectionPool(host='mailman-web', > port=8000): Read timed out. (read timeout=5) > > Removing the template allows normal subscriptions and the generic > welcome message is sent out. > How are you deploying your images? With the default compose file provided with the images, `mailman-web` container should be reachable from `mailman-core` container at "http://mailman-web:8000". If that does not work, there is something wrong in how you are deploying the images. You can set an environment variable to wherever Django from Mailman-web container is listening at " POSTORIUS_TEMPLATE_BASE_URL=http://IP:port" -- thanks, Abhilash Raj (maxking)

6 years, 4 months

Re: footer template priority

by Mark Sapiro

On 6/19/25 15:42, Sam Darwin via Mailman-users wrote: > It takes time to figure out a new feature. I see what is happening. :-) Or, merely one step further. > > After a template is stored in the DB you can remove POSTORIUS_TEMPLATE_BASE_URL because the value is cached in the DB. That explains the caching. > > Next, without POSTORIUS_TEMPLATE_BASE_URL, it assumes http://localhost:8000/mailman3/ . On our server this is not correct, because it's listening on a unix socket, as well as 80 and 443, but not 8000. Actually, it assumes whatever the default is which might be `http://localhost:8000`. See https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/settings/m…. It's Postorius that adds the /mailman3/... when setting the template table entry. If that is not correct for your server, you need to set the correct value in settings.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

Re: list footer web customization procedure

by Mark Sapiro

On 11/29/21 8:13 PM, Philippe B wrote: > I am new to Mailman 3 and I've been reading all the documentation that I could find, but I haven't been able to figure out how a list owner can use the web interface to customize the footer that appears at the end of each e-mail from the list. > > We're actually after something much simpler (in theory), which is to eliminate the built-in footer altogether for some of our lists. > > Could someone share the instructions for doing that? Thanks. In Postorius go to the Templates tab for the list, click New Template, then in the Name dropdown select [list:member:regular:footer], leave the Data box empty and Save. Do the same for [list:member:digest:footer] if you want to eliminate that one too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Do not display any lists on index the page (/postorius/lists/) by default (when you create the list it defaults to Hide) - Debian package install

by daniel.botting＠codethink.co.uk

Hi all, I am currently in the process of moving from mailman 2.1 to mailman 3, the basic functions are completed (mailing list and archiving). On our current mailman 2.1 install it advises there are no publicly advertised lists, when I visit mailman3-list.domain/postorius/lists/ I see all the lists that have been created, I require them not to be displayed. I know when you create a list you can on the 'Advertise this list' line select 'Hide this list in list index', but I would like it to default to this in case somebody forgets to select it. I am not a Python expert, though from the description at the top of the below file and the contents further down it looks like you are defining in base.py and then in default.py you are using what was defined, a class of 'Private' which should cause the lists not to be advertised, but they are? File: /usr/ib/python3/dist-packages/mailman/styles/base.py class Private: """Settings for private mailing lists.""" def apply(self, mailing_list): mlist = mailing_list mlist.advertised = False <-------------- mlist.archive_policy = ArchivePolicy.private mlist.subscription_policy = SubscriptionPolicy.confirm_then_moderate File: /usr/lib/python3/dist-packages/mailman/styles/default.py class PrivateDefaultStyle( Identity, BasicOperation, Bounces, Private, Discussion, Moderation): """Style for mailing-lists with private archives.""" name = 'private-default' description = _('Discussion mailing list style with private archives.') def apply(self, mailing_list): """See `IStyle`.""" Identity.apply(self, mailing_list) BasicOperation.apply(self, mailing_list) Bounces.apply(self, mailing_list) Private.apply(self, mailing_list) Discussion.apply(self, mailing_list) Moderation.apply(self, mailing_list) I added the below to /etc/mailman3/mailman.cfg: [styles] # The default style to apply if nothing else was requested. The value is the # name of an existing style. If no such style exists, no style will be # applied. default: private-default I took 'private-default' from /usr/lib/python3/dist-packages/mailman/styles/default.py, this means now when a new list is created the List style is 'Discussion mail list style with private archives so it is not displayed when you are logged out at /hyperkitty. Many thanks Daniel

2 years, 9 months

Re: Hyperkitty import from mailman2

by Sten Aus

Hi Thank you Mark and Simon for your input! I can see imported list from Hyperkitty GUI, but it's inactive. I can confirm that I can see those emails from command line (python shell shows Email Objects). Import shows everything is OK: # python2 manage.py hyperkitty_import --settings settings --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox Only emails after 2010-01-01 00:00:00+02:00 will be imported Importing from mbox file /tmp/test.mbox to test(a)list.domain.com /--some 22 emails being imported here --/ 22 emails read 22 email added to the database 22 emails are stored into the database Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index will be updated every minute. Run the 'manage.py runjob update_index' command to update it now. # python2 manage.py update_index --settings settings Indexing 50 emails NB! Only 6 of them are archived from new list (which has been created from Apache). I have imported 2 times 22 emails from /tmp/test.mbox file (to different lists). I am using Apache2.4 with mod wsgi and Postorius and Hyperkitty are in the same django application. Also tested with running server directly and then connecting to a port 8000, but I guess it does not matter, because both of them are using Python script. I have not yet managed to set up cron tasks, as this is relatively new installation, but I have ran them manually. Also, I have done update_index (runjob update_index and manage.py update_index, both ways). SQLite database shows emails, for example there's a thread FMXQVFDRQVRMINVXI4DJB4SHYTJ3EPWP, but If I insert it to web URL I get Django error: No Thread matches the given query. As Postorius and Hyperkitty are in the same Django, they share sqlite database (mailman/web/database.db). Mailman has it's own database in mailman/var/data/mailman.db. Happy holidays Sten On 22/12/2017 21:09, Simon Hanna wrote: > On 12/22/2017 03:39 PM, Sten Aus wrote: >> Hi >> >> I have installed mailman3 - it looks very great! >> >> Now I wanted to try import from mailman2 mbox, so i did: >> >> python2 manage.py hyperkitty_import --settings settings >> --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com >> /tmp/test.mbox >> >> It shows that it have sucessfully imported all emails and I can see >> them from database (sqlite3), but I cannot see them from GUI >> (hyperkitty). Only thing I can see is this inactive "test" list. >> > How did you try to access them using Hyperkitty? Can you try doing > that while logged in as a django superuser? Could you try using a > permalink for a message? If you can access the files from the database > you should be able to construct the urls using the list name and the > message_id_hash of a message. You should try this using DEBUG=True in > the settings.py. The URL would be similar to > http://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/… > > > Another option would be to check if you can access the data using a > python shell. > > `python manage.py shell` to open a python shell preconfigured for > Hyperkitty and then input the following two lines: > > from hyperkitty.models.email import Email > Email.objects.all() > > > This should print out all the messages that are stored in the > database. (You can limit them by appending "[10:]", or any other > python slice) > > What do you see in the UI? Is it somewhat similar to > http://lists.mailman3.org/archives/list/mailman-users@mailman3.org ? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 7 months

Re: how do I bulk-remove users from ML in MM3?

by Simon Hanna

Postorius is currently using this to mass unsubscribe. AFAIK there is an open issue in core to add such functionality On October 25, 2017 5:59:46 PM GMT+02:00, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >On 10/25/2017 07:35 AM, Barry Warsaw wrote: >> On Oct 25, 2017, at 03:08, Dmitry Makovey <dmakovey(a)stanford.edu> >wrote: >>> >>> I just realized that "mailman members" only offers to "add members" >via >>> "-a filename" but I see no remove option. >> >> It’s true, `mailman members` doesn’t currently have a —remove option. > >I found Rest API call for single user removal but I am questioning it's >effectiveness given that I need to use this operation to potentially >remove 1500 members > >-- >Sr System and DevOps Engineer SoM IRT -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

7 years, 9 months

Re: Unknown attribute: max_message_size

by Abhilash Raj

Hi Thor, On Wed, Dec 6, 2017, at 02:40 AM, Thor Atle Rustad wrote: > If I make changes here: > https://example.com/postorius/lists/test2.example.com/settings/message_acce…, > I get a warning that the Maximum Message Size field at the bottom is > mandatory. However, if I put a number in that field and save, I get > "Unknown attribute: max_message_size". That makes sense, since Mark > states > in > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > that max_messages_size is not exposed in REST. I have opened a new issue for this, turns out this was fixed but isn't a part of the 3.1.1 bugfix release of COre. https://gitlab.com/mailman/postorius/issues/246 > What to do? > > I have Maxking mailman-docker but can easily copy files into the image if > necessary. > > Thor > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

7 years, 8 months

Re: Mailman3 on Debian 10

by Mark Sapiro

On 1/30/20 8:24 AM, Bala Mutyam wrote: > Hi Mark, > > Thanks for the update and I managed to resolve the errors on the UI. > > I have 2 more questions about the mailman3. > > 1) how to create Mailing Lists? You can create lists with the `mailman create` command lint tool or via Postorius as a superuser. > 2) super user login is not working even with correct login credentials and giving me - The username and/or password you specified are not correct. How did you create the super user? You should do it with the django admin createsuperuser command. > 3) Password Reset Email urls and email confirmation web pages giving me - This site can't be reached error. If this is an error from your browser, there is something wrong with the host portion of the URL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Mailman-users search results for query "Postorius"