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

[MM3-users] Re: Emailing a list from the list server

by Mark Sapiro

On 6/1/20 11:56 AM, Mark Dadgar wrote: > On Jun 1, 2020, at 11:45 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> What's in Postfix's mail.log? > > > Jun 1 11:54:55 mail postfix/lmtp[238922]: 1F42613BEB5: to=<test3(a)pdc-racing.net>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.04, delays=0.02/0.01/0/0.02, dsn=2.0.0, status=sent (250 Ok) OK. It was delivered to Mailman's LMTP runner which presumably accepted it and queued it because that's the only case in which it returns '250' You could set [logging.smtp] level: debug in mailman.cfg to get more logging, but I think that that will just add confirmation of what we already know, i.e., it was queued in the in queue. So that leaves us with: some error in processing shunting the message. In that case the error would be logged in mailman.log and the message would be in var/queue/shunt. or some rule discarding the message. In that case, there should be a DISCARD: <message-id> entry in mailman.log. If that's the case, we still don't know which rule did the discard and why. One thing you might consider is the possibility that you've missed some message because it was delivered to a local mailbox rather than where you expect it. In my case, msapiro.net has an MX record pointing to my real mail server, but it is also the host name of my development box so mail generated on that box for me winds up in /var/mail/mark instead of being delivered to my real mail server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/7/25 02:30, MegaBrutal via Mailman-users wrote: > On Mon, Apr 7, 2025, 03:04 Mark Sapiro <mark(a)msapiro.net> wrote: > >> so it is saying there is only one choice for sender which I think means >> there is only one address associated with your login. That still doesn't >> explain why it thinks you're not a list member. >> > > Indeed, it doesn't explain. Are there any maintenance scripts or DB queries > you recommend to run to get to see what's happening under the hood? Not offhand. What is the exact email address that you are logging on to the web UI with. Does it match exactly with the address of a list member or are there mixed-case differences? You might try an interaction like this: ``` mailman-web shell Python 3.12.8 (main, Dec 21 2024, 12:52:28) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from django_mailman3.lib.mailman import get_mailman_client >>> client = get_mailman_client() >>> list_id = 'test.example.com' # your actual list_id >>> rest_list = client.get_list(list_id) >>> email = 'user(a)example.com' # your actual email >>> member = rest_list.get_member(email) >>> member This should print something like <Member 'user(a)example.com' on 'test.example.com' with role 'member'> ``` This is exactly what HyperKitty is doing except in your case rest_list.get_member(email) is throwing a ValueError exception instead of returning the member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 1 week

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

4 years, 9 months

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

1 year, 10 months

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

Search results for query "sapiro"