Search results for "Postorius" - Mailman-users

Re: User integration with Django application

by Abhilash Raj

On Sat, Sep 21, 2019, at 12:06 PM, Victoriano Giralt wrote: > Hi! > > Is there a way to integrate Mailman3 user database with an already existing > Django application? And then, generate the list roster with a subset of > those users. > > I've been scavenging the archives and failing to find an answer. You can set AUTH_USER_MODEL = 'customauth.MyUser' From Django's docs at https://docs.djangoproject.com/en/2.2/topics/auth/customizing/#specifying-c… Postorius and Hyperkitty should be able to use this user model, in theory. No one has tried this yet and there could be things that don't work. Although, I would be happy to accept any patches should there be any bugs related to this. Abhilash > Thanks! > -- > Victoriano Giralt CIO > University of Malaga > +34952131415 SPAIN > ================================================================== > Note: signature.asc is the electronic signature of present message > A: Yes. > > Q: Are you sure ? > >> A: Because it reverses the logical flow of conversation. > >>> Q: Why is top posting annoying in email ? > > _______________________________________________ > 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/ > > > *Attachments:* > * signature.asc -- thanks, Abhilash Raj (maxking)

5 years, 8 months

Re: Cloned mailman3 from the gitlab site, having issues locating the mailman3 file to start it

by Mark Sapiro

On 5/17/24 12:06 PM, Keith Christian wrote: > The path to the mailman3.py file is: > /home/mailman3/mailman/src/mailman/bin/mailman.py > I created a mailman3 user, then, set the ownership on all directories > and files in /home/mailman3 and below to mailman3:mailman3. You need to install all the dependencies and also have /home/mailman3/mailman/src/mailman in your PYTHONPATH. If you just want Mailman Core and given that you've already cloned it from gitlab, I suggest creating a Python virtual environment as the mailman3 user with `python3 -m venv /path/to/your/venv` and then as the mailman3 user activate the venv, `source /path/to/your/venv/bin/activate`, and do `pip install /home/mailman3/mailman` to install Mailman and it's dependencies in the venv. Then you can just run `mailman info`. I suggest a venv for this to isolate the dependencies from things that might already be installed system wide with differing versions. To install the whole suite including the Postorius web UI for list management and the HyperKitty archiver, see https://docs.mailman3.org/en/latest/install/virtualenv.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

Re: how do I bulk-remove users from ML in MM3?

by tlhackque

On 25-Oct-17 12:05, Simon Hanna wrote: > Postorius is currently using this to mass unsubscribe. > AFAIK there is an open issue in core to add such functionality Yes, see https://gitlab.com/mailman/mailman/issues/419 Yes, the current API has a number of scaling issues. Delete is bad, but other operations can require multiple API calls... (e.g. get state to conditionally create; create+patch; create user+create subscription, ...) https://gitlab.com/mailman/mailman/issues/367 (and others) Mass modify is also missing - https://gitlab.com/mailman/mailman/issues/241 notes one such case. > On October 25, 2017 5:59:46 PM GMT+02:00, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >> On 10/25/2017 07:35 AM, Barry Warsaw wrote: >>> On Oct 25, 2017, at 03:08, Dmitry Makovey <dmakovey(a)stanford.edu> >> wrote: >>>> I just realized that "mailman members" only offers to "add members" >> via >>>> "-a filename" but I see no remove option. >>> It’s true, `mailman members` doesn’t currently have a —remove option. >> I found Rest API call for single user removal but I am questioning it's >> effectiveness given that I need to use this operation to potentially >> remove 1500 members >> >> -- >> Sr System and DevOps Engineer SoM IRT

7 years, 7 months

Re: Message-Footer after migrating to Mailman3

by Stephen J. Turnbull

Peter Münster writes: > On Thu, Sep 01 2022, Stephen J. Turnbull wrote: > > I'm not very familiar with Django's handling of such files, > > I don't think, that Django is involved here. Ah, you're right. My GSoC student is working on Postorius so I have Django on the brain. > My language setting is "fr", so I've copied templates/site/en > templates/site/fr and now it works. > > So no real problem, but the question remains: why did it not work > with "en"? The template to be used is determined by the language setting of the user, or the default if the user is anonymous. You have to repeat the process with all of the templates that might be used on your system due to users' language settings. Presumably it *would* have worked for any user whose language setting was "en". But if you do have "de" users, you'll need to replace the "de" template as well. If you mean that you switched your language setting to "en" or have an "en" user, and tested it, we can take a look at it, but as I understand the situation, you have a "fr" setting so you saw the "fr" template. Steve

2 years, 9 months

Re: mailman import21 passwords

by Mark Sapiro

On 9/16/24 16:25, Sam Darwin via Mailman-users wrote: > > Why can't passwords be imported from mailman2 to mailman3? How difficult would it be to do? > (is there a link to where this is already explained? ) Mailman 3 users have a _password attribute which isn't actually used for anything. The importer used to set this from the MM 2.1 member's password, but this was dropped by <https://gitlab.com/mailman/mailman/-/merge_requests/565>. See <https://mail.python.org/archives/list/mailman-developers@python.org/thread/…> for a discussion of this. Also note that since member passwords were stored in plain text in MM 2.1 and periodically emailed, those passwords are inherently not secure and have possibly been exposed so setting that password, even though encrypted in MM 3, is not a good idea. As far as creating a Django user for an imported member, whether or not with the member's MM 2.1 password, it is at least as expensive as just encrypting the password and would result in poor performance. Further, and perhaps more importantly, Mailman 3 is modular. There is no guarantee that any Mailman Core installation into which a MM 2.1 list is imported actually also supports Django users for Postorius and/or HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/4/22 11:15, gordon(a)dickens.com wrote: > > 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /mailman3/postorius/lists/members.georgiajets.org/ HTTP/1.1" 404 282 > 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /favicon.ico HTTP/1.1" 200 318 > > So, I get File Not Found error 404 for the web page but the favicon.ico file appears to be found successfully. Therefore, I suspect that my apache configuration file for mailman3 may be at the source of my problems and specifically the alias for the static directory. Here is my apache configuration file: It's not the alias for static > Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > # ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost > </IfModule> It's the fact that ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost is commented out. This should not be commented assuming you are using uWSGI and it is listening on the socket /run/mailman3-web/uwsgi.sock -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Re: [Mailman-Developers] Docker files for mailman

by Danil Smirnov

Okay I've found that image can be built if you base on Ubuntu Trusty distro (line 6 of the Dockerfile: "FROM ubuntu:trusty") and add ruby-sass to the set of packages to install (line 13: "apt-get install -y git python3-dev python3-pip python-dev python-pip python-virtualenv ruby-sass"). I'm not sure whether I need to change it in the Wiki... On 18 November 2016 at 16:08, Danil Smirnov <danil(a)smirnov.la> wrote: > Hi Simon! > > I've just tried to build docker image from the Dockerfile mentioned on page > https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile > > The building has stopped with the following error > > Installing mailman. >> The executable python3.4 (from --python=python3.4) does not exist >> /tmp/tmpez1ftK/run: 2: /tmp/tmpez1ftK/run: /mailman3/mailman-bundler/venv-3.4/bin/pip: >> not found >> While: >> Installing mailman. >> >> An internal error occurred due to a bug in either zc.buildout or in a >> recipe being used: >> Traceback (most recent call last): >> File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py", >> line 1995, in main >> getattr(buildout, command)(args) >> File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py", >> line 666, in install >> installed_files = self[part]._call(recipe.install) >> File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py", >> line 1410, in _call >> return f() >> File "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0. >> 11-py2.7.egg/collective/recipe/cmd/__init__.py", line 56, in install >> self.execute() >> File "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0. >> 11-py2.7.egg/collective/recipe/cmd/__init__.py", line 69, in execute >> run_commands(cmds, self.shell) >> File "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0. >> 11-py2.7.egg/collective/recipe/cmd/__init__.py", line 39, in run_commands >> check_call('%s %s' % (shell, tmpfile), shell=True) >> File "/usr/lib/python2.7/subprocess.py", line 541, in check_call >> raise CalledProcessError(retcode, cmd) >> CalledProcessError: Command 'sh /tmp/tmpez1ftK/run' returned non-zero >> exit status 127 >> The command '/bin/sh -c buildout' returned a non-zero code: 1 >> > > Do you have any clue what happens? > > Danil > > > On 17 July 2016 at 20:06, Simon Hanna <simon.hanna(a)serve-me.info> wrote: > >> Hi, >> >> I started working on docker files for Mailman. >> >> I created three repositories: >> - https://github.com/simonsmiley/postorius-docker >> Holds the files needed to create a postorius container >> - https://github.com/simonsmiley/mailman-docker >> Holds the files needed to create a core container >> - https://github.com/simonsmiley/mailman-compose >> Holds docker-compose files that greatly simply the process of running >> the containers >> >> * The mailman repo currently lacks documentation >> * Currently no emails can be sent. >> I still have to figure out what the best way is... >> * Hyperkitty will be added next >> (together with a complete "bundler" install) >> >> >> I pushed two images to the docker hub. Their names are >> thelinuxguy/postorius and thelinuxguy/mailman >> >> I created two organizations >> mailman on docker hub and gnu-mailman on github >> https://github.com/gnu-mailman >> https://hub.docker.com/u/mailman/ >> >> I know we shouldn't use github, but there is no way around >> github/bitbucket for automated builds on docker hub. >> >> I post here to inform you about the docker images and I also to ask if >> I'm allowed to keep these two organizations and move my images/repos >> there. I'll happily give push/owner access to additional people if >> requested. >> >> The repositories could be mirrored to the gitlab mailman group, >> sadly the process doesn't work the other way round just yet. >> >> In case this request gets denied, I'll just remove the organizations and >> let the images be "unofficial". >> >> cheers, >> Simon >> _______________________________________________ >> 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/ma >> ilman-developers%40python.org/ >> Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/ >> danil%40smirnov.la >> >> Security Policy: http://wiki.list.org/x/QIA9 >> > >

8 years, 7 months

Re: List users from different domains getting blocked.

by Mark Sapiro

On 12/14/23 14:19, bob B via Mailman-users wrote: > I am running MM3 and have a list that has users from different organizations and email domains. > > So let's say I am orga.com and hosting mailman > Bill is borg.com > Cindy is mew.com > > When Bill sends a message to my MM3 list it gets sent out, However, cindy's email system rejects it cause it sees the message is sent from Bill(a)borg.com but it came from my MM3 server which is under orga.com, so it rejects it. You need to apply DMARC mitigations. Normally mitigations are only applied if the From: domain publishes DMARC p=reject or p=quarantine, but recently this has become problematic. For example, gmail.com pubpishes DMARC p=none yet google servers effectively apply p=reject to mail From: gmail.com. Mailman >= 3.3.9 and Postorius >= 1.3.9 allow setting dmarc_addresses to a list of email addresses and regexps matching addresses and domains to which DMARC mitigatations will be applied regardless of puublished policy. For older releases and for cases where domains are not known in advance one can always set dmarc_mitigate_unconditionally True to apply mitigations to all mail. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

Re: Invalid FilterAction: discard. Treating as discard

by Mark Sapiro

On 5/8/19 4:45 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: > >> I'll post a follow-up with how to change pass_types via mailman shell >> when I work it out. > > Look forward to that, thanks. OK. in mailman shell with your list as 'm' >>> list(m.pass_types) ['multipart/mixed', 'multipart/alternative', 'text/plain'] >>> m.pass_types = ['multipart', 'text/plain', 'text/html'] >>> commit() >>> list(m.pass_types) ['multipart', 'text/plain', 'text/html'] >>> If you want to allow text from forwarded messages, add 'message/rfc822' in the pass_types list above. This setting will allow inspection of all elementary parts within any multipart parts ant will accept only text/plain and text/html. Then if collapse_alternatives is True (settable here or in Postorius), any multipart/alternative parts will by replaced by the first, presumably text/plain, sub-part. Finally, if convert_html_to_plaintext is True (settable here or in Postorius), any remaining text/html parts will be converted to plain text by lynx or whatever is configured as html_to_plain_text_command in mailman.cfg. This will ensure that filter_action is applied only to those messages which have no text/plain or text/html parts. -- 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: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Hi Mark, Any suggestions over my earlier email? I am waiting for your reply. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Oct 27, 2020 at 1:16 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > Hi Mark, > > Thank you for your help. I have traced the versions of > different components of mailman 3. I am downloading through GIT LAB because > I need to modify the code according to my organization's requirements like > to add SMS notifications when a mail is waiting for pending approval and so. > > With your help, I have found out the commits I am using in my > environment. I got them using the way you suggested "git log". That may be > helpful for you to help dummies like me. > > *### Mailman Core Version ###* > > *commit 437cb49ffc29ef8960ef26d18bd883ed5aa61ded* > *Merge: 98cf97b 0bca998* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Thu Oct 15 14:02:36 2020 -0700* > > * Merge branch 'template' into 'master'* > > * Clarify the posting instruction in the list welcome message.* > > * See merge request mailman/mailman!723* > > *### django-mailman3 Version ###* > > *commit d9e675e5cc1b966f9cd02b2e492649972f8ddc40* > *Merge: ea2b33a c091e43* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 00:40:51 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use GHCR for the CI image* > > * See merge request mailman/django-mailman3!108* > > *### Hyperkitty Version ###* > > *commit 36f43466763c2686cf4d69c982ea64b956c30939* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Mon Oct 5 04:54:44 2020 +0000* > > * Use GH registry to pull CI image.* > > *### Mailmanclient Version ###* > > *commit aaa529808e2d61899f90509da4ea802a70d2c8ff* > *Merge: ff39dd8 8670751* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 01:09:32 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use GHCR for the CI image* > > * See merge request mailman/mailmanclient!130* > > *### Mailman Hyperkitty Version ###* > > *commit 87db8b03cc4ceba8ef8eafedeaaf11f99f2e50e0* > *Merge: 35ff801 04deff5* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Fri Jun 19 18:15:57 2020 +0000* > > * Merge branch 'fix_25' into 'master'* > > * Add a test for the presence of surrogates in the stringified message.* > > * Closes #25* > > * See merge request mailman/mailman-hyperkitty!7* > > *### Mailman-suite Version ###* > > *commit 3b8780f26d544cb333970eae43ccffc7e34314aa* > *Merge: 74e7927 4463b31* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Sat May 30 00:32:40 2020 +0000* > > * Merge branch 'doc_mb4' into 'master'* > > * Added comment about OPTIONS = {'charset': 'utf8mb4'} to settings.py.* > > * See merge request mailman/mailman-suite!8* > > *### Postorius Version ###* > > *commit 02e3183c3cd9e069d8d886426b76b08504ea5e1e* > *Merge: 61242d2 321310c* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 00:43:14 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use the GHCR registry for CI image.* > > * See merge request mailman/postorius!549* > > I have removed only mailmanclient and re-cloned it from gitlab and > ran the python setup.py develop command. But still the same error. > > Is there anything else I can do to get rid of that error. > > Thanks in advance. > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_6854939421424022049_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Tue, Oct 27, 2020 at 6:56 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: >> > >> > How to find out the versions of the each and every component >> > of the mailman 3 like mailman core, mailmancilent, postorius, >> > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, >> > after installation? >> >> >> cd to the directory in which you cloned the gitlab project for the >> component and do `git log` >> >> >> > If I am running an old mailmanclient or older version of any >> > other mailman component, please suggest how to upgrade either one or >> > multiple components based on the requirement. Is there any link that >> > would help me to upgrade ? >> > >> > I have used the >> > link https://docs.mailman3.org/en/latest/devsetup.html to install the >> > mailman 3 components. I expected that the procedure followed in this >> > link would install the latest versions of the mailman 3 components. >> > Please correct me if I am wrong. Is there any latest version >> > compatibility table ? >> >> >> If you installed each of mailman, mailmanclient, django-mailman3, >> postorius and hyperkitty according to instructions like >> >> $ cd ~/mailman >> $ git clone https://gitlab.com/mailman/mailmanclient.git >> >> Then set up mailmanclient: >> >> $ cd mailmanclient >> $ python setup.py develop >> $ cd .. >> >> from that document, you should have the latest version. If that is the >> case, `git log` in the mailmanclient directory should begin like >> >> commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, >> origin/master, origin/HEAD) >> Merge: ff39dd8 8670751 >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Thu Oct 15 01:09:32 2020 +0000 >> >> Merge branch 'fix-ci' into 'master' >> >> Use GHCR for the CI image >> >> See merge request mailman/mailmanclient!130 >> >> commit 8670751caff689733751ef323ef521c4a3fa1237 >> Author: Abhilash Raj <raj.abhilash1(a)gmail.com> >> Date: Wed Oct 14 17:36:58 2020 -0700 >> >> Use GHCR for the CI image >> >> commit ff39dd8f03a820f442f2251553c444370df3b914 >> Merge: 80ebed4 76d44e1 >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Fri Aug 7 19:35:05 2020 +0000 >> >> Merge branch 'invite' into 'master' >> >> Add support for inviting an email address to join a list. >> >> See merge request mailman/mailmanclient!129 >> >> or if you did this before Oct 15, maybe it starts with >> commit ff39dd8f03a820f442f2251553c444370df3b914 >> >> The particular commit you need for your issue is >> >> commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 >> Merge: c8dcb1e 28d1c3a >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Sat May 16 08:02:21 2020 +0000 >> >> Merge branch 'held-count' into 'master' >> >> Add a new get_held_count() API to get a count of held messages. >> >> See merge request mailman/mailmanclient!122 >> >> >> >> Note that unless you intend to do actual development of Mailman 3, you >> should be following >> <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather >> than <https://docs.mailman3.org/en/latest/devsetup.html>. >> >> -- >> 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/ >> > > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 7 months

Mailman-users search results for query "Postorius"