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

[MM3-users] Re: Gmail emails bouncing - anybody seen this problem?

by worik

On 12/02/19 11:25 AM, worik wrote: > Friends > > On a fresh install (docker) on a fresh VPS I am getting all Mailman > messages to Gmail addresses bouncing telling me I am sending too many > messages. Has anybody else have this problem? > > I am getting the following error in mail.log: "Our system has detected > an unusual rate of 550-5.7.1 unsolicited mail originating from your IP > address. To protect our 550-5.7.1 users from spam, mail sent from your > IP address has been blocked. 550-5.7.1 Please visit 550-5.7.1 > https://support.google.com/mail/?p=UnsolicitedIPError to review our 550 > 5.7.1 Bulk Email Senders Guidelines. l26si395949wme.8 - gsmtp" > > I have been to the URL mentioned and exhausted my options there. > > Worik > Well. Golly. I complained to Google, and heard nothing back. But with no changes on my end they have stopped bouncing my emails. Now they are just marked as spam. I can live with that. Very frustrated with google's levels of service. What a pain! Thank you Brian Carpenter, who may well have been right about "warming up the IP". What ever that might mean. I have not read that RFC, but I have a lot to learn. Thank you Mark Sapiro, for your patience. Thank you every body for the obviously hard work creating this system. I have a long way to go until I know how to use it properly, but I am no longer stopped at the google cliff. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) I have a lot of onion pie, that explains the aroma

7 years, 8 months

[MM3-users] Re: Error -- postorius Un-handled exception

by Odhiambo Washington

On Thu, Apr 11, 2024 at 11:00 PM Ron / BCLUG <admin(a)bclug.ca> wrote: > Mark Sapiro wrote on 2024-04-10 14:09: > > > I suspect you are not starting the services with your venv active. > > What's in your mailman3.service and mailman3-web.service files? > > Thanks for the pointer! > > I had my mailman3-web.service starting `mailman-web` instead of `uwsgi` > somehow. > > > I changed that to match the docs, did the `systemctl daemon-reload`, > etc. but still had similar problems. > > > I went through all my config files carefully, I wiped the static folder > completely and rebuilt it, and I finally have the last piece of the > puzzle in place and my web interface is working! > > I'm not sure which change actually fixed the issue though. > > > (When looking at "Available lists" my header has "example.com" in the > top-left corner?!?) > See also this: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… But read it as "example.com", not example.org :-) I think I need to backup what I have and do a clean re-install so I have > a better grasp of what's going on with all these components. > Way to go! Before I got MM3 working on the sites that I manage, it took me lots of installs and wipes until I could figure out what's going on. I was literally being hand-held by the good developers. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 6 months

[MM3-users] Re: "Approved:" header from mailman2 times

by Abhilash Raj

On Mon, Apr 9, 2018, at 8:59 PM, Mark Sapiro wrote: > On 04/09/2018 03:59 PM, Abhilash Raj wrote: > > On Mon, Apr 9, 2018, at 3:00 PM, Dmitry Makovey wrote: > >> Hi, > >> > >> is there any equivalent to "Approved" header that was present in MM2 in > >> MM3 land? Google is not very helpful in that. > > > > It does exist in Mailman 3 as a carry-over from Mailman 2, but AFAIK it is broken. > > > I don't think it is broken, but it requires setting the > moderator_password attribute for the list which can be set visa REST but > I think not by mailmanclient. > Thanks Mark for clarification. > > > Also, I have been thinking of not having this as a feature in Mailman 3, mostly because of the issue of having shared passwords. No one should be sending out passwords anyway through plain emails anyway. > > > > > Agreed. This is a shared password. and would be sent in plain text as a > header or body line. > > It would be nice though to have some feature to enable, for example, > spoof proof posting to a one-way (announce only) list. > > One thought on how to do this would be to have a list attribute that > says posts from 'authenticated' owners and moderators can be auto > approved and authentication could be by PGP signing the post. This would > require Mailman to have the ability to verify a PGP signature from an > owner or moderator which is not currently the case. +1 on using PGP signatures for doing this and that is exactly what I was thinking :) -- Abhilash Raj maxking(a)asynchronous.in

8 years, 6 months

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 13/2/21 11:55, Victoriano Giralt wrote: > On Fri, 2021-02-12 at 12:24 -0800, Mark Sapiro wrote: >> If the manage.py in the directory in which you ran this is the >> correct one for your Mailman Django project, I don't know why it >> didn't work. > Me neither :-( That's why I asked, and probably Guillermo, as well. > >> Is your Mailman installed in a virtualenv? If so, was the virtualenv >> activated? > No virtualenv. Mine is deployed using system python on a CentOS 7 > system, toghether with another in house developed low requirements > Django project, both served by uWSGI vassals. And mine, as well, in a FreeBSD 12.2-RELEASE, no virtualenv and uWSGI approach with apache24 server. > > And then, all of a sudden, while I was writting this, it dawned on me! > > Postorius, Hyperkitty and django-mailman are installed with pip, so, > the end up in the site-packages directory (usually > /usr/local/lib/python3.x/site-packages), That is my case, too. > but, normally, django projects > are deployed somewhere in the web server hierarchy (/var/ww/django in > my case, due to old personal tastes), and applications properly defined > in the settings.py for the project. > > So, the message files are out of reach for manage.py. > > Changing to /usr/local/lib/python3.x/site-packages/X > (with X being postorius, hyperkitty and django_mailman3) and using > django-admin compilemessages all works! And for me as well. Thanks a lot Victoriano, I owe you a beer > > Thanks for pushing my thoughts in the right direction! > > > _______________________________________________ > 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: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Marc SCHAEFER

Hello, On Sat, May 25, 2024 at 11:38:40AM -0400, Mark Sapiro wrote: > The host name displayed in the web UI is based on the SITE_ID setting in > Django's settings. This is a system configuration not associated with any > lists. it references an entry in the django_sites table in the database. Thank you, will look into this. > As far as the comment/display name in From: is concerned, what specific > emails are you talking about? This. Sorry, I mixed From: with Subject: and the content: Date: Sat, 25 May 2024 13:37:29 -0000 From: postorius(a)lists2.alphanet.ch To: schaefer@XXX Subject: [example.com] Please Confirm Your E-mail Address Hello from example.com! You're receiving this e-mail because user Schaefer-XXX has given your e-mail +address to register an account on example.com. To confirm this is correct, go to [ ... ] Thank you for using example.com! example.com I guess it's the same SITE_ID setting in Django's DB: $ grep SITE_ID /usr/share/mailman3-web/settings.py SITE_ID = 1 However, I guess it's the default creation, by the Debian package, of the SQLite local database which presumably was done with example.com. I will anyway switch to a remote PostgreSQL database, and thus create a new one with the correct names. That should fix it. > for ADMINS in your Django settings. ADMINS = ( ('Mailman Suite Admin', 'schaefer(a)alphanet.ch'), ) That looks correct. > The `mailman import21` command will properly import the Mailman 2.1 > from_is_list and Sender filters -> dmarc_* DMARC mitigation settings. Thank you. Aka mailman-wrapper import21 on Debian so to switch to the correct user. > If you have some customization in this area, that probably won't be handled. Obviously.

2 years, 5 months

[MM3-users] Re: Caching problem with templates

by Mark

On Thu, 2025-06-26 at 18:36 -0700, Mark Sapiro wrote: > > You can delete the cached entry from the database via `mailman shell > as in > >>> cm = getUtility(ICacheManager) > >>> uri = 'the_uri_from_the_template_table' > >>> cm.get(uri, expunge=True) > >>> commit() > ``` > > You can also delete the entry from the file_cache table, but if you > do > that, the actual file containing the cached data will remain. To > remove > it, > > Rather than doing any of the above, if you want to manipulate the > database, just set the expires_on column in the file_cache table > entry > to a date in the past. > Hi Mark, Thank you for this information. I've given the options a good workout over the last couple of days and found that: 1. Deleting the cache via the mailman shell does the job, but is beyond me to script. There are numerous lists and list owners updating their templates. 2. Changing the expires_on date (to a date in the past) in the file_cache table didn't prevent the cached entry from being used; 3. What did work was removing the records in the file_cache table PLUS removing the corresponding files in var/cache/*/*/* -- for example: /opt/mailman/mm/var/cache/3a/2f/* This I was able to script in bash and cron to run every minute. A hack I know, but it's working for now. I've attached the script in case it's of use to anyone else. (mailman_clear_template_cache.txt) Note: change <USER> in the script to what suits. Does Mailman really need to cache the templates? It seems to be an unnecessary complication. Anyways it happy days again. Thank you again, very much. Your guidance was appreciated immensely as always. Best, Mark

1 year, 4 months

[MM3-users] Re: Change Member's Address

by alain williams

On Tue, Jan 13, 2026 at 11:14:04AM -0800, Mark Sapiro wrote: > >>> um = getUtility(IUserManager) > >>> addr = um.get_address('address_to_change') > >>> addr.email = 'new_address' > >>> commit() > ``` > However, the preferred way is for the user to log in, go to > https://whatever/accounts/email/, add the new address to their account, make > it primary, go to the list info page at https://whatever/lists/LIST, and if > their Subscription Address is still the old address (because they weren't > subscribed by primary address), click Manage Subscription and change it, and > then possibly remove the prior address. That should be trivial for any user to do that - certainly I, and others on this list, would not have a problem. However: many of my users would find those instructions baffling, they can just about manage email - on a good day. Like it or not it is sometimes easier for me to do that sort of thing than try to explain it to them. In the past I have done it by running up MySQL and hacking the table directly. I host several mail lists, some of which I do not manage - my 'clients' do that and, with a bit of hand holding have learned to add/remove/... people to lists via the web interface. They do not know what the mailman shell is - and I would not want to give them shell access to the machine. So: it would be really useful if the list manager were able to do this via the web interface. Please! -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

9 months, 2 weeks

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Sat Oct 22, 2022 at 9:56 PM WAT, Mark Sapiro wrote: > On 10/22/22 13:07, Onyeibo Oku wrote: > > On Sat Oct 22, 2022 at 7:44 PM WAT, Mark Sapiro wrote: > >> The specific error you reported refers tp > >> /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO > >> > >> what does > >> ``` > >> ls -l > >> /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO > >> ``` > >> show? > >> > > > > See below: > > > > command: > > ls -lh /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO > > > > output: > > -rw-r--r--. 1 mailman mailman 7.8K Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO > > > This is actually strange. What does `pip --version` in your venv show? > Did you do anything to install mailman and other packages in your venv > other than `pip install`. > > I ask because I don't think there should be *egg-info directories in > /opt/mailman/venv/lib/python3.10/site-packages/ at all. In particular, > in addition to the actual code directories, I only see files and > directories with names ending in nspkg.pth and dist-info. > It is strange indeed. So I decided to start all over again. I deleted both "mm" and "venv" folders and recreated "venv" first. I noted that after reinstalling the virtual environment pip was at version 21.3.1. I assumed that version may be buggy and upgraded to pip 22.3 before performing subsequent installations. Next came the wheel package, followed by psycopg2. I checked the /opt/mailman/venv/lib64/python3.10/site-packages/ path to confirm that things were clean. All good -- no egg-info/* folders. I then installed mailman. Now Mailman starts, and stops as desired when running as mailman user (both in virtual and non-virtual environments). However, running the service via systemd still fails. I now get a different traceback: Oct 23 03:43:00 mail.server.tld mailman[19410]: Traceback (most recent call last): Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/bin/mailman", line 8, in <module> Oct 23 03:43:00 mail.server.tld mailman[19410]: sys.exit(main()) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 1130, in __call__ Oct 23 03:43:00 mail.server.tld mailman[19410]: return self.main(*args, **kwargs) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 1054, in main Oct 23 03:43:00 mail.server.tld mailman[19410]: with self.make_context(prog_name, args, **extra) as ctx: Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 920, in make_context Oct 23 03:43:00 mail.server.tld mailman[19410]: self.parse_args(ctx, args) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 1613, in parse_args Oct 23 03:43:00 mail.server.tld mailman[19410]: rest = super().parse_args(ctx, args) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 1378, in parse_args Oct 23 03:43:00 mail.server.tld mailman[19410]: value, args = param.handle_parse_result(ctx, opts, args) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 2360, in handle_parse_result Oct 23 03:43:00 mail.server.tld mailman[19410]: value = self.process_value(ctx, value) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 2322, in process_value Oct 23 03:43:00 mail.server.tld mailman[19410]: value = self.callback(ctx, self, value) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/bin/mailman.py", line 95, in initialize_config Oct 23 03:43:00 mail.server.tld mailman[19410]: initialize(value) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/core/initialize.py", line 217, in initialize Oct 23 03:43:00 mail.server.tld mailman[19410]: initialize_1(config_path) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/core/initialize.py", line 122, in initialize_1 Oct 23 03:43:00 mail.server.tld mailman[19410]: mailman.config.config.load(config_path) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/config/config.py", line 142, in load Oct 23 03:43:00 mail.server.tld mailman[19410]: self.push(filename, user_config.read()) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/config/config.py", line 148, in push Oct 23 03:43:00 mail.server.tld mailman[19410]: self._post_process() Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/config/config.py", line 160, in _post_process Oct 23 03:43:00 mail.server.tld mailman[19410]: self.ensure_directories_exist() Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/config/config.py", line 262, in ensure_directories_exist Oct 23 03:43:00 mail.server.tld mailman[19410]: with Lock(lock_file): Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/flufl/lock/_lockfile.py", line 461, in __enter__ Oct 23 03:43:00 mail.server.tld mailman[19410]: self.lock() Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/flufl/lock/_lockfile.py", line 328, in lock Oct 23 03:43:00 mail.server.tld mailman[19410]: self._write() Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/flufl/lock/_lockfile.py", line 492, in _write Oct 23 03:43:00 mail.server.tld mailman[19410]: with open(self._claimfile, 'w') as fp: Oct 23 03:43:00 mail.server.tld mailman[19410]: PermissionError: [Errno 13] Permission denied: '/opt/mailman/mm/var/locks/mailman-cfg.lck|server.tld|19410|619270043958240354' Oct 23 03:43:00 mail.server.tld systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE

4 years

[MM3-users] Re: Moving/cloning mailman3

by Abhilash Raj

Just take a dump of the database and move to other one, almost everything is stored in database. Outside of database, if you need to move log files and currently pending emails in shunt or held queue (broken or pending emails), you need to move the 'var' directory of Core and it's configuration. If you are using docker installation, database container holds the database and '/opt/mailman/core/var' is what you are looking for. Thanks, Abhilash Raj (Apologies for top post) On October 18, 2017 1:29:58 PM PDT, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >On 10/18/2017 11:10 AM, Mark Sapiro wrote: >> On 10/18/2017 08:56 AM, Dmitry Makovey wrote: >>> Hi, >>> >>> I am drawing a blank looking for documentation for mailman3 >migrations. >>> How can one dump existing settings for mailman and import it into >>> another instance? >> >> >> The Mailman 3 command 'mailman import21' is what does this >> ><http://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/import.ht…>, >> however there are issues in that not all 2.1 settings are imported at >> all or correctly and in at least one case on an announce only list, >the >> membership wasn't imported. >> >> I intend to work on this, but haven't got as far as even documenting >the >> problems, much less coming up with fixes. > > >isn't above more about MM2 -> MM3 moves? I can't file .pck files for >MM3 >setup thus assuming there are some other files/commands I need to >tackle >to move MM3 from host to host. > > >-- >Sr System and DevOps Engineer SoM IRT -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

9 years

[MM3-users] Re: Disabling mail/news gateway was: Moderation action "None" is misleading

by Thomas Krichel

Mark Sapiro writes > For older releases you can add > ``` > [runner.nntp] > start: no > ``` > to mailman.cfg Following this advice, I reverted the change I made to /usr/lib/python3/dist-packages/mailman/utilities/modules.py Then I believe I implemented Mark's suggestion root@server~# diff /etc/mailman3/mailman.cfg~ /etc/mailman3/mailman.cfg 312c312,318 < jump_chain: hold \ No newline at end of file --- > jump_chain: hold > > ## dont't start nntp because library is missing > > [runner.nntp] > start: no > ok, but root@server~# systemctl status mailman3.service × mailman3.service - Mailman3 server Loaded: loaded (/usr/lib/systemd/system/mailman3.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2025-02-05 23:36:35 UTC; 9min ago Duration: 2month 3w 6d 6h 21min 31.400s Invocation: 746a7d496ddd47f6a63795e55348b6f9 Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 416285 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=exited, status=1/FAILURE) Mem peak: 74.2M CPU: 1.712s Feb 05 23:36:34 server mailman3[416285]: File "<frozen importlib._bootstrap>", line 935, in _load_unlocked Feb 05 23:36:34 server mailman3[416285]: File "<frozen importlib._bootstrap_external>", line 1026, in exec_module Feb 05 23:36:34 server mailman3[416285]: File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed Feb 05 23:36:34 server mailman3[416285]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_gatenews.py", line 24, in <module> Feb 05 23:36:34 server mailman3[416285]: import nntplib Feb 05 23:36:34 server mailman3[416285]: ModuleNotFoundError: No module named 'nntplib' Feb 05 23:36:35 server systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Feb 05 23:36:35 server systemd[1]: mailman3.service: Failed with result 'exit-code'. Feb 05 23:36:35 server systemd[1]: Failed to start mailman3.service - Mailman3 server. Feb 05 23:36:35 server systemd[1]: mailman3.service: Consumed 1.712s CPU time, 74.2M memory peak. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 21797th day.

1 year, 8 months

Search results for query "sapiro"