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

[MM3-users] Re: EMWD/Affinity/Empathy in 2023

by Stephen J. Turnbull

Mark Sapiro writes: > I have had some contact [with EMWD], but not much. As far as I > know, they are still in business and offering list hosting > including Mailman 3 lists with Affinity and Empathy. They no longer > offer support for installation and maintenance of Mailman on other > people's servers. That exactly describes my experience. To jaboyib556, I recommend you contact them directly and make your own judgment. I do not know the current operators of EMWD, but I do know that the Carpenter family carefully vetted several bids. And their concentration on servers they run suggests they know what they're good at and have focus. I think they're a good bet, but only you can judge. > As far as I know, it was only EMWD that did this and for business > reasons, kept it proprietary. I corresponded with Brian about this.[1] He said that a third-party consultant (not sure if they're related to the current operators) built the Affinity and Empathy applications in PHP on a limited budget, and he felt that he needed to keep them proprietary as a temporary "no competition" measure until they could build up a nest egg to support on-going development. He said, and I have no reason to disbelieve him, that he thought it would take a year to build the reputation, another year to recoup the investment, and within that time frame he planned an open source release. I suspect he planned a Aladdin Ghostscript-like strategy: with the publication of release N, he would release N-1 as open source. He made no commitments, but I believe that was his aspiration. He was always a great supporter of Mailman, giving generously of his time and expertise to people on our lists including those hosting with other businesses. We miss him a lot. Footnotes: [1] On friendly terms: "hope for an open-source release" is not a matter of moral imperative with me, and I believe I speak for all Mailman developers on that.

3 years, 6 months

[MM3-users] Re: Problem with digests not being sent daily

by Mark

On 6/21/24 02:07, Mark wrote: >> ...The mmdf files don't exist in the list's directory although there >> have been many posts to the list throughout the day. On 2024-06-21 15:55, Mark Sapiro wrote: > Assuming your mailman/app/digests.py is unmodified, there is some race > condition. The code beginning at > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/digests.py… > finds the file and size is > 0, but by the time it gets to > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/digests.py… > the file is gone. > > What other crons run at the same time? The digest.py file is out-of-the-box and unmodified. ls -la /opt/mailman/venv/lib/python3.11/site-packages/mailman/app/ ... -rw-r--r-- 1 mailman mailman 4642 Jan 30 08:06 digests.py The /var/log/cron.log shows the crons running at the same time as digest at 22:30 hours. # tail -f cron.log ... 2024-06-21T22:30:01.368407+00:00 deu CRON[3422196]: (root) CMD (sh /templates/mailman_custom_templates.sh > /dev/null) 2024-06-21T22:30:01.369050+00:00 deu CRON[3422197]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs quarter_hourly) 2024-06-21T22:30:01.371586+00:00 deu CRON[3422198]: (mailman) CMD (/opt/mailman/venv/bin/mailman notify) 2024-06-21T22:30:01.371878+00:00 deu CRON[3422199]: (mailman) CMD (/opt/mailman/venv/bin/mailman digests --periodic) 2024-06-21T22:30:01.372190+00:00 deu CRON[3422202]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs minutely) /////////////////////////////////////////////////////////////////////////////////////////////////////////////// The mailman crons are more or less out-of-the-box: MAILTO=imark(a)posteo.net 30 22 * * * /opt/mailman/venv/bin/mailman digests --periodic 30 22 * * * /opt/mailman/venv/bin/mailman notify #@daily /opt/mailman/venv/bin/mailman digests --periodic #@daily /opt/mailman/venv/bin/mailman notify # * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly # The root cron just runs a bash script every 5 minutes to copy custom templates from the mailman and mailmanweb databases and write them to files. ...

2 years, 1 month

[MM3-users] Re: ARC signing outgoing mails

by Wolfgang Bock

Hello, thanks for these hints. Now it works and outgoing mails from my lists are no longer greylisted. .... ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=xx.de ... .... ARC-Seal: i=1; s=dkim; d=xx.de .... Here my mailman.cfg (debian buster/dovecot/postfix/rspamd/mysql/mailman3) quote [ARC] enabled= yes selector= dkim privkey: /path/to/rspamd/dkim/{conf.ARC.domain}.{conf.ARC.selector}.key unquote The below mentioned hash should be deleted. In the above mentioned directory the dkim key-files are saved in following style [domain].[selector].key Regards Wolfgang Am 02.11.2019 um 01:19 schrieb Mark Sapiro: > On 11/1/19 4:04 PM, Wolfgang Bock via Mailman-users wrote: >> Hello, >> >> in >> https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/arc_sign… >> I found this hint >> >> "It is highly recommended that Mailman maintainers configure ARC siging >> of their outgoing email. ..." >> >> So I added in my mailman.cfg: >> " >> [ARC] >> privkey: /path/to/private.key >> " >> >> >> But I don't understand the meaning of >> >> >> "... and located at: >> " >> #{config.ARC.selector}._domainkeys.#{config.ARC.domain} –ex.– >> test._domainkeys.example.com >> " > This doesn't seem correct. The DNS TXT record should be added to > #{config.ARC.selector}._domainkey.#{config.ARC.domain} (note _domainkey, > not _domainkeys) > > I.e., this is a normal DNS TXT record containing the public key for DKIM > signing. > >> Where can I find this string or where do I have to place it. I am using >> bind9 as dns-handler. > > Read the entire ARC section beginning at > <https://gitlab.com/mailman/mailman/blob/master/src/mailman/config/schema.cf…>. > You have to configure more than just privkey. > > Once you have configured > > enabled: yes > privkey: /some/location/yourprivatekey.pem > selector: test (or whatever you want) > domain: your_domain.com > > The substitutions for #{config.ARC.selector} and #{config.ARC.domain} > should be more clear. >

6 years, 8 months

[MM3-users] Re: Connection lost during _handle_client()

by Alain D D Williams

On Wed, Nov 27, 2024 at 08:47:38PM -0800, Mark Sapiro wrote: > On 11/27/24 5:58 PM, Alain D D Williams wrote: > > Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) connection lost > > Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) Connection lost during _handle_client() > > > > I am concerned about the connection lost message above. > > > It is normal and not a concern. > > > > Mailman sees it, the message ID matches that at the end of the first line > > in the exim log (above): > > /var/log/mailman3/mailman.log > > Nov 28 00:59:45 2024 (1268377) ACCEPT: <Z0fAe9xODd2y33N8(a)phcomp.co.uk> > > > So Mailman got the message and accepted it. > > > > Is there any more logging that I can look-at/switch-on to see what is happening ? > > Is there anything else in mailman.log? Does the message get archived? > Is there anthing in any of Mailman's var/queue/* directories? /var/lib/mailman3/queue/out/ contains 4 .pck files and one .bak file. There are being continually read & replaced by other files of similar names - like 1732809409.1069376+eb3354a0fc1f0a9bfa95ff7e15e2430ab7c2b885.pck The process doing this is a 'qrunner' I am getting ~50 lines/second appended to /var/log/mailman3/web/mailman-web.log [pid: 1348330|app: 0|req: 4366/4366] ::1 () {54 vars in 1065 bytes} [Thu Nov 28 17:02:18 2024] GET /mailman3/hyperkitty/api/mailman/urls?mlist=chat%40bray.phcomp.co.uk&msgid=Z0iJAoTHHrzK2ypO%40phcomp.co.uk => generated 126 bytes in 3 msecs (HTTP/1.1 200) 7 headers in 220 bytes (1 switches on core 1) Yes: the mail list is chat(a)bray.phcomp.co.uk /var/lib/mailman3/queue/shunt/ contains 4 .pck files. > Is Mailman core running? Systemctl says so & ps shows me one 'master', several 'runner' & 2 uwsgi > Does `mailman members --nomail enabled` list any members? Yes: it gives the list that I expect. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year, 7 months

[MM3-users] Re: Auth question

by David Krantz

On Sat, Apr 1, 2017 at 6:36 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > No, I'm using Django 1.9.9. I suppose that means it will quit working if > I upgrade to Django 1.10. > > So, I updated my urls to > > url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), > > and updated the attached files at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. Very good. That will be helpful. Now everything works for me except the archiver. There I get strange errors where it requires authentication. I _have_ set MAILMAN_ARCHIVER_KEY (in production.py) and api_key in mailman_hyperkitty.conf to the same value within single quotes. This is probably something extremely silly that my jetlagged brain cannot see. [mailman.log] Apr 09 19:10:42 2017 (14388) HyperKitty failure on https://example.com/archives/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) Apr 09 19:10:44 2017 (14388) HyperKitty failure on https://example.com/archives/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) Apr 09 19:10:44 2017 (14388) HyperKitty failure on https://example.com/archives/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) Apr 09 19:10:45 2017 (14383) HyperKitty failure on https://example.com/archives/api/mailman/archive: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) Apr 09 19:10:45 2017 (14383) Exception in the HyperKitty archiver: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> Apr 09 19:10:45 2017 (14383) Traceback (most recent call last): File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> No big deal for me currently, but as I have an archiver I must find out either how to activate it or how to completely remove it. I like having the option, for some kinds of lists archives are useful. Cheers // David

9 years, 3 months

[MM3-users] Re: Bottom line of message footer

by Brian Carpenter

On 2/14/21 9:05 PM, Mark Sapiro wrote: > On 2/14/21 5:40 PM, Tom Stoddard wrote: >> Here's another question that I have. A regular message just came into my >> email from one of the lists I'm a member of and it had a 3 line footer. >> The first two lines are fine, they just include the list's email address >> and an address to send unsubscribe requests to. The third line is this: >> >> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >> >> It looks to me like it should be a link to the group's list info page. >> Is this a bug or is there something I can do to fix it? It looks like it >> might be missing a forward slash after the first "s". > This is a list whose msg_footer was imported by The Mailman 3 process > that imports Mailman 2.1 lists. This import process will recognize the > default msg_footer and not create a list specific template for it, but > other things in the footer result in a list specific template which > needs to be reviewed for issues like this. > > The way for you to fix it is to create a list:member:regular:footer (and > maybe a list:member:digest:footer) template in your web UI which will > then override the existing list specific template. The available > replacements are listed at > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. > In templates they are all $ strings, e.g. $name. The %(name)s > replacements are Mailman 2.1 and won't work. Also, there is no > replacement for web_page_url because Mailman Core doesn't know what that > is, so you have to include the actual 'https://.../' value if you want > to include a web link. Thank you Mark. @Tom the templates you want to modify to add a Mailman 3 footer to replace the above are: Regular Message Footer Digest Footer -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

[MM3-users] Re: Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line

by Thomas Ward

See, that's the oddness. There appears to be SOME weird mail loop here where $ORIGIN (MS365/Exchange) hands it once, then there's back-and-forth between SMTPPROXY and Mailman. IT's really odd how it behaves, and I have no explanation for it. Right now I'm away from the office where this happens, but when I'm back there I'll grab logs from both sides. Thomas On 12/5/23 17:54, Mark Sapiro wrote: > On 12/5/23 10:08, Thomas Ward via Mailman-users wrote: >> We use a multi-hop SMTP system to go from the inside of our network >> out to the Internet at the domain test.lists.example.com. >> >> The setup is this way for ingress: >> >> {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 >> Connector) -> Mailman for delivery to listserv >> >> Egress is this: >> >> Mailman -> Postfix SMTP Relay (smtpproxy) -> INTERNET >> >> -- >> >> When a message is sent an invalid list (we'll call it >> invalid(a)test.lists.example.com) we end up with a nasty side effect in >> the system. The "no such recipient" response gets sent to the >> smtpproxy machine and then *it gets redelivered back to Mailman* as a >> redelivery as if it isn't accepting a permanent-failure condition code. > > > I don't understand why this is happening. Whatever MTA is seeing the > "no such recipient" status and creating the response DSN should be > sending it to the envelope sender of the original message so it should > not be sent to the invalid mailman address. Is one of the MTAs in the > delivery chain to Mailman rewriting the envelope sender? > > What are the MTA log messages from all the MTAs whos logs you have > access to? >

2 years, 7 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Andrew Hodgson

Mark Sapiro <mark(a)msapiro.net> wrote: >On 9/21/23 17:30, Thomas Ward wrote: >> >> MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). >> >> If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. >It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. Ok guys the plot thickens. Yesterday using the Mailman Shell I unbounced all the users on that list. We had a couple of messages yesterday and I also enabled the From munging for all messages sent to the list partway through those messages coming to the list. This morning we got all Gmail users bounced again, with no NDR attached to the message. However on one of the messages the NDR was attached, and so I'm going to send that to Mark separately. It looks like the NDR included the information for all the bouncing messages though, and that is probably because Mailman sends the messages to all users in one SMTP transaction. The message returned from Google was: user(a)gmail.com 9/22/2023 9:44:55 AM - Server at PAVPR08MB9257.eurprd08.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' 9/22/2023 9:24:03 AM - Server at gmail-smtp-in.l.google.com (142.250.27.27) returned '421 4.4.2 Connection dropped due to SocketError' Thanks. Andrew.

2 years, 10 months

[MM3-users] Re: Manual setup - permissions

by Abhilash Raj

On Mon, Sep 23, 2019, at 3:02 AM, Tobias Hachmer via Mailman-users wrote: > Hi Mark, > > thanks for your response. > > On 9/23/19 1:29 AM, Mark Sapiro wrote: > > On 9/22/19 2:11 AM, Tobias Hachmer via Mailman-users wrote: > >> > >> Now, running the scheduled tasks (which run from user+group "nginx") for > >> django I ran into permission problems, because the nginx user can't > >> access/write to the needed files in /opt/mailman3/core/... > >> > >> I would appreciate any hints how to run the different peaces of mailman3 > >> with the correct user/groups/permissions. > > > > > > Set up everything as user:group mailman3:mailman3. I.e., > > > > chown -R mailman3:mailman3 /opt/mailman3/web > > > > and set the uwsgi service to drop privileges to user+group "mailman3". > > So simple, now the scheduled tasks are working, but the whole web > service did not work because the web server user nginx can't access and > write to the uwsgi socket anymore /opt/mailman3/web/project/run/uwsgi.sock. > > # chown -R nginx:mailman3 /opt/mailman3/web > > This works for all. But isn't it a security risk that e.g. manage.py and > settings.py is read- and writeable by the webserver? You just need them to be readable, not writable. You could possibly use xattrs to do just grant read privs. You could also configure uwsgi to create a socket somewhere nginx can read it, `/var/run/uwsgi.sock` should be good enough. You can in theory also try https://uwsgi-docs.readthedocs.io/en/latest/Systemd.html for systemd setup in which case you don't have to manually create sockets as systemd can do that for you. > > Regards, > Tobias > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > *Attachments:* > * signature.asc -- thanks, Abhilash Raj (maxking)

6 years, 10 months

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by Abhilash Raj

> On Mar 13, 2021, at 1:09 PM, John Covici <covici(a)ccs.covici.com> wrote: > > On Sat, 13 Mar 2021 14:46:55 -0500, > Mark Sapiro wrote: >> >> On 3/13/21 11:14 AM, John Covici wrote: >>> >>> Now one thing came up while trying to create the database, I got a >>> traceback complaining about a revision error because gentoo had a >>> slightly different version (3.3.2) instead of 3.3.3 using pip. When I >>> upgrade mailman, am I going to have to do something to the database as >>> well and why should the database have some kind of reference to the >>> mailman version? >> >> >> I don't know why this is an issue. You shouldn't need to do anything >> with the database when you upgrade. Please post the full traceback and >> error message. > > Sorry I can't reproduce it, after dropping and recreating the database > the error went away, but it was in alembic and it was talking about an > invalid revision and gave a long hex string. > My guess is that you updated the database (perhaps, by invoking the mailman command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes up and sees a new revision for the database migration added from 3.3.3 but can’t find the same migration in its source (because it is 3.3.2). But that’s just my guess without looking at the traceback. > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > covici(a)ccs.covici.com <mailto:covici@ccs.covici.com> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

5 years, 4 months

Search results for query "sapiro"