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

[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

9 months, 2 weeks

[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, 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, 3 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

1 year, 10 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

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

2 years, 5 months

[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

4 years, 6 months

[MM3-users] Re: Broken web UI after upgrade - SOLVED

by Odhiambo Washington

On Sat, Dec 17, 2022 at 9:59 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Sat, Dec 17, 2022 at 9:33 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/16/22 22:21, Mark Sapiro wrote: >> > >> > I suggest you look at ownership and permissions. >> > >> > ``` >> > find /opt/mailman/mm/static/ -not -user mailman >> > find /opt/mailman/mm/static/ -not -perm -u+rw >> > find /opt/mailman/mm/static/ -type d -not -perm -u+x >> > ``` >> > and the same on >> > /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ >> > >> > >> >> If the above doesn't reveal anything substantial, then let me know and >> I >> >> can bump up the verbosity. >> > >> > >> > I don't know if --verbosity 3 will reveal anything or not. You could >> try. >> >> >> Did you see the post at >> < >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>? >> >> Have you tried >> ``` >> django-admin clear_cache >> > > (venv) mailman@list:~$ /opt/mailman/mm/bin/django-admin clear_cache > Cache "default" has been cleared! > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/ > total 16 > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 . > drwxr-xr-x 9 mailman mailman 4096 Dec 4 06:38 .. > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 css > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 js > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/css/ > total 8 > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 . > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 .. > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/js/ > total 8 > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 . > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 .. > (venv) mailman@list:~$ > > So all the css files that were in /opt/mailman/mm/static/CACHE/css/ are > gone after running `django-admin clear_cache`. > > After that, I did run my mailman-post-update script again which created > dirfferent files under CACHE/css/ as the date shows > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/ > total 20 > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:46 . > drwxr-xr-x 9 mailman mailman 4096 Dec 4 06:38 .. > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 css > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 js > -rw-r--r-- 1 mailman mailman 621 Dec 16 22:46 manifest.json > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/css/ > total 176 > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 . > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:46 .. > -rw-r--r-- 1 mailman mailman 162923 Dec 16 22:46 output.1d3a3c0dd51d.css > -rw-r--r-- 1 mailman mailman 1209 Dec 16 22:46 output.9a7b11621c5a.css > -rw-r--r-- 1 mailman mailman 569 Dec 16 22:46 output.e68c4908b3de.css > (venv) mailman@list:~$ > > I then rebooted the system just to be sure everything is restarted. > > And the PROBLEM IS SOLVED :-) > > Thank you very much for your time spent in following this up with me to > the conclusion. > So just for the record, I have added the clear_cache option to the script. Maybe this will benefit someone else one day. <CUT> #!/bin/bash set -e BINDIR="/opt/mailman/mm/bin" CONFDIR="/opt/mailman/mm" SETTINGS="settings" DJANGO_CONTROL_SCRIPT="$BINDIR/django-admin" STATIC_DIR="$CONFDIR/static" DEBUG="False" set -x if [ "$DEBUG" == "False" ]; then mkdir -p "$STATIC_DIR" || : "$DJANGO_CONTROL_SCRIPT" clear_cache "$DJANGO_CONTROL_SCRIPT" collectstatic --clear --noinput --verbosity 0 "$DJANGO_CONTROL_SCRIPT" compress "$DJANGO_CONTROL_SCRIPT" compilemessages fi syncdb_cmd="$DJANGO_CONTROL_SCRIPT migrate" if [[ ! -t 1 ]]; then # stdout is not a terminal syncdb_cmd="$syncdb_cmd --noinput" fi $syncdb_cmd echo 'Do you want to rebuild the search index? This takes a long time.' echo 'Type "Yes" to continue; anything else to quit.' read -p "> " response if [ "x$response" != "xYes" ] ; then exit; fi "$DJANGO_CONTROL_SCRIPT" update_index </CUT> The important thing here is that after an update, it helps to run the following 4 options with your "django-admin" script (whatever it is named) - clear_cache, collectstatic, compress, compilemessages. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

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

[MM3-users] Fwd: Re: Removing a mail addresses and users

by Allan Hansen

All, This disconnect between Mailman Core and Django and Postorius is, by far, the weakest and, for subscribers, most confusing aspect of MM3 (once it has been installed, which is extremely hard and confusing). In a true account-centric system, you set up a web account and from there manage your emails and, for each email, your subscriptions. Subscription options would be hierarchical: account/email/list, with lower levels inheriting/overriding settings from/the level above. That’s really what I had expected when I pushed for us to move our 50 email lists to MM3 and I was very excited about the prospect, as it would solve a lot of system/subscriber management issues I had managing MM2. Alas, I was very surprised that that’s not how MM3 works. Some things got harder, even, such as the inability to change subscription addresses, which should have been a showstopper from the start! I still hope that MMxx OOTB will get there, but I guess it’ll be along haul. Would we be talking about MM4 to be released 20 years from now? Some dedicated and skilled developers are currently investing heavily in a replacement for Postorius, but I really believe that any work is better spent transforming Mailman Core etc. into a true account-based system. Then, and only then, will it make sense to build new and better interfaces on top, as, without a healthy core, such interface will currently may have to inherit the confusion and disconnect that currently is so aggravating. The above is not meant to aggravate the MM3 development team, for which I have utmost respect and gratitude, and which I admire for their tireless support given over decades to the community of admins. Software development is devilishly hard and time consuming. Yours, Allan Hansen hansen(a)rc.org > Begin forwarded message: > > From: Mark Sapiro <mark(a)msapiro.net> > Subject: [MM3-users] Re: Removing a mail addresses and users > Date: June 10, 2020 at 12:46:01 PDT > To: mailman-users(a)mailman3.org > > On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: >> Hello. >> >> I tried to remove random email address signing ups (which I signed up >> while testing) via admin panel. After removing I tried to sign up again, >> but I am getting, >> >> 'A user is already registered with this e-mail address' > > You removed the user's subscription from the list, but you didn't remove > the user from the system. > > Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. > User's have addresses and a user or one of the user's addresses can > belong to a list with one or more roles (non-member, member, moderator > or owner) > > >> Combing through the database, I found auth_user table in mailman3web db >> still contain those mail address. How to wipe email address entirely >> from the db so I can signup again without the 'forget password' method > > There are a couple of things. If you log in to the web UI as a django > superuser, you can go to the django admin UI -> Users section and delete > the User, but I think that will only delete the web user and not delete > the user from Mailman core. > > You can also log in to the web UI as the user and go to > <https://lists.mailman3.org/user-profile/delete>, but that again only > deletes the web user, and if you could do that, you could just subscribe > once you're logged in, so I assume that's what you want to avoid. > > I don't think there is a way for a user as opposed to a site admin to > delete her user record from Mailman core and even for a site admin, > there's no way in Postorius to delete a user from core. It has to be > done via REST > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > or `mailman shell`. > > -- > 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/

4 years, 11 months

Search results for query "sapiro"