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

[MM3-users] Re: redirecting -bounces replies

by Mark Sapiro

On 10/31/24 16:17, Hirayama, Pat wrote: > > Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list? > > In Mailman2, I know that I could do that by modifying the aliases table. You can do the same in MM3 if you want to just deliver to a person and not to normal bounce processing, but if you want to do both, and your MTA is Postfix, you would need to add and alias domain to your lists domain and configure Postfix according to https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. Then for example if your list domain is example.com and its alias domain is x.example.com, you could modify one line in the postfix_vmap file for the `listname` mappings from ``` listname-bounces(a)example.com listname-bounces(a)x.example.com ``` to ``` listname-bounces(a)example.com listname-bounces(a)x.example.com, person(a)example.com ``` and then run postmap on the file. The problem is any time you create or delete a list or run `mailman aliases` or run `mailman start` with the --generate-alias-file option, the file is regenerated and you will have to edit it again. To avoid that issue, you can create a separate vmap file containing only the ``` listname-bounces(a)example.com listname-bounces(a)x.example.com, person(a)example.com ``` entry and then add that file to virtual_alias_maps in Postfix main.cf, being sure to add it ahead of the postfix_vmap entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: Cannot locate manage.py

by Mark Sapiro

On 1/21/20 4:08 PM, Frank van den Heuvel wrote: > Hello, > > While following https://docs.mailman3.org/en/latest/migration.html, I > want to execute: > > python manage.py hyperkitty_import -l foo-list(a)example.com > $var_prefix/archives/private/foo-list.mbox/foo-list.mbox > > Of course edited with values for my list. But I already get stuck in not > being able to locate "manage.py". > > When I run "locate manage.py", I get: > > /opt/mailman/mm/venv/lib/python3.7/site-packages/django/conf/project_template/manage.py-tpl > > /opt/mailman/mm/venv/lib/python3.7/site-packages/example_project/manage.py > /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py > > Which one is the right one? Probably none of those. I'm not that familiar with the file layout in the Debian package if that's what you installed, but I would expect to find it in /opt/mailman/mm/venv/bin/ and I'd expect to find the files django_admin and django_admin.py. Both of those will run the Django management interface, but they won't work because they won't access your settings. I put the following executable in /opt/mailman/mm/bin #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ This assumes my settings.py file is /opt/mailman/mm/settings.py. If yours is elsewhere you may need to adjust PYTHONPATH and/or DJANGO_SETTINGS_MODULE. For example, on another server with the settings at /opt/mailman/mm/mailman_web/production.py I have export DJANGO_SETTINGS_MODULE=mailman_web.production -- 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: Edit archived email? Is it possible?

by Mark Sapiro

On 9/28/21 6:02 AM, Prasanth Nair wrote: > Hello, > > Does anyone know how to edit an archived email in Mailman3? It is possible > in Mailman2 ( > https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M…) > Is there any option similar to this in Mailman3? In some sense the process is the same but possibly even simpler in Mailman 3. You need to modify the underlying data which requires appropriate access to the server. In Mailman 3, the data are in the hyperkitty_email table in Mailman's database. You can get the Message-ID hash from the URL to the archived message, e.g. for the message to which I'm replying, the URL is https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have access, you can do database queries like ``` SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; ``` and ``` UPDATE hyperkitty_email SET content = '<new content>' WHERE message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; UPDATE hyperkitty_email SET subject = '<new subject>' WHERE message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; ``` If the message has attachments, they are in the hyperkitty_attachment table and can be referenced by `email_id` which is the corresponding `id` from the hyperkitty_email entry. You can also do similar things via `django-admin shell`. E.g. ``` $ django-admin shell Python ... (InteractiveConsole) >>> from hyperkitty.models.email import Email >>> x = Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') >>> print(x[0].content) ``` but this requires some knowledge of HyperKitty's models and Django's ORM. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

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

by Mark Sapiro

On 2/8/22 17:57, Philippe B wrote: > Thanks. I'm getting: > > >>> owner.delivery_status > <DeliveryStatus.by_moderator: 4> > > for the 2 lists with that odd behavior (as opposed to `<DeliveryStatus.enabled: 1>` for several other lists I checked). > > What does that 4 mean? It means that owner's delivery was disabled by moderator action[1]. You want to set it enabled as I indicated in my prior post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…. That is why the owners don't get notices, and you need to set their delivery status enabled so they will. Note that this only affects notices. It doesn't affect list posts assuming they are list members. That is controlled by the member's delivery status And because there are no eligible owner or moderator recipients the notices go to the configured site_owner. [1] The disabled by moderator status can occur in the following way for a list imported from Mailman 2.1. If the address in MM 2.1 is both an owner or moderator and also a list member, and the list member's delivery was disabled in MM 2.1, both the imported member and owner/moderator will have delivery disabled. This is really a bug in import21 as in Mailman 2.1, owner/moderator delivery couldn't be disabled, it shouldn't be imported as disabled. I have just created https://gitlab.com/mailman/mailman/-/issues/977 for this. -- 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: Mailman 3 bounce handling and DKIM mitigation

by Mark Sapiro

On 09/05/2017 01:14 PM, David Krantz wrote: > > I have a question on bounce handling. I get the impression that > bounces are just lost and neither handled nor forwarded to the list > admin. Is this a known problem? I am running mailman from git, but > about version 3.1 and use postfix. Bounce processing in Mailman 3 is currently not done. See <https://gitlab.com/mailman/mailman/issues/343>. > I find lots of things in the > bounceevents table. Is there any way to find out more on these events? > I probably can configure postfix to send listname-bounce@domain to an > admin adress. Or for that matter hack mailman to send it to the > correct admin. Your ideas are possible. Until it's fixed, you could just make postfix forward the listname-bounces address to listname-owner. I think this will then get the LMTP runner to send them to the owner. > Also the DKIM mitigation does not seem to detect DKIM domains. If I > force the mitigation for all mails it works but that of course has > annoying consequences although mostly cosmetic. This has caused quite > a number of bounces for my lists (as well as being temporarily banned > by at least Microsoft). I assume you mean DMARC mitigation. It should work for From: domains that publish DMARC policy 'reject' or 'quarantine' without setting DMARC Mitigate unconditionally. What if anything do you see in mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: I did something stupid. Can i back out of it?

by Mark Sapiro

On 2/19/22 08:33, William Oliver wrote: > > So... I run a small mailinglist using mailman3 that has been workiing > great for a couple of months. Last week, all my users from gmail got > kicked off because gmail decided that the list messages were > "unsolicited email". I didn't find out about it until the users hit > their mailman3 bounce limit. I *thought* would be seeing all the > bounce messages, but apparently not. I didn't see any config settings > for "see all the bounce messages" so i thought to myself, "Self, well > maybe that's because my mailinglist username doesn't have a mailbox in > /home/listname". Assuming your Mailman core version is 3.3.5 and Postorius is 1.3.6, you will see settings like `Notify owner on bounce increment`, ` Notify owner on disable` and `Notify owner on removal` under `Bounce Processing`. Presumable you did get the notification of removal, so delivery to the owner works. Are the increment and disable (or maybe just disable if your versions are older) notices set to Yes? > So, I decided to try that. I created /home/listname/Maildir/* and > logged in as fplist to see if it would put mail there. In order to log > in as listname, I gave the user listname a password. Can't you just reverse those steps. I.e. remove /home/listname/ and remove the listname user? -- 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: How to promote non-members to members?

by Mark Sapiro

On 3/17/22 10:19, Quanah Gibson-Mount wrote: > > So then I ran your code to confirm it, and it blows up with an error: ``` >>>> for token, data in pendings.find(pend_type='subscription'): > ... if data['token_owner'] != 'subscriber': > ... continue > ... if data['email'] != 'xxxxxxxx(a)xxxxx.org': > ... continue > ... sub_mgr.confirm(token) > ... > Traceback (most recent call last): > File "<console>", line 6, in <module> > File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", > line 545, in confirm > workflow.restore() > File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line > 149, in restore > setattr(self, attr, data[attr]) > File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", > line 119, in address_key > assert self.address is not None > AssertionError ``` This says that there is no Address object with the email xxxxxxxx(a)xxxxx.org What do you get in `mailman shell` for ``` >>> um = getUtility(IUserManager) >>> um.get_address('xxxxxxxx(a)xxxxx.org') >>> um.get_user('xxxxxxxx(a)xxxxx.org') ``` These should return an Address and a User respectively. If they don't, did you perhaps run some process to delete the user? If the user is gone, you should be able to replace ``` ... sub_mgr.confirm(token) ``` in the above with ``` ... wfm = getUtility(IWorkflowStateManager) ... pendings.confirm(token, expunge=True) ... wfm.discard(token) ``` to clear the pending subscription and workflow and then be able to mass subscribe the user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: digests are created but not sent out

by Mark Sapiro

On 1/9/19 1:37 AM, "Jörg M. Schulz" wrote: > > Normal, non-digest messages are sent correctly. Administrative messages as well. > > Using GNU Mailman 3.2.0 (La Villa Strangiato) > > Where could I look for errors / stuck queues? > > /var/lib/mailman3/lists > /var/lib/mailman3/lists/mailman.unswolke.de > /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.3.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.3.2.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.2.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.6.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.4.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.1.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.3.1.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.mmdf > /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.3.mmdf When a digest is to be sent by 'mailman digests', the digest.mmdf file is renamed to digest.x.y.mmdf (x and y are the volume and issue numbers) and an entry placed in queue/digests to send that digest. The digest runner then picks up that entry, prepares the digest, queues it in queue/virgin to be sent to the recipients if any and removes the digest.x.y.mmdf file. Since the digest.x.y.mmdf files are not removed, either the digest runner is not running at all in which case there will still be entries in queue/digests or it is encountering an error in processing in which case there should be messages with tracebacks in Mailman's error log and probably messages in queue/shunt. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 4/11/19 10:02 AM, brian(a)emwd.com wrote: > I followed Kelly's guide and ran into some issues but were able to resolve most of them. It seems I have one out standing issue: Hyperkitty. When I post to a list, I am getting the following in the /var/log/mailman3/mailman.log: > > Apr 11 14:01:15 2019 (1334) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF/$ > <html><head> > <title>503 Service Unavailable</title> > </head><body> > <h1>Service Unavailable</h1> > <p>The server is temporarily unable to service your > request due to maintenance downtime or capacity > problems. Please try again later.</p> > <hr> > <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address> > </body></html> > (503) ... > Everything else works fine. Postfix is receiving and delivery mail to Mailman3. List members are receiving the posts. I can access the list on Hyperkitty just no archived messages. What URL do you use to access HyperKitty. The problem URL above, http://localhost/mailman3/hyperkitty/api/mailman/archive is based on the base_url setting in mailman-hyperkitty.cfg which in your case is http://localhost/mailman3/hyperkitty/, byt the web server listening on localhost:80 is returning the Service Unavailable. It probably doesn't like the IP or name 'localhost'. Set base_url in mailman-hyperkitty.cfg to use an acceptable host name instead of localhost or adjust your apache config to accept localhost. -- 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: DKIM signatures with message footers or subject prefixes

by Mark Sapiro

On 3/11/22 09:37, Stanisław Findeisen via Mailman-users wrote: > Dear Experts > > What is the best way to go about reconciling GNU Mailman3-made message modifications (like message footers or subject prefixes) with sender-made DKIM signatures? I am aware of the "DMARC mitigations" tab in the list settings, not bad, but it looks that "replace From: with list address" doesn't help (of course), whereas wrapping the message in an outer message often looks ugly. Is there a better way?... > > BTW I would like to point out that broken DKIM signature can be a problem even with an easy DMARC policy; for example ProtonMail will display this flashy red warning: https://protonmail.com/support/knowledge-base/email-has-failed-its-domains-… in its webmail. (I guess nothing can be done about it except "DMARC Mitigate unconditionally"). ProtonMail is broken - see https://www.rfc-editor.org/rfc/rfc6376.html#section-6.1 That said, BCP recommends removing the signatures that the MLM will break https://www.rfc-editor.org/rfc/rfc6377.html#section-5.7 Mailman implements this with the mailman.cfg setting ``` [mta] remove_dkim_headers: yes ``` Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your valid DKIM signature and no prior Authentication-Results:. ARC <https://www.rfc-editor.org/rfc/rfc8617.html> is intended to address this while preserving prior authentication results and is supported by Mailman, but is not accepted by all receivers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

Search results for query "sapiro"