Search results for "Postorius" - Mailman-users

Re: Importing config and archives only partially succeeded?

by Eric Broens

Thanks for your prompt reply.To import the config and archives I ran the commands as outlined in Migrating from Mailman 2.1 to Mailman 3 — Mailman Suite 3.3 documentation : mailman import21 foo-list(a)example.com /path/to/mailman2/foo-list/config.pck python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox After running these commands the archives became available for most of the mailinglists. I didn't run the Django admin command with arguments "update_index_one_list" to build the indices for each mailinglist seperately. After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. Best regards,Eric On Sunday, December 13, 2020, 12:12:46 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 2:33 PM, Eric Broens via Mailman-users wrote: > Today I have migrated about 30 mailinglists from mailman 2.1 to mailman 3.3.2 & Hyperkitty 1.3.3. > Although no error responses were given when importing the 2.1 pck files, and neither for importing the archives, for about half of the mailinglists the hyperkitty webpage doesn't show any subscribers, nor archived emails. > The imported members and other settings are correctly shown in the postorius page. > Is there anything that I can verify why the archive is not shown on the hyperkitty page?The hyperkitty_email database table does contain the emails. Did you specify --no-sync-mailman when you ran hyperkitty_import? If so did you run the django sync_mailman job when you finished importing? -- 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/

3 years, 11 months

Re: Setting for archiving multi email domains?

by Duane Raymond

Thanks! So - I've documented what I did below. Now that I am getting bouces, I got an email that said "The response from the remote server was: 550 5.1.1 <test(a)emaildomainA.com>: Recipient address rejected: User unknown in virtual alias table" Specifically to some ot the questions above: > What do you mean by "set"? That the list has archiving enabled? Yes. I meant that archiving had been enabled for the test(a)emaildomainA.com test list. Shunting error: I think the shunting error is a distraction if it is caused by not having a recipient. Early tests to the test list had me as an administrator, but not as a member - so this would have caused that. Once I added myself (before I sent the original message in this thread), the result (not sending the message to the list using a 'virtual' domain and not archiving it) continued. Virtual Domains: So based on the Postfix virtual domain documentation and the Mailman3 specific "Unusual Postfix configuration' section, I added the following to my postfix main.cf file: virtual_alias_domains = emaillistA.com emaillistB.com virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap and removed those domains from the 'mydestination' setting. I then created the postfix_vmap file and added to it: emaillistA.com DOMAIN # emaillistB.com DOMAIN ...then ran postmap with the path and reloaded postfix. On testing I also noticed that a previous counce was to emaildomainC.com - an alias for emaildomainA.com I had originally setup in the Postorius domain setup and then removed. I guessed that it was still in the postfix config, so I double checked in the MM generated postfix_domains file and ran postmap /path-to/postfix_domains and reloaded postfix again...and sent another test message.... This then generated the error email at the top from my email client (gmail). ...but the end result is no email sent and thus the reason there is no archive.... Any further suggestions? I can supply other log messages and configuration options if it helps. Duane

3 years, 8 months

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

by Stephen J. Turnbull

Wikinaut writes: > I fully understand. Need to look up how to smoothly backup the > mailman3 settings and list databases in order to make that move > with losing stuff... (kinda "mailman3 backup all" and mailman3 > restore all" :-) One piece of generic Python advice: don't mix OS packages and pip (except for Python itself). Always use a venv if you need to use pip for packages that aren't in your OS distro. (Of course it's possible to do so in many cases if you *really* know what you're doing, but it's almost never worth the pain.) All of the site configuration data should be in /etc/mailman3 (except for a few template files in $var_dir/templates), and all of the domain, list configuration, and archive data is in the RDBMS (usually PostgreSQL or MySQL). The RDMBS should be backed up regularly according to its procedures, but that's completely out of scope for Mailman.[1] The RDBMS should "just work" with exactly the same Mailman-side configuration as Debian.[2] As I think Odhiambo mentioned, the Mailman side of the site configuration also does not change (for example, the RDBMS URL and authentication). What you do want to change is the file system configuration. Except for /etc/mailman3, it should be completely different -- as with pip'ing packages, you don't want to share files across a local venv and the OS version of the same package. It just leads to pain. I think among the developers the preferred root = /opt/mailman (or /opt/mailman3) for Mailman's directory hierarchy. This will be populated with subdirectories when you run `mailman info` (or start Mailman) the first time. The directories relevant to configuration are all under $root/var, and you inform Mailman about this by setting `var_dir` in mailman.cfg. If there are other file and directory configurations in mailman.cfg, they need to changed from the Debian values (probably /var/lib/mailman3/...). You may do fine by simply deleting all other directory configurations and let Mailman decide where to put them relative to the `var_dir`, You will need to fix the setting for STATIC_ROOT (I think that's the name, if not search for "static") in settings.py, and maybe in mailman-web.cfg. While it's not necessary (and may be a little inconvenient), I recommend changing the root for Mailman's log files from the Debian value (probably /var/log/mailman3) to the Mailman default of $root/var/logs, and similarly for the Django logs in settings.py. Non-Mailman settings I think you will need to change the settings for your MTA (usually Postfix or Exim4) so that it will recognize Mailman lists and route them to Mailman correctly. There will probably be mailman-related files in /etc/$MTA/conf.d (or something like that). You can edit them directly, but I recommend changing the name (paranoia so that dpkg doesn't overwrite them). The only thing I can think of for the webserver (Apache?) is the location of the static directory. I think Debian uses uwsgi by default so you may need to adjust its configuration too. I think you need to fix logrotate's configuration in /etc/logrotate.d. Not sure how many mailman-related config files are in there. I think you mentioned systemd .service files. If so that doesn't make sense to me -- Debian should provide those. You need to make sure those are disabled or deleted so that Debian Mailman services don't start on reboot. This is automatic if you delete the Debian packages, of course, but not for any files you created yourself. Probably the Debian .service files will work, but you need to make sure they refer to the venv Mailman (using the full path to the `mailman` utility in the venv's bin directory will work, and similarly for `mailman-web`). systemd does not configure the /opt hierarchy in it search path by default. I put the mailman, qcluster, and gunicorn (if you use that instead of uwsgi) .service files in /usr/local/lib/systemd/system, and that works for me. Flotsam and jetsam If you have run Mailman with any success at all, you may find some stuff in Debian's $var_dir/queue/* directories or in its $var_dir/lists/* directories. The queue/* directories contain incoming messages at various stages of processing, and the lists/* directories contain files containing multiple messages that are scheduled to be sent out as digests. You can read the queue files with `mailman qfile /path/to/queue/file.pck`, and the digests are just text files. That way you can check if there's anything important in them. If not, you can just delete them. If there is, you can just copy them to the same place in the venv $var_dir as they were in Debian's $var_dir, but you may want to ask here first before doing that. It's best to let Mailman run until all the queues are cleared (except maybe bad and shunt, but if those have any files in them you need to intervene anyway). Afterword I'm sure this sounds complicated, but in fact it's a pretty short list. When you get there we'll help you. Footnotes: [1] But not for this list. You may as well ask here, somebody probably will tell you the basics quickly. But for troubleshooting, go the the RDBMS's own channels. [2] In fact, it is possible to keep the Debian installation, copy the the mailman.cfg somewhere, edit it, stop Debian Mailman, and start up the venv Mailman. I don't recommend this -- the point is that the venv and the databases are that isolated from the rest of the system.

1 year, 1 month

Re: Template path

by Seth Seeger

> On Sep 19, 2020, at 3:02 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > Are you using the provided docker-compose file or are you using something else like Kubernetes to deploy the container images? I am using the provided docker-compose file. > It seems like your mailman-core container isn't able to talk to Postorius on the default dns name, mailman-web, in the provided docker-compose file. These dns names are setup by default if you are using the docker-compose.yaml provided with the repo, but would otherwise needs either changing the value of POSTORIUS_TEMPLATES_BASE_URL or manually setting up the mailman-web DNS in the `/etc/host` of the mailman-core container. Telnet isn’t included in the container, so I tested with curl: $ sudo docker exec -it -u mailman mailman-core bash bash-5.0$ grep mailman-web /etc/hosts bash-5.0$ curl http://mailman-web:8000 bash-5.0$ mailman-web does not seem to be in /etc/hosts of mailman-core, but it does resolve and port 8000 is reachable. (I tested with a bad hostname and a different port and did get error messages.) Is there a URL I can pull that will show that it’s working properly? My original (slightly censored) docker-compose.yaml file is below. Thanks, Seth version: '2' services: mailman-core: image: maxking/mailman-core:latest container_name: mailman-core hostname: mailman-core restart: always volumes: - /opt/mailman/core:/opt/mailman/ #stop_grace_period: 30s links: - database:database depends_on: - database environment: - DATABASE_URL=postgres://xxx:xxx@database/mailmandb - DATABASE_TYPE=postgres - DATABASE_CLASS=mailman.database.postgresql.PostgreSQLDatabase - HYPERKITTY_API_KEY=xxxxxx networks: mailman: ipv4_address: 172.19.199.2 mailman-web: image: maxking/mailman-web:latest container_name: mailman-web hostname: mailman-web restart: always depends_on: - database links: - mailman-core:mailman-core - database:database volumes: - /opt/mailman/web:/opt/mailman-web-data environment: - DATABASE_TYPE=postgres - DATABASE_URL=postgres://xxx:xxx@database/mailmandb - HYPERKITTY_API_KEY=xxxx - SERVE_FROM_DOMAIN=lists.example.com - DJANGO_ALLOWED_HOSTS=lists.example2.com - MAILMAN_ADMIN_USER=xxx - MAILMAN_ADMIN_EMAIL=xxx@xxxx - SECRET_KEY=xxxxxx networks: mailman: ipv4_address: 172.19.199.3 database: environment: POSTGRES_DB: mailmandb POSTGRES_USER: xxx POSTGRES_PASSWORD: xxx restart: always image: postgres:9.6-alpine volumes: - /opt/mailman/database:/var/lib/postgresql/data networks: mailman: ipv4_address: 172.19.199.4 networks: mailman: driver: bridge ipam: driver: default config: - subnet: 172.19.199.0/24

4 years, 2 months

Re: getting all registered users and their lists

by Mark Sapiro

On 1/26/22 00:16, IOhannes m zmoelnig wrote: > > hi, > > TL;DR > is there a scriptable way to get all users that have registered in my > mailman3 (3.2.1) instance and which lists they are subscribed to (if any)? It's in Postorius >= 1.3.6 > longer version: > > we are running Mailman3-3.2.1 as shipped with Debian/buster (i know that > this is not the newest version; at this point, please refrain from > asking me to upgrade my Debian installation or even to switch to a venv > installation of mailman3: i'll eventually do that but right now i've gt > a problem to solve :-)) See above. ... > for this i would like to get a listing of all users that are not > subscribed to any mailinglist. > i would also like to query, when a given user has signed up (so i can > reduce the number of false positives) > > how would i do that? > ideally i would rather not work on an SQL level. You can do this in mailman shell ``` $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> um = getUtility(IUserManager) >>> for usr in um.users: ... if len(list(usr.memberships.members)) > 0: ... continue ... adr = usr.addresses[0] ... print(f'Name: {adr.display_name}, Email: {adr.email}, Created: {usr.created_on}') ... ``` Or to skip older ones ``` >>> from datetime import datetime >>> um = getUtility(IUserManager) >>> for usr in um.users: ... if len(list(usr.memberships.members)) > 0: ... continue ... if usr.created_on < datetime(2022, 1, 1): ... continue ... adr = usr.addresses[0] ... print(f'Name: {adr.display_name}, Email: {adr.email}, Created: {usr.created_on}') ... ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

Re: Programmatic Creation of Users

by Mark Sapiro

On 7/30/22 05:25, jciesla(a)techsupportme.com wrote: > > After a lot of research I now understand that what I am doing in the Core Shell is creating a User entity which has one or more email addresses as well as one or more roles and preferences that exist at the global level. This user entity can Subscribe to zero or more lists. If I am incorrect in the summation please let me know! Almost correct. A User does have preferences but does not have roles. Roles are associated with list memberships, not users. > Assuming that the previous information is correct that brings us to my current dilemma. Specifically, the User entity can Subscribe and interact with lists using the email commands, but they can't Login using the Postorius web interface. If I understand correctly the reason that they can't login is that the underlying Django system does not recognize their account because the account that was created in Core isn't accessible by Django. Instead the user needs to create a Django-specific account at which point the information from Core becomes available in the user's web UI. The simple view is that Django users and Mailman Users are unrelated. Either can exist without the other. They only tie together if they have the same email address. That is the only connection between them. > If that is in fact accurate then I want to take the next logical leap: is it possible to programmatically create an account in Django that is tied to the account that was created in Core? See the script at https://www.msapiro.net/scripts/clean_users.py. This is an example that deals with Django users and Mailman Users and deletes some Django users. See https://docs.djangoproject.com/en/4.0/topics/db/queries/#creating-objects for information about creating objects. Also see the UserManager class in django/contrib/auth/models.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

Re: Add domain to Mailman, can't create list with that new domain

by Odhiambo Washington

On Thu, Oct 17, 2024 at 5:32 PM Andy Matthews <andy.matthews(a)zaxiom.com> wrote: > I'm testing locally to try and support additional domains. > > I can add new mailing lists with a domain: announce-123(a)mydomain.com > I can't add a new mailing list with an alternate domain: > announce-123(a)testing.com > > Following the documentation for domains I'm able to successfully add the > new domain (locally) with the following steps: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… > > 1. Shell into the mailman server > 2. Shell into the mailman Python environment: mailman shell > 3. Add a new mailing list. > from mailman.interfaces.domain import IDomainManager > from zope.component import getUtility > manager = getUtility(IDomainManager) > manager.add('testing.com') > show_domains() # with method from the above documentation URL > <Domain testing.com> > <Domain mydomain.com> > > But then when I run a cURL command (from the mailman server) to add a list > with that new domain I get an error: > $ curl -k -u restadmin:restpass -X POST -H "Content-Type: > application/json" --data '{"fqdn_listname": "new-list(a)testing.com"}' > https://0.0.0.0:8001/3.1/lists > {"title": "400 Bad Request", "description": "Domain does not exist: > testing.com"} > > Am I doing something wrong, or missing a step? If not, how do I add > support for additional domains such that I can provide mailing list support > for that domain? > I am not sure I understand your question. Do you use Postorius and you can't add new domains from there? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 month, 1 week

Affinity Mailman Is Now Beta

by Brian Carpenter

Dear Mailman Admins and Users, Affinity Mailman is our new admin interface for Mailman 3 and we intend to use it to replace Postorius. It has been under development for about 3 months now and it recently reached beta. Calling For Beta Testers Now that Affinity is in beta, we are looking for list admins to help us beta test it. We are interested in getting some feedback and feature requests from beta users. If you are interested in helping us test out Affinity and get a sneak peek of the future of Mailman administration, then email me at brian_carpenter(a)emwd.com <mailto:brian_carpenter@emwd.com?subject=Affinity%20Beta&body=I%20am%20interested%20in%20Beta%20Testing%20Affinity> and I will begin the process of setting you up with an Affinity Mailman admin account and provide 2 test lists to use for beta testing purposes. While I am at it: Empathy Is Now Under Development "So what in the world is Empathy? I mean really - first Affinity and now Empathy?" That is correct. We figured if we are going to replace the default admin UI (Postorius) for Mailman 3, we might as well replace the default forum/archive UI (Hyperkitty) for Mailman 3. With Empathy, we are bringing a beautiful and user-friendly experience for those who wish to use Mailman 3 as a modern forum. We want Empathy to bring a true community like approach to the use of Mailman 3 via a browser. It will supplement the mailing list feature of Mailman 3 with an easy to use online forum. So Mailman 3 users will get the best of both worlds: a modern mailing list app AND a modern forum app. Empathy can also be used to display your list threads (archives) in an easy-to-read manner, and those threads can be categorized by tags and will be searchable. -- 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/

4 years, 5 months

Re: Congrats on the instructions for installation on ubuntu, what about migration?

by Bill Oliver

Thanks. I'll think on that. My tables have a different prefix, so I'll have to remember where to change those config files... billo On Wed, 2024-10-09 at 13:18 -0700, Mark Sapiro wrote: > On 10/8/24 5:45 PM, Bill Oliver wrote: > > > > Is there a tutorial/instructions on migrating data from an old > > system > > to a new one? It's actually not the end of the world if I don't > > get > > all the old emails transferred, but I'd like to get the email > > addresses > > of the participants moved over easily... I believe that I set it > > up > > in 2020, but did not do any version upgrades since then... > > > There's no explicit doc, but there are some posts in the archives of > this list, e.g. > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/me > ssage/FTIC47FPQER5FLR4IW4CGI7JB6ALKIX4/>. > > The easiest scenario is if you want to migrate everything. You just > dump > the database on the old server and load it on the new one using the > database manager's tools. > > If you only want to move some, but not all lists, it's more > complicated, > but possibly the easiest thing is to migrate everything and then > delete > the unwanted lists and their archives from Postorius and HyperKitty. > > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to billo(a)billoblog.com

1 month, 2 weeks

Re: HyperKitty: Thread matching query does not exist

by C. R. Oldham

> Start by posting the traceback... Apologies...I know better. :-D Environment: Request Method: GET Request URL: https://listsredacted.invalid/hyperkitty/list/my-redacted-list@listsredacte… Django Version: 1.10 Python Version: 2.7.13 Installed Applications: ('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', 'paintstore', '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') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.auth.middleware.SessionAuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py" in inner 39. response = get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in _legacy_get_response 249. response = self._get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in _get_response 187. response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in _get_response 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python2.7/site-packages/hyperkitty/lib/view_helpers.py" in inner 136. return func(request, *args, **kwargs) File "/usr/local/lib/python2.7/site-packages/hyperkitty/views/mlist.py" in overview 128. threads = mlist.recent_threads File "/usr/local/lib/python2.7/site-packages/hyperkitty/models/mailinglist.py" in recent_threads 133. return self.cached_values["recent_threads"]() File "/usr/local/lib/python2.7/site-packages/hyperkitty/models/common.py" in __call__ 61. return self.get_or_set(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/hyperkitty/models/mailinglist.py" in get_or_set 271. return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/local/lib/python2.7/site-packages/django/db/models/manager.py" in manager_method 85. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py" in get 385. self.model._meta.object_name Exception Type: DoesNotExist at /hyperkitty/list/my-redacted-list(a)listsredacted.invalid/ Exception Value: Thread matching query does not exist.

7 years, 2 months

Mailman-users search results for query "Postorius"