On Sat, Aug 31, 2024 at 09:06:28AM -0500, Tom Browder wrote:
On Sat, Aug 31, 2024 at 03:42:17PM +0200, Geert Stappers wrote:
On Sat, Aug 31, 2024 at 08:22:40AM -0500, Tom Browder wrote:
I have a class website that I would like to programmatically send noreply@mydomain messages to my list of classmate emails when I periodically update the site. (I used to do that circa 2010 via
Gmail’s API but that changed and I had to stop.)
With modern email handling restrictions I’m not sure that’s
easily done now without lots of hoop jumping. Anyone have a pointer
to a recipe for doing that?
I’m running multiple virtual hosts with modern Apache with
https on my own remote server running Debian. My DNS provider
is Namecheap.
Here a happy user and happy admin of mailman.
But because it is python2 based, I tired mailman3.
Current still a happy user and happy admin of mailman,
but stuck on a Bullseye system.
The 'still happy with mailman' should be read
as 'NOT happy with mailman3', for what it is worth.
Thanks for reminding me
on https://github.com/jaredmauch/mailman2-python3/issues/4
My plan is to go for mailman2-python3 on a Bookworm system.
Yes, I also used Mailman2, but hoped MM3 would cure its warts—unfortunately it ruined it for me.
Maybe I should revisit it.
Just do it. And when there is something to share with the mailinglist,
share it with the right amount context.
Groeten
Geert Stappers
Re-added context that was totaly removed
--
Silence is hard to parse
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)