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

[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

6 years, 10 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

[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, 9 months

[MM3-users] Re: Link to account

by Lars Bjørndal

Thanks a lot! After further consideration, I will stay with the defaults, e.g. have accounts, archive etc at the same level as mailman3. Lars On Wed, Apr 12, 2023 at 08:32:27AM -0700, Mark Sapiro wrote: > On 4/11/23 23:08, Lars Bjørndal wrote: > > > > I would like to have postorius at .../mailman3 and admin, accounts etc. under .../mailman3/admin .../mailman3/accounts etc. > > > Try this. > > In urls.py > ``` > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), > permanent=True), > ), > path('mailman3/archives/', include('hyperkitty.urls')), > path('', include('django_mailman3.urls')), > path('mailman3/accounts/', include('allauth.urls')), > path('mailman3/admin/', admin.site.urls), > path('mailman3/', include('postorius.urls')), > ] > ``` > > In apache > ``` > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "/mailman3/archives" > "http://127.0.0.1:8000/mailman3/archives" > ProxyPass "/mailman3/accounts" > "http://127.0.0.1:8000/mailman3/accounts" > ProxyPass "/mailman3/admin" "http://127.0.0.1:8000/mailman3/admin" > ProxyPass "user-profile" "http://127.0.0.1:8000/user-profile" > ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" > </IfModule> > ``` > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to lars(a)lamasti.net

3 years, 4 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/1/21 11:53 AM, David Partain via Mailman-users wrote: > Thanks for being patient with me. I'm still baffled but might have found the problem. > > > I've done the above, to no avail. > > > If I look at the queries being sent to mysql, I see stuff like this: > > > 174 Connect mailman3web@localhost<mailto:mailman3web@localhost> on mailman3web using TCP/IP > > 174 Query SET sql_mode='STRICT_TRANS_TABLES' > > 174 Query COMMIT > > 174 Query SET AUTOCOMMIT = 0 > > 174 Query SET AUTOCOMMIT = 1 > > 174 Query SET AUTOCOMMIT = 0 > > > I note that there is nothing about the charset, so something's clearly wonky. > > > As previously stated, /etc/mailman3/mailman-web.py has the right thing: > > > 'OPTIONS': { > > 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", > > 'charset': 'utf8mb4', > > }, > > > but that latter is having no effect. > > > I then found /var/lib/ucf/cache/:etc:mailman3:mailman-web.py which doesn't have charset > > (but does have init_command), but I _think_ that's only about the package management system. I think that's correct. I doubt that that's the problem, but if all else fails, you might just remove it. I don't think that would hurt as it's purpose is just todetect on upgrade of the package if you've changed the file from the distributed one and ask you what you want to do about it. > So... I found that /usr/share/mailman3-web/settings_local.py is just a link to /etc/mailman3/mailman-web.py > > (which obviously has the right thing), but what about the .pyc file? > > > # grep -i STRICT_TRANS_TABLES /usr/share/mailman3-web/settings_local.pyc > > Binary file /usr/share/mailman3-web/settings_local.pyc matches > > # grep -i charset /usr/share/mailman3-web/settings_local.pyc > > # > > > It ain't in the .pyc file. Am I overly optimistic that that might the be problem? > > > If so, I'd be grateful if someone'd tell the newbie how to recreate that file without > > trashing something. This is a bit strange: Here's how it works. .pyc files are byte-compiled versions of the corresponding .py file. When Python runs or imports from a .py file, it first looks for a corresponding .pyc file and if that is as new or newer than the .py, it uses the .pyc. If not, it uses the .py and byte-compiles it and if it has permission, writes an updated .pyc Except recent Python3 (at least I think 3.5 and newer doesn't use a .pyc in the same directory as the .py Its uses a __pycache__ directory in the same directory as the .py and within that directory a file like in this case settings_local.cpython-37.pyc (or whatever the python version is) In any case, I would remove the existing settings_local.pyc. That can't hurt, but I'm curious what ls -lR /usr/share/mailman3-web/ shows. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command

by Perry Kollmorgen

Ok, thanks for the information. Regards, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, 10 June 2024 2:10 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command On 6/9/24 5:26 PM, Perry Kollmorgen wrote: > Hi, > > This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. > > I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt > > When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. > > However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. This is a bug. Currently only `mailman create` sends this notice, but as you note, list creation via rest should do it too. I have created https://gitlab.com/mailman/mailman/-/issues/1156 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to pcjkollmorgen(a)hotmail.com

2 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Before changing the DEBUG var to false everything was working fine after I changed it started the problems... El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > find them: > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > > > > > Should I run any command to activate the CACHE dir? > > > You need to ensure you have a working sass compiler. As I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > Then you need to run commands like > > django-admin collectstatic --clear > django-admin compress > > > -- > 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

9 years

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail. I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)." Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list. Also after clearing the browser cache, the above behavior is seen. Best Regards,Eric On Sunday, December 13, 2020, 03:58:47 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 5:24 PM, Eric Broens via Mailman-users wrote: > I just notice in the webserver logfile, the same request for the same mlist, msgid and key several times per second for about 3 hours now: > "GET /archives/api/mailman/urls?mlist=....&msgid=...&key=... HTTP/1.1" 200 105 "-" "python-requests/2.25.0" Is there a message in Mailman's var/archives/hyperkitty/spool/ directory? If so, what's logged in mailman's mailman.log -- 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/

5 years, 8 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/28/20 10:51 PM, joseverde(a)gmail.com wrote: > Okay, I *think* I killed the processes. When I run > > ps -fwwA|egrep 'master|runner' > > I just get > > root 7595 1 0 Jul26 ? 00:00:04 /usr/lib/postfix/sbin/master -w > mailer 21851 21001 0 22:45 pts/1 00:00:00 grep -E --color=auto master|runner Yes, there are no mailman processes running. > As far as the permissions, you asked does your systemd script set the user to the Mailman user? I don't know how to check that, but I saw many files in /var/lib/mailman3 were owned by a user named list. Last time I tried to run mailman status, it threw a permission error on mailman.cfg, which was owned by root. I changed owner to list, and it produced a different error. So I'm guessing we are on the right path? There was no mention of a user named mailman in the system before, but maybe I need to check something. You are apparently using the Debian/Ubuntu packages. In those, the Mailman user is `list`. There is no `mailman` user. As far as what user the systemd script sets, just look at the script, but if it was installed by the Debian/Ubuntu package, it's probably OK. The script is named xxx.service where 'xxx' is the name you might use in systemctl commands (probably 'mailman3'). It should be at /etc/systemd/service/ or one of the subdirectories. > Lastly, I deleted everything in /var/lib/mailman3/locks. > > However, running mailman status now throws this permission error > > File "/usr/bin/mailman", line 11, in <module> > load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() > File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main > initialize(config_path) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 188, in initialize > initialize_1(config_path) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 123, in initialize_1 > mailman.config.config.load(config_path) > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 107, in load > self.push(filename, user_config.read()) > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 113, in push > self._post_process() > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 125, in _post_process > self.ensure_directories_exist() > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 227, in ensure_directories_exist > with Lock(lock_file): > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 334, in __enter__ > self.lock() > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 203, in lock > self._write() > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 417, in _write > with open(self._claimfile, 'w') as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/mailman-cfg.lck|[redacted server name]|21787|3720843219351355903' > > That file was removed when you told me to clear the locks folder (I save a copy, however). So I'm stuck again. Sorry for all the questions and thanks very much for the help. Does the `list` user own /var/lib/mailman3/ and /var/lib/mailman3/locks/? Are you running `mailman` commands as user `list`? Also see <https://wiki.list.org/x/12812344>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 1:08 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 3:00 PM, Odhiambo Washington wrote: > > On Sat, May 15, 2021 at 12:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Those are headers for compiling some sass. Possibly you actually have a > >> `sassc` installed in which case you may need > >> > >> COMPRESS_PRECOMPILERS = ( > >> ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > >> ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > >> ) > >> > >> > > This change makes the error I was getting to go away. However, I cannot > > login to manage lists, even after restarting mailman. > > > > The error details are here: https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ > > > The relevant part of which is > > OfflineGenerationError at /accounts/login/ > You have offline compression enabled but key > "fa788b08b65fd318d68cfc5afebc18acd3e93cebffadb54d863572ad1754f368" is > missing from offline manifest. You may need to run "python manage.py > compress". Here is the original content: > > I.e., something went wrong with your compress command. Try it again. > I have successfully run the following commands: /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 /opt/mailman/mm/bin/django-admin compress /opt/mailman/mm/bin/django-admin compilemessages /opt/mailman/mm/bin/django-admin migrate But the error at https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ persists. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

5 years, 3 months

Search results for query "sapiro"