Search results for "Postorius" - Mailman-users

Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

I don't think this reply got to the mailing list, so I am sending it again, sorry if its a duplicate. On Sat, 13 Mar 2021 00:33:58 -0500, Mark Sapiro wrote: > > On 3/12/21 7:36 PM, John Covici wrote: > > Hi. I am having a great deal of difficulty installing mailman3 using > > gentoo and sendmail. Also, I want to upgrade my old mailman2 data to > > mailman3. > > > > What I have done so far is to install the mailman3 packages from my > > repository and got this: > > django-mailman3 version 1.3.4, mailmanclient version 3.3.1, mailman > > version 3.3.2 (apparently the core), postorius version 1.3.3 and > > hyperkitty version 1.3.3. I also have mariadb and postgresql already installed. > > > Are these gentoo packages? If so, I have no idea how they are > configured. Anyway I can tell, there was no configuration (we call them use flags) they just seemed to install the files in what seems to be the correct places. > > > > Now trying to read your documentation, it seems it wants me to > > reinstall some packages using pip in the home directory of the mailman > > user in a python virtual environment, that was the first thing. But I > > would like to avoid multiple package managers wherever possible -- > > gentoo is already a lot of maintainance without dealing with pip's > > maintainance. The binaries also seem to be different from my gentoo packages. > > > Our documantation generally covers installing from source. If you are > installing gentoo packages, you should be looking at gentoo docs and > going to gentoo for help. > > We recommend installing Mailman and the web components in a virtualenv, > but it is not a requirement. We also suggest that postgresql is a better > choice than MariaDB. > I sort of am installing from source, gentoo installs from source. No one on the gentoo users mailing list seems to be able to help me, except to tell me to use a different mailing list mechanism called mlmmj. > > > So, how do I proceed with getting mailman3 up and working, configuring > > the database, configs, etc and I guess after doing that upgrading > > mailman2 and getting sendmail to interface properly with mailman3? > > Importing lists from Mailman 2 is done with the `mailman import21` > command. See > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>. > Importing archives is done with the Django management > `hyperkitty_import` command. See > <https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#import…> > > For sendmail, see > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> Thanks. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 3 months

Re: Problems with New MM3 Installation

by Mark Sapiro

On 5/11/21 7:46 PM, Jeff wrote: > > I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: > > 1) some emails that arrived before I got the archive working are still sitting in: > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new > > Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a collection of messages in maildir format. This is how the prototype archiver stores messages. This has nothing to do with HyperKitty. It is a separate archiver. If you don't want messages to be stored there, you can disable the prototype archiver for the list by unchecking prototype in Postorius -> Settings -> Archiving -> Active archivers or disable it entirely for the installation by setting ``` [archiver.prototype] enable: no ``` in mailman.cfg > 2) Some messages that arrived while I was having other problems with the setup have been stored in: > > /usr/local/mailman3/mm/var/queue/shunt > > What should I do to get these messages processed? Assuming the issues that caused them to be shunted have been fixed, just run the command ``` mailman unshunt ``` > 3) Similar to above, some messages are in: > > /usr/local/mailman3/mm/var/queue/bad > > How can I get these messages processed? First examine the messages with ``` mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> ``` To be sure you want them. Also examine mailman.log for the times they were stored in the `bad` queue. You are looking for 'Skipping and preserving unparseable message: <file>' and/or 'SHUNTING FAILED, preserving original entry: <file> messages and you want to determine which runner preserved the message. There may be a 'whichq' entry in the message's metadata in which case, that's the answer. Once you have determined the queue, you can just move the .psv file from the bad queue to the appropriate queue, renaming it from .psv to .pck in the process. > 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? I know little about uwsgi. setting it to `uwsgi://localhost:8000` might work. You could also set it to the base URL that a user would use to access the web UI, e.g. `https://example.com` and that would presumably be proxied to uwsgi. For example, on the server for this list we have ``` POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' ``` which gets proxied to gunicorn, but the idea is the same. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Re: Mailman core: basic internationalization howto?

by thor.rustad＠gmail.com

I made it work, sort of, after creating the directory structure templates/site/no and put the templates inside the 'no' folder. However, I can't make it work without setting the language manually for each list first. New lists are created with English as their language, breaking the creation of welcome mail. Also, I can not add members to the lists from Postorius. I want all new lists to use utf-8 without having to use mailman shell. How can it be done?

7 years, 8 months

mail host choices when creating a new list

by Andrew Hodder

Hi! So, I'm trying to create a new list and pick one of the other mail domains we have configured (from the django admin panel), yet in the "Create New List" page in postorius, I see only a single option (the first domain we'd added/set as the default) in the drop-down under "Mail Host". Am I missing somewhere else I need to add alternative mail domains to? Thanks in advance! Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541

7 years, 7 months

Unknown attribute: max_message_size

by Thor Atle Rustad

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. What to do? I have Maxking mailman-docker but can easily copy files into the image if necessary. Thor

7 years, 6 months

Re: confirm-email: error NoReverseMatc

by Peter Münster

On Wed, Jan 31 2018, Simon Hanna wrote: >> LOGIN_REDIRECT_URL = '' > > I guess that's the issue. Try using something else for LOGIN_REDIRECT_URL Indeed, you're right, thank you! > It should either be a valid path so "/postorius/" for instance > or a valid view name like "list_index" '/' works well for me. -- Peter

7 years, 4 months

Re: list of subscribers

by Mark Sapiro

On 02/02/2018 01:24 PM, Peter Münster wrote: > > Where on the web interface is it possible to see the list of subscribers > of a mailing list please? Since this is a Mailman 3 list I assume you're asking about Mailman 3/Postorius. The short answer is it's a tab on the list's settings page, but you have to be a list or site admin to even see the tab. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

Re: list of subscribers

by Mark Sapiro

On 02/02/2018 02:50 PM, Peter Münster wrote: > > Yes, the question is rather: where can *normal* members (or moderators) > can see the subscriber list? Currently, they can't. If you think they should be able to, you can file an issue at <https://gitlab.com/mailman/postorius/issues/new>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

Re: list of subscribers

by Peter Münster

On Fri, Feb 02 2018, Mark Sapiro wrote: >> Yes, the question is rather: where can *normal* members (or moderators) >> can see the subscriber list? > > Currently, they can't. If you think they should be able to, you can file > an issue at <https://gitlab.com/mailman/postorius/issues/new>. Thanks. Done. It seems, that even the owner of the list cannot get the full names of the subscribers, only the email addresses. Is there any other possibility for the owner (or the site admin) to get the subscriber list with full names (perhaps with some Python scripting)? TIA for any help, -- Peter

7 years, 4 months

Mailman 3 Installation Assistance

by brian＠emwd.com

I am making a serious attempt at installing Mailman 3 using docker. I have a CentOS 7 server setup via Linode. I am using the following documentation to setup a Mailman 3 server: https://xiaoxing.us/2018/01/02/Deploy-Mailman-3-on-AWS-using-Docker/ I have Docker, Postfix, and Nginx installed and working fine. The installation of the Mailman 3 container went fine. However I am getting the following error when I go to test Posterius via shell: curl http://172.19.199.3:8000/postorius/lists/ curl: (7) Failed connect to 172.19.199.3:8000; Connection refused I assume this has something to do with uwsgi which I have no experience with. Appreciate any assistance with getting Mailman 3 up and running. Thanks! Brian Carpenter

7 years, 2 months

Mailman-users search results for query "Postorius"