Search results for "Postorius" - Mailman-users

Re: Easiest way to install a new mailman3 deployment?

by Matthew Alberti

I had a very similar experience. I don't mean to knock the dev team; Mailman3 is an awesome tool that really meets a need. It is really much much more than a 'tool.' A very comprehensive software suite. For me, I ended up using the docker option on Ubuntu 20.04. My advice is to give up on the idea of using OS package managers. They just aren't current enough (certainly for Ubuntu LTS), or updated frequently enough, for the current development of Mailman3. Nothing but problems for me on Ubuntu, and Debian is about the same. Pypi, or installation in a virtualized environment, was equally challenging. I strongly recommend the docker installation method. It is not quite turnkey, but the documentation is close enough where it might 'just work' in your environment. I used MariaDB, and that introduced some challenges. If you are using postgre, postfix, and nginx, you are pretty close to a very easy installation. This list is very supportive, with very frequent responses from the core dev team. And there are guys like me who really struggled to get to a production instance. Please let us all know what isn't working in the docker approach, and we will try to help I'm sure. - Matt Alberti ⁣Get BlueMail for Android On Dec 31, 2020, 8:15 PM, at 8:15 PM, ieso(a)johnwillson.com wrote: >So I've been trying for the last two weeks to get a new mailman3 server >running on a virtualized server (any server), and I'm turning to this >list after having failed many times and running out of holiday time. > >I started trying a non-docker installation on Ubuntu 18.04 >(https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) >, which got me the closest. Except I had a problem with inbound email >only being triggered when it came from certain accounts. But that >clearly wasn't good enough for production, so after many attempts to >figure out where it was failing, I decided to turn to docker as a >solution that should be cleaner. > >A few attempts at doing a docker installation on digitalocean.com >failed, which I realized might be due to it not routing private IP >addresses, so I moved to AWS after checking that their VPC policy would >fit mailman's docker requirements. I found a great but slightly >outdated guide on how to do this >(https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/) >By this point I knew enough to correct a number of places where the >environment had changed since the procedure was written, but postorius >still failed at the curl test. > >The challenge for me has been the difficulty to know how to >troubleshoot the different different systems and network infrastructure >that are used to keep mailman3 humming. I've tried about 7 different >installation walkthroughs (there are no recent ones on Youtube by the >way, in case anyone wants to seize that opportunity!), and the good >guides provide ways to check each stage to try to help you a bit on >that front. > >Nonetheless, I feel stuck and thought I'd ask the simple question... >for a completely basic, barebones new installation, what's the easiest >way to get a mailman3 installation up-and running? (e.g. Which server >provider? Which operating system and version? Docker or otherwise?) > >Any pointers highly appreciated. Google Groups is clearly on its way >out, as it no longer allows for people to easily join groups by sending >an email or clicking a link, so that should be a big opportunity for >mailman3 to step up and help give those mailing list migrants a new >home... which is what we're looking for. We're just not quite as smart >as you guys. ;-) >_______________________________________________ >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/

4 years, 7 months

Re: Whitelist non subscriber

by Mark Sapiro

On 08/10/2017 07:12 AM, Mark Ziranski wrote: > > I want to whitelist an email address on all lists to bypass moderation. > The email address is not a subscriber. On google I > found accept_these_nonmembers but I do not know how to use it. > Please show me some examples how to whitelist someone(a)example.org. Since this is a Mailman 3 list, I assume you are asking about MM 3. Mailman 3 defines the list attribute accept_these_nonmembers, but it is not currently implemented to actually have any effect, nor is it exposed in Postorius. At the present, I think you would have to create a user record with the address and add that user to all lists with role nonmember and moderation_action 'defer' to apply subsequent tests or 'accept' to unconditionally accept posts from that address. (In MM 2.1, accept_these_nonmembers is a list of addresses and regexps matching addresses whose posts are to be accepted, subject to subsequent tests, and is exposed in the web admin UI) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 17/9/21 19:58, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 17/9/21 17:24, Mark Sapiro wrote: >> On 9/17/21 6:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> wrote: >>> On 16/9/21 16:40, Mark Sapiro wrote: >>>> >>>> Are you asking what the equivalent MM 3 scripts would be? >>>> >>> More or less: I'm asking for a general direction here. I think I >>> cannot use tthe "withlist" method as before, inside a python script, >>> and I'm not sure how to do it. >> >> >> You can run scripts via withlist in Mailman 3 similarly to Mailman 2. >> See >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… >> >> > First, thanks for the prompt response, Mark. > > Maybe I'm a little bit ofuscated, but I readed this doc many times > when I was searching how to do it... but I cannot imagine how to do a > shell or a python script, using the needed parameters, that sets hold > on a member of a list. > > I'll try to do some tests tomorrow. I've followed the indications of a mailman -C /usr/local/mailman3/var/etc/mailman.cfg shell --details I've been trying to "translate" the python script that I made for mailman2 to new mailman3, but obviously, I'm missing something. It seems that mailman cannot locate the "module" needed. The script is named "moderar.py": *-*-*-*-*-*-*-*-*-* (begin of /usr/local/mailman3/moderar.py) /usr/local/mailman3 # cat moderar.py #! /usr/local/bin/python3 # # script via withlist para moderar a pelo en mailman3 # import os import sys sys.path.insert(0, '/usr/local/mailman3') os.environ['PYTHONPATH'] = '/usr/local/mailman3' os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' os.environ['MAILMAN_CONFIG_FILE'] = '/usr/local/mailman3/var/etc/mailman.cfg' import mm_cfg def moderar(mlist, member): if not mlist.Locked(): mlist.Lock() mlist.setMemberOption(member, mm_cfg.Moderate, True) mlist.Save() mlist.Unlock() *-*-*-*-*-*-*-*-*-* (end of /usr/local/mailman3/moderar.py) When I execute a mailman withlist -r moderar -l list_to_use(a)mydomain.com address(a)moderate.com The system returns: Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> load_entry_point('mailman==3.3.4', 'console_scripts', 'mailman')() File "/usr/local/lib/python3.7/site-packages/click/core.py", line 829, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 782, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.7/site-packages/mailman/bin/mailman.py", line 68, in invoke return super().invoke(ctx) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1259, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1066, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 610, in invoke return callback(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/click/decorators.py", line 21, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/mailman/commands/cli_withlist.py", line 293, in shell r = call_name(dotted_name, m, *run_args) File "/usr/local/lib/python3.7/site-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) File "/usr/local/lib/python3.7/site-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 965, in _find_and_load_unlocked ModuleNotFoundError: No module named 'moderar' I've done a ln -s /usr/local/mailman3/moderar.py /usr/local/lib/python3.7/site-packages/mailman/bin/moderar.py But with the same result. And I'm not sure if I'm doing well importing "mm_cfg" in the script. My enviroment is open wide installation of mailman, python, etc. in a FreeBSD 12.2-RELEASE-p10 Mailman Core Version GNU Mailman 3.3.4 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 6 2020, 21:14:59) [Clang 8.0.1 (tags/RELEASE_801/final 366581)] Postorius version: 1.3.5 If someone can give a hint it will be much appreciated.

3 years, 10 months

Mailman 3 - Header Filter

by Thomas Lehker

I am a Mailman neophyte and need help with filtering posts based on the subject field. We have a few list owners that want 'Out of Office' replies discarded. When using the below syntax in Postorius/Header filter the post is not discarded but ends up in 'Held Messages'. Is there any syntax I am missing or a setting in the lists that needs to be disabled/enabled to get these posts dropped? Any help is much appreciated. Header: ^subject: subject: subject Pattern: Automatic Reply 'Automatic Reply' "Automatic Reply" Action: Discard DISCLAIMER: The information contained in this message is privileged and confidential. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the message and delete/destroy any copy of this message. Information in this message that does not relate to the official business of the firm shall be understood as neither given nor endorsed by it.

6 years, 3 months

Re: Alleviating confusion regarding"Subscription options" that are left unselected.

by Mark Sapiro

On 5/31/23 15:41, Mark London wrote: > > So instead I added the following line to the web page. Which is > displayed on other options setting web pages, but is not displayed when > you click "Manage Options" for a specific mailing list. I added this, > to the file list_options.html: > > <p>{% trans 'Any options displayed as not set here, inherit at runtime > from your global preferences (viewable on other tab)' %}</p> > <hr /> More correctly it should say "Any options showing as not set inherit at runtime from your global or address specific preferences (viewable on other tabs)" as it says, e.g., at https://lists.mailman3.org/mailman3/accounts/per-subscription-preferences/. > Although I had to fix the wording, as elsewhere it says: "Any options > showing as not set here have inherit at runtime.." That's been fixed. See https://gitlab.com/mailman/postorius/-/merge_requests/810 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

Re: Hyperkitty fulltext search performances

by Mark Sapiro

On 10/4/20 8:07 AM, Brian Carpenter wrote: > > On 10/4/20 8:59 AM, Loïc Dachary wrote: >> After a little digging it turns out the mailman3-web Debian GNU/Linux >> package I'm using is configured to use Woosh as a haystack backend. >> And it is not fit for volumes greater than a few hundred mega bytes. I >> should switch to something else from the list of supported >> backendshttps://django-haystack.readthedocs.io/en/master/backend_support.html >> > For our servers running Postorius/Hyperkitty, we use Xapian. I believe > the mailman-users (MM3) list also uses Xapian. It is a lot quicker. For > our Affinity/Empathy servers, we use Elasticsearch which we are very > happy with. Elasticsearch does have a higher memory requirement I > believe than Xapian. Brian is correct about this list. We started with Whoosh, then went to Elasticsearch and ultimately to Xapian. Each step gave better performance and a smaller footprint than the one before. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/accounts/XXXXX/login/

by Odhiambo Washington

Where XXXXX from the subject implies github|fedora|openid|gitlab, etc, I edited my settings.py and removed those references to socialaccount auth providers, except google: INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', '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', 'allauth.socialaccount.providers.google' ) On a daily basis, I get messages like below, referring to all those socialaccount auth providers that I removed. I am beginning to think that MM3 is reading a file other than that which I think it should. PS: I have restarted mailman, uwsgi, apache, and even the whole server. These messages just won't go away. Whole message here: Ubuntu Pastebin <https://pastebin.ubuntu.com/p/QPYDtXg5Fn/> -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 9 months

Setting for archiving multi email domains?

by Duane Raymond

Hi again, I have a Debian-postfix-postgres-nginx-Hyperkitty-Postorius setup with a primary domain (e.g. primarydomain.com) and several 'secondary' domains used for email lists (e.g. emaillistA.com and emaillistB.com) When sending emails to a list using the primarydomain.com address, the email is received, sent to subscribers and archived properly. But when it is sent to one of the secondary domains like tes(a)emaillistA.com - the email doesn't seem to be sent and isn't archived - despite it being set to be. What I've tried so far (after searching these archives and looking at the documentation) is to: 1) Adding emaillistA.com and emaillistB.com to the MAILMAN_ARCHIVER_FROM setting in the settings_local.py file (and then restart mailman) 2) Adding emaillistA.com and emaillistB.com to the mydestination setting in the postfix main.cf file (and the restarting postfix). ...I even tried adding to /etc/hosts 127.0.0.1 emaillistA.com and 127.0.0.1 emaillistB.com but removed it as it didn't seem appropriate there. Does anyone have any hits of what else I need to configure to get it working for these 'secondary' email domains? Cheers, Duane

4 years, 4 months

Re: Post-installation documentation?

by David Newman

On 11/24/21 2:36 PM, Mark Sapiro wrote: > On 11/24/21 9:40 AM, David Newman wrote: >> >> IMO post-installation docs for list admins would be a big help in >> Mailman3 adoption. I'm willing to help with this. > > > Thank you for being willing to contribute. I think the place for list > admin docs would be in the https://gitlab.com/mailman/mailman-suite-doc > project which is the source for https://docs.mailman3.org/en/latest/. > There is currently a userguide there at source/userguide.rst and > referenced from source/index.rst. the addition of an adminguide.rst > would be welcom if you want to work on that. Thanks, will get into this ASAP. Am happy to contribute once I acquire a bit more clue. > > >> When I say "working": I'm looking to migrate Mailman2 mailing lists to >> Mailman3, but am struggling with even basic setup tasks before we >> attempt list migtration. >> >> For example, on admin page I've set up two lists, one public and one >> private (each with unique list IDs), but neither appear in the site's >> list index. > > > Here are the steps to migrate a 2.1 list named `alist(a)example.com` and > its archives. > > run Mailman's `bin/mailman create alist(a)example.com` > > follow that with > ``` > bin/mailman import21 alist(a)example.com > /path/to/mailman2.1/lists/alist/config.pck > ``` > That will create the list and import its members and settings. > > To import archives run the Django admin command with arguments > ``` > hyperkitty_import -l alist(a)example.com > /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox Good up to here, but ... hyperkitty_import not found. This wasn't covered in the venv docs: https://docs.mailman3.org/en/latest/install/virtualenv.html or in the web frontend docs [1]: https://docs.mailman3.org/en/latest/config-web.html or in the howto Brian Carpenter (RIP) wrote for Debian 10: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 Also, I had previously created two other lists under the site admin page. These do not appear in the site's mailing lists page, nor does the list I successfully imported from MM 2.1 appear in the admin page, under mailing lists. > ``` > >> And I don't know where to add list members. > > > For imported lists, they are already added, but for new lists, you can > add them in Postorius under Mass operations -> Mass subscribe or via the > bin/mailman commands `addmembers` or `syncmembers`. See > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > > > >> And clicking the site archives link throws this error: >> >> django.urls.exceptions.NoReverseMatch: Reverse for 'hk_list_overview' >> with keyword arguments '{'mlist_fqdn': 'wheee'}' not found. 1 >> pattern(s) tried: ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/$'] > > > Did you specify the list's fqdn as in > https://www.example.com/archives/list/list@example.com/ No. I clicked the archives icon at the top of a Postorious page. This is possibly related to the hyperkitty_import issue above. Thanks again. dn [1] In addition to the web frontend docs, there is also a hyperkitty docs page: https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html I found this page unhelpful. For example it starts with this command: sudo python setup.py install but doesn't say where setup.py resides, or which directory the command should be run from. (And yes, different OSs use different locations. I'd setting for one being named, along with a YMMV disclaimer.) Then this doc goes to database setup, with this example: django-admin migrate --pythonpath example_project --settings settings Again, this is unclear. I don't know what "example_project" is, or in what context it's used here. This doc also describes a different, and less straightforward, import-from-2.1 procedure than Mark described above. It's possible the hyperkitty doc is now outdated. I'd be glad to help bring the various different install guides together and update them -- once I better understand how they work. Thanks.

3 years, 8 months

Re: Problems with New MM3 Installation

by Jeff

Thanks Mark and Abhilash (who responded separately). I have worked out all the issues I was having and now the list is running smoothly. The trick for POSTORIUS_TEMPLATE_BASE_URL with uwsgi was "http://[hostname]/mailman3/ <http://[hostname]/mailman3/>“. I appreciate all the help I’ve received from this mailing list. > On May 11, 2021, at 11:43 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/11/21 7:46 PM, Jeff wrote: >> >> I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: >> >> 1) some emails that arrived before I got the archive working are still sitting in: >> >> /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new >> >> Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a > collection of messages in maildir format. This is how the prototype > archiver stores messages. This has nothing to do with HyperKitty. It is > a separate archiver. If you don't want messages to be stored there, you > can disable the prototype archiver for the list by unchecking prototype > in Postorius -> Settings -> Archiving -> Active archivers or disable it > entirely for the installation by setting > ``` > [archiver.prototype] > enable: no > ``` > in mailman.cfg > >> 2) Some messages that arrived while I was having other problems with the setup have been stored in: >> >> /usr/local/mailman3/mm/var/queue/shunt >> >> What should I do to get these messages processed? > > > Assuming the issues that caused them to be shunted have been fixed, just > run the command > ``` > mailman unshunt > ``` > >> 3) Similar to above, some messages are in: >> >> /usr/local/mailman3/mm/var/queue/bad >> >> How can I get these messages processed? > > > First examine the messages with > ``` > mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> > ``` > To be sure you want them. Also examine mailman.log for the times they > were stored in the `bad` queue. You are looking for 'Skipping and > preserving unparseable message: <file>' and/or 'SHUNTING FAILED, > preserving original entry: <file> messages and you want to determine > which runner preserved the message. There may be a 'whichq' entry in the > message's metadata in which case, that's the answer. > > Once you have determined the queue, you can just move the .psv file from > the bad queue to the appropriate queue, renaming it from .psv to .pck in > the process. > > >> 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? > > > I know little about uwsgi. setting it to `uwsgi://localhost:8000` might > work. You could also set it to the base URL that a user would use to > access the web UI, e.g. `https://example.com` and that would presumably > be proxied to uwsgi. For example, on the server for this list we have > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' > ``` > which gets proxied to gunicorn, but the idea is the same. > > -- > 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/

4 years, 2 months

Mailman-users search results for query "Postorius"