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

[MM3-users] Re: Problem creating list members using REST API

by Mark Sapiro

On 1/18/22 2:11 PM, Stephen Daniel wrote: > The REST API documentation is a bit informal. As someone who is not > familiar with mailman, and who doesn't know python, they are a bit of a > slog. Agreed. I guess we sort of assume that people dealing directly with the REST API are familiar with both. > It might be worth seeing if the code can be enhanced to allow the boolean > values to be sent in using JSON booleans as well as JSON strings. I think here we only have to deal with the REST API because other uses of as_boolean are all on strings that come from config files. We can't modify as_boolean directly, as it is part of a third party dependency and is intended to be used with config files, not JSON objects, but I think something like this will do it. ``` --- a/src/mailman/rest/helpers.py +++ b/src/mailman/rest/helpers.py @@ -249,6 +249,8 @@ class GetterSetter: """ if self.decoder is None: return value + if self.decoder is as_boolean and isinstance(value, bool): + return value return self.decoder(value) ``` Perhaps you could try to test that. I just created https://gitlab.com/mailman/mailman/-/issues/970 for this. It would help me in fixing this if you could provide a small piece of your code that throws the error. -- 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: Detectors and Bounces

by Mark Sapiro

On 8/5/22 14:03, summersan(a)nclack.k12.or.us wrote: > > Previously, there were `34775` files in the `/opt/mailman/mm/var/queue/bounces` directory, ranging from June 7 to August 4. For background, there's typically a time in the summer where many user accounts are purposely disabled (generally near July-August, I think). From the bounce file dates, I wonder if this bounce-related issue has been happening for longer than I first realized. The issue is that sometimes the bounce runner dies. This can be from an OOM error or some other reason, but I have observed it even on systems I admin. The master SHOULD restart it, but it doesn't. See https://gitlab.com/mailman/mailman/-/issues/898. Anyway, it appears your bounce runner died sometime on or before June 7 (if you have syslog from then it might have a clue), and you didn't stop and start Mailman core until August 4 when the bounce runner started again and began chugging through it's queue. I.e., I think everything in your installation is OK and the excessive load was just due to processing the 34775 queued bounces that should have been processed gradually over the previous 2 months. Although 500 bounces per day seems like a lot, but if you have a lot of lists, and bouncing users aren't being disabled because bounce runner isn't running, this may be normal. -- 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: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/26/20 12:33 AM, Alan So wrote: > Thanks. Just filed an issue: > https://gitlab.com/mailman/mailman/-/issues/725 Thank you for your "well formed" issue. I have started to work on this, but I have run into a snag. The patch at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> doesn't work. The problem is msg.get_all(header, []) does not parse the header and return a list of addresses. It just returns a list, the items of which are the raw values if the header instances in msg. I.e., if there is only one Cc: header, msg.get_all('cc', []) returns a list of one string which is the raw value of that header. If there were two Cc: headers in the message it would return a list of two strings with the two raw values. Thus, we would need to parse the strings returned into the individual email addresses. The simple minded way to do that is addrs = [] for hdr in msg.get_all(header, []): for addr in hdr.split(','): addrs.append(parseaddr(re.sub('[\r\n]', '', addr))) but that will fail if the header contains a quoted display name containing a comma such as "last, first" <user(a)example.com> So, I need to go back to using getaddresses, but do the unfolding first. Watch the issue for the final fix. -- 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

[MM3-users] Re: List in list, mutiple reply-to addresses

by Mark Sapiro

On 11/25/21 11:00 PM, Stefan Bauer wrote: > Mother: > Anonymous list: No > First strip reply to: No > Reply goes to list: No Munging > DMARC mitigation action: Replace From: with list address > DMARC mitigate unconditionally: Yes > > > > Daughter: > Anonymous list: No > First strip reply to: Yes > Reply goes to list: No Munging > DMARC mitigation action: Replace From: with list address > DMARC mitigate unconditionally: Yes > Because of DMARC mitigation, you can't do what you want. With the settings you have the mother list puts the original From: in Reply-To: and it's own address in From:. Then regardless of what the daughter does with the incoming Reply-To:, it will add the incoming From: to Reply-To: so the Reply-To: of a message from the daughter will always contain the address of the mother. The best you can do, unless you are willing to set DMARC mitigation action: to No DMARC mitigations is what you started with which is First strip reply to: No on the daughter which will at least put the original From: to the mother in Reply-To: from the daughter along with the mother's address, but you can't remove the mother's address from the daughter's Reply-To: because DMARC mitigation will always put it there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Mark Sapiro

On 4/28/22 10:59, bob B via Mailman-users wrote: > We had an issue where a program went rogue and sent out 30k email alerts to one of our lists, so now I have a few questions. > > When the issue happened I turned on emergency moderation and we have resolved the issue so.. > > 1. How do I easily delete 30k of held messages? It looks like the GUI only allows me to do 200 at a time? is there a way to flush all held messages easily? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and the thread containing it. > 2. When I enabled Emergency moderation, I expected it to stop notifying the admin on every held message, but it appears that is not the case? Also, does it reply to the sender of every held message when Emergency moderation is on? > > it seems like the steps are: > turn on "Emergency moderation" > turn OFF "Notify users of held messages" > turn OFF "Admin immed notify" MM 2.1 didn't notify the admins of emergency holds. This is not the case in MM 3. It probably should be, but isn't. Senders are or aren't notified per "Notify users of held messages". So the steps above are correct. -- 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: using SSH/TLS with external MTA

by Mark Sapiro

On 7/24/24 06:35, Roland Giesler via Mailman-users wrote: > I have managed thus far to get things working on my new install, but I > need to use a secure logon to send mail from an external MTA. I have > set up: > > /etc/mailman/mailman.cfg: > > smtp_host: box2.gtahardware.co.za > smtp_port: 465 > smtp_user: roland(a)giesler.za.net > smtp_pass: <hidden> > smtp_secure_mode: smtps > smtp_verify_cert: no > smtp_verify_hostname: no This looks OK, but > I'll get a cert installed later, for now just want to get it going. The `no` values for smtp_verify_cert and smtp_verify_hostname may be part of your issue. ... > "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line > 125, in _send > self.connection.sendmail(from_email, recipients, > message.as_bytes(linesep='\r\n')) > File "/usr/lib/python3.10/smtplib.py", line 901, in sendmail > raise SMTPRecipientsRefused(senderrs) > smtplib.SMTPRecipientsRefused: {'roland(a)giesler.za.net': (454, b'4.7.1 > <roland(a)giesler.za.net>: Relay access denied')} > > However, the mailserver is in daily use and accept logon all the time. I > believe I'm missing something that should be installed to make SMTPS > (SSL) work, but what? It is the mail server at box2.gtahardware.co.za that is refusing to relay this message. I think this issue needs to be resolved in that MTA's configuration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Error: ConnectionRefusedError at /accounts/login/

by Mark Sapiro

On 2/27/25 12:36, Kim Sunggun via Mailman-users wrote: > script: > #!/usr/bin/env python3 > import smtplib > > host = 'localhost' > port = 25 > connection = smtplib.SMTP(host=host, port=port) > connection.ehlo() > connection.quit() > > result: > Traceback (most recent call last): > File "/opt/mailman/./testone.py", line 7, in <module> > connection = smtplib.SMTP(host=host, port=port) > File "/usr/lib64/python3.9/smtplib.py", line 255, in __init__ > (code, msg) = self.connect(host, port) > File "/usr/lib64/python3.9/smtplib.py", line 341, in connect > self.sock = self._get_socket(host, port, self.timeout) > File "/usr/lib64/python3.9/smtplib.py", line 312, in _get_socket > return socket.create_connection((host, port), timeout, > File "/usr/lib64/python3.9/socket.py", line 856, in create_connection > raise err > File "/usr/lib64/python3.9/socket.py", line 844, in create_connection > sock.connect(sa) > ConnectionRefusedError: [Errno 111] Connection refused So you are doing the same thing Django allauth is doing with the same result. Do you even have an MTA listening on localhost, port 25? You need to figure out what settings you need to be able to connect to your outgoing MTA and set EMAIL_HOST EMAIL_PORT and maybe some of EMAIL_HOST_USER EMAIL_HOST_PASSWORD EMAIL_USE_TLS EMAIL_USE_SSL EMAIL_SSL_CERTFILE EMAIL_SSL_KEYFILE appropriately so you can connect to the MTA. If outgoing mail from Mailman works, look in the [mta] section in mailman.cfg for the appropriate settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 2 weeks

[MM3-users] Re: postorius ssl-certificates for virtual hosts

by Mark Sapiro

On 11/15/19 3:45 AM, Wolfgang Bock via Mailman-users wrote: > > That doesn't solve the problem. I changed that in mailman-web.py > (MAILMAN_REST_API_URL = https://localhost:8001) and after that in > mailman.cfg (use_https: yes). But got the same errormessage on postorius > website. You posted this log excerpt: Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=0&page=1 HTTP/1.1" 200 90 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=10&page=1 HTTP/1.1" 200 606 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.1/domains HTTP/1.1" 200 1438 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - code 400, message Bad HTTP/0.9 request type The first 3 GETs are a normal sequence of GETs from Postorius when you go to the Mailing Lists view. That should be followed by a GET like "GET /3.1/domains/domain.tld HTTP/1.1" where domain.tld is a configured domain. Do you have any domains configured?/0.9'? I'm not sure what the issue is. You have an older version of mailmanclient < 3.2.3a1 which uses httplib2 rather than requests. https://pypi.org/project/httplib2/ says: HTTP and HTTPS HTTPS support is only available if the socket module was compiled with SSL support. but I don't think this can be the issue because the first 3 GETs work. You might try upgrading mailmanclient to 3.3.0. I don't know if that will help, but it may. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Using external services for deliverability?

by Mark Sapiro

On 6/30/20 7:03 AM, Brian Carpenter wrote: > On 6/30/20 9:56 AM, tom(a)gather.coop wrote: >> I have a Mailman 3 server up and running but I'm terrified to migrate >> to it from my existing Mailman 2 provider for fear that services like >> Gmail will randomly start blacklisting my IP with little I can do >> about it. I have SPF records set up so I'm hoping I'll be Ok but I'd >> like to have a backup plan. ... > There is no reason to be afraid if you are sending out legitimate > communications. SPF records will help. You will also need to enable > DMARC mitigation on your lists and Mailman 3 does that very well as > Mailman 2 did. It also helps if you sign your outbound mail with DKIM. > With those 3 things in place, you should have no problem sending mail. > Keep in mind AT&T will probably block you if the IP address you are > using is new. That is standard practice for them. It's easy to get that > block remove. Same goes for Comcast using their Vader RBL. You also need to ensure you have full circle DNS <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. That together with SPF and DKIM signing of outbound mail is virtually essential for deliverability. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Mailman stops processing....... where to start looking for root cause?

by Mark Sapiro

On 3/29/24 12:34, bob B via Mailman-users wrote: > Today was the 2nd time mailman stopped sending out mail, it receives mail but sends nothing out. To resolve the issue I restarted the mailman services and then all the incoming/queued mail was sent out... last time this happened was 21 days ago.... Before that, it has been rock solid for years. ... > So where can I look to try to determine a cause? > If it happens again, what and where can I cook to troubleshoot before restarting the service? One of the runners has died, most likely the `out` runner, but possibly another. The missing messages are stuck in a queue. Do ``` ls -laR /opt/mailman/core/var/queue ``` to see in which queue the messages are. The runner that processes that queue is gone or possibly stuck. Do ``` ps -fwwu mailman|grep runner= ``` when things are working to get a list of what runners should be there. Do it again when things aren't working to see what's missing. There also should be something in mailman.log about why the runner died, but if it was killed for some external reason, there may not be anything. Look in `syslog` for something like an out of memory (OOM) or other issue that caused the runner to die. -- 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

Search results for query "sapiro"