Search results for "Postorius" - Mailman-users

Re: Installing mailman 3

by Abhilash Raj

On Tue, Aug 1, 2017, at 02:29 PM, Rafael Mora wrote: > Hello Abhilash, > > I have this in my settings.py file: > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > #EMAIL_HOST_USER = 'mailing(a)labbrands.com' > #EMAIL_HOST_PASSWORD = '******' This looks good to me. > > What should I use in user and password?? Does Django use postfix to send the email??? I think you don't need a password and username as long as your postfix is configured to relay local emails without authentication (which it is by default if you installed from distro packages and if you haven't changed the settings). > > Thanks > > > > > El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió:>> Hi, >> >> >> >> On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: >> > It's ok now, but still I can't make it send the confirmation email>> > >> > This is from mailman.log: >> > >> > >> > [mailman@localhost logs]$ tail -f mailman.log >> > Aug 01 15:59:18 2017 (2327) lmtp runner started. >> > Aug 01 15:59:18 2017 (2333) virgin runner started. >> > Aug 01 15:59:18 2017 (2332) retry runner started. >> > Aug 01 15:59:18 2017 (2330) pipeline runner started. >> > Aug 01 15:59:18 2017 (2325) command runner started. >> > Aug 01 15:59:19 2017 (2328) nntp runner started. >> > Aug 01 15:59:19 2017 (2326) in runner started. >> > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET >> > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 >> > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET >> > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 >> > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200>> > 90 >> > >> > >> > >> > >> > What should I do? >> >> If you are talking about Account confirmation emails, they usually are>> sent out from Django and not Mailman Core itself. >> >> To configure Django you need to edit the `settings.py` file, wherever>> that is one your installation. If you are following the guide mentioned>> at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at>> `mailman-suite/mailman-suite_project/settings.py`. >> >> To configure your Django to send emails, have a look at >> http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required.>> >> That documentation page has pretty much everything you need in order to>> have a running Web Frontend, please go through it and make sure you have>> everything configured. >> >> Finally, the actual emails from Mailing lists are supposed to be handled>> by Core. You need to configure Postorius & Mailman both to communicate.>> The settings are mentioned >> http://docs.mailman3.org/en/latest/config-core.html#configuring-mta >> here. >> >> >> Hope that helps! >> >> > >> > >> > >> > >> > >> > >> > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>)>> > escribió: >> > >> > > On 8/1/17 1:14 PM, Rafael Mora wrote: >> > > > >> > > > Why does it say Address already in use? >> > > >> > > >> > > Because you are starting lm tp runner and it's already running.>> > > >> > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill>> > > any if necessary. Then do 'mailman start'. >> > > >> > > -- >> > > 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 >> > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>> > > >> > -- >> > >> > Atentamente / Best Regards >> > >> > Ing. Rafael Mora >> > _______________________________________________ >> > Mailman-users mailing list >> > mailman-users(a)mailman3.org >> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>> >> >> -- >> thanks, >> Abhilash Raj >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> -- > Atentamente / Best Regards > Ing. Rafael Mora -- thanks, Abhilash Raj

8 years, 7 months

Mailman Core 3.3.2rc2 Released

by Abhilash Raj

Hi Everyone, I am pleased to announce that Mailman Core 3.3.2rc2 is now out. This release includes both bug fixes and some new features. Some notable changes include: - Support for inviting users to join mailing lists. - New `adddmembers`, `delmembers` and `syncmembers` command to manage membership from CLI. - Addition of new REST API endpoints that return the count of held messages and subscription requests of much faster page loads in Postorius. - Addition of support for filtering in some API endpoints like Members and Subscription requests. - Support for `address=` option in email join command to subscribe an address other then sending address. - Addition of `who` email command to lookup memberships. - Expose emergency field for MailingList resource in REST API. - Several bug fixes to support new major version of libraries like dnspython, flufl.* etc. Since this is a pre-release, you can install it using: $ pip install --pre --upgrade mailman If there are no new major bugs, 3.3.2 will be released in 2 weeks time. We are now in strings freeze, so if you would like to help with translations to your native language, now is the time. We use Weblate for translations [1] and see here[2] for more documentation about i18n process in Mailman. There are a couple of new templates and more user friendly email templates & subjects for Mailman generated emails that could use translations. [1]: https://hosted.weblate.org/projects/gnu-mailman/mailman/ [2]: https://docs.mailman3.org/en/latest/translation.html -- thanks, Abhilash Raj (maxking)

5 years, 4 months

Re: Link another address

by Mark Sapiro

On 5/18/20 5:13 PM, Brian Carpenter wrote: > I am thinking about incorporating the following Postorius/Django account feature into Affinity: > > Other emails: (no other email) Link another address > > However I cannot think of a serious real-world need for this. What are the developers' reasoning behind this? Was this feature highly demanded by Mailman 3 users? Just trying to find out what I am missing here. In mailman 2.1 there was no concept of user. There were only lists and list members and list members were just email addresses that had no connection to other list members even if they happened to have the same email address. In mailman 3 we have users. Users can have multiple addresses. a user or a particular user's address can be a regular member and an owner of one list, a moderator of another list and a non-member of a third list. Some other address of that user can be a digest member of the first list. All of these addresses and roles can belong to a single user and be managed from that user's one account. Sure, each address can be separate with it's own login, but isn't it more convenient if they are all linked under one login if they all belong to one individual. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

Hi all: I need to provide the list moderators a way to change the moderation flag for users from whichever it is (normally "list default processing") to "hold for moderation" and viceversa (to "list default" or to "accept") I understand that it could be done via console script (That's the way I did on mailman2: I made two commands using "withlist", one to hold, moderar.py, and other one to accept, desmoderar.py. I show you below) But I think I'm not the only one that could use as an improvement a way to do this on postorius/web. Before to trying implementing them on mailman3, I beg you to tell me if they could do that on mailman3. Thanks in advance. ****************** (moderar.py) #! /usr/local/bin/python # # script via withlist para moderar a pelo # """moderar un miembro. Save as bin/moderar.py Run via bin/withlist -r moderar <listname> <member> """ from Mailman import mm_cfg def moderar(mlist, member): if not mlist.Locked(): mlist.Lock() mlist.setMemberOption(member, mm_cfg.Moderate, True) mlist.Save() mlist.Unlock() ****************** (desmoderar.py) #! /usr/local/bin/python # # script via withlist para desmoderar un miembro # """desmoderar un miembro. Save as bin/desmoderar.py Run via bin/withlist -r desmoderar <listname> <member> """ from Mailman import mm_cfg def desmoderar(mlist, member): if not mlist.Locked(): mlist.Lock() mlist.setMemberOption(member, mm_cfg.Moderate, False) mlist.Save() mlist.Unlock() --

4 years, 5 months

Re: URLs in moderation messages

by Odhiambo Washington

On Fri, Mar 3, 2023 at 8:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/3/23 01:55, Tim Cutts wrote: > > > > I’ve clearly got something wrong in my configuration, but I can’t work > out what. > > > > All my URLs seem to have the “mailman3” part duplicated, i.e. > > > > Https://example.com/mailman3/mailman3/lists > > > > Is where I have to go to get a list of my mailing lists, which just > doesn’t seem right. > > > > In my settings.py file I have: > > > > POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com/mailman3/' > > > > If I change the value of this to just https://example.com/ it doesn’t > change this, > > > That setting has nothing to do with your issue. It only determines the > base part of the URL that's used to retrieve templates set in Postorius. > > What is your web server configuration? This is probably where the > problem lies. See > > https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… > for a suggested nginx config and > > https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… > for Apache. > Are these proposed VirtualHost configs independent of whether one is using gunicorn/mod_wsgi/uwsgi? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years

Re: mm3 floods syslog

by Mark Sapiro

On 10/31/21 4:18 AM, Wolfgang Bock via Mailman-users wrote: > Dear friends, > > I got another problem: mailman floods my syslog. > > I deleted a domain/webdomain (further mentioned as deleted.org) in > postorius, django web. No entries are now in > /var/lib/mailman3/data/postfix_domains or postfix_lmtp or > /var/lib/mailman3/lists. > > > Here an extract of my syslog (anonymized): > Oct 31 10:49:02 myserver mailman3[1284]: Oct 31 10:49:02 2021 (1284) > Certificate did not match expected hostname: localhost. Certificate: > {'subject': ((('commonName', 'deleteted.org'),),), 'issuer': > ((('countryName', 'US'),), (('or > ganizationName', "Let's Encrypt"),), (('commonName', 'R3'),)), 'version': 3, > 'serialNumber': '0326A733CA7B16D13C830EE707EA614E25F9', 'notBefore': 'Oct 30 > 20:21:08 2021 GMT', 'notAfter': 'Jan 28 20:21:07 2022 GMT', > 'subjectAltName': (('DN > S', 'deleteted.org'), ('DNS', 'lists.deleteted.org'), ('DNS', > 'mail.deleteted.org'), ('DNS', 'ns.deleteted.org'), ('DNS', > 'www.deleteted.org')), 'OCSP': ('http://r3.o.lencr.org',), 'caIssuers': > ('http:/ > /r3.i.lencr.org/',)} > > This appears nonstop. Your ssl certificate is for the domain `deleted.org` with alt names `lists.deleted.org`, `ns.deleted.org`, `mail.deleted.org` and `www.deleted.org`. Django is accessing things at a URL for a different domain. Get a new certificate for the domain(s) you are actually using. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Mailman 3.1 beta coming soon

by Barry Warsaw

Hello Mailman 3 users and developers! It's been a long slog but I think we are finally ready to begin the release process for Mailman 3.1. I am pretty happy about the state of the Core, and Florian is going to do some more integration testing with HyperKitty and Postorius. We still have a few issues and a merge proposal or two to address, but I am planning to spin a beta of Core this weekend to facilitate testing. Here is the Core's 3.1 milestone page: https://gitlab.com/mailman/mailman/milestones/2 If your favorite issue or merge request isn't on that list, please do get in touch. Otherwise it will be deferred to 3.2. I'm also not entirely promising I'll get to all of these; I really want to release 3.1 in 2016 so if we run out of time, it will get deferred. Here's the project-wide list of 3.1 issues: https://gitlab.com/groups/mailman/issues?scope=all&state=opened&utf8=%E2%9C… and merge requests: https://gitlab.com/groups/mailman/merge_requests?scope=all&state=opened&utf… Except that HyperKitty isn't on this list. Please do test whatever you can and let us know how it goes. Cheers, -Barry _______________________________________________ Mailman-Developers mailing list Mailman-Developers(a)python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/mark%40msapiro.n… Security Policy: http://wiki.list.org/x/QIA9

9 years, 3 months

KeyError: 'subject_prefix'

by Stephen J. Turnbull

Torge Riedel writes: > today I had the following error in my inbox: > > KeyError: 'subject_prefix' > AttributeError: 'MailingList' object has no attribute > 'subject_prefix' This isn't very helpful. Does this happen for all lists? A particular list? How long have you been running this version of Mailman 3 (time since last update)? Is there anything in the logs from Mailman core (this error is coming from the client side of the REST API module)? > I checked the database, Which database? It looks to me like subject_prefix is declared in both Mailman core and HyperKitty (I haven't checked Postorius). I'm not real familiar with this code, so it could be that eventually everything boils down to REST calls to Mailmman core, but it looks like Django's database is involved for HyperKitty. > there is a column "subject_prefix", so I feel it is something in > the code causing the error. Sure, but what? We eventually see this: > File "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call > error_msg, response, None) > urllib.error.HTTPError: HTTP Error 500: <html> > <head> > <title>Internal Server Error</title> > </head> > <body> > <h1><p>Internal Server Error</p></h1> > > </body> > </html> which is mailmanclient passing on the REST API's report that Mailman core is very confused. There should be a log message from core for this.

5 years, 3 months

Re: Migrating mailman3 to latest ubuntu lts

by Helio Loureiro

Hi, And here we have it: (venv) mailman@new=server ~ (v3.3.9)> mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0004_alter_emailaddress_drop_unique_email... OK Applying account.0005_emailaddress_idx_upper_email... OK Applying admin.0003_logentry_add_action_flag_choices... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_mailman3.0003_sessions... OK Applying django_q.0010_auto_20200610_0856... OK Applying django_q.0011_auto_20200628_1055... OK Applying django_q.0012_auto_20200702_1608... OK Applying django_q.0013_task_attempt_count... OK Applying django_q.0014_schedule_cluster... OK Applying hyperkitty.0016_auto_20180309_0056... OK tl;dr: it was the database. So the django was spitting out absolutely horrible traceback errors to diagnose the issue. I modified the code to print the query and then raise exception (what is expected from an error, not only "I just failed, sorry do whatever"). Then I got the query and tried manually. And it failed. (venv) mailman@new-server ~ (v3.3.9)> mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0004_alter_emailaddress_drop_unique_email...Error running query: b'*ALTER** TABLE `account_emailaddress` DROP INDEX `email`'* Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) [...] (venv) mailman@new-server ~ (v3.3.9) [0|1]> mysql -umailman3web -p -h localhost mailman3web Enter password: Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 32 Server version: 10.6.12-MariaDB-0ubuntu0.22.04.1 Ubuntu 22.04 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [mailman3web]> *ALTER TABLE `account_emailaddress` DROP INDEX `email`;* ERROR 2013 (HY000): Lost connection to server during query MariaDB [mailman3web]> *ALTER TABLE `account_emailaddress` DROP INDEX `email`;* ERROR 2006 (HY000): Server has gone away No connection. Trying to reconnect... Connection id: 32 Current database: mailman3web ERROR 2013 (HY000): Lost connection to server during query So I looked to the mysql error logs and searched Internet for the issue. It recommended to run a "mysql_upgrade", which failed with another error: root@seliius26224 /e/mailman3# mysql_upgrade -u root --force Phase 1/7: Checking and upgrading mysql database Processing databases mysql mysql.column_stats OK mysql.columns_priv OK mysql.db OK mysql.engine_cost Error : Table 'mysql.engine_cost' doesn't exist status : Operation failed mysql.event OK mysql.func OK [...] sys.x$wait_classes_global_by_avg_latency OK sys.x$wait_classes_global_by_latency OK sys.x$waits_by_host_by_latency OK sys.x$waits_by_user_by_latency OK sys.x$waits_global_by_latency OK Phase 4/7: Running 'mysql_fix_privilege_tables' ERROR 1932 (42S02) at line 477: Table 'mysql.innodb_index_stats' doesn't exist in engine FATAL ERROR: Upgrade failed I searched again the Internet and found a fix: https://stackoverflow.com/questions/37856155/mysql-upgrade-failed-innodb-ta… Now migration is progressing. Thanks for all the patience and support. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Tue, 19 Dec 2023 at 15:23, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/19/23 3:11 AM, Helio Loureiro wrote: > > Hi, > > > > No luck :( > > > > (venv) mailman@new-server ~ (v3.3.9)> *pip install -U > > django-allauth==0.58.0* > > You need to install django-allauth<0.58.0 as in > ``` > pip install django-allauth\<0.58 > ``` > > -- > 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 helio(a)loureiro.eng.br >

2 years, 2 months

Re: Invalid FilterAction: discard. Treating as discard

by Mark Sapiro

On 5/7/19 6:19 AM, Henrik Rasmussen wrote: > Having set the Filter content to Yes - regardless of other setting in the "Alter Messages" tab, make a HTML message come out empty. I can replicate this on my test list. I don't understand the question? Are you asking why the log contains "invalid FilterAction: discard. Treating as discard"? If so, that's a bug. See <https://gitlab.com/mailman/mailman/issues/592>. If you are asking why the message is empty after filtering and discarded, It is presumably because it is a text/html message as opposed to a multipart/alternative message with text/plain and text/html alternative parts. > I have tried debugging by changing each setting one-by-one and sending the user's mail, but no change makes the mail come out with a content. However setting "Filter content" to "no" makes the mail come out okay. There are list attributes filter_types and pass_types (also filter_extensions and pass_extensions, but those probably aren't relevant here) which affect this and which aren't exposed in Postorius. See <https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/filterin…> for more info of content filtering. Presumably, the combination of filter_types and pass_types is not allowing text/html. You need to examine these settings in mailman shell, e.g. list(m.pass_types) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

Mailman-users search results for query "Postorius"