Search results for "Postorius" - Mailman-users

Re: Digests not working correctly

by Joel Lord

The May 4th digest that went out was _also_ size-triggered, so this may have nothing to do with periodic digests at all, and possibly my periodic digests aren't working. I'm not on any of my own lists in digest mode, I'm slowly extracting diagnostic information out of people who are. Also, since this is a ~2 month cycle, it's really difficult to get data points to work with. I'll need to remember to go in and look when this settles down again (new cycle of activity started last night) to see if there's anything left pending. (venv) root@host2:/home/lists/mailman/venv/bin# pip freeze | grep -i hyper HyperKitty==1.3.7 On 6/4/2023 10:05 PM, Mark Sapiro wrote: > On 6/4/23 18:35, Joel Lord wrote: >> >> The periodic digests do seem to be coming out. I also now have >> confirmation that the one message in this morning's digest that was >> from May 4th was also included in the last digest back on May 4th, so >> it seems that the one message was left behind in the digest queue when >> the periodic digest was sent. > > I don't see how that can happen. The process that sends a digest renames > the var/lists/<list-id>/digest.mmdf mailbox file in which the messages > are accumulated to var/lists/<list-id>/digest.<volume>.<issue>.mmdf, > where <volume> and <issue> are the volume and issue numbers of that > digest, and then queues a message in the `digest` queue to tell the > digest runner to create the digest from the messages in that mbox and > send it. Thus, it leaves no var/lists/<list-id>/digest.mmdf mailbox file > behind and that is created anew when the next post arrives. Further, if > there is a non-empty digest.mmdf file, its messages should be sent no > later than the next 11 PM `cron digests`. > > >> There was one earlier message to the list back on May 4th, before the >> one that got duplicated, but I can't tell if that triggered a >> size-based digest to be sent: the logs aren't clear enough on that >> detail for me to tell > > > OK > > >> Just to inform things: >> >> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman >> django-mailman3==1.3.9 >> mailman==3.3.8 >> mailman-hyperkitty==1.2.1 >> mailman-web==0.0.6 >> mailmanclient==3.3.5 >> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper >> mailman-hyperkitty==1.2.1 > > Actually, it's HyperKitty, not hyperkitty, but I assume HyperKitty is up > to date as are the others. > >> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post >> postorius==1.3.8 >> >> > -- Joel Lord

1 year, 5 months

using SSH/TLS with external MTA

by Roland Giesler

I have managed thus far to get things working on my new install, but I need to use a secure logon to send mail from an external MTA. I have set up: /etc/mailman/mailman.cfg: smtp_host: box2.gtahardware.co.za smtp_port: 465 smtp_user: roland(a)giesler.za.net smtp_pass: <hidden> smtp_secure_mode: smtps smtp_verify_cert: no smtp_verify_hostname: no I'll get a cert installed later, for now just want to get it going. This error occurs when I try to create a new user in postorius. ERROR 2024-07-24 15:29:45,572 2150 django.request Internal Server Error: /accounts/login/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/utils/decorators.py", line 43, in _wrapper return bound_method(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/debug.py", line 89, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 146, in dispatch return super(LoginView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 74, in dispatch response = super(RedirectAuthenticatedUserMixin, self).dispatch( File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 102, in post response = self.form_valid(form) File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 159, in form_valid return form.login(self.request, redirect_url=success_url) File "/usr/lib/python3/dist-packages/allauth/account/forms.py", line 196, in login ret = perform_login( File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 175, in perform_login send_email_confirmation(request, user, signup=signup, email=email) File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 346, in send_email_confirmation email_address.send_confirmation(request, signup=signup) File "/usr/lib/python3/dist-packages/allauth/account/models.py", line 62, in send_confirmation confirmation.send(request, signup=signup) File "/usr/lib/python3/dist-packages/allauth/account/models.py", line 169, in send get_adapter(request).send_confirmation_mail(request, self, signup) File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 464, in send_confirmation_mail self.send_mail(email_template, emailconfirmation.email_address.email, ctx) File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 136, in send_mail msg.send() File "/usr/lib/python3/dist-packages/django/core/mail/message.py", line 284, in send return self.get_connection(fail_silently).send_messages([self]) File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 109, in send_messages sent = self._send(message) File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 125, in _send self.connection.sendmail(from_email, recipients, message.as_bytes(linesep='\r\n')) File "/usr/lib/python3.10/smtplib.py", line 901, in sendmail raise SMTPRecipientsRefused(senderrs) smtplib.SMTPRecipientsRefused: {'roland(a)giesler.za.net': (454, b'4.7.1 <roland(a)giesler.za.net>: Relay access denied')} However, the mailserver is in daily use and accept logon all the time. I believe I'm missing something that should be installed to make SMTPS (SSL) work, but what?

4 months

Re: Updating from Ubuntu-20.04 LTE installation

by Abhilash Raj

On Sat, May 23, 2020, at 8:28 PM, Mark Sapiro wrote: > On 5/23/20 7:02 PM, Peter Adebahr via Mailman-users wrote: > > > > Our installation was done by "apt-get install" in Ubuntu 20, thus still > > running MM 3.2.2 (and python 3.8.2). > > > > Do you have any advise, how to upgrade from there to your current > > version? I know this might be a bit dangerous, but with today's VMs the > > risk is much less than it used to be: > > > It shouldn't be difficult, but I can't give you details because I don't > know exactly how the Debian/Ubuntu package installs things. Also I don't > know whether "current version" refers to the 3.3.1 release or the head > of the https://gitlab.com/mailman/mailman master branch. > > > > Do you think it would be possible, just to replace the code and library > > parts, keeping the database and config files as is? > > > Yes. It should be fairly straightforward. You first need to find where > the Mailman Core package is. You should be able to just replace the > contents of the `mailman` package directory with ours. You may be able > to do this via pip > > pip install --upgrade mailman > > globally or within Mailman's virtualenv if it is installed in a virtualenv. This is probably not a good idea, global install quite often breaks a lot of stuff (Like I broke Yum on my work computer since I wanted something newer than 10yo python packages). A better idea would be to install Mailman from scratch inside a virtualenv somewhere in /opt/mailman and then letting it consume the same configurations. I think Ubuntu/Debian have their configurations in `/etc/mailman3/` and Mailman Core installed anywhere should just pick that up without any special work. Same goes for Postorius/Django stuff. You can switch to a different Django project and just point to Debian/Ubuntu's settings.py (location of which should be in README.debian of the Debian package I presume). > However, there are caveats. There are Debian patches at > <https://sources.debian.org/patches/mailman3/3.2.2-1/>. The big `0002` > patch replaces importlib_resources with importlib.resources because > importlib_resources is not available in Debian. Most of the patches > apply to tests, and for the actual working code, we fixed this > differently as of Mailman 3.3.1, so I don't think you need the Debian > patches. > > > -- > 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, Abhilash Raj (maxking)

4 years, 6 months

Hyperkitty issue(s)

by Bryan Loniewski

Hello -- I'm stuck trying to integrate Hyperkitty. I see the following errors in mailman.log and mailmansuite.log respectively: <snipped> [2020-05-27 16:42:11 -0400] [5140] [ERROR] Error handling request /3.1/lists/bry_test4.lists-test.rutgers.edu/archivers Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 134, in handle self.handle_request(listener, req, client, addr) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 175, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", line 269, in falcon.api.API.__call__ File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 406, in on_get for archiver in archiver_set.archivers File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 407, in <dictcomp> if archiver.system_archiver.is_enabled} File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/model/mailinglist.py", line 587, in system_archiver raise AssertionError('Archiver not found: {}'.format(self.name)) AssertionError: Archiver not found: hyperkitty and <snipped> Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/postorius/middleware.py", line 42, in __call__ return self.get_response(request) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/core/handlers/exception.py", line 36, in inner response = response_for_exception(request, exc) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/core/handlers/exception.py", line 90, in response_for_exception response = handle_uncaught_exception(request, get_resolver(get_urlconf()), sys.exc_info()) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/core/handlers/exception.py", line 125, in handle_uncaught_exception return debug.technical_500_response(request, *exc_info) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/views/debug.py", line 89, in technical_500_response reporter = ExceptionReporter(request, exc_type, exc_value, tb) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/views/debug.py", line 254, in __init__ self.template_info = getattr(self.exc_value, 'template_debug', None) File "/opt/mailman/mm/venv/lib/python3.6/tempfile.py", line 479, in __getattr__ file = self.__dict__['file'] KeyError: 'file' Note that I've kinda followed the Virtualenv route along with using Mark's helpful webpage re: his experiences. Some relevant? config files... mailman.cfg: <snip> [archiver.prototype] enable: yes [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg <snip> mailman-hyperkitty.cfg: [general] base_url: https://a_real_domain/mm3/hyperkitty api_key: <movealong> I can provide additional conf file setups if warranted? I am curious (and perhaps this is in fact the issue) why when I run mailman conf I don't see the archiver.hyperkittty section even though its in the mailman.cfg file? While at the same time I do see archiver.{mail_archive,mhonarc}? I know it's reading my mailman.cfg based on other sections I've already setup/manipulated. Another data point: $ grep -i hyperkitty requirements.txt HyperKitty==1.3.2 mailman-hyperkitty==1.1.0 Any suggestions? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator

4 years, 5 months

Re: HYPERKITTY_ATTACHMENT_FOLDER

by Ugnius S

Could You please confirm that this parameter should be placed in mailman-hyperkitty.cfg file? I have checked mailman/postorius/hyperkitty owner user can write files there and web user group has privileges to write and to read, but *no any files appear there*. Mailman works, it is possible to download attachments from hyperkitty. Mailman restarted, uwsgi restarted, runjobs restarted. No files in /full/path/to/folder/ File looks like: [general] base_url: https://flistserv.example.com/hyperkitty/ api_key: BlaBlabla HYPERKITTY_ATTACHMENT_FOLDER = /full/path/to/folder/ BR Ugnius 2019-09-11, tr, 21:21 Ugnius S <ugniusviln(a)gmail.com> rašė: > Thank You so much. > > 1) https://hyperkitty.readthedocs.io/en/latest/install.html > Close to the end before the "UPDATE" topic, chapter "Customization". > > 2) > https://buildmedia.readthedocs.org/media/pdf/hyperkitty/stable/hyperkitty.p… > Page 10, chapter 2.8 "Customization" > > BR > Ugnius > > 2019-09-11, tr, 20:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: > >> >> >> On Wed, Sep 11, 2019, at 9:52 AM, Ugnius S wrote: >> > Hi. >> > >> > Can anybody send example how to set it? It is mentioned in >> documentation, >> > but very vaguely. >> >> If you can point out where did you find it in docs, I can update it. >> Information is kind of duplicated in a few places. >> >> > HYPERKITTY_ATTACHMENT_FOLDER = /full/unix/path >> >> This is the right value. >> >> It is a path on the filesystem, where the user running Hyperkitty is >> allowed to write. >> >> > >> > HYPERKITTY_ATTACHMENT_FOLDER = http://localhost:8000/something >> > >> > HYPERKITTY_ATTACHMENT_FOLDER = ./var/data/something/ >> > >> > Has anybody experience of using this, maybe have recommendations of >> using >> > it? Better under project user or better under web content owner where >> the >> > static content is. I would like to store attachments separately to avoid >> > growing database. >> > Hyperkitty documentation: >> > By default, HyperKitty stores the email attachments in the database. >> If >> > you would rather have them stored on the filesystem, you can set the >> > HYPERKITTY_ATTACHMENT_FOLDER configuration value to a directory. >> > Make sure that the user running the Django process (for example, apache >> or >> > www-data) has the permissions to write in this directory. >> > >> > ------------- >> > _______________________________________________ >> > 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, >> Abhilash Raj (maxking) >> _______________________________________________ >> 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/ >> >

5 years, 2 months

Re: Newbie hyperkitty question

by Stephen Daniel

Thanks. Very helpful. On Tue, Jan 11, 2022 at 2:03 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/11/22 8:27 AM, Stephen Daniel wrote: > > Mailman users -- > > > > I am setting up a new mailman3 installation, and this is my first > > experience with the suite. All of the software is up and running, but I > > cannot tell if hyperkitty is actually running. > > > In Postorius, in the list's `info` view can you click the Archives > button and see archived messages? That's HyperKitty. > > If the messages aren't there with the hyperkitty archiving option > enabled, check `mailman.log` for why. > > Also do messages from the list have an Archived-At: header? > > > > When I look at my test mailing list, two archive options are available, > > hyperkitty and "prototype", and both are enabled. I can see that my > email > > is being archived, but I think "prototype" is what is doing the > archiving. > > I see that a test message will end up in > > > /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... > > and nowhere else. This suggests that "prototype" is archiving, but > > hyperkitty is not. > > > No this says the prototype archiver is working. It says nothing about > Hyperkitty. > > > > So, this opens up a raft of questions on hyperkitty: > > > David Newman has answered some of this, but ... > > > > - How do I tell if hyperkitty is actually running? > > > It doesn't actually run. it is a Django web UI and a web API that serves > things on request. > > > > - Does hyperkitty have a web-UI for admins or users? How would I > access > > it? > > See above. > > > > - I can not find any documentation on hyperkitty, other than > > installation instructions and change logs. Does documentation exist? > > No, not really. > > > > - How do I set policies on how long archives are kept? > > - Assuming I want to back up my archives, what do I need to back up? > > > Messages are kept forever unless you do something to delete them. > HyperKitty's messages are stored in the database configured in the > DATABASES setting in your Django settings. How you backup the database > depends on the database manager. You already found the prototype > archiver's messages. > > > -- > 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/ >

2 years, 10 months

Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

Help! Regards Onyeibo On Thu Oct 13, 2022 at 6:03 AM WAT, Onyeibo Oku wrote: > On Wed, 12 Oct 2022 17:52:47 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: > > Thanks Eggert and Sapiro. > > > > > As Eggert suggests, see > > https://docs.mailman3.org/en/latest/install/virtualenv.html and > > follow that. > > I already started out on the above route. Its an adaptation because I > am running Fedora. I had no problem with system-wide installations via > dnf package management. However, some parts of the documentation does > not add up. > > > You don't need to download the source from GitLab. > > Following that doc will get the latest releases from PyPI via pip. > > Those are still somewhat out of date - we really should make new > > releases - so if you want the latest from GitLab, there are a couple > > of ways to do it. Perhaps the easiest is to just run the various `pip > > install` commands as documented and then upgrade Mailman core in your > > venv with ``` > > pip install --upgrade git+https://gitlab.com/mailman/mailman@master > > ``` > > and update the various mailman web packages with > > ``` > > pip install --upgrade git+https://gitlab.com/mailman/xxx@master > > ``` > > where xxx is mailman-web, mailman-hyperkitty, django-mailman3, > > postorius, hyperkitty. I.e., run it 5 times, once for each value of > > xxx. > > > > I will come to this eventually (assuming that does not break things > later). I aim to get it all working with regular pip packages first. I > have installed mailman core already. > > Fedora expects mailman files to reside at /usr/lib/mailman. It appears > to ship with a mailman unix user. I adapted to those system defaults. > > Now I observe that "su - mailman" gives me the proper prompt but > .bashrc doesn't kick in. I still have to manually change to the > virtual environment despite setting the automatic change in .bashrc. > However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". > Is this normal? > > Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which > should correspond to "/usr/lib/mailman/mm/var/*" on my instance. > However, I don't see any instructions on how to get the "/mm" folder > and the associated sub-folders. I just have "/usr/lib/mailman" > > I am lost > > "pip list" within the venv environment confirms that I have "mailman > 3.3.5". What am I missing? > > Regards > Onyeibo > > > _______________________________________________ > 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/

2 years, 1 month

Re: Missing Base64 encoding from control message reply

by Jana Berger

On 22.09.2023 18:32, Stephen J. Turnbull wrote: > lists-mailman3(a)janaberger.de writes: > > > I have a setup with GNU Mailman 3.3.8 where a user tried to > > subscribe. When replying to the "confirm" message, the user > > received a completely garbled response, like so: > > > > N?z?????zf???&???j?????u?[zZ0:???v???,j?z???k?e?0 > > > 4D???r?^b??r?????*'???y????{ax?L?X????0:???v???,j?z???k?d?m?-???zz?rn??l]y+???-E?( > > > ?^N??'??M???t???Mz?????^i?????}?o?\????6sN?zf??????r??z?????????b?{h?????f?r?ne== > > To diagnose, we really need to see that in context of the raw message > as received by the user. You can see the same or similar result by opening the EML I quoted. Does the list support attachments? Then I will attach the file directly. > > > The user then forwarded the .eml file to me, which clearly shows > > the contents of the mail as plain text while being announced as > > base64 (Content-Transfer-Encoding: base64): > > It also clearly doesn't show anything like the mojibake above. What > is the relation between the two? Sorry, I should have made that clearer - when opening the EML file with e.g. Thunderbird, the contents (message text) of the mail as displayed is the garbled string. I assume it is the result of Thunderbird trying to process the contents as base64-encoded, which it is not. > > While the problems could be related to Mailman, it could also be any > MTA along the way or the user's mail client. > > I suspect that the .eml file has been significantly altered by > intervening software. As far as I know, the Python email package does > not MIME-encode plain ASCII text as you see in the email's subject. I have multiple control messages, all received from my instance which all contain the "Content-Transfer-Encoding: base64" marker, their contents is plain text (Content-Type: text/plain; charset="utf-8"), but they are still encoded using base64. Of course that is not proof, but an indication that it is either done by the mail server itself or widely across MUAs. > > The only other thing I can think of is it might have something to do > with your internationalization settings. What is the default language > of the list? (This is available in Postorius.) Have you changed the > default encoding for English on your site? (I think you need to look > in mailman.cfg for this.) What is the default language of the site? Global "Preferred language" is "English (USA)", which is not overridden by the list in question. I have not changed the default encoding. Is there a surefire way to detect this? My mailman.cfg has no section pertaining to encoding, and all related files also do not mention encoding.

1 year, 2 months

Re: Archive not updated

by Marc SCHAEFER

Hello, On Mon, Sep 02, 2024 at 09:08:09AM -0000, mailman3--- via Mailman-users wrote: > Debian bookworm Archival works here. Here is my simplified auto-deployement script (some might not be useful to you, I am using a local Postfix): PS: replace services_install by apt-get install djangoauth=@@@REPLACE # this is a bash array: server, user, pw psqlauth=@@@REPLACE services_install postfix (while read line do case $line in *=*) postconf -e "$line";; *) echo "TOSSING: $line" >&2;; esac done) <<EOF myhostname = $lists mydestination = $lists mynetworks = 127.0.0.0/8 inet_protocols = ipv4 inet_interfaces = all transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = hash:/var/lib/mailman3/data/postfix_domains relayhost = @@@REPLACE EOF cat >> /etc/aliases <<EOF postorius: root www-data: root root: ${djangoauth[1]} EOF newaliases services_install dbconfig-pgsql cat > /etc/dbconfig-common/mailman3.conf <<EOF dbc_install='true' dbc_upgrade='true' dbc_remove='false' dbc_dbtype='pgsql' dbc_dbuser='${psqlauth[1]}' dbc_dbpass='${psqlauth[2]}' dbc_dbserver='${psqlauth[0]}' dbc_dbname='mailman' dbc_dbadmin='postgres' EOF sed < /etc/dbconfig-common/mailman3.conf \ > /etc/dbconfig-common/mailman3-web.conf \ "s/^dbc_dbname=.*/dbc_dbname='mailmanweb'/" chmod 600 /etc/dbconfig-common/mailman3.conf \ /etc/dbconfig-common/mailman3-web.conf services_install mailman3-full mailman3-web sed --in-place "s/^site_owner: .*/site_owner: ${djangoauth[1]}/" \ /etc/mailman3/mailman.cfg # archiving mails from mailing-lists automatically cat >> /etc/mailman3/mailman.cfg <<'EOF' [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg [styles] default: private-default EOF # enable archiver key sed -i "s%^api_key:.*%api_key: $(egrep MAILMAN_ARCHIVER_KEY /etc/mailman3/mailman-web.py | awk '{print $NF;}' | sed "s/'//g")%" /etc/mailman3/mailman-hyperkitty.cfg # work-around: SQLAlchemy no longer supports "postgres" sed --in-place "s%^url: postgres://%url: postgresql://%" \ /etc/mailman3/mailman.cfg sed --in-place "s/.*'Mailman Suite Admin', 'root@localhost').*/('Mailman Suite Admin', '${djangoauth[1]}'),/;s/^EMAILNAME\s*=.*/EMAILNAME = '$lists'/;/django_mailman3.lib.auth.fedora/d" /etc/mailman3/mailman-web.py # aliases mailman <-> postfix mkdir -p /var/lib/mailman3/data chown list:list /var/lib/mailman3/data for i in postfix_lmtp postfix_lmtp postfix_domains do touch /var/lib/mailman3/data/$i postmap /var/lib/mailman3/data/$i done chown list:list /var/lib/mailman3/data/postfix_* # work-around for django_q # (does not seem to work, and DEFAULT_AUTO_FIELD should be also # configured to django.db.models.BigAutoField) dpkg-divert --rename /usr/lib/python3/dist-packages/django_q/conf.py sed < /usr/lib/python3/dist-packages/django_q/conf.py.distrib \ > /usr/lib/python3/dist-packages/django_q/conf.py \ 's%TIMEOUT = conf.get("timeout", None)%TIMEOUT = conf.get("timeout", 59)%' pkill -e -2 --full 'python3 manage.py qcluster' || true # fix example.com PGPASSWORD=${psqlauth[2]} psql -h ds-services-psql -U ${psqlauth[1]} mailmanweb -c "UPDATE django_site SET domain = '$lists', name = '$lists' WHERE id = 1" # workaround required? #chgrp list /var/lib/mailman3/locks/ #chmod g+rwx /var/lib/mailman3/locks/ chgrp list /var/log/mailman3/*.log # https://docs.djangoproject.com/en/3.0/ref/django-admin/#django-admin-create… env DJANGO_SUPERUSER_PASSWORD=${djangoauth[3]} \ DJANGO_SUPERUSER_USERNAME=${djangoauth[2]} \ DJANGO_SUPERUSER_EMAIL=${djangoauth[1]} \ mailman-web createsuperuser --noinput \ || echo "django super user already exists in DB, ignored" # then I migrate the lists

2 months, 2 weeks

Re: Can creating too many Django accounts crash Mailman3 server?

by Abhilash Raj

On Tue, Sep 15, 2020, at 12:09 AM, Stephen J. Turnbull wrote: > Mohsen Masoudfar writes: > > > It seems anybody can go to the site: > > https://LISTSERVNAME/mailman3/postorius/lists/ > > and click on the [Sign up] on the top-right corner and create an > > account. > > Yes. > > > This can easily be automated, even though the next step, confirming > > the email address, being ignored. I believe it can be used as a > > target for a DOS attack by creating so many accounts, that > > eventually causes an 'out of space' error. > > > > Is this a justified concern? > > "Justified" depends on who you think the attacker is. Theoretically > it's a real possibility, but the space used by an unverified account > is not large. I suspect there are always much more painful DoS > attacks to worry about. > > > Is there a way to manage this feature in a secure way? > > In some sense, I don't think there is. The point of the feature is to > allow anybody to sign up without authentication beyond having a usable > email address. Either you allow the DoS attack or anything you do is > likely to deny service to legitimate users. > > Brian's approach (cron job purging unverified users) is generally good > hygiene, but I don't think it would do much against an deliberate > attack. And it shouldn't be hard to automate the confirmation > process. I guess you could handle that by purging accounts with no > subscriptions or other roles on any lists, but that might annoy a few > legitimate users. > > Probably the best you could do for an open server would be to throttle > user creation to say 1 per minute (adjustable to the scale of your > site). > > I don't know if there is currently a way to require admin approval for > account creation (as opposed to list subscription). Perhaps we should > add that if we don't have it. I checked django-allauth, it doesn't have a feature like that. We could implement something on-top of that to optionally allow for admin approval but some other details would need to be figured out and would be a sizeable task involving a new view for account approvals. We potentially also would have to modify the models used in django-allauth to add the flag for "approved", which I am not sure would be an easy task to figure out. Perhaps, it might be easier to make a feature request and implement it in django-allauth though. > > Steve > _______________________________________________ > 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, Abhilash Raj (maxking)

4 years, 2 months

Mailman-users search results for query "Postorius"