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

7 years, 10 months

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

3 years, 7 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

8 years, 6 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.

4 years, 6 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, 1 month

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 >

1 year, 5 months

Re: Problem with digests not being sent daily

by Mark Sapiro

On 6/21/24 22:04, Mark wrote: > > At ~04:50 I posted an email to the list. The message was delivered to > members and archived. > > Nothing showed up in /opt/mailman/mm/var/lists/<LISTID> Probably because (in Postorius) Settings->Digest->Enable Digests is No > Then, as "mailman", I ran "mailman digests --periodic" manually and got > the same error (as expected since there is nothing there) ... > > $ /opt/mailman/venv/bin/mailman digests --periodic > Traceback (most recent call last): ... > FileNotFoundError: [Errno 2] No such file or directory: > '/opt/mailman/mm/var/lists/<LISTID>/digest.mmdf' -> > '/opt/mailman/mm/var/lists/<LISTID>/digest.6.3.mmdf' This error should not occur if there is no digests.mmdf. It only does occur because you have set Digest size threshold to 0 under the assumption that 0 means unlimited which it doesn't. If you don't want digests sent on size, you need to set Digest size threshold to a very large number. I've created https://gitlab.com/mailman/mailman/-/issues/1158 to avoid throwing the exception, but setting the threshold to 0 is still wrong as it will cause a digest to be sent on every post. If the Enable Digests setting is Yes, then the lack of digests needs more investigation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

Re: Bulk update of members' moderation settings

by Mark Sapiro

On 11/18/21 12:37 PM, Alex King via Mailman-users wrote: > I imported a list from mailman 2.1 using > https://docs.mailman3.org/en/latest/migration.html. > > It happens that emergency moderation was set on the mailman 2.1 list, > and this has resulted in all members having Moderation set to Hold. I > now want to change that to Default Processing for all members. > > Is there a way to achieve that in bulk without clicking through the > members options for each member in Postorius? I don't understand how this happened. The mailman 2.1 list's emergency setting should hsave been imported as the emergency setting of the Mailman 3 list and should not affect individual member's moderation at all. However, to set the moderation action for all members of a list to default processing You can do something like this in mailman shell ``` 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 >>> from mailman.interfaces.action import Action >>> for member in m.members.members: ... member.moderation_action = Action.defer ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Re: MM2 to MM3 Archives Loading

by Alain D D Williams

On Wed, Dec 04, 2024 at 08:45:02PM -0000, Joshua Bushe wrote: > This link is an example you sent earlier: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ > > This link is above is the page where i can't see any of my lists outputs on my mailman3 gui. All i visually see is three loading icons spinning. Also, mark said it will only show threads with post in the last 30 days. so i made a test list and made a new thread and still the problem persists. Still see the three loading icons spinning. I've manually added the test list and also did it through the gui. Same outcome. This is one of the things that I had few problems with. The command that I used was: # su - list -s /usr/bin/bash -c 'python3 /usr/share/mailman3-web/manage.py hyperkitty_import -l senate(a)mm-test.phcomp.co.uk /tmp/senate.mbox' • This was on a Debian system, installed via apt-get • /tmp/senate.mbox needs to be readable by the user list • Done after the list had been created via postorius, then I ran: # su - list -s /usr/bin/bash -c 'mailman --run-as-root import21 senate(a)mm-test.phcomp.co.uk /tmp/senate.pck' -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

6 months

Re: Installing mailman 3

by Rafael Mora

Why isn't it sending emails? What do you think? El mar., 1 ago. 2017 a las 16:34, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > > > > 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 > > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 10 months

Mailman-users search results for query "Postorius"