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

[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. >

3 years, 11 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

2 years, 4 months

[MM3-users] Re: External MTA incoming mail: configuration

by Roland Giesler

On 2024/07/30 22:39, Mark Sapiro wrote: > It appears you have a situation where the MX for the Mailman domains > is not the Mailman server. You need to configure the MTA on > box2.gtahardware.co.za to relay Mailman's mail to the mailman server. > You can to this by configuring that MTA to use transport_maps, etc as > if it were the Mailman server. In order to get Mailman's generated > files on the other server, you need to create a process to do that. > When Mailman makes changes by adding or deleting lists or when it is > started, it updates the postfix_lmtp and postfix_domains files and > calls a command (normally postmap) to update the corresponding .db > files. The command can be set by setting `postmap_command` in the > `[postfix]` section in mailman.cfg. I'm not able to find any documentation about `postmap_command`, not even in the schema.cfg. If I have to provide method to update the postfix_lmtp and postfix_domains on another server, then it would have to something like sftp? mailman changes the files on the mailman server (in a location I set) and then postmap_command copies those files to the destination on the MTA server. Is that in principle what needs to be done? thanks again! Roland

1 year, 4 months

[MM3-users] Re: Problems with web interface after upgrade

by Victoriano Giralt

De: Mark Sapiro <mark(a)msapiro.net> > On 2/9/21 3:26 PM, Victoriano Giralt wrote: >> >> It's CentOS7, but sassc was already installed and has -t as short for --style. > > You wrote > >> ModuleNotFoundError: No module named 'sassc -t compressed {infile} {outfile}' > > It should be looking for just sassc, not 'sassc -t compressed {infile} > {outfile}'. Whats in your settings for COMPRESS_PRECOMPILERS. I'll check this anyhow. > That may not be the issue. You also wrote > >> compressor.exceptions.FilterError: Error: It's not clear which file to >> import for '@import "../libs/bootstrap/stylesheets/bootstrap"'. >> Candidates: >> ../libs/bootstrap/stylesheets/_bootstrap.scss >> ../libs/bootstrap/stylesheets/bootstrap.scss >> Please delete or rename all but one of these files. >> on line 4 of static/hyperkitty/sass/hyperkitty.scss > > You need to remove the older of > > hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap.scss > > and > > hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_bootstrap.scss > > That may be the whole issue. And it was! You clearly have telepathy, as I was testing this while you were writing, and your message arrived when I had just clicked send on my "SOLVED" message :-D :-D -- Victoriano Giralt Sent from mobile device

4 years, 10 months

[MM3-users] Re: Digests not working correctly

by Joel Lord

Finally got a scenario where there was contents queued up for digest delivery and not enough traffic to kick off size based digest volumes. Running "/usr/local/bin/mailman digests --periodic --verbose" ran through all the lists and kicked out digests successfully. So something is making this work when I run it as the lists user by hand, but fail when I run it from cron as the lists user. Clearly this is on my end, I'll report back if I find anything useful or interesting. On 6/13/2023 2:14 PM, Mark Sapiro wrote: > On 6/13/23 10:58, Joel Lord wrote: >> I ran the "/usr/local/bin/mailman digests --periodic" again, sadly >> without the --verbose, and it kicked out the digests as it ought to >> have the first time. Now I have to wait for some list traffic to come >> in to "recharge" the digests so I have something to test with again. > > Even with the --verbose option, it wouldn't have helped much because it > worked. What we would really like to see is the output with the > --verbose option when it fails. > > It is a mystery to me why it would sometimes fail and sometimes not with > the same digest.mmdf file. > -- Joel Lord

2 years, 5 months

[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/ >

6 years, 11 months

[MM3-users] Re: Getting connection timed out

by peter＠chubb.wattle.id.au

>>>>> "Stephen" == Stephen J Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> writes: Stephen> blackout69 writes: >> Il 23/05/21 01:21, Mark Sapiro ha scritto: > Can you successfully >> telnet to port 25 on mail.simail.it from the > Mailman server? No >> > If you can connect (via telnet) to port 25 on mail.simail.it from >> the > Mailman server, then I'd suggest stopping and restarting >> Postfix. >> >> if i try from the mail server i get >> >> telnet mail.simail.it 25 Trying 217.27.113.30... telnet: Unable to >> connect to remote host: Connection timed out Stephen> mail.simail.it is ignoring your mail server. This is not a Stephen> Mailman problem. 1. Check to see if that server has a Stephen> stated policy for "abusive" mail and some way of getting back Stephen> in their good graces. 2. Check if your mail server is in Stephen> the RBLs. Some of them are very aggressive about adding IPs Stephen> and domains. 3. Try writing the postmaster at Stephen> mail.simail.it. 4. Ask your subscriber(s) at mail.simail.it Stephen> to write their postmaster. Also check your firewall rules. Outgoing port 25 is usually blocked by ISPs unless you explicitly ask for it not to be. Peter C

4 years, 6 months

[MM3-users] Re: import an mm3 hyperkitty archive

by Eggert Ehmke

Thank you Mark, this got me on the right track. But I still think this not at all clear when reading the docs. My system is in a venv. I had to run these commands: mailman-web hyperkitty_import --since=01.01.2022 -l mylist@mydomain my-mbox-file mailman-web update_index_one_list mylist@mydomain Where is it stated that in this situation I have to run mailman-web instead of django-admin? Thanks anyway, problem solved. Am Donnerstag, 8. Dezember 2022, 17:51:58 CET schrieb Mark Sapiro: > On 12/7/22 05:57, Eggert Ehmke wrote: > > I was able to export the archive of my old mm3 installation in hyperkitty. > > However, I seem to be blind when looking for hyperkitty_import in the > > documentation. Where to start? > > There is documentation at > <https://docs.mailman3.org/projects/hyperkitty/en/latest/development.html#im > porting-the-current-archives> and also at > <https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy>. > You can also run `django-admin hyperkitty_import --help`. The docs refer > to importing messages from MM 2.1, but you can import messages from any > unix like mbox file. > > Note in the above, `django-admin` is the command you use to invoke > Django's management which may be `django-admin`, `manage.py`, > `mailman-web` or something else depending on how Mailman is installed.

3 years

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/29/20 11:26 AM, Mark Sapiro wrote: > On 10/29/20 5:17 AM, Brian Carpenter wrote: >> On 10/29/20 4:27 AM, Alex Schuilenburg via Mailman-users wrote: >>> On 29/10/2020 01:57, Brian Carpenter wrote: >>>> With Mailman 3, every list owner has the ability to remove a reply in >>>> a thread, a complete thread, and even the entire archives. That is a >>>> welcome difference from MM2 in my opinion. >>> A very welcome difference, only I don't see this option in the web >>> interface of my debian 3.2.1 installation. Is this a shell only >>> option, 3.3 feature or configuration option I have missed? >> It is not a shell option. It can be done via Hyperkitty but I am not >> sure when that feature showed up. > > Actually, with current HyperKitty, only site admins can remove messages > or threads or the archive. The ability for list owners to do it is > <https://gitlab.com/mailman/hyperkitty/-/issues/261>. Thanks Mark. To clarify more, we have this ability for List owners with our own custom admin interface (Affinity). I thought Postorius had that. When I checked out Postorius, I was indeed logged in as server owner. Sorry for the incorrect info. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Stephen J. Turnbull

Mark Sapiro writes: > On 1/6/22 6:28 PM, Stephen J. Turnbull wrote: > > In my Debian configuration [mod_proxy_http.conf] is needed > > because it contains the necessary directives to enable proxying. > > Actually though, I think that's enabled as part of proxy. The Apache documentation strongly implies that this needs to be explicitly enabled by the admin: The forward proxy is activated using the ProxyRequests directive. Because forward proxies allow clients to access arbitrary sites through your server and to hide their true origin, it is essential that you secure your server so that only authorized clients can access the proxy before activating a forward proxy. By contrast for a reverse proxy: A reverse proxy is activated using the ProxyPass directive or the [P] flag to the RewriteRule directive. It is not necessary to turn ProxyRequests on in order to configure a reverse proxy. Both are from https://httpd.apache.org/docs/2.4/mod/mod_proxy.html. > However, see > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > I now suspect the real issue is there's no wsgi server listening on port > 8000. Could be. Apache docs notwithstanding, I'm happy to trust your intuition, and that would make things simple for the OP. :-) Steve

3 years, 11 months

Search results for query "sapiro"