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

[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

6 years, 2 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

4 years

[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

3 years, 6 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

1 year

[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

5 years, 7 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, 11 months

[MM3-users] Re: duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Mark Sapiro

On 3/24/22 01:11, Stanisław Findeisen via Mailman-users wrote: > Hi > > I am having 4 different virtual domains (FILTER_VHOST = True). However on the domain list page in Postorius: https://.../postorius/domains/ I can see only 3 different SITE_IDs: 1,1,4,3. If I recall correctly, the "3" and "4" were created manually using the Postorius Web UI, whereas the two "1"s were created using the Mailman Client: > > client.create_domain(name) > > Is this a bug? Or did I mess something up? > What significance do those SITE_IDs have? The issue is client.create_domain doesn't support setting a Web Host. Web Hosts are the sites in the django_site table and SITE_ID is the id of the table entry. See `sites` in the Django admin UI. So when you create a domain with client.create_domain it gets arbitrarily assigned to a `site` > What I also noticed is that in the Postorius Web UI: https://.../postorius/lists/ both "1" domains display the lists contained in "3", whereas both "3" and "4" display correctly their lists. Except the "3", all domains are empty at the moment (no lists) (so "4" correctly displays no lists). Not sure if this is related?... FILTER_VHOST = True is imperfect. Lists have no Web Host attribute, only a Mail Host. Thus, with FILTER_VHOST = True, we get the Mail Host from the domains that have a Web Host matching the host in the http request. If that results in only one Mail Host, we limit the display to only those lists with that Mail Host, but otherwise we don't limit by domain. In other words, FILTER_VHOST = True only works if each Mail Host domain has a unique Web Host. If you have multiple Mail Host domains with the same Web Host (SITE_ID), FILTER_VHOST won't work for that Web Host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok I'll take a look at it Thanks El mar., 25 jul. 2017 a las 16:14, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 01:43 PM, Rafael Mora wrote: > > Ok, should I install the SASL authentication daemon saslauthd and start > it? > > > Probably not. > > If you are trying to configure Postfix to send via a remote server, see > <http://www.postfix.org/SOHO_README.html#client_sasl_enable>. > > -- > 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, 6 months

[MM3-users] Re: Receiving 8bit-clean mail

by Mark Sapiro

On 10/17/19 3:02 PM, Alyssa Ross wrote: > A subscriber to a mailing list I administer has been sending 8bit UTF-8 > encoded mail, with no further quoted-printable / base64 / > etc. encoding. This is handled fine by my MTA and MUA, but Mailman > seems to have trouble with it. When mail is sent out from Mailman, the > « character is replaced by ??. > > Is this a bug, or is there just a configuration option or something I > need to set? I couldn't find anything in the documentation. It works for me. I created this message > From: Mark <mark(a)example.net> > To: test(a)example.net > Date: Thu, 17 Oct 2019 22:02:04 +0000 > Message-ID: <87wod39gkj.fsf(a)alyssa.is> > MIME-Version: 1.0 > Subject: [MM3-users] Receiving 8bit-clean mail > Content-Type: text/plain; charset=utf-8 > Content-Transfer-Encoding: 8bit > > A subscriber to a mailing list I administer has been sending 8bit UTF-8 > encoded mail, with no further 8bit / base64 / > etc. encoding. This is handled fine by my MTA and MUA, but Mailman > seems to have trouble with it. When mail is sent out from Mailman, the > « character is replaced by ??. > > Is this a bug, or is there just a configuration option or something I > need to set? I couldn't find anything in the documentation. > and posted it to a test list. The message was delivered and archived. The delivered message had the list footer added and was base64 encoded, but in both the delivered and archived message, the « character was intact. In what other ways does Mailman modify the message. Does it add a msg_header and/or msg_footer, if so, are they added to a simple text/plain message body or is the message more complex so they are added as separate mime parts. Does content filtering remove anything? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Recipient address rejected: User unknown in local recipient table

by Mark Sapiro

On 4/17/20 11:24 AM, Mohsen Masoudfar wrote: > [mta] ... > configuration: python:mailman.config.postfix What's in this configuration file (mailman/config/postfix.cfg)? ... > in main.cf: > local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp > transport_maps = hash:/opt/mailman/var/data/postfix_lmtp > virtual_alias_maps = hash:/opt/mailman/var/data/postfix_vmap > > Bur for some reason the postfix_lmtp.db is older than postfix_lmtp, which means it does not get updated automated, I guess. This leads me to think that your mailman/config/postfix.cfg contains transport_file_type: regex in which case all of the Mailman mappings defined in main.cf should be regexp: tables rather than hash: tables. If you had transport_file_type: hash The .db files would be generated/updated whenever the corresponding text files are generated/updated. > I restarted the whole stack and added a new list. In postfix logs I see: > Apr 17 18:20:28 mailmandev01 postfix/smtpd[31399]: error: open database /opt/mailman/var/data/postfix_domains.db: No such file or directory Where are you even referencing that? Did you forget relay_domains = hash:/path-to-mailman/var/data/postfix_domains in the above list? ... > In addition, I found out this : > > On my old mailman2 I have a setting in postfix main.cf: > alias_maps = dbm:/usr/local/mailman/data/aliases > > the file /usr/local/mailman/data/aliases says in its first line: > # This file is generated by Mailman, and is kept in sync with the > # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE > > This makes a lot of sense to me. > > The point is I am missing any similar settings on postfix on mailman3. Mailman 2.1's data/aliases and data/virtual-mailman files have been replaced by the data/postfix* files in Mailman 3. I think your whole issue is you've configured Postfix with hash: tables but Mailman is generating regexp: tables. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Search results for query "sapiro"