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

[MM3-users] Re: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Johannes Rohr

Am 09.01.23 um 06:30 schrieb Mark Sapiro: > On 1/8/23 01:37, Johannes Rohr wrote: >> >> Am 16.09.21 um 01:13 schrieb Mark Sapiro: >>> >>> Currently Mailman 3 does not support whitelisting the members of >>> another list. >> >> Is this still true in the current version? I have been using this >> quite extensively with mailman2, so loosing it is the one major >> drawback of the migration. > > > Yes it is still true. This is > https://gitlab.com/mailman/mailman/-/issues/794 Thanks! I assume, there is a reason why this cannot be easily implemented, else it would have been. Asking because I know a number of people would make extensive use of this in MM2. Johannes

2 years, 8 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Mark Sapiro

On 3/31/23 14:17, Andrew Hodgson wrote: > Hi. > > Has anyone managed to get this script running using the Mailman-Web setup in a venv? It was working when Settings.py was in the /opt/mailman/mm directory but since moving to Mailman-Web has it in /etc/mailman3. I have been trying to import Mailman-Web to get the Django environment running but every time I do this I get a not configured exception raised. First, get the latest version of the script from https://www.msapiro.net/scripts/clean_users.py - not the one in this threat attached to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Then, you need to change `/opt/mailman/mm` in three places to `/etc/mailman3` as in ``` --- /opt/mailman/mm/bin/clean_users.py 2021-05-08 20:03:31.657565251 -0700 +++ clean_users.py 2023-03-31 15:48:31.772383287 -0700 @@ -2,13 +2,13 @@ import os import sys -sys.path.insert(0, '/opt/mailman/mm') +sys.path.insert(0, '/etc/mailman3') # The above line is required. The next line doesn't hurt, but it doesn't work # because the PYTHONPATH environment setting is processed by Python's setup # and must be in the environment when Python starts to be effective. -os.environ['PYTHONPATH'] = '/opt/mailman/mm' +os.environ['PYTHONPATH'] = '/etc/mailman3' os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' -os.environ['MAILMAN_CONFIG_FILE'] = '/opt/mailman/mm/mailman.cfg' +os.environ['MAILMAN_CONFIG_FILE'] = '/etc/mailman3/mailman.cfg' import django django.setup() ``` Also, look at this ``` # If we delete the Django user and there is a Mailman user with no memberships # shall we delete the Mailman user too. DELETE_MAILMAN_USER = False # Shall we delete the Django user if there is a Mailman user with no # memberships or only if there is no Mailman user. DELETE_DJANGO_IF_MAILMAN = True ``` and consider whether you want to set `DELETE_MAILMAN_USER = True` to also delete the Mailman user if any, and/or set `DELETE_DJANGO_IF_MAILMAN = False` to not delete the django user if there is a Mailman user with no memberships. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Mark Sapiro

On 7/26/24 09:21, Elias Rudberg wrote: > > Yes, there are strange-looking long queries there at the times when > these errors happen. > > Here is an example of what such a request URL looks like, where I have > replaced some parts with [...] to avoid including anything sensitive: > > Request URL: > https://[...ip-address...]/mailman3/postorius/lists/?widget=[...]svg[...]onload=confirm[...]xss-widget[...]&height=[...]svg[...]onload=confirm[...]xss-height[...]&screen=[...]svg[...]onload=confirm[...]xss-screen[...]&pass2=[...]svg[...]onload=confirm[...]xss-pass2[...]&redirect_to=[...]svg[...]onload=confirm[...]xss-redirect_to[...]&items=[...]svg[...]onload=confirm[...]xss-items[...]&string=[...]svg[...]onload=confirm[...]xss-string[...]&hidden=[...]svg[...]onload=confirm[...]xss-hidden[...]&f=[...]svg[...]onload=confirm[...]xss-f[...]&step=[...]svg[...]onload=confirm[...]xss-step[...]&role=[...]svg[...]onload=confirm[...]xss-role[...]&preview_nonce=[...]svg[...]onload=confirm[...]xss-preview_nonce[...]&date=[...]svg[...]onload=confirm[...]xss-date[...]&event=[...]svg[...]onload=confirm[...]xss-event[...] I see similar ones from time to time. > I looked up the IP address that those requests come from (all seem to > come from the same IP address) and that corresponds to a hostname called > something with "scanner" that looks like it belongs to some > cybersecurity company. There are also many other requests from that same > IP address, including things like "GET /file://etc/passwd" and similar, > so it looks like someone is bombarding us with various weird requests as > a form of "scanning" where they are trying to find vulnerabilities. That > could also explain why we see those "Internal Server Error" errors > recurring every day, if they run that vulnerability scan daily. Yes, I think these are attempts to find vulnerabilities. > So maybe those strange request URLs that lead to the error messages > "[Django] ERROR (EXTERNAL IP): Internal Server Error" that we are > seeing, are constructed by someone who is actively trying to trigger bugs. I don't think this is a DOS attack or an attempt to trigger bugs. I think they are attempts to find and then exploit vulnerabilities. > But anyway, no matter what strange request URL comes in, I guess the > "Internal Server Error" indicates something going wrong in Mailman or in > Django, a bug in how the request is processed? I'm not certain, but I think it's a Django issue rather than a Mailman issue. In my case, I don't get that many and I just ignore them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

sorry, in this directory: /var/lib/mailman/var/logs Thanks El mar., 1 ago. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 10:15 AM, Rafael Mora wrote: > > Hello, > > > > I got postfix installed and I can use the command mail to send emails. > The > > thing is that mailman can't send the confimation mail yet, where should I > > look for the error?? > > > Look in Mailman's logs and Postfix's 'maillog'. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

[MM3-users] Re: moderation notices for list-owner being redirected to mailman address

by Mark Sapiro

On 2/7/22 16:11, Philippe B wrote: > I think that your last sentence helped us figure out what's going on. > > When Mailman generates a moderation message "To: LIST-owner" it actually delivers it to the address(es) of the LIST's moderator(s), which makes sense. No, it delivers the message to the union of the sets of owner addresses and moderator addresses. > In all the cases where we've seen that behavior, it turns out that the list involved didn't have any moderator, and we have site_owner set to "mailman"... You don't need to have moderators. The owners get the message too. > However, the lists had an owner, and we're not seeing those moderation messages being sent to their owner (instead). Is that something that needs to be configured explicitly somewhere? The only things that might affect this are if Settings -> Automatic Responses -> Autorespond to list owner is Respond and discard message or if the owners delivery_status is other than DeliveryStatus.enabled. Note that finding an owner's delivery status is tricky. The owner can find it in Postorius by going to https://www.example.com/mailman3/accounts/subscriptions/ and clicking on the entry for the list with role owner. This delivery status is not the same as the delivery status for the same address with a member role if there is one. For an admin you could do ``` $ bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> owner = m.owners.get_member('user(a)example.com') >>> owner.delivery_status <DeliveryStatus.enabled: 1> If you needed to set it here, you could do >>> owner.preferences.delivery_status = DeliveryStatus.enabled >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

Jan Eden wrote: > I tried setting permissions on /opt/mailman/fulltext_index to 777 > temporarily, but the issue remained (as expected). It occurs in the > Whoosh backend of Haystack (whoosh_backend.py, line 132-133): > > if self.use_file_storage and not os.path.exists(self.path): > > > > os.makedirs(self.path) > > > where self.path is referenced, which is defined in line 110 (as part of > the __init__ function): > > def __init__(self, connection_alias, **connection_options): > > super().__init__(connection_alias, **connection_options) > > self.setup_complete = False > > self.use_file_storage = True > > self.post_limit = getattr(connection_options, "POST_LIMIT", 128 * 1024 * 1024) > > self.path = connection_options.get("PATH") > > > > Unfortunately, I cannot see where the PATH key for connection_options is > defined. It is defined in the HAYSTACK_CONNECTIONS dictionary in your Django settings.

2 years, 9 months

[MM3-users] Re: The email confirming the registration of an account on postorius is not correctly translated in Italian

by Mark Sapiro

On 7/30/20 9:43 AM, Massimo Zappalà wrote: > > Everything works, except for this: > > When I register a new account on postorius, he sends me a confirmation email totally in English, except the following final block which is sent in Italian: > > in my /usr/lib/python3/dist-packages/allauth/locale/it/LC_MESSAGES/django.po > > #: templates/account/email/email_confirmation_message.txt:7 > #, python-format > msgid "" > "Thank you from %(site_name)s!\n" > "%(site_domain)s" > msgstr "" > "Grazie da %(site_name)s!\n" > "%(site_domain)s" OK. > By carefully analyzing the same file .po, I notice that the Italian translation of the whole text already exists. > Why does the confirmation email arrive in English? > > #: templates/account/email/email_confirmation_message.txt:1 > #, fuzzy, python-format This is marked fuzzy so it isn't used. If you believe the translation is correct, remove the above line (or remove ' fuzzy,' from it) and then recompile the django.mo with msgfmt. Note that the current HEAD on github <https://github.com/pennersr/django-allauth/blob/master/allauth/locale/it/LC…> has the above line as just #, python-format > #| msgid "" > #| "User %(user_display)s at %(site_name)s has given this as an email " > #| "address.\n" > #| "\n" > #| "To confirm this is correct, go to %(activate_url)s\n" > msgid "" > "Hello from %(site_name)s!\n" > "\n" > "You're receiving this e-mail because user %(user_display)s has given yours " > "as an e-mail address to connect their account.\n" > "\n" > "To confirm this is correct, go to %(activate_url)s\n" > msgstr "" > "Ciao da %(site_name)s!\n" > "\n" > "L'Utente %(user_display)s di %(site_name)s ha registrato questo indirizzo e-" > "mail.\n" > "Per confermare, clicca qui %(activate_url)s\n" -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/4/21 6:30 AM, Duane Raymond wrote: > FYI: in the mailman log was also the following traceback > > Mar 04 14:08:24 2021 (5044) Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/core/runner.py", line 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/core/runner.py", line 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/runners/pipeline.py", line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/core/pipelines.py", line 50, in process > handler.process(mlist, msg, msgdata) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/handlers/member_recipients.py", line 84, in process > for member in mlist.regular_members.members > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/handlers/member_recipients.py", line 83, in <genexpr> > recipients = set(member.address.email > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/roster.py", line 239, in members > yield from self._get_members(DeliveryMode.regular) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/roster.py", line 226, in _get_members > if member.delivery_mode in delivery_modes: > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/member.py", line 212, in delivery_mode > return self._lookup('delivery_mode') > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/member.py", line 174, in _lookup > pref = getattr(self.address.preferences, preference) > AttributeError: 'NoneType' object has no attribute 'preferences' > Mar 04 14:08:24 2021 (5044) SHUNTING: 1614866904.2741017+f1f320a5d0006e885586be5b33543e364e3829b4 Assuming this relates to the missing messages, there is no issue with delivery to Mailman. This message is getting to Mailman but throws the above exception during processing and is shunted. You can examine this messages with `mailman qfile var/queue/shunt/1614866904.2741017+f1f320a5d0006e885586be5b33543e364e3829b4.pck` and similarly for other shunted messages. The issue here is Mailman is going through the roster of regular (non-digest) list members to find those with delivery enabled and it finds a member that has no associated address. Can you view the members of this list? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Add domain to Mailman, can't create list with that new domain

by Mark Sapiro

On 10/17/24 15:06, Andy Matthews wrote: > Hey Mark, I'm looking at the documentation here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… > > Which seems to indicate that adding a domain via the CLI is as easy as: > > from mailman.interfaces.domain import IDomainManager > from zope.component import getUtility > manager = getUtility(IDomainManager) > manager.add('example.org') > > It's not until much further down the page that there's any reference to "committing" a change. But sure enough when I add the following three lines to the previous 4, I'm able to create a mailing list with staging.mydomain.dev using the REST API. > > from mailman.config import config > transaction = config.db > transaction.commit() I don't know how you are running these Python interactions, but if you are using `mailman shell` interactively, things like IDomainManager, and getUtility and lots of other things are imported automatically and commit() and abort() are also predefined. > I created an issue suggesting as much on GitLab: > https://gitlab.com/mailman/mailman/-/issues/1178 Also when using `mailman shell`, at startup it says: ``` Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. ``` I've seen issue #1178. The issue is actually more widespread than that. There are lots of things done in the Python snippets in the docs to support the fact that they are all actually run as doctests as part of our CI to ensure they are correct. In practice it is generally easier to run these in `mailman shell`. However, the docs themselves don't say that. We say a bit at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… but I don't know a good way to say that globally. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 3 weeks

[MM3-users] Re: Mailman 3 installation, no mails in hyperkitty, unable to add footer.

by Mark Sapiro

On 8/23/19 8:11 AM, ugniusviln(a)gmail.com wrote: > I have read documentation, but still have stupid questions, could You please help, because I can't make it working. I do not understand something important. I have no experience with python at all. I have mailman 3, python 3.5 in my debian OS system, and additional packages like uwsgi and ect. using https://buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman… about till chapter 6. I understand mailman suite has hyperkitty already. But I am not sure about: > > 1. Does mailman-suite have hyper-kitty inside? Because if I run $python manage.py runserver - it runs. In installed it under dedicated OS user home and fonfigured to run. > I can create lists, event add lists to hyperkitty page using: $django-admin runjob new_lists_from_mailman list server sends messages to list members as well. But nothing happens more. No emails come to hyperkitty, arciver log 0 size. > $ python manage.py runjobs -l shows the lists of the jobs, so seems nothing to add. How exactly did you install Mailman? The document you reference gives alternatives. You don't say exactly what you did. > 2. If I (using Postorius web interface) add footer template to my list under regular message, something strange happens. Mailman stops to send messages for list members. No any entries in the logs. Just Mailman log writes: "unable to connect localhost port 25" and no more explanation. If I delete list's footer template (web interface), mailman starts working again. What is bad here? How to add custom footer? In mailman 2 if was working so good and was easy to setup. It appears that no MTA is listening on localhost port 25. Is your MTA even running? It is extremely unlikely that this has anything to do with adding a termplate in Postorius. You might be better off installing Debian's 'mailman3-full' package <https://packages.debian.org/search?keywords=mailman3-full&searchon=names&su…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

Search results for query "sapiro"