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

[MM3-users] Re: HyperKitty failure

by Mark Sapiro

On 1/2/22 4:34 AM, horvath.arpad.szfvar(a)gmail.com wrote: >> Can you go to https://lists.xxx.hu/hyperkitty/api/lists and get a >> response from Django REST framework which is a json representation of >> your mailing lists info? > > In this list I have just one list that I created for testing. And I can't see there the two lists I've imported from mailman2, e.g. korus. I guess because of admin is not a list list member there. I can see the korus at https://lists.xxx.hu/hyperkitty/ , but not at https://lists.xxx.hu/postorius/lists/ . when you view https://lists.xxx.hu/postorius/lists/ is there a Filter by Role dropdown at the top of the listing? If so, if you select `All` do you then see the lists. Postorius by default shows only those lists in which you have a role. If you still don't see the lists, what does the command `mailman lists` show? > I guess the setting below is not good. > > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') > > Should I set it to > ('https://lists.xxx.hu/hyperkitty', '::1') ? Doesn't seem to work, like that. It needs to be an IP. Set it to `('xxx.xxx.xxx.xxx', '127.0.0.1', '::1')` where xxx.xxx.xxx.xxx is the IP of lists.xxx.hu or just `('xxx.xxx.xxx.xxx',)` would probably work. > And what about MAILMAN_REST_API_URL? > How can I found its proper value? It's currently the default value > but if I try to reach it with > wget http://localhost:8001 > I get a 404. not found. How can I find the right value? If Postorius works, It's good. `wget http://localhost:8001` returns a 404 as it should because this is a REST API and `/` is not a known endpoint. Something like `wget --user restadmin --password restpass http://localhost:8001/3.1/lists` should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/17/23 9:10 AM, eboltz(a)lhtservices.com wrote: > Mark, > > Here is my postconf -n > > alias_database = hash:/etc/aliases > alias_maps = hash:/etc/aliases > always_add_missing_headers = yes > append_dot_mydomain = no > biff = no > compatibility_level = 2 > default_destination_concurrency_limit = 15 > default_destination_recipient_limit = 30 > header_checks = regexp:/etc/postfix/header_checks > header_size_limit = 409600 > inet_interfaces = all > inet_protocols = ipv4 > local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp > mailbox_size_limit = 0 > mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain > myhostname = lists.example.com > mynetworks = 127.0.0.0/8 [::fff:127.0.0.0]/104 [::1]/128 > myorigin = /etc/mailname > readme_directory = no > recipient_delimiter = + > relay_domains = hash:/var/lib/mailman3/data/postfix_domains > relayhost = [mail.smtp2go.com]:587 > smtp_always_send_ehlo = yes > smtp_sasl_security_options = noanonymous > smtp_tls_CApath = /etc/postfix/o365_smtp_cert.pem > smtp_tls_security_level = may > smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache > smtp_use_tls = yes > smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination > smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem > smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key > smtpd_tls_security_level = may > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > unknown_local_recipient_reject_code = 550 > virtual_alias_maps = hash:/var/lib/mailman3/data/postfix_vmap It looks like you are now following <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. > What would I have to do to ensure that MM3 and postfix (same new server) use the newly created lists.example.org domain, which only exists within Postfix when setting up the Postorius domain and lists? > I want to have it so that whatever the list name is, for example 'Staff(a)lists.example.org' will route through Postfix correctly. Have you set an alias_domain for the lists.example.org domain? What are the contents of /var/lib/mailman3/data/postfix_vmap and /var/lib/mailman3/data/postfix_lmtp? If you feel it is necessary to anonymize the domains in these, please only change the tld so we can see the actual subdomains. -- 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: Message is received but is not sent out. Another, similar message, is processed fine.

by Mark Sapiro

On 6/26/23 8:09 PM, Allan Hansen wrote: > Hi all, > > One of my subscribers is trying to send a message to a list, but it is not being posted. > The smtp.log shows that her first message was posted, but a second message (with 2 retries) was not: > > mailman@list:~/logs$ grep herName smtp.log > Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=40109' > Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) sender: herName(a)hotmail.com > Jun 18 11:25:01 2023 (1243318) <CH3PR12MB82593510B90D8F05177C606BBE5EA(a)CH3PR12MB8259.namprd12.prod.outlook.com> post to theList(a)domain.tlc from herName(a)hotmail.com, 40061 bytes > Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=18343' > Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) sender: herName(a)hotmail.com > Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=19123' > Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) sender: herName(a)hotmail.com > Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=18930' > Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) sender: herName(a)hotmail.com > > At the second retry she copied me and I saw nothing untowards in her message. > She's not getting any error return messages and her subscription is OK. > Both messages were multipart/alternative and both contained Hebrew text. > > I told her I'd look at this, but I'm at a loss. smtp.log is not very useful for diagnosing things like this. It only says a message was received, not why it didn't result in a post from the list as in the first case. What's in mailman.log with those timestamps? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Digests not working correctly

by Joel Lord

Sadly, no cron output emails. On 6/13/2023 1:53 PM, Mark Sapiro wrote: > On 6/13/23 10:46, Mark Sapiro wrote: >> >> If there is nothing in Mailman's mailman.log, I don't know what the >> issue is unless the list's digest_send_periodic flag is False. > > One more thought. Output from these cron jobs written to stdout and/or > stderr will be emailed. You can control to where with a `MAILTO=...` > line in the crontab. Otherwise, they will be mailed to the owner of the > crontab, probably `list` or maybe `root`. Check your MTA logs from > 23:00+ to see if any emails are sent and to where. > -- Joel Lord

2 years

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Mark Sapiro

On 12/12/19 12:42 AM, Marvin Gülker wrote: > > But I now have a different problem. I've removed all offending messages > (it were more than just one that caused the UnicodeEncodeError), but I > still can't access the page for the held messages queue. It gives an > error 500, now with a different exception in the log. I've included it > below. It looks to me that the messages haven't properly been deleted. They have, but I apologize - more is required. > What I did was this: for each offending message hash > > 1. I ran the DELETE query > 2. I deleted the file from the file system > 3. I ran the delete_message() function > > I originally wanted to run only the delete_message() function, but a > quick check on the DB and the file system after running it for one hash > told me that it neither deletes the message from the DB nor from the > file system. The argument for delete_message() is not the hash, it is the <message-id> including the angle brackets. So I did everything at once. I do have a backup of both the > DB and the filesystem from before I started this, in case this broke > something. > > Is there something left that I have to do now? Yes, my bad for not realizing this. There are still references to these messages in the _request table. The columns in that table are id | key | request_type | data_hash | mailing_list_id key is the <message-id> of the request message request_type is 1 for a held message mailing_list_id is a numeric index into the mailinglist table The issue is there are still held message requests there for the messages you removed. You need to delete those entries from the _request table. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: getting all registered users and their lists

by Mark Sapiro

On 1/26/22 00:16, IOhannes m zmoelnig wrote: > > hi, > > TL;DR > is there a scriptable way to get all users that have registered in my > mailman3 (3.2.1) instance and which lists they are subscribed to (if any)? It's in Postorius >= 1.3.6 > longer version: > > we are running Mailman3-3.2.1 as shipped with Debian/buster (i know that > this is not the newest version; at this point, please refrain from > asking me to upgrade my Debian installation or even to switch to a venv > installation of mailman3: i'll eventually do that but right now i've gt > a problem to solve :-)) See above. ... > for this i would like to get a listing of all users that are not > subscribed to any mailinglist. > i would also like to query, when a given user has signed up (so i can > reduce the number of false positives) > > how would i do that? > ideally i would rather not work on an SQL level. You can do this in mailman shell ``` $ bin/mailman shell 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. >>> um = getUtility(IUserManager) >>> for usr in um.users: ... if len(list(usr.memberships.members)) > 0: ... continue ... adr = usr.addresses[0] ... print(f'Name: {adr.display_name}, Email: {adr.email}, Created: {usr.created_on}') ... ``` Or to skip older ones ``` >>> from datetime import datetime >>> um = getUtility(IUserManager) >>> for usr in um.users: ... if len(list(usr.memberships.members)) > 0: ... continue ... if usr.created_on < datetime(2022, 1, 1): ... continue ... adr = usr.addresses[0] ... print(f'Name: {adr.display_name}, Email: {adr.email}, Created: {usr.created_on}') ... ``` -- 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: Programmatic Creation of Users

by Mark Sapiro

On 7/30/22 05:25, jciesla(a)techsupportme.com wrote: > > After a lot of research I now understand that what I am doing in the Core Shell is creating a User entity which has one or more email addresses as well as one or more roles and preferences that exist at the global level. This user entity can Subscribe to zero or more lists. If I am incorrect in the summation please let me know! Almost correct. A User does have preferences but does not have roles. Roles are associated with list memberships, not users. > Assuming that the previous information is correct that brings us to my current dilemma. Specifically, the User entity can Subscribe and interact with lists using the email commands, but they can't Login using the Postorius web interface. If I understand correctly the reason that they can't login is that the underlying Django system does not recognize their account because the account that was created in Core isn't accessible by Django. Instead the user needs to create a Django-specific account at which point the information from Core becomes available in the user's web UI. The simple view is that Django users and Mailman Users are unrelated. Either can exist without the other. They only tie together if they have the same email address. That is the only connection between them. > If that is in fact accurate then I want to take the next logical leap: is it possible to programmatically create an account in Django that is tied to the account that was created in Core? See the script at https://www.msapiro.net/scripts/clean_users.py. This is an example that deals with Django users and Mailman Users and deletes some Django users. See https://docs.djangoproject.com/en/4.0/topics/db/queries/#creating-objects for information about creating objects. Also see the UserManager class in django/contrib/auth/models.py -- 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: The paradox of VERP probe messages

by Mark Sapiro

On 1/28/25 13:04, Jeremy Stanley wrote: > tl;dr: Is there a way to have VERP probe messages not include copies > of the bounce message that triggered them? Currently you'd need to patch code. This would do it. ``` --- a/src/mailman/model/bounce.py +++ b/src/mailman/model/bounce.py @@ -231,7 +231,7 @@ class BounceProcessor: # Try to get the dsn from the message store. It should be there. msg = getUtility(IMessageStore).get_message_by_id(event.message_id) if as_boolean(config.mta.verp_probes): - send_probe(member, msg=msg, message_id=event.message_id) + send_probe(member, message_id=event.message_id) action = 'sending probe' else: # Bounce score is reset by sending a probe but needs to be ``` You could submit an issue at https://gitlab.com/mailman/mailman/-/issues/new to make this configurable. ... > This behavior raises a more significant concern as well. The MTA on > the Mailman server in this case (Exim if it matters) wants to > perform batch deliveries when there are multiple subscribers who all > share the same remote MTAs. If multiples of those reject a list > post, then the NDR back to Mailman aggregates those multiple > rejections into a single message. If that incident triggers a VERP > probe, the bulk NDR enumerating the addresses of all the subscribers > who were rejected gets forwarded along as part of the VERP probe, > disclosing a potentially sensitive litany of random subscriber > addresses to other subscribers within that batch. I don't know > whether this is a misconfiguration, or an unintended consequence of > the intersection of Mailman and MTA features. I'm sure you can configure Exim to not do that. For Postfix it's ``` smtp_destination_recipient_limit = 1 ``` Also if you configure Mailman to VERP all deliveries ``` [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 ``` each recipient will be sent separately with a different envelope sender so the MTA can't combine them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: The Use of Hyperkitty as a Forum and Archiver

by Mark Sapiro

On 7/14/20 6:51 AM, Brian Carpenter wrote: > Dear Mailman 3 Users, > > Since Mailman 3 includes a forum feature via Hyperkitty, I would like to > know the following: > > - Has the forum feature (Hyperkitty) of MM3 been received well by your > list members or is it mostly ignored? > > - Do you see an increase in the use of HK as a forum from your list > members? For this list, I don't know other than myself, and for myself I receive the list and read it by email. I will occasionally reply from HyperKitty if I have reson to reply to a post that I have deleted from my mail server. For mail.python.org, there are multiple list members (including Guido) on multiple lists who use HyperKitty exclusively in lieu of mail. For my bicycling club lists, very few users use HyperKitty for anything and most didn't use pipermail either even though we had htdig integration. Those few that do use it probably use it primarily for search. > - What kind of feedback have you received from your list members > considering the forum function of MM3? Positive or negative? They find warts, in part due to the still developmental markdown rendering <https://gitlab.com/mailman/hyperkitty/-/merge_requests/160> that's installed there and on this list too, but overall those that use it, like it and prefer the forum model to the email list model. > - Do you think HK is received well by your list members as an archiver > and do you think it provides a better user experience for > viewing/searching archives vs Pipermail of MM2? Yes and Yes. > Thank you for anything you shared. I am very curious to know the state > of Hyperkitty among the Mailman 3 user community. > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: new list not working

by Mark Sapiro

On 3/9/23 13:26, Christian via Mailman-users wrote: > I am only having issues with the new list. > > > > Below are logfile entries > > > > Smtp.log > > ++++++ > > Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > > Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982) > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:<christian(a)naturalintelligence.us> SIZE=3653' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: christian(a)naturalintelligence.us > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:<redlatinleg(a)lists.ccalternatives.org>' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: redlatinleg(a)lists.ccalternatives.org > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost during _handle_client() This is the post being delivered to mailman and is expected. > > > Access.log Irrelevant. > Mailman.log > > ++++++++ > > Mar 09 20:57:09 2023 (9400) ACCEPT: <032101d952c9$caf09990$60d1ccb0$(a)naturalintelligence.us> > > Mar 09 13:03:42 2023 (9397) HyperKitty archived message <032101d952c9$caf09990$60d1ccb0$(a)naturalintelligence.us> to https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalternat… These are the expected messages (there seems to be a time zone difference) and in the absence of any other error type messages say the message should have been delivered to the eligible recipients. Are there any? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… or the results from ``` mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org ``` > mailmansuite.log not relevant. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

Search results for query "sapiro"