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

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Wed, 9 Jan 2019 at 19:25, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/8/19 10:50 PM, Odhiambo Washington wrote: > > > Now that has clarified the matter for me. That even when I am logged out, > > the scripts do the neccessary > > to activate the venv to run things. > > > As mentioned before, a virtualenv is not like a container. It is only a > directory that contains among other things a bin/ directory with > activate scripts and easy_install, python, pip and wheel commands. > > When you activate a virtualenv in your shell, all it really does is add > a deactivate command, modify the command prompt and insert its bin/ > directory at the beginning of its PATH. > > What this means is whether or not a virtualenv is "active", running a > command from the bin/ directory in the virtualenv is using the virtualenv. > Thank you very much for the elaboration. What used to confuse me was the early stage documents which detailed how to run MM3 in a virtual environment - I am talking about the BETA days. I think from this point onward, I have the complete foundation information to move forward. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

7 years, 7 months

[MM3-users] Re: Moderate mails from owner

by Malcolm Austen

On Wed, 20 Mar 2019 18:42:10 -0000, Mark Sapiro <mark(a)msapiro.net> wrote: > However, this is apparently not relevant because both the Member and > Non-Member actions are Hold. Thus, the post should be held unless it has > an Approved: header with the list's moderator_password attribute if > there is one, or it matches a Header filter rule with an accept action. At the risk of getting this really wrong - I have only limited MM3 knowledge - I will ask what is, I fancy, a closely related question ... My only experience of MM3 is with Ancestry's 'RootsWeb' installation. From the emails I can see a header "X-Mailman-Version: 3.1.0" but I can't find anything to identify Postorius which is the only interface I have to the system. From symptoms seen and described by others, I have deduced that the Postorius admin-per-user moderation options of "Default processing" and "List default" mean that a user may be set (by default on the rootsweb system!) to use the system default moderation settings rather than the list default settings. Are my deductions correct? And if so, could this be the explanation of the issue detailed in this thread? Apologies if I'm barking up entirely the wrong tree, Malcolm. -- Malcolm Austen <malcolm.austen(a)weald.org.uk>

7 years, 4 months

[MM3-users] Re: Hyperkitty shows "<" as <

by Andreas Schamanek

Thanks Mark, Your support is unparalleled. On Tue, 4 Apr 2023, at 10:44, Mark Sapiro wrote: > On 4/4/23 09:53, Andreas Schamanek wrote: >> All "<" and ">" in old and new messages are shown as "<" and ">" in >> message views _however_ they are shown correctly in overview abstracts e.g. >> at //server/mm3/hyperkitty/list/testlist@server/latest > > I don't think I've ever seen this. Certainly it is not the case on this list > with either current messages such as those in this thread > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> I tried to dig deeper and realized that on my test list "<" and ">" are only mangled when they surround email addresses as e.g. in <user(a)example.net> (ie. < user @ example . net >) I see that lists.mailman3.org renders such addresses as e.g. <a target="_blank" href="mailto:user@example.net">user(a)example.net</a> whereas my Hyperkitty shows them as <user(a)example.nett> But I have not yet found the responsible code or setting since it seems this is related to the option to obscure addresses. Or is my Hyperkitty 1.3.4 simply too old? -- -- Andreas :-)

3 years, 4 months

[MM3-users] Re: Mailman stops processing....... where to start looking for root cause?

by Stephen J. Turnbull

Mark Sapiro writes: > One of the runners has died, most likely the `out` runner, but > possibly another. The missing messages are stuck in a queue. Do ``` > ls -laR /opt/mailman/core/var/queue ``` to see in which queue the > messages are. The runner that processes that queue is gone or > possibly stuck. I have seen "stuck", in a multisite installation where Mailman's smarthost ended up being about 1000 miles from Mailman. I'm not sure what the issue is (we fixed the DNS, not Mailman :-), but every once in the while the connection would hang. In that case nothing showed up in the log. The only symptoms were the buildup in the out queue and a stale connection to port 25 on the smarthost. If your smarthost is not "network far" from the Mailman host, this is quite unlikely from my experience, although Mark may know better. In any case, I think the best way to start diagnosis is to check the Mailman and MTA queues for stuck messages. Of course in normal operation you will often see messages in the queue, but long queues or messages older than a minute are 99% a dead or stuck queue runner. Steve

2 years, 4 months

[MM3-users] Re: Disable Sign-up per domain

by Mark

On 2025-07-31 03:31, Mark Sapiro wrote: > Anything is possible, it's only code ;) > > You could make your own user_adapter.py which is modified like > > and set that as the ACCOUNT_ADAPTER. This depends on whatever is > proxying to Django setting the appropriate HTTP_HOST header. Thank you Mark. It's so close. After wrangling your solution a bit it's working a treat on my test server (wrangled solution below) . When I add it to the production server (same OS, MM installation, etc) I'm getting a "Bad gateway" error page and the log reports ... ... raise self.model.DoesNotExist( django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. I cannot for the life of me get my head around that. I suspect it's something to do with what you said -- "whatever is proxying to Django setting the appropriate HTTP_HOST header." -- which I don't understand. Any additional advice gratefully received. ================================== /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py ================================== COMMENT OUT THESE 2 LINES... # def is_open_for_signup(self, req): # return False REPLACE WITH THE FOLLOWING... def is_open_for_signup(self, req): if req.META['HTTP_HOST'] == 'lists.mydomain.com': return False else: return True ================================== /etc/mailman3/settings.py ================================== Append the following ... ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' ================================== systemctl restart mailman3 systemctl restart mailmanweb ==================================

1 year

[MM3-users] Re: MM3 in virtualenv - FreeBSD-11

by Odhiambo Washington

I am keeping all of my steps in a text file. If I end up with a functional install, then I believe FreeBSD users will be able to install MM3 using virtualenv. I am banking on the help of the experts here to achieve that and document it. So far, I don't know anyone who is using FreeBSD who has managed to install and run MM3. This will be the first time anyone has ever done it. I therefore beg all of you to accommodate my stupidity. I'm 50 in April so it's not a mean feat 😂 😂 On Fri, Jan 11, 2019, 23:10 Mark Sapiro <mark(a)msapiro.net wrote: > On 1/11/19 6:51 AM, Odhiambo Washington wrote: > > > > Now that I look at it, I think you should clarify that if one is not > > interested in using PostgreSQL (which is what `pip install > psycopg2-binary` > > is for), > > then there should be some different binary they need to install, no? And > > which one is it? > > > I have added a note to the comment at > https://wiki.list.org/DOC/Mailman%203%20installation%20experience which > says: > > """Also, please note the first paragraph of the introduction. This is > documentation of my decisions and experiences. It is not a how-to and > does not replace the documentation at http://docs.list.org/""" > > In particular, documentation of the requirements for different databases > is at > <https://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html>. > > > > Under your "*Recommended Configuration*", I have followed each step, > > getting the files and editing them to suite my needs, until I got to > where > > you refer to: > > /opt/mailman/mm/settings.py (copy of the mailman-suite settings.py file > but > > with DEBUG = False) > > I tried to get this file using `git clone > > https://gitlab.com/mailman/mailman_suite.git` > <https://gitlab.com/mailman/mailman_suite.git> and realized that > > authentication is required in order to get it. > > > Because you should be getting > <https://gitlab.com/mailman/mailman-suite.git> (hyphen, not underscore) > which works without authentication. > > Or you could just go to > < > https://gitlab.com/mailman/mailman-suite/blob/master/mailman-suite_project/… > > > and copy it from there. > > > > What is the reason you did not include a copy like for the rest?? > > > Because it's available on GitLab. > > > > I have created the executables - all of them. > > I have created the templates and did `find . -type f -exec sed -i.BAK 's/ > > mailman3.org/mydomain.name/g' {} \;` > > Maybe you should state explicitly that once one gets these templates, > they > > need to change the url to match theirs. You said it, but it doesn't come > out > > forcefully :0 > > > I added "Of course, if you use these you need to edit the URLs for your > site." > > > > In your "MTA" section, I suppose you need to be a little more generic as > > well and accommodate Exim users. > > First I suggest you clearly state that one needs to edit /opt/mailman/mm/ > > mailman.cf to ensure that the values under [mta] match what is required. > > Maybe there is a different file to edit for MTA settings??? > > > Again, I'm documenting MY experience, not trying to replace the official > documentation. I refer to > < > https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#postfix > > > because I use Postfix. That same page also has Exim documentation. > > > > So far ..... > > > > Next, I will be looking into "Running Things".... which is where I > believe > > things will get thicker .... > > > Perhaps when you're done you will write u your experiences with FreeBSD > and Exim. > > -- > 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/ >

7 years, 7 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, Am 13. Dezember 2019 um 17:10 Uhr -0800 schrieb Mark Sapiro: >key is the <message-id> of the request message >request_type is 1 for a held message >mailing_list_id is a numeric index into the mailinglist table > >The issue is there are still held message requests there for the >messages you removed. You need to delete those entries from the _request >table. Thank you again for your valuable help. I've now taken the easy route and ran DELETE FROM _requests WHERE request_type=1; , i.e. I cleared the entire held messages queue. As it turned out, there were no requests of any other type than type 1. I've deleted all remaining files below /var/lib/mailman3/messages as well (after seeing it was only spam anyway, this time non-broken spam, but still spam). Now, finally, I can go to the held messages queue in Postorius again without a 500 error. The list of held messages there is now empty, but this is obviously expected. Let's hope that disabling SMTPUTF8 prevents the problem from further occuring. In any case, I've asked a friend report the problem to the Ubuntu tracker: https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1856181 I'm back on track now. Thanks everyone! Marvin -- Blog: https://mg.guelker.eu

6 years, 8 months

[MM3-users] Re: Installing MM3 via pip fails…

by Patrick Ben Koetter

* Mark Sapiro <mark(a)msapiro.net>: > On 2/18/20 10:45 AM, Patrick Ben Koetter wrote: > > Has anyone managed to install MM3 recently using pip on Ubuntu 18? > > > > I followed the instructions at > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…. > > As soon as I get to the Django part things get hairy. It seems Django requires > > something that was removed from it. > > > What exactly is the issue? I just tried following the doc starting at > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup> > and doing everything through > > (venv)$ python3 manage.py runserver > > and I encountered no issues. One possibility is the Ubuntu 18.04 box on > which I did this already had ruby-sass and python3-dev globally installed. > > sudo apt install ruby-sass > sudo apt install python3-dev > > Did you install these? Yes, I did. But to be sure I'll try on a vanilla VM and see how it goes if I install ruby-sass and python3-dev beforehand. p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

6 years, 6 months

[MM3-users] Re: multiple sites on a mailman3 server question

by William Oliver

On Wed, 2021-12-29 at 09:21 -0800, Mark Sapiro wrote: > On 12/29/21 8:48 AM, William Oliver wrote: > > > > What I'm trying to figure out is where uwsgi yanks control from > > nginx > > and does the rewriting. Pulling that proxypass stuff out will stop > > mailman3 from coming up, and adding it allows mailman3 to show its > > interface, but the address gets referred regardless. > > > > Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow > > tell > > nginx not to push it to port 8000. But I don't see where nginx is > > getting told to go to 8000 in the www.domain.com section. > > > If you are following > https://docs.mailman3.org/en/latest/install/virtualenv.html you have > ``` > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > ``` > in your nginx config and everything goes to uwsgi. What you want is > to > put those proxy directives in only the mailman locations as at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > and then configure your document root so other locations are served > from > there. >

4 years, 7 months

[MM3-users] Re: Any possible way to reduce robot spam accounts?

by Franklin Weng

Hi Mark, Mark Sapiro 於 2023/7/21 12:01 寫道: > On 7/20/23 20:42, Franklin Weng wrote: >> >> Thank you. When I set it in my settings_local.py, I clicked register >> and got an error: >> >> ModuleNotFoundError at/accounts/signup/ >> No module named 'django_mailman3.views.user_adapter' >> >> (In the document the path is /etc/mailman3/settings.py but I >> installed it with Debian packages so I guess the path is somewhat >> different, and I thought setting in setting_local.py should work >> too. It seems work since it gave me the error above.) >> >> Do I have to install something else? Or disable some other options? > > > What is the version of django_mailman3 in your Debian package? As it > says in the FAQ article, "You would need django-mailman3 >= 1.3.6 for > these settings to work." > Debian Bullseye goes with 1.3.5, and Debian Bookworm goes with 1.3.9 but as I have said in another thread it has problems in django admin. So I downloaded the 1.3.9 source code, extracted it, and copied django-mailman3/views/user_adapter.py to /usr/lib/python3/dist-packages/django_mailman3/views. It worked! For a record here. Thanks for your help. Thanks, Franklin

3 years

Search results for query "sapiro"