Search results for "Postorius" - Mailman-users

Re: Exception with processing subscription confirmation email

by Mark Sapiro

On 4/29/21 7:56 AM, Eric Broens wrote: > Hi, > > A new user tried to subscribe to a mailinglist, received the confirmation > mail, and replied to it. > > The subscriber is however not subscribed and remains listed in the "pending > confirmation" list. > > The following exception appears in the error.log. > > Does anyone knows how to resolve this? In the past we didn't experience any > issues and no changes but security updates have been installed. > > Apr 29 16:15:55 2021 (1581) deque: do_confirm_verify > > Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 69, in __next__ > > return step() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 356, in _step_send_confirmation > > raise StopIteration > > StopIteration Tracebacks like the above are normal and probably shouldn't be logged at all. > Apr 29 16:16:28 2021 (1490) Uncaught runner exception: Expecting ':' > delimiter: line 1 column 256 (char 255) > > Apr 29 16:16:28 2021 (1490) Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration > > self._process_one_file(msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 266, in _process_one_file > > keepqueued = self._dispose(mlist, msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/runners/command.py" > , line 208, in _dispose > > mlist, msg, msgdata, parts, results) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/eml_confir > m.py", line 54, in process > > mlist).confirm(token) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 578, in confirm > > workflow.restore() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 146, in restore > > data = json.loads(state.data) > > File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads > > return _default_decoder.decode(s) > > File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode > > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > > File "/usr/lib64/python3.6/json/decoder.py", line 355, in raw_decode > > obj, end = self.scan_once(s, idx) > > json.decoder.JSONDecodeError: Expecting ':' delimiter: line 1 column 256 > (char 255) > > Apr 29 16:16:28 2021 (1490) SHUNTING: > 1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5 This one is the issue. There was some problem with the user's confirmation reply. View the shunted message with the command ``` mailman qfile path/to/var/queue/shunt/1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5.pck ``` although that probably won't show anything wrong as it appears that the issue is with the saved workflow. You can get the token from the shunted message and then look at the database with something like ``` SELECT data FROM workflowstate WHERE token = '<the token>' ``` but I suspect the issue is because the database is MySQL or MariaDB, your Mailman core is older than 3.3.3 and your database server mode is such that data too long for column results in truncation, and the data in this case is truncated to 255 bytes. In Mailman 3.3.3, this column was changed from VARCHAR(255) to VARCHAR(510) for MySQL. As far as subscribing the user is concerned, you can in Postorius view the subscriptions waiting user confirmation and delete this one and then `mass subscribe` the user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

Re: Confirm on mass subscription

by Mark Sapiro

On 7/5/17 1:48 PM, David Krantz wrote: > > Is there a way of requiring all mass subscribed users to confirm their > email adress? I have an use case where we have a current mail list but > when moving it to mailman I for different reasons would like to > confirm all subscribers. Some very shallow testing suggests that if I > just add them using mass subscribe, they will not have to confirm at > all. > > I have yet to upgrade to 3.1 but I will do so in due time. In MM 2.1, you just send the users invitations rather than subscribing them. In MM3/Postorius, this does not seem to be an option at present. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

Re: Try to Implement Template for The message sent to subscribers when a subscription confirmation is required

by Mark Sapiro

On 2/16/26 18:37, msok--- via Mailman-users wrote: > -The URL syntax > https://mailman.example.com/mailman3/lists/list-id/confirm/?token=$token > > -The error message when tried to add subscriber > HTTP Error 400: HTTPSConnectionPool(host='localhost', port=443): Max retries exceeded with url: /postorius/api/templates/list/list-id/list:user:action:subscribe (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1029)'))) What is your setting for POSTORIUS_TEMPLATE_BASE_URL? How is your Mailman installed? Did you follow <https://docs.mailman3.org/en/latest/install/virtualenv.html>, install packages or install some other way? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months

Re: MM3 Docker

by Abhilash Raj

On Tue, Jan 8, 2019, at 5:52 AM, Odhiambo Washington wrote: > On Tue, 8 Jan 2019 at 03:29, Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 1/7/19 1:18 AM, Odhiambo Washington wrote: > > > On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark(a)msapiro.net> wrote: > > >> > > >> Please help me understand what steps are missing and I will try to > > >> provide the information. > > > > > > > > > Okay. > > > > > > At the installation stage, you say the following: > > > "I already had some things set up in /opt/mailman including a git > > > subdirectory containing clones of the GitLab mailman, mailmanclient, > > > mailman-hyperkitty, hyperkitty, django-mailman3 and > > > postorius projects. On the third server I have added mailman-suite > > > because I use the settings.py from that project as the basis for mine." > > > > > > Please assume that the reader is a newbie to python3 virtualenv and give > > the > > > details of the commands they need to execute to (a) clone all the > > projects > > > needed > > > and (b) create the virtualenv. > > > > > > The next steps are: > > > mkdir /opt/mailman/mm > > > > > > Then you say "I then created a /opt/mailman/mm directory and within that > > a > > > Python 3.6 virtualenv" > > > What happens here is something that needs clarification, because you are > > > specific about "python3.6". > > > I have googled and realized that one has to be specific about the python > > > version they want to use in their virtualenv > > > as shown here -> > > > > > https://stackoverflow.com/questions/45293436/how-to-specify-python-version-… > > > > > > exact command to execute to create the /opt/mailman/mm/venv > > > exact command to execute to activate virtualenv > > > > > > I have added a comment to the page which I hope gives you what you want. > > > > I also added a section on templates instead of referring to a prior > > version of the page. > > > > That makes it better. > However, as a newbie, something is not yet clear: > > "When active in a particular shell, it can be deactivated with the command > > deactivate > or by exiting that shell." > > HI am trying to understand the effect of detaching from a venv. I am > assuming that a virtualenv is a container that is supposed to be always > active for the services within to be accessible. Is that right? So, how do > I ensure it's always running/up, or that does not matter as the scripts > which run the services will always refer to the files? virtualenv is not actually a container that is supposed to be active. It is merely a set of settings that are applied to your SHELL when you are in the virtual environment. It is not supposed to be always active, only when you actually want to run commands in that virtual environment. The services will keep on running after you deactivate your shell and would function like other normal services on your machine. -- thanks, Abhilash Raj (maxking)

7 years, 6 months

Re: Message Sent to A Re-Created List Results In Error

by matthew＠alberti.us

I checked all over the mailman core logs and couldn't find a problem. But then I noticed that the 550 error was coming from dovecot-lmtp. I should rename this thread because the actual problem seems to be unrelated to re-created lists. It seems like the actual problem seems to occur in the following situation: * Using Postfix * Using Dovecot * /etc/postfix/virtual includes addresses with same domain as mailman lists. * An e-mail address subscribed to a mailman list is in the /etc/postfix/virtual file as an alias (possibly also if destination address for an alias). * (Possibly related) E-mail address is also one of the list owners. In that environment, Postfix seems to check only 'virtual_transport' list, which in my case is dovecot-lmtp, and when it doesn't find the mailman listname@domain entry in there, it sends a 550 user unknown. It seems to be that it isn't getting passed to 'transport_maps', which is mailman-lmtp. When I remove that one address (that is in /etc/postfix/virtual) from the list of subscribers, I'm able to post again. Interestingly enough, when I put it back in as a subscriber. I'm still able to post. So it seems unsubscribing and re-subscribing that address fixed it, or adding an additional list owner and deleting it fixed it, or some combination of those. I know this might be shaping up to be a very unlikely scenario. But basically the account is mine, an admin, doing testing before/after a deployment.. I'll try to create a few test procedures to document the method to reproduce the problem, and also hopefully fix it. If I can do that, I'll open another thread. This could also be a postfix config error of some kind, which is definitely possible if not likely. Thanks for reading. - Matt Alberti -----Original Message----- From: Abhilash Raj <maxking(a)asynchronous.in> Sent: Monday, December 14, 2020 11:42 PM To: matthew(a)alberti.us; Mailman users <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Message Sent to A Re-Created List Results In Error On Tue, Dec 15, 2020, at 10:00 AM, matthew(a)alberti.us <mailto:matthew@alberti.us> wrote: > I created a list in the Postorius interface, used it, and then deleted > it. A week or so later, I re-created the list, and things were fine > thru the creation and subscription process. But when I sent a message > to the list, a > "550 user unknown" error was sent back. Can you share more error details from the Mailman logs? If 550 error response was sent, there must be some internal error traceback in the logs. > > > I tried to determine if this is a known issue by searching the issues > in Gitlab; but didn't find anything. But wanted to ask if this was a > known issue or not? I personally don't remember seeing such an issue, but Mark or others might know. > > > > Thanks. > > > > - Matt Alberti > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> To > unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking) _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 7 months

what process creates webui tables (mailmanweb db)?

by tflatley＠gmail.com

hello again, running a venv installation i think the tables in 2 databases (mailman/mailmanweb) were initially created by running mailman-web migrate - this wrapper is not available in a package install - so i think i need to run something like this after editing my settings.py file python3 manage.py migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. i do see tables in the mailman db but mailmanweb is empty - is there a different flag i need to run to seed the mailmanweb db? Thanks

3 years, 9 months

Re: [GSoC 2026] [Feature Proposal] Per-List Backup and Restore Support

by sonika gutha

Thank you Stephen, this is very helpful. I understand that the implementation discussion is better continued on mailman-developers, and that mailman-users is more appropriate for feedback about user experience and feature demand. Your guidance on scope and architecture is especially useful. My current understanding is: - the backup/restore logic should live in Mailman Core - the initial interface should be exposed through the mailman utility - Postorius, if added, would come later as an additional UI - the backup format should be versioned and include metadata such as timestamp and schema compatibility - archives and site-wide web template customizations are out of scope for the first version - subscription preferences and restore permissions need special care I will refine the proposal in that direction and continue the implementation discussion on mailman-developers. Thank you again.

4 months, 1 week

[Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by blackout69

Hello everybody,I received this error message and from that moment the maiilan3 has stopped working.I restarted the following services mailman3 and mailman3-web and everything started working fine.Can you tell me what is the problem my django server has encountered? Internal Server Error: /hyperkitty/list/direttivo(a)catania.linux.it/top-threads DoesNotExist at /hyperkitty/list/direttivo(a)catania.linux.it/top-threads Thread matching query does not exist. Request Method: GET Request URL: https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/t… Django Version: 1.11.29 Python Executable: /usr/bin/uwsgi-core Python Version: 3.7.3 Python Path: ['.', '', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/usr/local/lib/python3.7/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Ven, 26 Feb 2021 20:10:53 +0100 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', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount') 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.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 41. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 187. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py" in inner 134. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py" in overview_top_threads 196. 'threads': mlist.top_threads, File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" in top_threads 157. return self.cached_values["top_threads"]() File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py" in __call__ 59. return self.get_or_set(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" in get_or_set 365. return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" in <listcomp> 365. return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/django/db/models/manager.py" in manager_method 85. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py" in get 380. self.model._meta.object_name Exception Type: DoesNotExist at /hyperkitty/list/direttivo(a)catania.linux.it/top-threads Exception Value: Thread matching query does not exist. Request information: USER: blackout69 GET: No GET data POST: No POST data FILES: No FILES data COOKIES: csrftoken = 'tqNIiLrMWyYNHYhkmnmQfjRdd0AtCeCAAW46VOL24wk2g7Opl5LSZWB2dZ2p79Sb' sessionid = 'brhb9jd3ko9blnluuc6bz3c1627u6h22' META: CONTENT_LENGTH = '' CONTENT_TYPE = '' CSRF_COOKIE = 'tqNIiLrMWyYNHYhkmnmQfjRdd0AtCeCAAW46VOL24wk2g7Opl5LSZWB2dZ2p79Sb' DOCUMENT_ROOT = '/usr/share/nginx/html' HTTPS = 'on' HTTP_ACCEPT = 'text/html, */*; q=0.01' HTTP_ACCEPT_ENCODING = 'gzip, deflate, br' HTTP_ACCEPT_LANGUAGE = 'it-IT' HTTP_COOKIE = 'csrftoken=tqNIiLrMWyYNHYhkmnmQfjRdd0AtCeCAAW46VOL24wk2g7Opl5LSZWB2dZ2p79Sb; sessionid=brhb9jd3ko9blnluuc6bz3c1627u6h22' HTTP_HOST = 'lists.catania.linux.it' HTTP_REFERER = 'https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/' HTTP_TE = 'trailers' HTTP_USER_AGENT = 'Mozilla/5.0 (Android 11; Mobile; rv:86.0) Gecko/86.0 Firefox/86.0' HTTP_X_REQUESTED_WITH = 'XMLHttpRequest' PATH_INFO = '/hyperkitty/list/direttivo(a)catania.linux.it/top-threads' QUERY_STRING = '' REMOTE_ADDR = '2.38.155.170' REMOTE_PORT = '39208' REQUEST_METHOD = 'GET' REQUEST_SCHEME = 'https' REQUEST_URI = '/hyperkitty/list/direttivo(a)catania.linux.it/top-threads' SCRIPT_NAME = '' SERVER_NAME = 'lists.catania.linux.it' SERVER_PORT = '443' SERVER_PROTOCOL = 'HTTP/2.0' uwsgi.core = 1 uwsgi.node = b'glugct.catania.linux.it' uwsgi.version = b'2.0.18-debian' wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'> wsgi.file_wrapper = '' wsgi.input = <uwsgi._Input object at 0x7f0e65582f00> wsgi.multiprocess = False wsgi.multithread = True wsgi.run_once = False wsgi.url_scheme = 'https' wsgi.version = '(1, 0)' Thank you in advance -- blackout69

5 years, 4 months

Re: Re-enable member after bouce processed disable

by Henrik Rasmussen

Henrik Rasmussen wrote: > Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces. > When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or. It seems that I was right, however, I need to re-enable all members on a single list who have been disabled due to bounces. Using the `mailman members` command it is possible to list such members, however how do I enable them using either the `mailman shell` command (available) og the mailmanclient (needs first to be installed in the docker container)? Regards, Henrik Rasmussen

4 years, 6 months

Re: Speed up importing mailman2 lists

by Jeremy Stanley

On 2025-02-20 07:15:57 +0000 (+0000), Stephen J. Turnbull wrote: [...] > I've done two massive migrations in the last year. In the first (~20k > lists), the lists were down for maybe two hours, but it took 22 hours > for HyperKitty to populate, mostly in Xapian indexing we realized in > post-mortem analysis. In the second (~1k lists), no perceptible > downtime because they have their own bespoke archiver that has a > list-manager-agnostic API. Our sites didn't have nearly that many mailing lists, but we were migrating from multiple side-by-side MM2 installs for domains hosted on one server to a multi-domain MM3 deployment on another. In our case we did piecemeal outages one domain at a time rather than having one mass migration for everything all at once, and that kept the impact to each individual domain/site minimal. > The trick to zero delivery downtime is that you can configure your MTA > to route to Mailman 3 if the list exists there, if not route to > Mailman 2 if the list exists there, and if not continue to any lower > priority routes. It worked as designed (mops sweat off brow ;-). We > did take Postorius and the Mailman 2 management CGIs and email command > addresses offline for the duration (3 hours in the first case, 30 > mminutes in the second). This is sraightforward if Mailman 2 and > Mailman 3 are running on the same host. Life is more complex if > you're spinning up Mailman 3 in a separate node but it should be > possible. Yes, our downtime included finalizing a warmed rsync over the Internet and waiting for DNS changes to propagate (we tried to time things so that the import occurred in parallel with DNS settling out, even with lowered TTLs it helped some for larger sites). We didn't have a lot of incentive to avoid downtime entirely in that situation, and instead just warned the various communities in advance when we'd scheduled their particular migration for and what they should expect. We relied primarily on delivery deferrals between taking a domain offline on one server and bringing up the imported copy on the other, and just accepted that the associated Web content would be offline during the maintenance window but that posts anyone sent at that time would still make it to the lists once they were back. > I think if you're migrating to HyperKitty you can speed up the > migration by shutting off indexing, and doing that later at the cost > of confusing people who expect the lists to be indexed. I'm not sure > if it's possible to migrate the archives concurrently with accepting > new posts, or maybe to migrate archives in advance and backfill any > posts that arrive during the list migration. And there's no reason > why you can't leave the legacy Mailman 2 archives up for browsing > as a backup for as long as needed. In our case, "as long as needed" is approximately forever, but we did install some redirects in Apache for things like list info pages and archive roots. We drew the line at trying to develop an automated mapping to redirect individual posts in the archives though, which is the main reason we keep the pre-migration pipermail content around, since we'd rather not break random links elsewhere on the Web, e.g. in news articles that link to list discussions. -- Jeremy Stanley

1 year, 5 months

Mailman-users search results for query "Postorius"