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

[MM3-users] Re: [MM3-users][RESOLVED] HELP: mailman send empty mails

by Mark Sapiro

On 2/4/22 05:31, Axel Rau wrote: > Too many concurrent DB server connections seems to be the reason: > - - - > connection failed: FATAL: remaining connection slots are reserved for > non-replication superuser connections > - - - > A 2nd mailman instance was unintentionally activated and had stolen the > connections slots. Your analysis may be correct, but see https://gitlab.com/mailman/mailman/-/issues/955 >> The content of this message was lost. It was probably cross-posted to >> multiple lists and previously handled on another list. This is a dummy message which is returned on an attempt to get a message from the messagestore that doesn't exist. The message should only be in the message store in the first place if it was held for moderation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Archiving error

by Mark Sapiro

On 10/05/2018 09:39 AM, Enrique Terrazas wrote: > > I have a follow up question, I tried setting the base_url to https but received SSL errors in the mailman.log. The nginx.conf is using a valid certificate from a CA and the sites(Django admin, Postorius, Hyperkitty) all load with https in the browser, they are redirected from http as well. But it seems that internal communication is failing when I try to specify https in the base_url > Is this something that I should be concerned about and can be configured? I have base_url: https://host.name/... without a port in mailman-hyperkitty.cfg on several servers and that works fine. I think the issue is when you specify https://host.name:8000/... you are going directly to Django and bypassing nginx and it's nginx that has your SSL certificates. -- 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: Setting for archiving multi email domains?

by Mark Sapiro

On 3/5/21 10:12 AM, Duane Raymond wrote: > Thanks for the continued input on this. It's really appreciated! > > I've reverted the changes I made with virtual domains and tried again (after restarting postfix and mailman). The result back was like > > <test(a)oldlist.com> (expanded from <test(a)emaillistA.com>): host > oldlisthost.com[ip] said: 550 5.1.1 > <test(a)oldlist.com>: Recipient address rejected: User unknown in > virtual alias table (in reply to RCPT TO command) > > But I can't find oldlist.com in the configuration settings. It was set as an alias for emaillistA.com domain, but was removed. > > So still looking for a solution...am considering a reinstall from scratch....but that seems rather drastic! Please post the output from `postconf -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, 6 months

[MM3-users] Re: can't get mail into mailman3 in docker

by Mark Sapiro

On 8/10/21 11:29 AM, bob B wrote: > /opt/mailman/core/mailman-extra.cfg. now has > #lmtp_host: localhost > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > But but mail log shows > 2021-08-10T14:13:28.927266-04:00@####### postfix/qmgr[37253]: DDF5D3083EC2: from=<user(a)user.com>, size=8181, nrcpt=1 (queue active) > 2021-08-10T14:13:28.973273-04:00@####### postfix/lmtp[39368]: DDF5D3083EC2: to=<test@.....>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.07, delays=0.04/0.02/0.01/0, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while receiving the initial server greeting) > > Also to clarify the images no longer have hard coded ips so I should NOT DO this correct? > ----------------------------- > lmtp_host: 172.19.199.2 > lmtp_port: 8024 > smtp_host: 172.19.199.1 > smtp_port: 25 > ----------------------------- I think that's correct, but I'm at a loss for helping further. Hopefully @maxking will be able to help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Mark Sapiro

On 1/16/20 10:51 AM, Torge Riedel wrote: > > Such SPAM mails are currently hold for moderation with reason "not from > a list member". Is there no check for the "X-Spam: Yes" header or is > this check done later? If you set a Header Filter (in Postorius the Header filters tab) those checks are done before non-member moderation. This won't work for posts from members because the header checks are done between member moderation checks and non-member moderation checks, but if you create a Header Filter for header 'x-spam' and pattern 'yes' with action hold, a message from a non-member which has an X-Spam: Yes header should be held for that reason. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Apache Configuration for Subdomain

by Mark Sapiro

On 7/26/22 15:29, Mail Person wrote: > So adding the slashes did not fix, but I did get a workaround to work from the other thread: > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost > ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost > > Now makes it so that lists.example.com/mailman3 works sort of correctly. Weirdly enough, however, it redirects to lists.example.com/mailman/postorius/lists/ rather than */mailman3/* > > AND, if you go to lists.example.com/mailman it errors out with a 404 but redirects to > > lists.example.com/mailma > > So somehow a letter is getting deleted for some reason. This is a known issue with some versions of uWSGI. The only information I have is in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: No DBA password when installing Mailman3 with remote database server

by Mark Sapiro

On 10/31/22 07:04, Markus Ludwig Grandpré wrote: > Dear Mailman3 list, > > I try to install the Mailman3 software 3.3.3-1 on a Debian 11 system > with a remote Postgres database server. During the installation process > dpkg is asking for the DBA password that our DBA team would not provide > to me. So what can I do? This is really a question for Debian, but apparently dpkg wants to create databases for Mailman and Mailman Web. You will need to get your DBA team to create these databases (probably named `mailman` and `mailmanweb`) and a Mailman user (probably `list`) with all access to these databases and probably manually configure the `[database]` section of mailman.cfg and `DATABASES` on Django's settings -- 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: Monthly Password Reminders

by Mark Sapiro

On 2/3/23 04:05, Stephen J. Turnbull wrote: > > For the passwords, yes. It was frequently reported as a bug, in fact. > Mostly the reminders generate requests to know how to shut them off. > You're the first in probably a decade who's asked how to turn them on! > > While in theory we could protect in transit with SMTP over TLS, we > can't guarantee end-to-end encryption (eg, if there's a .forward at > the subscribed address), and while TLS is widely implemented, it's > still not universal. Perhaps more significantly, all passwords are now stored in encrypted form, so for practical purposes we couldn't send the unencrypted password because we don't know it and the encrypted password is not useful to the user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Error -- postorius Un-handled exception

by Mark Sapiro

On 4/10/24 03:42, admin(a)bclug.ca wrote: > > After `systemctl restart mailman3.service mailman3-web.service` I'm still getting: > >> ERROR 2024-04-10 10:19:19,739 104735 postorius Un-handled exception: HTTP Error HTTP Error 500: {"title": "500 Internal Server Error"} >> File "/opt/mailman/venv/lib/python3.10/site-packages/mailmanclient/restbase/connection.py", line 161, in call >> raise HTTPError(params.get('url'), response.status_code, >> urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} >> ERROR 2024-04-10 10:19:19,744 104735 django.request Internal Server Error: /mailman3/lists/new_test.domain.tld/ >> ERROR 2024-04-10 10:19:19,744 104735 django.request Internal Server Error: /mailman3/lists/new_test.domain.tld/ >> ERROR 2024-04-10 10:19:19,745 104735 django.server "GET /mailman3/lists/new_test.domain.tld/ HTTP/1.0" 500 8667 > > > Anyone have suggestions? What's in var/logs/mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

Mark Sapiro wrote: > Thus, the issue occurs downstream of lmtp runner. It will take more > investigation to determine where. The issue occurs in mailman/handlers/avoid_duplicates.py. That module will rewrite the Cc: header after possibly deleting some of the entries. That module calls msg.get_all('cc') to get the original Ccs and calls email.utils.getaddresses() on that to get a list of all the name, address pairs. In our case, msg.get_all('cc') returns one of two things. If the message came via LMTP with CRLF line endings, it returns ['"ABC DEF\r\n (XYZ)" <mark(a)msapiro.net>'] If the message came from `mailman inject` with LF line endings, it returns ['"ABC DEF\n (XYZ)" <mark(a)msapiro.net>'] then email.utils.getaddresses() calls internally email.utils.parseaddr on each item in the list to make a list (of one in our case) of name, address pairs. The result is different depending on the line endings which explains why it works with `mailman inject` but not with LMTP. In the case where the line endings are LF, the return is [('ABC DEF\n (XYZ)', 'mark(a)msapiro.net')] but if the line endings are CRLF, the return is [('XYZ', 'ABC DEF')] If the "folding" is not quoted as in ABC DEF (XYZ) <mark(a)msapiro.net> then the return is ('ABC DEF (XYZ)', 'mark(a)msapiro.net') regardless of the line ending as it should be. I can't really fault parseaddr() here because the only time it produces an unexpected result is when the CRLF line folding occurs in the middle of a quoted string which is clearly non-compliant. For Mailman to defend against this, something like the attached patch would do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

Search results for query "sapiro"