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

[MM3-users] Re: "Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all'

by Mark Sapiro

On 05/28/2017 06:07 AM, Simon Liebold via Mailman-users wrote: > Is deleting threads from the archive (via Hyperkitty) currently > supported? I am getting the error indicated above if I click on "Delete > this thread". I just tested this on another list on this server. and both 'delete message' and 'delete thread' worked for me with the latest release Hyperkitty 1.1.0, django_mailman3 1.1.0 and Django-1.10.7. Did you get to the confirmation page and then get the 500 or did the 500 come before getting the confirmation page? Is there a full traceback in mailman_web.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

[MM3-users] Re: MM3 & postfix ... (mail loops back to myself)

by Mark Sapiro

On 01/18/2018 02:25 PM, Dmitry Makovey wrote: > > transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp > local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp > relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains The initial implementation of Mailman's regexp maps for Postfix was broken. This was fixed by <https://gitlab.com/mailman/mailman/merge_requests/323>. The bottom line is if /opt/mailman/core/var/data/postfix_lmtp contains entries like /^foo-bounces(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 /^foo-confirm(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 these entries (only the -confirm and -bounces, not the others) need to be /^foo-bounces(\+.*)?(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 /^foo-confirm(\+.*)?(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 because Postfix recipient_delimiter = + is not effective for regexp tables. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: MM3 Docker

by Mark Sapiro

On 1/8/19 10:03 AM, Odhiambo Washington wrote: > > Thank you for clarifying. > So once I have a venv created, the services will just run as long as the > startup scripts are running even when I'm logged out of the system? As long as the startup scripts actually reference things in the venv. If you look at the samples in the Recommended Configuration section at <https://wiki.list.org/x/17891998> for /opt/mailman/mm/bin/django-admin (sample) Script to run Django management commands. /opt/mailman/mm/bin/mailman (sample) Script to run mailman commands. and /opt/mailman/mm/bin/gunicorn (sample) Script to start Gunicorn. You will see they all do things like activate the venv or run a command from venv/bin. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by Mark Sapiro

On 12/9/20 6:06 PM, matthew(a)alberti.us wrote: > Thanks Mark. Also, just to confirm, should the database connection string > also be updated? In both the core and web configuration, I have something > like: > > DATABASE_URL=mysql+pymysql://mailman:password@database/mailmandb > > Note the trailing UTF-8 encoding stuff isn't there. Should we be specifying > utf8mb4 there as well? In the mailman.cfg database section, you probably want url: mysql+pymysql://myuser:mypassword@mymysqlhost/mailman?charset=utf8mb4&use_unicode=1 I don't know why you would have a DATABASE_URL setting in the web configuration. Exactly where is this? I don't think it would be meaningful in any Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: archiving problem & updates

by Mark Sapiro

On 2/18/21 10:00 AM, Christian Stalberg via Mailman-users wrote: > Archiving has stopped working. No changes were made to the server. How can I diagnose and troubleshoot this please? Start by looking at Mailman's logs and also see if there are messages to be archived in Mailman's var/archives/hyperkitty/spool/ directory. > Are there instructions for how to update mailman3 somewhere? Is there a listing of bug fixes also? There are some instructions at <https://docs.mailman3.org/en/latest/upgrade-3.2.html>. Bug fixes are listed in each project's 'news', e.g., <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.…> for Mailman core and <https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html> for HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Disabled by bounce

by Mark Sapiro

On 2/1/23 10:32, Allan Hansen wrote: > Thank you, Mark. > By > > "However, all of the above can be avoided without any DMARC changes by > enabling bounce probes." > > Do you mean that I can get rid of the 'From' mangling, which has been a frequent source of embarrassment because the list address is captured and reused by type-ahead when sending non-list messages and those messages instead going to 1000 subscribers. No. If you enable bounce probes, it will prevent users having delivery disabled and being unsubscribed by bounce if the only bounces are for DMARC policy reasons, but they will still be missing mail if you don't apply DMARC mitigations. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: 120 gmail users removed from lists !

by Mark Sapiro

On 10/24/23 10:04 AM, Andrew Hodgson wrote: > > Speaking of the new additions in Mailman 3.3.9, does anyone have a list of the domains Google are using which we can add to the list so we can disable the unconditional DMARC mitigations for all list posts? Its probably somewhere obvious on a Gitlab issue or similar, but haven't found it yet. The only domains you need to consider are those of your list members, probably only gmail.com, and maybe googlemail.com. I'm not sure how gmail would treat mail From: user(a)some.other.domain where the MX for some.other.domain is a google server, but that could be potentially any domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Detecting abuses (login errors)

by Mark Sapiro

On 5/30/24 03:52, Marc SCHAEFER wrote: > Hello, > > If someone tries to access an account multiple times with a bad password, > is there anything in the Mailman3 web app to report this? > > 1. I didn't see any info about login errors in the logs I have, maybe > I need to enable something? > > 2. is it possible to customize log output so that the proxified > IP address is written in the log? (I use a reverse proxy) > > The idea would be to trigger fail2ban & AbuseIPdb on those. Web logins are handled by django-allauth <https://pypi.org/project/django-allauth/> This is a question for that project. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: How to run this script (attached) in the mailman shell (or withlist)?

by Mark Sapiro

On 8/5/25 15:18, Wikinaut wrote: > Okay, the mileage was long. > It now works finally. Thank you for your patience. > > How to place the script somewhere else ( outside /opt/mailman/venv/bin ), is this possible to have it in /home/maillistgen for example? It can be anywhere, but it has to be importable by Python which means it needs to be in a directory somewhere in sys.path. You could put it in /home/maillistgen if you `export PYTHONPATH='/home/maillistgen'` before running `mailman shell` The PYTHONPATH environment variable will add that directory to sys.path for subsequent python invocations. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

[MM3-users] Re: After moving to a another server, mail footers show only this smart text "Cache content lost"

by Mark Sapiro

On 9/10/25 06:58, Wikinaut wrote: > After moving to a another server, mail footer shows only text "Cache content lost". > > I moved the two databases (mailman3, mailmanweb) to another server, but now my Mailinglist shows this in the footer, uh, what did I forget to move? You copied the database which includes entries for cached templates in the file_cache table but you didn't copy the CACHE_DIR ($var_dir/cache). The easiest thing is probably to just clear the cache. In mailman shell >>> getUtility(ICacheManager).clear() >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

Search results for query "sapiro"