Hi Ralph,
On Mar 17, 2021, at 5:14 PM, Ralph Weber <roweber@ieee.org> wrote:
I am moving the website www.t10.org from a private/corporate VM to AWS EC2s.
For many years, t10.org has had very happy results with using Mailman 2 for its email reflector, and I have no real concerns about moving to Mailman 3. My bugbear is the fact that I need the following mixed bag of incoming email addresses to work in concert with each other to receive and handle emails.
t10@t10.org (Primary Mailman Reflector) chair@t10.org (Mailman Reflector to direct messages to the T10 chair and his designates)
- docs@t10.org (document posting mechanics - serviced by a small mountain of home-grown code code)
- bbs@t10.org (other publicly accessible services - serviced by code that recalls the days when everything as done on a Bulletin Board System, BBS)
I am not entirely sure what a “Reflector” really is.
My best guess is that the AWS Simple Email Service (SES) needs to sit in front of both Mailman and the home-grown code, to properly direct the incoming emails to the right places. The big worry is as follows...
All available evidence read to date suggests that the default AWS installation of Mailman 3 assumes that Mailman 3 is the *only* receiver of emails in the configuration. If true, then putting SES in front of Mailman could be a Herculean challenge.
Which specific AWS installation guide are you referring to?
Mailman doesn’t really care about being the only receiver of emails. Mailman can receive emails via LMTP or HTTP protocols. If you can do either of those two, you should be good. I don’t remember offhand someone sharing SES configs/setups for receiving emails, but maybe if someone did get that working, hopefully they’ll chime in.
Sending out emails with SES is easy, you just need to setup the right SMTP server in Mailman’s config.
-- thanks, Abhilash Raj (maxking)