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

[MM3-users] Re: question about recommended postfix configuration

by Mark Sapiro

On 10/02/2017 05:37 AM, Marc Sluiter wrote: > > I got almost everything working besides confirm mails (see my other mail), but I had to use another postfix configuration than recommended, I’m wondering why the recommended way didn’t work. Sidenote: I’m not a postfix expert. Neither am I ;) > This is recommended: > > transport_maps = > regexp:/opt/mailman/core/var/data/postfix_lmtp > local_recipient_maps = > regexp:/opt/mailman/core/var/data/postfix_lmtp > relay_domains = > regexp:/opt/mailman/core/var/data/postfix_domains > > This didn’t work, all mails to mailman were rejected. Postfix did not even check the “local_recipient_maps”. After a lot of reading that made sense to me, because when I understand it correctly, “local_recipient_maps” is only checked for domains in “mydestinations”. And there I only have localhost. On mail.python.org which is a complex Postfix environment with both Mailman 2 and Mailman 3 lists in the @python.org domain, for Mailman 3 I have just transport_maps and relay_domains as recommended (but as hash tables) I don't have anything for Mailman in local_recipient_maps, but python.org is in virtual_alias_domains (not in virtual_mailbox_domains). I think it could be either, and virtual_alias_maps (or virtual_mailbox_maps) does not require anything for Mailman because transport_maps handles it. I think the bottom line here is the list domain must be in one of mydestination or virtual_*_domains. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: including a template failed

by Mark Sapiro

On 9/23/20 3:03 PM, Wolfgang Bock via Mailman-users wrote: > > Dear Mark, > > Q: Can you get > https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li > sts.domain-03.de/list:member:regular:footer on the Mailman machine? > > A: No > > Q: What is your setting for POSTORIUS_TEMPLATE_BASE_URL? > > A: > was: POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' > > Changed it to: POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' Can you get https://localhost/mailman3/postorius/api/templates/list/mylist.lists.domain… on the Mailman machine? > Now another problem occurs: > > Sep 23 22:51:34 2020 (13492) Cannot connect to SMTP server localhost on port > 25 > HTTPSConnectionPool ... 'localhost' doesn't match either of > 'blog.domain-04.de', 'lists.domain-04.de', 'mail.domain-04.de', > 'domain-04.de', 'www.domain-04.de'"))) The 'HTTPSConnectionPool' message has nothing to do with the 'Cannot connect' issue. > Port 25 entry results from the manual regarding the postfix configuration: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht > ml > > e.g.: > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: mail.example.com > lmtp_port: 8024 > smtp_host: mail.example.com > smtp_port: 25 And I wonder why it's trying to connect to localhost when smtp_host is mail.example.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: {Spam?} Server name in new account confirmation email

by Mark Sapiro

On 12/3/20 9:26 AM, Meehan, John wrote: > Hi, when someone creates a new account (Sign Up), an email is sent to them to confirm their email address. It has the form below. Does anyone know how I can change the server name in the URL (From server.example.com to something else)? I have an SSL proxy server that I want to direct users through. Thanks. - John This message comes from django_allauth. The domains come from the django_site database table. If you have Postorius >= 1.3.3 The Domains view will show you the SITE_ID for the domain and has an `Edit` link the the Django admin UI entry for that site. Otherwise, you can go to the Django admin `Sites` view and see the DOMAIN NAME and DISPLAY NAME for each defined site, and you can edit the domain name. You may also need to adjust the SITE_ID setting in your Django settings to match the site you want. The trick here is the SITE_IDs aren't displayed in the Django admin UI or in Postorius < 1.3.3, and they may not be sequential or start at 1. If you query the database with `SELECT * FROM django_site;` you'll see entries with columns id, domain and name which will tell you the SITE_ID. -- 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

[MM3-users] Re: mm3 floods syslog

by Mark Sapiro

On 10/31/21 4:18 AM, Wolfgang Bock via Mailman-users wrote: > Dear friends, > > I got another problem: mailman floods my syslog. > > I deleted a domain/webdomain (further mentioned as deleted.org) in > postorius, django web. No entries are now in > /var/lib/mailman3/data/postfix_domains or postfix_lmtp or > /var/lib/mailman3/lists. > > > Here an extract of my syslog (anonymized): > Oct 31 10:49:02 myserver mailman3[1284]: Oct 31 10:49:02 2021 (1284) > Certificate did not match expected hostname: localhost. Certificate: > {'subject': ((('commonName', 'deleteted.org'),),), 'issuer': > ((('countryName', 'US'),), (('or > ganizationName', "Let's Encrypt"),), (('commonName', 'R3'),)), 'version': 3, > 'serialNumber': '0326A733CA7B16D13C830EE707EA614E25F9', 'notBefore': 'Oct 30 > 20:21:08 2021 GMT', 'notAfter': 'Jan 28 20:21:07 2022 GMT', > 'subjectAltName': (('DN > S', 'deleteted.org'), ('DNS', 'lists.deleteted.org'), ('DNS', > 'mail.deleteted.org'), ('DNS', 'ns.deleteted.org'), ('DNS', > 'www.deleteted.org')), 'OCSP': ('http://r3.o.lencr.org',), 'caIssuers': > ('http:/ > /r3.i.lencr.org/',)} > > This appears nonstop. Your ssl certificate is for the domain `deleted.org` with alt names `lists.deleted.org`, `ns.deleted.org`, `mail.deleted.org` and `www.deleted.org`. Django is accessing things at a URL for a different domain. Get a new certificate for the domain(s) you are actually using. -- 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: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 5/27/24 1:55 AM, marcus--- via Mailman-users wrote: > > What I also notice is that it is not yet storing anything in the archives. Could this be a setting that has changed, or an incorrect authorization (/var/lib/mailman3/archives/ belongs to list but is empty) or is the archive creation only running via a cronjob that perhaps still needs to run? There are two things stored in that directory If the prototype archiver is enabled, each list which has prototype checked as an Active archiver will have messages stored in maildir format in archives/prototype. If the hyperkitty archiver is configured and enabled, when mailman-hyperkitty fails to send a message to hyperkitty, it queues that message in archivers/hyperkitty/spool. If there no current failed messages, that directory will be empty, and if there have never been failures, that directory may not exist. Enabling archivers is done in mailman.cfg similarly to ``` [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg [archiver.prototype] enable: yes ``` > I don't need Usenet, thanks :-) Then no list should have it's Gateway to mail or Gateway to news setting = Yes. Also, you can disable nntp runner by putting ``` [runner.nntp] start: no ``` in mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Mailman3 breaking DKIM signatures

by Mark Sapiro

On 1/21/25 4:40 AM, jefdriesen(a)hotmail.com wrote: > Hi, > > I have configured a mailman3 mailinglist to not modify the headers and body (e.g. no footer, no subject prefix, etc) to avoid breaking DKIM signatures. This worked well, until I encountered an email where the DKIM signature was still broken. After some debugging, the problem is caused by an attachment, where the mime header is changed by mailman3. ... > The Content-Type header is modified (word-wrapped), and this breaks the DKIM signature. > > How can I prevent this from happening and configure mailman to not modify the email? You could try a patch like ``` --- a/src/mailman/runners/lmtp.py +++ b/src/mailman/runners/lmtp.py @@ -186,7 +186,8 @@ class LMTPHandler: listnames = set(getUtility(IListManager).names) # Parse the message data. If there are any defects in the # message, reject it right away; it's probably spam. - msg = email.message_from_bytes(envelope.content, Message) + msg = email.message_from_bytes(envelope.content, Message, + policy=email.policy.Compat32(max_line_length=0)) msg.set_unixfrom(envelope.mail_from) except Exception: elog.exception('LMTP message parsing') ``` This should prevent folding headers, but this is problematic. It may be that the incoming message contains a folded header and this change will not fold it in the outgoing message. I think not, but I don't know for sure. You'll have to test this. -- 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: Postfix Hooks and Fetchmail

by Mark Sapiro

On 11/14/25 09:01, dap1--- via Mailman-users wrote: > No joy. Here is what I did. I did the mysql update per your instructions. I then created the file /opt/mailman/var/data/virtual_aliases: > > mailman@localhost mailman > > I ran postmap virtual_aliases then added: > > virtual_alias_maps = hash:/opt/mailman/var/data/virtual_aliases > > To /etc/postfix/main.cf. I said > I think you can solve this by instead adding 'localhost' as an alias > domain for the ddddddddd.net domain and configuring Postfix per > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… I now think that is wrong. I think you need to remove the alias domain from the domain table entry UPDATE domain SET alias_domain = '' WHERE mail_host = 'ddddddddd.net'; And then run `mailman aliases` to update the postfix_* files in /opt/mailman/var/data/ THIS STEP IS IMPORTANT Then you can remove the /opt/mailman/var/data/postfix_vmap file that should have been created previously, and edit your /opt/mailman/var/data/virtual_aliases file with this content. llllllllll@localhost llllllllll(a)ddddddddd.net llllllllll-bounces@localhost llllllllll-bounces(a)ddddddddd.net llllllllll-confirm@localhost llllllllll-confirm(a)ddddddddd.net llllllllll-join@localhost llllllllll-join(a)ddddddddd.net llllllllll-leave@localhost llllllllll-leave(a)ddddddddd.net llllllllll-owner@localhost llllllllll-owner(a)ddddddddd.net llllllllll-request@localhost llllllllll-request(a)ddddddddd.net llllllllll-subscribe@localhost llllllllll-subscribe(a)ddddddddd.net llllllllll-unsubscribe@localhost llllllllll-unsubscribe(a)ddddddddd.net -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months

[MM3-users] Re: Mailing lists sometimes do not honor moderation_action of non-members

by Mark Sapiro

On 10/31/19 2:21 AM, Alan So wrote: > We notice that sometimes mailing lists do not honor moderation_action of non-members. Instead, it follows the default action of the lists. It looks like we can sometimes fix the issue by adding/removing the non-members or adding/removing them as owner in certain order but we are not sure about exactly what we have to do. So, it looks like that it is not caused by the list configuration. We have already verified from the web UI, mailman client and the DB table member that moderation_action of the corresponding non-members are set correctly. Any clues for us to provide further information to troubleshoot the issue and any recommended workaround to get around the issue? Thanks a lot. Reasons why a post From: a non-member would not be treated according to that non-members moderation_action include the following: If any address in any of the places configured in mailman -> sender_headers (default = From: header, envelope sender, Reply-To: header, Sender: header) is that of a member, that member's moderation_action will apply. If any of the addresses above matches an address or pattern in one of the lists *_these_nonmembers attributes that action will apply rather than the corresponding non-member's moderation_action. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Why aren't I getting bounce texts any more?

by Mark Sapiro

On June 8, 2026 4:31:31 PM PDT, Paul Tomblin via Mailman-users <mailman-users(a)mailman3.org> wrote: >I swear I used to get the exactly text of the bounce message when email to a list member bounced, but I'm not seeing it any more. Is there a setting I've overlooked? I've turned on "*Notify owner on bounce increment"* which was off for some reason. With "Notify owner on bounce increment" set to Yes, the list owner should receive a notice containing the bounce DSN whenever a user's bounce score is incremented. Since it was off for some reason, these would not have been sent. The other relevant settings are "notify owner on disable" and "notify owner on removal". The disable notice should also contain the DSN. What were these settings? >I just had 24 users bounced off a mailing list this morning for excessive bounces Removed or just had delivery disabled? If the latter, I can only think that both the bounce increment and disable notice settings were off. , and I can only think their ISP suddenly took exception to my setup somehow. It would have been nice to have to a warning when the first bounce happened. And you should have gotten it, but the setting was off. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

4 months, 1 week

[MM3-users] Re: Example Logrotate files for Mailman3

by Mark Sapiro

On 6/30/20 2:10 PM, Andrew Hodgson wrote: > Hi, > > Does anyone have any usable Logrotate files for Mailman3 (especially for the web stuff)? Here are two. They differ in the name and location of the Django log. Both of them signal gunicorn to reopen its logs. If you are using uWSGI or some other WSGI support, you'll need to figure that out. In this one, all the logs including Django's are in /opt/mailman/mm/var/logs/ > /opt/mailman/mm/var/logs/*.log { > missingok > sharedscripts > su mailman mailman > postrotate > /opt/mailman/mm/bin/mailman reopen &>/dev/null || true > if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then > PID=`cat /opt/mailman/mm/var/gunicorn.pid` > kill -s USR1 $PID > fi > endscript > } This one is actually two because the Django log is in /var/log/ rather than /opt/mailman/mm/var/logs/. > /opt/mailman/mm/var/logs/*.log { > missingok > sharedscripts > su mailman mailman > postrotate > /opt/mailman/mm/bin/mailman reopen &>/dev/null || true > if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then > PID=`cat /opt/mailman/mm/var/gunicorn.pid` > kill -s USR1 $PID > fi > endscript > } > } > /var/log/mailman-web/*.log { > missingok > notifempty > delaycompress > su mailman mailman > } -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

Search results for query "sapiro"