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

[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, 4 months

[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

9 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

6 years

[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, 5 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, 8 months

[MM3-users] Re: Error when click on mailing list: An error occurred while processing your request.

by Mark Sapiro

On 7/14/24 21:40, adam.heathcote(a)utas.edu.au wrote: > Hi Mark, > > Sorry about the delay in replying. > > You're correct, I am clicking on the list in the Mailing List view. > > Navigating to the list URL directly while not logged in produces the same error and even produces the error when a different user is logged in. Now it's my turn to apologize. I've been traveling. In your original post you wrote "I've tried removing it and reimporting it to no avail." What exactly does this mean. You removed the list how? Then you reran the import21. Was the list broken at that point, or only after removing the old owners and adding yourself? What if you try the following steps in order and try to view the list in Postorius after each step. - remove the list with `mailman remove list(a)example.com` and recreate it with `mailman create list(a)example.com` - run `mailman import21 list(a)example.com path/to/config.pck` - in Postorius, add yourself as owner. - in Postorius, delete one of the other owners. - repeat the deletion and viewing the list for the other unwanted owners one at a time. If the view throws the error at some point, after which step? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Customise Postorius templates?

by Mark Sapiro

On 2/1/22 09:47, Duane Raymond wrote: > Hi, > > I'm looking to do some radical customisation of the Postorius (and Hyperkitty) templates over the next 6 ish months and was wondering if there is a 'best practice' way to do this that will survive updates to MM3. I've searched around and not found much and also tested copying > venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html > to > var/templates/lists/summary.html > > As suggested in some posts - but it didn't seem to pick up the customisation - only customisations in the venv path worked - and they get overwritten on update. The var/templates directory has a specific structure and is only for custom list specific, domain specific and sitewide templates used for notifications from Mailman core. It has nothing to do with Postorius or HyperKitty templates. > Is there a 'best' way for this? I'd also like to eventually share them with the community and maybe add them to the repo if people want that....but for now I'll start with my own experiments. (and if there is documentation I have missed for this, let me know!) I don't know about a `best` way, but the way I do this is to keep all local mods as patches to the base and apply those patches as part of the upgrade process. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Problem replying via Hyperkitty

by Mark Sapiro

On 6/30/22 10:07 AM, Jeff wrote: > Hello Everyone, > > A few of my users read our mailing list through Hyperkitty. Whenever they reply through the web, their replies simply disappear. One example from today was logged as follows: > > [pid: 2287|app: 0|req: 116007/153551] xxx.xx.xx.xx () {72 vars in 1992 bytes} [Thu Jun 30 11:26:16 2022] POST /archives/list/listname(a)domainname.org/message/46WUOPZITVMKJN4TXR6CP3WMFUEAVJKD/reply => generated 3213 bytes in 70 msecs (HTTP/1.1 200) 6 headers in 188 bytes (3 switches on core 0) This looks like the post of the reply to HyperKitty. What does the user see in response to that? There should be a brief alert popup indicating the message was sent. > A couple of basic questions: > > 1) when a users replies in this manner, does their response go to the list or to the subscriber to whom they are replying? To the list. > 2) what log files could I check to see what — if anything — happens to these emails? Mailman's var/logs/mailman.log, The MTA logs and the Django logs. > 3) Are there any settings that need to be set to make this work? There shouldn't be as long as the list and archiving work. Note, a user can select 'Use email software' when replying which should open a composition dialog in their email client to post a reply yto the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: No e-mail distribution after import of archive

by Mark Sapiro

On 11/12/24 00:52, Markus Grandpré wrote: > > In smtp.log I found: > > Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO > mailman-app-test.kim.uni-konstanz.de' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL > FROM:<markus.grandpre(a)uni-konstanz.de> SIZE=9649 BODY=8BITMIME' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: > markus.grandpre(a)uni-konstanz.de > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT > TO:<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: > Import_mm3_testliste(a)mailman-test.uni-konstanz.de > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost > during _handle_client() > > I have no idea why there is a "connection lost". What do you think? How > can I increase the log level? This is delivery of the message to Mailman. `connection lost` is normal and not a problem. This has nothing to do with your issue. -- 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: Which folder should I share between pods with kubernetees persistentVolumeClaim ?

by Mark Sapiro

On 2/6/25 02:37, antoine.depoisier--- via Mailman-users wrote: > > There are all the folders in mailman > archives cache data etc lists locks logs master.pid messages queue templates Here's my opinion. archives - If the prototype archiver is enabled for a list, its posts are archived here in maildir format. This should be shared for consistency, but if you don't care about this, you can put `enable: no` in the [archiver.prototype] section of mailman.cfg to disable it. cache - you're already sharing data - doesn't need to be shared unless it contains a sqlite mailman.db that's actually used. etc - doesn't need to be shared. lists - should be shared as it contains the mailboxes (digest.mmdf) for accumulating messages for a list's digest locks - should be shared master.pid - must not be shared as it contains the pip of the master process running on that node. messages - you're already sharing which you should. queue - this is tricky. If it isn't shared once a message gets queued in virgin/ or in/ on a node, only that node's runners will process it through its queues. This may have an impact on load balancing. templates - doesn't need to be shared, but should be synced between nodes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 1 week

Search results for query "sapiro"