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

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

4 years, 10 months

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

8 months

[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

5 years, 9 months

[MM3-users] Re: Mailman 3 - Header Filter

by Mark Sapiro

On 9/25/23 06:30, Henrik Rasmussen wrote: > > In my case I would be more interested in holding or discarding mails with subject 'Out of Office' if the mail would otherewise be send the to the list members due to a non-moderated list. > > I would emagine that the order of "check for member moderation" and header_matches would not be significant if holding or discarding the mail due to header_matches, am I right? 🤞🏻 No. It depends on what the check for member moderation rule does. If the post is from a non-member or from a member and the members moderation is Default Processing or if it is List default and the list's Default action to take when a member posts to the list is Default Processing, then the Header Filters will be applied. However, if the post is from a member and the members moderation is directly or via list default any of Hold, Reject, Discard or Accept, that is the action that will be applied. > If so, I would think that Header "subject:" or "subject" with Pattern "^(?i)(.*)autosvar(.*)" - without the double quotes - and Function "Hold for moderation" or "Discard" should either hold or discard any message with "Autosvar" (danish word for "Out of Office reply") somewhere in the subject, but that doesn't happen. What is the correct syntax? Do not include the : in the header name. Other than that, your pattern should be OK but the ^, the (?i) and the parentheses around .* are all unnecessary. > *) In a prevous mail I was told that ^ would tell Mailman that it is a regex. That is true for lots of things where either a string value or a regexp is acceptable such as the * these nonmembers entries, but the Pattern entry for Header Filters is always a regexp and is searched with re.search with re.IGNORECASE, so while your pattern above should work, a much simpler pattern is just "autosvar" (w/o the quotes). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Manage Member(s) Mailman Settings / Display Names

by Mark Sapiro

On 1/11/20 2:43 AM, Jim Ward wrote: > I will admit I was partial to the MM 2.1 columns and checkboxes but the end result is the same, HOWEVER: > > 1) The member 'Display Name' does not seem to be available to be managed by me the domain/list administrator. > 2) The 'Search Members' function appears to be limited to the email address only and does not include display name > > These items are important to me as the list I am running includes many that are not, nor will they really ever be, technically savvy enough to access and manage their own account. Part of this is because of the architecture of Mailman 3. In mailman 2.1, we have lists and members of those lists and no connection between a member of one list and a member of another list, even if their email addresses are the same. Thus, a member of a list and that member's display name are things associated only with that list, and can be manipulated by the list admin. Mailman 3 is different. In mailman 3 we have users and addresses. A user has a display name and one or more addresses, one of which is preferred, and each address has a display name. These are independent of any list and belong to the user. Then, a list member can be a user, in which case, the address associated with this member is the user's preferred address and the display name is the user's display name (or maybe the display name of that address, I'm not sure). Or, a list member can be an address in which case, the member's display name is the display name associated with that address. Thus, in Mailman 3 the display name associated with a list member can be one of several, and these belong to the user, not to the list. As far as not searching display names is concerned, this is <https://gitlab.com/mailman/postorius/issues/378>. -- 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: hyperkitty: "incorrect string value" for botched utf-8 encoding

by Mark Sapiro

On 5/25/20 9:47 AM, thoralf via Mailman-users wrote: > hi, > > my hyperkitty installation (3.2.1 from debian buster) started to act up > recently with > > (1366, "Incorrect string value: '\\xF0\\x9F\\x99\\x82\\x0AA...' for > column `mailman3web`.`hyperkitty_email`.`content` at row 1") > > for every new mail that is about to be archived, i'll quote the full > error mail at the end of this mail. > > i traced the issue to a slighty smiling face (aka u+1f642) in this > rather interestingly encoded email: > > […] > Content-Type: multipart/mixed; > boundary="===============2457401976140816263==" > > --===============2457401976140816263== > Content-Type: multipart/alternative; boundary="5ecb6fd9_327b23c6_2042" > > --5ecb6fd9_327b23c6_2042 > Content-Type: text/plain; charset="utf-8" > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > > kann halt NIE am mittwoch. viel spass =F0=9F=99=82 > […] > --5ecb6fd9_327b23c6_2042 > Content-Type: text/html; charset="utf-8" > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > > <html xmlns=3D=22http://www.w3.org/1999/xhtml=22> > […] > <div dir=3D=22auto=22>kann halt NIE am mittwoch. viel spass =F0=9F=99=82<= > /div> > --5ecb6fd9_327b23c6_2042-- > […] > --===============2457401976140816263==-- > > … which still lingers around in > /var/lib/mailman3/archives/hyperkitty/spool . > > is this to be expected, or might it be a good idea to amend mailman3 / > hyperkitty to deal with this more gracefully? When HyperKitty gets an exception like this in archiving a message, it queues it in /var/lib/mailman3/archives/hyperkitty/spool and on every new post, retries the queued messages. This message fails again on retry and is requeued. How would you suggest this be handled more gracefully? The underlying issue has been seen before. The basic problem is in MySQL and MariaDB the encoding is utf8 which only accepts utf8 encodings up to 3 bytes. It needs to be utf8mb4 to accept characters outside the base plane. I know there is a thread on this somewhere, but I can't find it right now. -- 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: Sender: header

by Mark Sapiro

On 11/30/21 7:51 PM, Philippe B wrote: > MM2 adds the header "Sender: LISTNAME-bounces@DOMAIN" to messages sent to list members. > > That causes Outlook (among others?) to display the "originator" of a message from a REAL POSTER as: > > LISTNAME-bounces@DOMAIN on behalf of REAL POSTER <REAL.POSTER@DOMAIN> > > That phrasing helps identify instantly what list a message is coming from, when that list doesn't use a Subject prefix and when its address isn't in the To: or Cc: headers. (And it turned out that some of our list members were even relying on it to trigger security alerts!) Mailman 2's adding of a Sender: header is an artifact from a time when some MTAs would return bounces to the Sender:. I think yours is the first comment I've seen that actually likes the way Outlook renders it. Most want to know how to prevent that which is why MM 2 has an option to not add it. As far as triggering alerts or filtering is concerned, there are other headers in list mail that can be used for that purpose. > It doesn't look like there's any current MM3 setting that would accomplish the same result, so the question is: How difficult would it be to revive the Sender: header? By revive, do you mean add a feature in MM 3 to add a Sender: header. If so, you could submit a request at `https://gitlab.com/mailman/mailman/-/issues`. If you mean how difficult would it be for you to do it. here's a one line patch that will unconditionally remove any pre-existing Sender: header and add one with the list posting address. ``` --- a/src/mailman/handlers/rfc_2369.py +++ b/src/mailman/handlers/rfc_2369.py @@ -67,6 +67,7 @@ def process(mlist, msg, msgdata): ('List-Owner', '<mailto:{}>'.format(mlist.owner_address)), ('List-Unsubscribe', '<mailto:{}>'.format(mlist.leave_address)), ('List-Subscribe', '<mailto:{}>'.format(mlist.join_address)), + ('Sender', mlist.posting_address), )) if not msgdata.get('reduced_list_headers'): # List-Post: is controlled by a separate attribute, which is somewhat ``` -- 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

Search results for query "sapiro"