Search results for "Postorius" - Mailman-users

Re: moderation notices for list-owner being redirected to mailman address

by Mark Sapiro

On 2/7/22 16:11, Philippe B wrote: > I think that your last sentence helped us figure out what's going on. > > When Mailman generates a moderation message "To: LIST-owner" it actually delivers it to the address(es) of the LIST's moderator(s), which makes sense. No, it delivers the message to the union of the sets of owner addresses and moderator addresses. > In all the cases where we've seen that behavior, it turns out that the list involved didn't have any moderator, and we have site_owner set to "mailman"... You don't need to have moderators. The owners get the message too. > However, the lists had an owner, and we're not seeing those moderation messages being sent to their owner (instead). Is that something that needs to be configured explicitly somewhere? The only things that might affect this are if Settings -> Automatic Responses -> Autorespond to list owner is Respond and discard message or if the owners delivery_status is other than DeliveryStatus.enabled. Note that finding an owner's delivery status is tricky. The owner can find it in Postorius by going to https://www.example.com/mailman3/accounts/subscriptions/ and clicking on the entry for the list with role owner. This delivery status is not the same as the delivery status for the same address with a member role if there is one. For an admin you could do ``` $ bin/mailman shell -l list.example.com 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. The variable 'm' is the list.example.com mailing list >>> owner = m.owners.get_member('user(a)example.com') >>> owner.delivery_status <DeliveryStatus.enabled: 1> If you needed to set it here, you could do >>> owner.preferences.delivery_status = DeliveryStatus.enabled >>> commit() >>> ``` -- 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

signup / registration error - permissions and cert chains

by David Newman

I'd like for regular (non-admin) list subscribers to be able to manage their subscription preferences and view list archives. However, when new users attempt to create logins from the Postorius "Sign Up" page, the server returns the error pasted below, and displays a "server error" page to users. If I'm reading the error correctly, this is related to an inability to verify the cert chain. The /etc/mailman3/settings.py file points to the same cert and key files used by Nginx, Postfix, and Dovecot. Since TLS works OK with these other services, it appears the cert and key are valid. (Viewing the cert in a web browser also supports this.) The keyfile has 0400 permissions. I tried changing this to 0640 and making the keyfile owned by root:mailman. Even after restarting mailman3 and mailmanweb the same error occurs. (Permissions in the cert and key directories and above are not blocking access.) The etc/mailman3/settings.py file includes these settings: EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = 'dnewman(a)networktest.com' EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know' EMAIL_USE_TLS = 'True' EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt' EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key' But this might only be for email, not Postorius/Django. I checked the Mailman Web docs and settings reference but didn't see anything relevant on either page. https://docs.mailman3.org/en/latest/config-web.html https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html What additional configuration is needed to allow regular users to create and manage their own accounts? Thanks. dn ERROR 2021-12-30 16:03:53,787 436935 django.request Internal Server Error: /accounts/signup/ Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/utils/decorators.py", line 43, in _wrapper return bound_method(*args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 230, in dispatch return super(SignupView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 74, in dispatch response = super(RedirectAuthenticatedUserMixin, self).dispatch( File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 204, in dispatch return super(CloseableSignupMixin, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 102, in post response = self.form_valid(form) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 248, in form_valid return complete_signup( File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/utils.py", line 209, in complete_signup return perform_login( File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/utils.py", line 175, in perform_login send_email_confirmation(request, user, signup=signup, email=email) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/utils.py", line 346, in send_email_confirmation email_address.send_confirmation(request, signup=signup) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/models.py", line 62, in send_confirmation confirmation.send(request, signup=signup) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/models.py", line 169, in send get_adapter(request).send_confirmation_mail(request, self, signup) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/adapter.py", line 464, in send_confirmation_mail self.send_mail(email_template, emailconfirmation.email_address.email, ctx) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/adapter.py", line 136, in send_mail msg.send() File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/message.py", line 284, in send return self.get_connection(fail_silently).send_messages([self]) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smtp.py", line 102, in send_messages new_conn_created = self.open() File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smtp.py", line 67, in open self.connection.starttls(keyfile=self.ssl_keyfile, certfile=self.ssl_certfile) File "/usr/lib/python3.9/smtplib.py", line 772, in starttls context = ssl._create_stdlib_context(certfile=certfile, File "/usr/lib/python3.9/ssl.py", line 787, in _create_unverified_context context.load_cert_chain(certfile, keyfile) PermissionError: [Errno 13] Permission denied

4 years, 8 months

Re: Mailman3 migration and/or archiving problem

by Odhiambo Washington

On Fri, Sep 6, 2024 at 11:43 AM <hnpilot(a)phnet.fi> wrote: > I have installed a mailman3 server following this documentation: > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > After a few hiccups I got mailman and postorius working and migrated one > list according to this documentation: > https://docs.mailman3.org/en/latest/migration.html > > It seemed to work and also hyperkitty_import was run without errors (or at > least none shown up). Running update_index command said that there were 0 > threads copied but I kjnow that the archive isn't empty. But now when I > tried to open the list info page from lists view it dies with 500 error. > > After diving into the different log files I found an error message that it > cannot find /etc/mailman3/mailman-hyperkitty.cfg. Great. Only that the cfg > file exists and seems to my (unexpert) eyes correct. > > After that problem I tried to create a new list. Creation seemed to go all > right but also with it, trying to open the list info page it shows 500 > error. > > When googling for a solution I landed on a message stating that there > might be double entries for the same list in listarchiver table but when I > checked ot turns out that the table is empty! > > I am a bit confused how to figure out the base cause of the problem and > would very much appreciate any pointers. > The documentation you followed is quite okay and reasonably detailed. Just wipe out your virtualenv and start over again. Practice it till you get it working. I suspect you missed a step - or did not understand well. You just need to seek clarification on that. Looking at the mailman-web logfile mentioned in that documentation might also help you. -- 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]

2 years

Hipperkitty failing to archive messages in a list

by Guillermo Hernandez (Oldno7)

First of all, best wishes and Happy New Year for everybody. Two days ago I had to reinstall all mailman3 related apps in a mailman 3 server (I tried to upgrade just hipperkitty, but it went bad). At first, all seemed running as before, but I just noted that the messages are not being archived. I did not change any config. Now the log is showing ERROR 2022-01-03 12:22:15,654 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:15,674 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:15,791 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:16,208 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-04 11:44:55,644 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:55,664 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,478 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,620 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,647 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header (it's a very low traffic list: just two messages in two days) I do believe I did the upgrade/reinstall procedure as in previous upgrades (using pip: it's a system wide installation, not using dockers or venv), but seems that I did something wrong The messages are being delivered normally, but it fails archiving Before I make a bigger hole for myself, where to look for? Versions installed: HyperKitty 1.3.5 mailman 3.3.5 mailman-hyperkitty 1.2.0 mailmanclient 3.3.3 postorius 1.3.6 uWSGI 2.0.19.1 Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 30 2020, 10:49:53) [Clang 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611a -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

4 years, 8 months

Re: Approve an email

by Lars Bjørndal

[Eggert] > Not sure about Fedora, but there seem to be some issues with distribution > specific packages. Many users have got good results with the virtualenv > installation described here: > > https://docs.mailman3.org/en/latest/install/virtualenv.html Thank you! I gave it a try. I installed postgresql and postgresql-server, created the databases according to the guide and tried to start mailman. I get this error: ===== Traceback (most recent call last): File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 3361, in _wrap_pool_connect return fn() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 325, in connect return _ConnectionFairy._checkout(self) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 888, in _checkout fairy = _ConnectionRecord.checkout(pool) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 491, in checkout rec = pool._do_get() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/impl.py", line 145, in _do_get with util.safe_reraise(): File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ compat.raise_( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/impl.py", line 143, in _do_get return self._create_connection() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 271, in _create_connection return _ConnectionRecord(self) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 386, in __init__ self.__connect() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 684, in __connect with util.safe_reraise(): File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ compat.raise_( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 680, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/create.py", line 578, in connect return dialect.connect(*cargs, **cparams) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/default.py", line 598, in connect return self.dbapi.connect(*cargs, **cparams) File "/opt/mailman3/venv/lib64/python3.10/site-packages/psycopg2/__init__.py", line 127, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) psycopg2.OperationalError: connection to server at "localhost" (::1), port 5432 failed: FATAL: Ident authentication failed for user "mailman" The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailman3/venv/bin/mailman", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.7', 'console_scripts', 'mailman')()) File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 1054, in main with self.make_context(prog_name, args, **extra) as ctx: File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 920, in make_context self.parse_args(ctx, args) File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 1613, in parse_args rest = super().parse_args(ctx, args) File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 1378, in parse_args value, args = param.handle_parse_result(ctx, opts, args) File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 2360, in handle_parse_result value = self.process_value(ctx, value) File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 2322, in process_value value = self.callback(ctx, self, value) File "/opt/mailman3/venv/lib64/python3.10/site-packages/mailman/bin/mailman.py", line 95, in initialize_config initialize(value) File "/opt/mailman3/venv/lib64/python3.10/site-packages/mailman/core/initialize.py", line 229, in initialize initialize_2(propagate_logs=propagate_logs) File "/opt/mailman3/venv/lib64/python3.10/site-packages/mailman/core/initialize.py", line 187, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/opt/mailman3/venv/lib64/python3.10/site-packages/mailman/database/factory.py", line 58, in create SchemaManager(database).setup_database() File "/opt/mailman3/venv/lib64/python3.10/site-packages/mailman/database/factory.py", line 86, in setup_database context = MigrationContext.configure(self._database.store.connection()) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/orm/session.py", line 1542, in connection return self._connection_for_bind( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/orm/session.py", line 1552, in _connection_for_bind return self._transaction._connection_for_bind( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/orm/session.py", line 747, in _connection_for_bind conn = bind.connect() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/future/engine.py", line 406, in connect return super(Engine, self).connect() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 3315, in connect return self._connection_cls(self, close_with_result=close_with_result) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 96, in __init__ else engine.raw_connection() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 3394, in raw_connection return self._wrap_pool_connect(self.pool.connect, _connection) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 3364, in _wrap_pool_connect Connection._handle_dbapi_exception_noconnection( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 2198, in _handle_dbapi_exception_noconnection util.raise_( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 3361, in _wrap_pool_connect return fn() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 325, in connect return _ConnectionFairy._checkout(self) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 888, in _checkout fairy = _ConnectionRecord.checkout(pool) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 491, in checkout rec = pool._do_get() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/impl.py", line 145, in _do_get with util.safe_reraise(): File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ compat.raise_( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/impl.py", line 143, in _do_get return self._create_connection() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 271, in _create_connection return _ConnectionRecord(self) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 386, in __init__ self.__connect() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 684, in __connect with util.safe_reraise(): File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ compat.raise_( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 680, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/create.py", line 578, in connect return dialect.connect(*cargs, **cparams) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/default.py", line 598, in connect return self.dbapi.connect(*cargs, **cparams) File "/opt/mailman3/venv/lib64/python3.10/site-packages/psycopg2/__init__.py", line 127, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: Ident authentication failed for user "mailman" (Background on this error at: https://sqlalche.me/e/14/e3q8) ===== And here I'm stucked. I have very litle experience with databases, so I don't know how to debug. Any hint? Thank you Lars > Am Montag, 26. Dezember 2022, 21:08:46 CET schrieb Lars Bjørndal: > > Hi, list! > > > > I'm on Fedora 36 with the packages mailman3-3.3.4-6.fc36.noarch and > > postorius-1.3.6-2.fc36.noarch installed. with the command > > > > sudo -u mailman mailman3 create <listname> > > > > I was able to create a list. > > > > I'm not able to find out how to setup and configure the postorius > > package. There's no mailman-web command. > > > > Hyperkitty will not installed du to a dependency conflict, but I dont > > need archiving for the list. > > > > Here comes my quesitons: > > > > - What's the easiest way to approve an email sent to the list? > > > > - How can I configure the list to accept messages also from non members? > > > > - How can I setup postorius to work on Fedora? I have django-admin, but > > I'm not sure where to go. > > > > Thanks in advance, Lars > > _______________________________________________ > > 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 > > /ZDUDQA57QRLF7QD4KPFIZBC6ZIF2FAVP/ > > > > This message sent to eggert(a)eehmke.de > > > > > _______________________________________________ > 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 lars(a)lamasti.net

3 years, 8 months

Re: Post installation issues (recipients refused) with Exim4 in a virtual host environment

by Odhiambo Washington

On Wed, Oct 11, 2023 at 11:15 AM Kyriakos Terzopoulos < kyriakos.terzopoulos(a)gmail.com> wrote: > Hi, > > I have set up (I believe successfully) and configured the following in a > Virtualhost environment (with HestiaCP): > > - A record for lists.mydomain.com > - Venv > - Mailman core > - Mailman web (run migrate, collectstatic, compress, compilemessages) > Postorius > - gunicorn, hyperkitty > - Nginx > - SMTP exim4 conf > > I can see Posrorius and I have logged in and created my first mailing list: > > [image: Screenshot 2023-10-11 at 10.57.31 AM.png] > > My issue is that even though I have subscribed to my list as you can see > above, I am not receiving the confirmation email. I get a "recipients > refused" error. The smtp log for mailman is as follows: > > Oct 11 10:41:20 2023 (1533666) > <169701007904.1534165.14569329382406660776@localhost> recipients refused: > {' > kyriakos.terzopoulos(a)gmail.com': (550, b'Verification failed for > <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu > >\nUnrouteable > address\nSender verify failed')} > > Oct 11 10:41:20 2023 (1533666) > <169701007904.1534165.14569329382406660776@localhost> smtp to > testlist(a)myproject.eu for 1 recips, completed in 0.26796579360961914 > seconds > > Oct 11 10:41:20 2023 (1533666) > <169701007904.1534165.14569329382406660776@localhost> post to > testlist(a)myproject.eu from > testlist-confirm+c9b20c5290bec43147a7e96a6b8cd825daf913d7(a)myproject.eu, > 1667 bytes, 1 failures > > Oct 11 10:41:20 2023 (1533666) > <169701007904.1534165.14569329382406660776@localhost> delivery to > kyriakos.terzopoulos(a)gmail.com failed with code 550, b'Verification failed > for <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu > >\nUnrouteable > address\nSender verify failed' > > I have used the configuration for exim that is here > < > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > > and > I have also tested with the alternative approach that is documented in > What do you have in the Exim's mainlog? -- 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]

2 years, 11 months

Re: Getting original message headers

by Mark Sapiro

On 1/5/26 01:32, Peter Chubb via Mailman-users wrote: > > We've been seeing some particularly pernicious spammers > recently. They're using gmail accounts; I'd like to report them to > Google. > > To do that I need to find the original message headers. By the time > the message gets to the archive, or to the mailing list recipients, > all the Received: headers seem to have been deleted, leaving only the > ones from my list server outwards. Only minimal information from headers is in the hyperkitty archive, but the headers should be in the delivered email and in the message archived by the prototype archiver if enabled (Mailman's var/archives/prototype/<list_address>/new/) For example, in the list message I'm replying to I see these headers from your server > DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; > d=chubb.wattle.id.au; s=2; h=Subject:To:From:Date:References:Reply-To; > bh=g3joi1iLtQO6etRPAxWSgcpVPoLlVQz6JOFqB1oHHfY=; b=jJEI+qHRRXm7S4bGnmZU6zaeh9 > lcPLZkay/lfqg4j9/ucMazFOyEkO3dolXuwz+mnI3CdapcNoGI0/VdZKgNCjINkq6g+Lrzfj5yPZN > o8QPyn42K6pP9A724/LPtKf/ltxymwQxBGm9DbYVx3SWLc8Dxl0e2lMdT1PlQfjHZ3pk=; > Received: from [2401:d002:1202:a00::9] (helo=wombat.chubb.wattle.id.au) > by mx3.chubb.wattle.id.au with esmtpsa (TLS1.3) tls > TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 > (Exim 4.98.2) > (envelope-from <peter(a)chubb.wattle.id.au>) > id 1vcgxA-000000015I8-1oLW > for mailman-users(a)mailman3.org; > Mon, 05 Jan 2026 20:32:45 +1100 > Received: from [192.168.77.170] (helo=gram.chubb.wattle.id.au) > by wombat.chubb.wattle.id.au with esmtpsa (TLS1.2) tls > TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 > (Exim 4.98.2) > (envelope-from <peter(a)chubb.wattle.id.au>) > id 1vcgxJ-0000000AhKz-0d8s > for mailman-users(a)mailman3.org; > Mon, 05 Jan 2026 20:32:53 +1100 I don't know why you are not seeing similar headers in your list mail. Perhaps the spammers are posting via HyperKitty. > Is there a way to access the original incoming emai, before DMARC > mitigation etc., has changed the headers? If you can arrange via list settings or header filters for the message to be held for moderation, you can see the raw held message in Postorius or in Mailman's var/messages/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

Re: Dump/restore users (with passwords) via API

by Abhilash Raj

On Tue, Sep 18, 2018, at 9:19 AM, Dmitry Makovey wrote: > On 09/17/2018 12:39 PM, Abhilash Raj wrote: > > On Mon, Sep 17, 2018, at 12:15 PM, Dmitry Makovey wrote: > >> We are trying to dump/restore users using API calls and it seems > >> that API allows us to dump password hashes (a good thing), but then > >> API does not allow to insert users back using saved password hashes > >> - only cleartext passwords. > > > > I'd say that is intentional. You don't want people to be setting up > > hashes as passwords. > > > >> Aside from create_user is there any other way to create > >> users/change their password? > > > > Not that I know of, not using the API atleast. You could potentially > > use the low level API that inserts records in the database or use SQL > > to dump and restore that data. > > > > What do you use the Core's user/password for? Currently, the user > > passwords are basically just a carry-over from Mailman2 and there > > shouldn't be any use for it. I have been considering removing that > > completely have Postorius do all the authentication/authorization. > > > > Email based authentication should rely on more reliable identities > > like email signatures, intead of having to send cleartext passwords > > over email. > > I think I am asking about the username/password auth for postorious and > how to dump/restore it. At present we have no tools for dump/restoring > users so that's what we're trying to build. Ah, why not take a database dump? There are a few specific tables that you can dump to get everything? We don't have a way to do that because we do not actually do not handle auth ourselves, but instead delegate it to allauth library. You may have to dig into internals of that to be able to fetch/restore users/passwords. -- thanks, Abhilash Raj (maxking)

8 years

Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 21:39, Mark Sapiro escribió: > On 10/27/22 03:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> Since I made all the mailman3 enviroment wide server open (not using >> venv) I already executed the migration doing a >> >> su -m mailman3 -c "python3 manage.py collectstatic" >> su -m mailman3 -c "python3 manage.py migrate" >> >> Being mailman3 the user who runs all of mailman3 related stuff >> >> I had problems doing the migrate part, showing an error of lacking >> perms. I solved it running the migration under root (I know it could >> be trouble after, but...) > > It would be much better to identify the problem files/directories and > adjust their ownership. It is possible that running stuff as root in > the past left things owned by root causing the issue. The problem was in the intent of execute one of the migrate parts and showed about python files. I'm pretty sure that I've been very carefull not running things as root before as I know it can mess all up. But this time it was an dead end and I needed to go through. In a few days I will upgrade another server. I will document the error if I find it again. > >> >> After that the compress part showed errors... but the postorius web >> maintenance was working well except for the CSRF error verification. >> I will trace the compress errors and will try to find the problem later. > > > Do you have `COMPRESS_ENABLED = True` in your settings? If that's not > the issue, it may be in the settings for COMPRESS_PRECOMPILERS > I will try to trace it and comment what I find. Thaks a lot for your support. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 10 months

Re: New attack in progress

by Jered Floyd

I've been seeing this again the past week; it's a variant on classic joe-jobbing spam. I assume Mailman3 instances are being targeted because Postorius has no built-in defenses, so you can generate ~unlimited unsolicited messages once you index all public instances, and flood a victim's gmail (etc) account. I looked into the debian patches for recaptcha, got frustrated, and deployed Anubis in a container in front of my Mailman instances. It took under an hour to learn, install, and test... as long as you're not allergic to catgirls it's the easiest solution. --Jered ----- On Aug 4, 2026, at 10:42 AM, Washington Odhiambo via Mailman-users mailman-users(a)mailman3.org wrote: > On Tue, Aug 4, 2026 at 5:17 PM Paul Tomblin via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Judging by the bounce messages I’m seeing, somebody or somebodies are >> trying to sign up for accounts on my Mailman instance using fake email >> addresses. Can’t imagine what the end game is, other than annoying people >> with “please confirm your email address” emails when they use a real >> address. >> > > > There are ways to play their game that was discussed here: > 1. Anubis - > https://cloud.uferwerk.org/s/a7nWGAjasrQpfSM?dir=/&editing=false&openfile=t… > > On my site, I use reCaptcha, but this solution is not portable without > pain, so go with Anubis. > If you aren't averse to pain then: > 2. https://eu.kictanet.or.ke/~wash/mailman3-captcha-guide.html > > -- > 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] > _______________________________________________ > 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 jered(a)convivian.com

1 month, 3 weeks

Mailman-users search results for query "Postorius"