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

[MM3-users] Re: Disabled by bounce

by Mark Sapiro

On 2/2/23 18:19, Allan Hansen wrote: > Mark, > > I can see your argument here, but if a 'Disabled by bounce' subscription is enabled, it would require just looking at that particular subscription and set the bounce count to 0, so that the next bounce (before staleness) does not disable it again. We are talking about two different issues here. One issue is not resetting the bounce score to zero when (or before) a disabled by bounce user's delivery is enabled. This is https://gitlab.com/mailman/mailman/-/issues/1061 and I'm working on it. The other issue is not resetting the user's bounce score when it goes stale as opposed to when another bounce is received and the score is stale. Other than the fact that one might be misled by seeing a non-zero bounce score which is stale, there are no other issues from waiting for a bounce to reset a stale score. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: [migration] to a another server - one year database apparently lacks fields for newer mailman3/django suite

by Mark Sapiro

On 10/20/23 14:04, Wikinaut wrote: > I also solved this issue. > How? > > By adding columns to two tables in the database mailman3web: > > alter table hyperkitty_mailinglist add column archive_rendering_mode varchar(255) default null; > alter table socialaccount_socialapp add column `provider_id` varchar(200) NOT NULL; > alter table socialaccount_socialapp add column `settings` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL CHECK (json_valid(`settings`)); The proper fix is just to run `mailman-web migrate`. See https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… You should also run that and `mailman-web collectstatic` `mailman-web compress` and `mailman-web compilemessages` any time you do any kind of update. See https://docs.mailman3.org/en/latest/install/virtualenv.html#collect-static-… et. seq. Running `mailman-web migrate` at this point may fail because of the changes you made manually. -- 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 11:51 AM, info(a)joergschulz.de wrote: > Am 24. Oktober 2023 um 18:07 schrieb "Yvan ♞" <elemac(a)free.fr>: > >> >> I add an SPF entry on my web hosting, domain name: "v=spf1 mx ptr >> include:_spf.google.com -all" and it seems to fix the problem. >> > Smart. As I understand above statement, it allows the google servers to send out emails for your domain. Not sure you want that. But you're right, mailman will eventually pick up the -all for the google addresses and apply the DMARC mitigation to google originating messages. Is this assumption correct? Wrong. Mailman in conditionally applying DMARC mitigations considers only the DMARC policy if any of the From: domain. Whether or not an outgoing message might be rejected for DMARC policy or any other reasons has no automatic effect on the application of DMARC mitigations to subsequent messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Mark Sapiro

On 8/18/25 12:06 PM, Wikinaut wrote: > Thank you. > As I need to go through ~20 mailing lists, is there any way to programmatically also modify the templates? > > I could not find a script for doing this but it would nice to have, as I managed, as known, to write and to run scripts, which is very helpful (because we re-generate the _whole_ mailsystem daily if there are changes in our membership database). If you want to use default templates for everything, just remove everything under /opt/mailman/mm/var/templates/. If you want a custom footer for all lists, remove list:member:generic:footer.txt from all the /opt/mailman/mm/var/templates/lists/LIST_ID/LC/ directories and create the footer at /opt/mailman/mm/var/templates/site/LC/list:member:generic:footer.txt -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: missing graphics in Postorius

by Mark Sapiro

On 12/7/21 4:01 PM, David Newman wrote: > On 12/7/21 11:17 AM, Mark Sapiro wrote: >> Add '127.0.0.1' to ALLOWED_HOSTS anyway. > > Done, thanks. > > Given that DNS works fine on this host, with localhost and 127.0.0.1 > resolving backward and forward, this seems like a bug. Shouldn't the > resolver be able to recognize localhost without hard-coding an address? It's probably a bug, but if so, it's a Django bug and not anything Mailman can do anything about. ... >> Assuming you have >> ``` >> STATIC_ROOT = '/opt/mailman/web/static' >> ``` >> in your /etc/mailman3/settings.py file, you may need to create that >> directory if it doesn't exist. You shouldn't need to manually create >> the /opt/mailman/web/static/postorius directory if the >> /opt/mailman/web/static directory exists and is writable/searchable by >> the Mailman user. > > Yes, that was it. Thanks. > > Previously you'd pointed out what you considered an error in the venv > docs, with the workaround to manually create the /opt/mailman/web > directory [1]. I think the same issue applies here, and also that > /opt/mailman/web and subdirectories need to be owned by the mailman user. I don't recall what I said about that but near the end of the Initial Configuration section at https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… it says ``` Make sure that the logging path is created. You can run mkdir -p /opt/mailman/web/logs to create the path. ``` I added ``` Also make sure the ``STATIC_ROOT`` directory is created. ``` after that. As far as things being owned by the mailman user, early in the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup there is a note that says ``` Make sure that you are running commands as mailman user from here forth. Setup Mailman user. ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: List description as sender

by Henrik Rasmussen

Yes, but even the Settings -> Alter Messages -> Anonymous list is set to No, the 'anonymous_list': is still True. That is my problem, I think. -- Henrik Rasmussen her(a)adm.ku.dk University of Copenhagen, Danmark -----Oprindelig meddelelse----- Fra: Mark Sapiro <mark(a)msapiro.net> Sendt: 24. september 2018 15:54 Til: mailman-users(a)mailman3.org Emne: [MM3-users] Re: List description as sender On 9/24/18 4:00 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: >> On 09/17/2018 01:04 AM, Henrik Rasmussen wrote: >> I think your choices are: >> >> 1) Don't configure the list as anonymous. > > I've just tested it on a list which was imported from Mailman 2, but changing the list to announced doens't seem to affect the From: ... > 'anonymous_list': True, Set anonymous_list False. -- 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/

7 years, 10 months

[MM3-users] Re: Any known limit of number of lists that one can be owner/member of?

by Mark Sapiro

On 5/14/19 6:34 PM, Alan So wrote: > Thanks for your explanation. Just verified with a normal user and notice that no lists will be shown when all is selected since all lists are not advertised. I thought that for a user with that issue (as owner of more than 50 lists) at least her subscription or lists with her as owner will be shown. I understand it can be confusing because "all" is one of the "roles" in the "Filter by Role" dropdown, but the unfiltered "all-lists" view is generated differently from the other filtered views and only shows unadvertised lists to a site admin (superuser). That's also why the all-lists view is paginated (and can show more than 50 lists) and the other roles are not. We will be fixing that part. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Mailman shell tutorial

by Mark Sapiro

On 6/11/19 6:00 PM, Andrew Bernard wrote: > > I have this going, and it is great. But I recall seeing something called > mmclient or similar which has simple commands like show user, show lists, > and so on. Is that still available? Are you thinking of the mailman command itself? Things like `mailman lists` and `mailman users`. Try running the `mailman` command itself with no arguments to see a list of sub-commands and then `mailman sub-command --help` to get the details of a particular subcommand. > Now knowing how mailman shell works, anybody could write their own commands, > but I don't want to reinvent wheels. I don't know what it is you are trying to accomplish, but yes, you can create scripts which you run via `mailman shell -run ...`, but is there something specific you are trying to do that is not currently available via the `mailman` command or the Postorius wb UI? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Help with troubleshooting mailman3 DNS lookups

by Mark Sapiro

On 2/23/21 3:11 PM, Simon Handfield via Mailman-users wrote: > However when messages are sent to mailman3 lists we're still seeing hits on the old DNS servers. > > I have tried to find a config that references the old servers but have not been able to find one. Because Mailman doesn't directly access DNS. As far as I know, there are only two pieces in Mailman core that indirectly access DNS. DMARC mitigations look up sending domain DMARC policy via the dnspython package <https://pypi.org/project/dnspython/> and if you have enabled ARC signing in Mailman via [ARC] enabled: yes it uses authheaders <https://pypi.org/project/authheaders/> I don't know what these packages might be looking at to see the old servers, but as far as I know, nothing else is doing DNS lookups. The modules that invoke these are mailman/rules/dmarc.py and mailman/handlers/arc_sign.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/7/21 1:32 AM, Marcus Granath wrote: > > Sorry, but actually I can not find any "Users dropdown" to select "Non-Members" at any Postorius in my web interface. :-( It's one of the various tabs across the top of the page. What Postorius version is this? Seversal versions back, I think it was called `members` rather than `users`. In current Postorius, the tabs are Info Subscription requests Held messages Users Templates Settings Mass operations Ban List Header filters Delete As I said, `Users` used to be `Members` and `Templates` was added at some point, but that's the general idea. > Maybe, could it be that I am actually not the admin of the mailman3 server, I'm "just" the admin of my mailman-list - so just admin for my mailman-list and not for the mailman server? As Steve said, the list admin should see all those. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

Search results for query "sapiro"