Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Can't add emails to accept_these_nonmembers

by Ibiam Chihurumnaya

Mark Sapiro wrote: > On 2/25/26 2:43 PM, Ibiam Chihurumnaya via Mailman-users wrote: > > I need to set some nonmembers to a list as these members send message to the list, but don't need to receive any message from the list. > > I've used list_name.settings['accept_these_nonmembers'].append to add members to the list, but it gets discarded once I run list_name.settings.save(). accept_these_nonmembers is a list hence the append, I didn't add the argument to append, maybe that's what caused the confusion. > > I don't understand what you are doing. The above makes no sense to me. > Please provide more detail on exactly what it is you are doing. > However, accept_these_nonmembersis an artifact from Mailman 2.1 and > only exists in Mailman 3 to support patterns as opposed to individual > email addresses. > In Mailman 3, there are two ways to accomplish this. One way is to > subscribe the user as a member and set the member's delivery to > disabled. The other way is to add the user as a nonmember and set the > nonmember's moderation_action to default processing. I had done the members part in the past, but the issue with it was I wanted certain members to not receive messages from the list, but only send to the list. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: "Must issue a STARTTLS command first" issue during social login 'send_email_confirmation'

by Mark Sapiro

On 12/17/19 3:05 AM, jean-christophe manciot wrote: > Ubuntu 20.04 > mailman3 3.2.2-1 > postfix 3.4.7-2 > > ```/etc/mailman3/mailman.cfg``` > ``` > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > smtp_host: localhost > smtp_port: 25 > smtp_user: user > smtp_pass: 'password' > smtp_secure_mode: SecureMode.STARTTLS > lmtp_host: 127.0.0.1 > lmtp_port: 9024 > configuration: python:mailman.config.postfix > ``` > The ```smtp_secure_mode``` value is based on https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/connection.ht…. > I am able to send emails using a mail client located on a remote device with the same user/password credentials. > Yet, trying to perform a social login leads to: > ``` > ERROR 2019-12-17 11:44:00,414 211904 django.request Internal Server Error: /accounts/github/login/callback/ > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner > response = get_response(request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/lib/python3/dist-packages/allauth/socialaccount/providers/oauth2/views.py", line 73, in view > return self.dispatch(request, *args, **kwargs) > File "/usr/lib/python3/dist-packages/allauth/socialaccount/providers/oauth2/views.py", line 143, in dispatch > return complete_social_login(request, login) > File "/usr/lib/python3/dist-packages/allauth/socialaccount/helpers.py", line 152, in complete_social_login > return _complete_social_login(request, sociallogin) > File "/usr/lib/python3/dist-packages/allauth/socialaccount/helpers.py", line 167, in _complete_social_login > ret = _login_social_account(request, sociallogin) > File "/usr/lib/python3/dist-packages/allauth/socialaccount/helpers.py", line 55, in _login_social_account > signal_kwargs={"sociallogin": sociallogin}) > File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 144, in perform_login > send_email_confirmation(request, user, signup=signup) > File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 312, in send_email_confirmation > signup=signup) > File "/usr/lib/python3/dist-packages/allauth/account/models.py", line 60, in send_confirmation > confirmation.send(request, signup=signup) > File "/usr/lib/python3/dist-packages/allauth/account/models.py", line 166, in send > get_adapter(request).send_confirmation_mail(request, self, signup) > File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 450, in send_confirmation_mail > ctx) > File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 137, in send_mail > msg.send() > File "/usr/lib/python3/dist-packages/django/core/mail/message.py", line 291, in send > return self.get_connection(fail_silently).send_messages([self]) > File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 110, in send_messages > sent = self._send(message) > File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 126, in _send > self.connection.sendmail(from_email, recipients, message.as_bytes(linesep='\r\n')) > File "/usr/lib/python3.7/smtplib.py", line 867, in sendmail > raise SMTPSenderRefused(code, resp, from_addr) > smtplib.SMTPSenderRefused: (530, b'5.7.0 Must issue a STARTTLS command first', 'user@mysite') > ``` > Any suggestion? I don't know the answer offhand, but this is Django encountering the issue and it appears that Mailman core for which the mailman.cfg [mta] settings and the doc to which you refer apply is not involved at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Mailman3 stopped working after Upgrade to Ubuntu 21.04

by Mark Sapiro

On 8/8/21 4:41 AM, Thomas Möhle via Mailman-users wrote: > Hey Mark, > > thanks for your reply!> In what way? Do list posts get delivered? What > works and what doesn't? > > What are the observable symptoms for things that don't work? > Yes, mails are not delivered. You can send a mail to the mailinglist > without getting a bounce, but you will not receive the mail back through > mailman. > In addition to that, I'm unable to edit mailing lists in the web > interface. After clicking on a list, I'll get a 404. > Plus, I noticed that mailman is constantly writing files to > /var/lib/mailman3/queue/out/ but they seem to get deleted right away > again. I'm getting alot of IO there though. So messages are being queued for the outgoing runner and then something is done with them. If there are no errors in mailman.log about this and nothing in the shunt queue, they are being delivered to the MTA. What's in the MTAs logs? > > What do you get for example if you go in a web browser with hyperkitty > > running to > > > > > https://mail.bitkomplex.de/mailman3/hyperkitty/api/mailman/urls?mlist=landw… > > I get a small gziped json file back. Key is "url", value is a link to a > message. OK. That's correct and it seems that Mailman core can communicate with the HyperKitty API, at least when HyperKitty is running. > > And please don't post secret keys and change the value of api_key: in > > mailman-hyperkitty.cfg and the corresponding value in > > MAILMAN_ARCHIVER_KEY in your Django settings. > I actually tried to redact the logs and config files, but I must have > failed to save my edits on that one file. I'll change it right away. The key was in the mailman-hyperkitty.cfg file you posted and was in multiple entries in mailman-web.log. There is some strangeness in the logs you posted. Mailman.log contains many of these: Aug 07 12:49:55 2021 (2343598) HyperKitty failure on https://mail.example.com/mailman3/hyperkitty/api/mailman/urls: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>503 Service Unavailable</title> </head><body> <h1>Service Unavailable</h1> <p>The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</p> </body></html> (503) and mailman-web log contains many of these [pid: 2343625|app: 0|req: 1/1] 10.133.3.2 () {60 vars in 1350 bytes} [Sat Aug 7 12:49:58 2021] GET /mailman3/hyperkitty/api/mailman/urls?mlist=aussen%40lists.example2.com&msgid=002601d777e2%244c34c540%24e49e4fc0%24%40example2.com&key=g8nOyDVbCNsi18L%2FjgTj%2BWDVKUQ2XeQM => generated 131 bytes in 279 msecs (HTTP/1.1 200) 5 headers in 160 bytes (1 switches on core 0) which actually seem normal except for the quantity, but the time stamps don't correlate. There's nothing in mailman-web.log for the times of the 'HyperKitty failure' messages in mailman.log. Was the web service even up during those times. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

Thats part of the issue. It looks like these are in the PendingsDB but not showing up in the UI. Even if I go into Subscription Requests -> Pending Approvals or Pending Confirmations no pending items are shown at all. But in the pendingDB via mailman shell I can see 3 pending unsubscriptions. -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:26 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 7:15 PM, Simon Coggins wrote: The version of postorius is 1.3.4 Then you should be able to click Subscription requests even though the badge shows 0 and click Unsubscription Requests in the dropdown. I know it's an issue, but the badge only counts subscription requests pending approval and not unsubscription requests. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Hyperkitty CSS issue

by Ryan Morash

I tried both the –clear flag and removing everything in my static directory with no luck. From: Mark Sapiro <mark(a)msapiro.net> Date: Sunday, June 14, 2020 at 5:22 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Hyperkitty CSS issue On 6/14/20 1:48 PM, Ryan Morash wrote: > I migrated my existing mailman3 install from using the Debian packages to a virtualenv setup. For the most part everything seems to be running fine, but I'm running into an issue where Hyperkitty 1.3.3 is referencing an incorrect CSS file. It is trying to load "/static/CACHE/css/hyperkitty.39ef00cc7454.css" which does not exist. If I replace that reference (using my browser's dev tools) with "/static/CACHE/css/output.12a071da81b1.css" everything looks fine. I've ran the collectstatic, compress, and migrate commands successfully with no change. Any ideas on how to fix this? Have you tried running collectstatic with the --clear option or removing everything in STATIC_ROOT before running collectstatic?, See, e.g., <https://docs.djangoproject.com/en/2.2/ref/contrib/staticfiles/> -- 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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.mailman3.org%2fma… Confidential Transmission This correspondence is confidential and may contain privileged materials or information. It is intended for the use of the addressee only and all others are prohibited from copying or disseminating this message or its contents. If you have received this transmission in error, delete it immediately and notify the sender.

6 years, 4 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/28/20 2:34 AM, Odhiambo Washington wrote: > > So, now I remember why I had to chown -R mailman3 /opt/mailman > Then now it seems like I have been doing things incorrectly, because I have > been doing > a lot of operations as root by simply: > cd /opt/mailman/mm > virtualenv venv > source venv/bin/activate > Looks like the correct way is to start with su - mailman3 Yes. All those things should be done as the Mailman user. >>> PS: There is the issue with qcluster, which doesn't seem to have been ... > I have run it from supervisord. It has forked 30 processes and refuses to > kill them when I stop supervisord. > I will look for options around it. I know nothing about supervisord, but there should be a parent process. E.g., here > msapiro@mail:~$ ps -fwwu mailman|grep qcluster > mailman 2885 1 0 Jul18 ? 00:00:00 /bin/bash /opt/mailman/mm/bin/mailman-web-django-admin qcluster > mailman 2889 2885 0 Jul18 ? 00:01:57 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 2930 2889 0 Jul18 ? 01:21:03 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 2944 2930 0 Jul18 ? 00:04:17 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 2945 2930 3 Jul18 ? 07:11:14 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 6467 2930 0 15:39 ? 00:00:03 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 12337 2930 0 15:00 ? 00:00:07 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 12639 2930 0 11:08 ? 00:00:11 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 14658 2930 0 Jul27 ? 00:00:22 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 15860 2930 0 01:41 ? 00:00:21 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 19205 2930 0 Jul27 ? 00:00:29 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > msapiro@mail:~$ pid 2885 is the parent which forked 2889 which in turn forked 2930 which forked all the others. stopping (sigterm) 2885 in this case will stop them all. I have seen an issue on one server where some of the qcluster workers become orphaned and their parent pid is 1. These are left when I stop the upstart service so I have this script. #! /bin/bash if echo `status qcluster` | grep -q 'running' ; then echo qcluster is running exit fi ps -fwwu mailman|grep '[a]dmin qcluster'|awk '{print $2}'|xargs kill to kill them. > PS: Did you by any chance find time to look into the issue about wsgi.py > that you had mentioned - the one that has me > stuck using it?? If you're referring to the issue at the end of <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>, I think that was caused by your not having the __init__.py file in /opt/mailman/mm/. If not, I probably need more information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/12/19 8:55 PM, Paul Arenson wrote: > I have found that my users in the discussion list are creating their own topics rather than using the existing ones, so decided to make it a read-only list and use WordPress moderated comments. Since I do not have the original settings for READ ONLY (this is a hosted version), I want to make sure that these are correct. Can someone comment. I'm guessing what you want and what you are saying First, I think you are saying your issue is that your users are using HyperKitty as a web forum and when replying to a message in an existing thread instead of using the 'reply' action on that message, they use the Start a new thread button. Is that really what you are saying? > MOST IMPORTANT—> What setting makes it a discussion list as opposed to read only? If by "read only" you mean the "Announce only mailing list style" as opposed to the "Ordinary discussion mailing list style" the only difference is that for the Announce only style the list attribute allow_list_posts is False and for the Discussion style, it's True. This is the setting in Postorius -> Settings -> Alter Messages -> Include the list post header an all it does is include or not include the List-Post: header in mail from the list. > ALTER MESSAGES > ----------------------- > Filter content Now YES > > Collapse Alternatives Now yes > > Convert html to plain text Now NO Above are not relevant. > Anonymous NOW YES Are you sure you want this. What it does is replace the From: address with the list posting address and removes all other headers that could aid in identifying the poster. It is intended for lists discussing things such as domestic abuse where people may want to be able to post anonymously. > Include RFC2369 headers Now Yes OK, but not relevant > Include the list post header Now Yes This is what the announce style will set to No. > Reply Goes to List Now No munging > > Pipeline Default > > > > DMARC MITIFGATIONS > ----------------------- > > Replace From with list address > > DMARC mitigate unconditionally Now NO > > > MESSAGE ACCEPTANCE > ----------------------- > > Require Explicit Destination Yes > > Administrivia YES The above are OK, but again not relevan to what I think you're asking. > > Default action to take when a member posts to the list Hold for moderation > > > Default action to take when a member posts to the list Hold for moderation Basically these two settings will hold all posts for moderator action, however if the user has a moderation setting other thgan list default, they won't apply. > OTHER? See the FAQ at <https://wiki.list.org/x/4030685>. This is written for Mailman 2.1 and older and some of the settings aren't relevant or exactly the same in Mailman 3, but it may help. On the other hand, if I'm not understanding what you want, please clarify. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Manage Member(s) Mailman Settings / Display Names

by Jim Ward

I will admit I was partial to the MM 2.1 columns and checkboxes but the end result is the same, HOWEVER: 1) The member 'Display Name' does not seem to be available to be managed by me the domain/list administrator. 2) The 'Search Members' function appears to be limited to the email address only and does not include display name These items are important to me as the list I am running includes many that are not, nor will they really ever be, technically savvy enough to access and manage their own account. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, January 10, 2020 7:05 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Manage Member(s) Mailman Settings / Display Names On 1/10/20 4:55 PM, Jim Ward wrote: > Mailman2 allowed me to list my members and modify a number of their attributes (display_name, etc) > > Postorius is a beautiful interface BUT I am evidently not finding how to manage my members to the extent that I could in Mailman2 It's not like MM 2.1 where you have a membership list with columns of checkboxes, but if you pull down the Users menu and select Members or Non-Members, each user has an options link that allows you to set/change options. -- 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://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

6 years, 9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Should Sign Up ?? Log In?? El vie., 21 jul. 2017 a las 18:56, Rafael Mora (<rafael.mora.guti(a)gmail.com>) escribió: > Nice! Up and running! > > How do I start using mailman? what are the steps?? > > REALLY thank you all for your patience and help! Really appreciated ! > > El vie., 21 jul. 2017 a las 18:48, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > >> On 07/21/2017 04:43 PM, Rafael Mora wrote: >> > YEEEES! At last!!! I can see the web UI. >> > >> > Now I´m getting this message in the web UI: >> > >> > Something went wrong >> > Mailman REST API not available. Please start Mailman core. >> > >> > >> > >> > Where do I configure the REST API ????? >> >> >> So I guess you figured out that ALLOWED_HOSTS is a Django setting in >> settings.py or wherever your Django settings are. >> >> Now you have to start Mailman Core. In your Python 3 'env' where you >> installed Mailman Core, run 'bin/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 > -- Atentamente / Best Regards Ing. Rafael Mora

9 years, 2 months

[MM3-users] How to Increase outgoing mail volume for Mailman 3

by Brian Carpenter

Hello everyone, We had a new client come on board that brought a list that had the largest out-going mail volume that I have ever dealt with. So I did what any sane server administrator would do that is running Mailman 3: I ran to Mark Sapiro for help! Here is what the Sage of all things Mailman counseled me to do: 1. Disabled VERP delivery. VERP can help improve mail delivery by delivering 1 message per SMTP transaction (I think I got that right). Using VERP is counter-productive as it can seriously delay outgoing mail delivery for a high-volume list. So you can use something like the following in the MTA section of your mailman.cfg: [mta] verp_confirmations: no verp_personalized_deliveries: no verp_delivery_interval: 0 2. I configured Mailman 3 to run 4 outgoing runners. The default is 1. This action was the game changer. It allows Mailman to handle 4 incoming messages at a time instead of 1. My client's incoming list volume was high enough where it was overwhelming the single outgoing runner. Here is what I added to the mailman.cfg file: [runner.out] instances: 4 Doing this step immediately solved the backlog in var/queue/out. 3. If you start up with a new server for a list that is high volume then keep an eye out for Proofpoint and Vade Security as they will block your new IP address quicker than Mark Sapiro can say "This is a bug. See <some Gitlab.com url>" Mark, thank you! -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 11 months

Search results for query "sapiro"