May 2020 - Mailman-users - lists.mailman3.org

Separating Lists by Domain
by brian＠emwd.com May 1, 2020

May 1, 2020

I have successfully setup a second domain with my Mailman3 setup. I also created a list using the second domain. So I have two domains with one list each. The issue I see at this point is all of the lists are shown via Postorius regardless of the list domain used. Is it possible to have only the lists to show that are part of the domain being used to access? For example: http://domaina.com/postorius/lists/ Only listnames(a)domaina.com show up. http://domainb.com/postorius/lists/ Only listnames(a)domainb.com show up. Right now both domaina AND domainb lists showup regardless of the domain being used to access Postorius. The same goes for Hyperkitty as well. Brian

6 11

Running mailman3 on AWS and dealing with SES email verification
by Mohsen Masoudfar May 1, 2020

May 1, 2020

Hi, This seems to be a very basic question and/or issue, but I could not find a reliable for it: Assume a list member with the email address like (just as an example) joe.student(a)university.edu<mailto:joe.student@university.edu> sends an email to a list, Mailman gets the email, processes it and would try to send that email to all members with a sender field as: 'joe.student(a)university.edu<mailto:joe.student@university.edu>'. plus listname(a)listserver.TLD<mailto:listname@listserver.TLD> AWS allows verified email addresses to send an email from an EC2 to internet, so the listname(a)listserver.TLD<mailto:listname@listserver.TLD> is OK, because listserver.TLD is already verified, BUT Joe's email is not and cannot be, because there are thousands of list users and they can change daily. The result is that Mailman's try to send the email would fail with the following error message: Message rejected: Email address is not verified. The following identities failed the check in region US-EAST-1: joe.student(a)university.edu<mailto:joe.student@university.edu> I changed the list property and made it an anonymous one, and it started sending the emails to the whole list members, but only with listname(a)listserver.TLD<mailto:listname@listserver.TLD> as the sender. So the list recipients cannot know the initiator of the discussion. I found some solution: * Asking the members to add their email to the signature * manipulating the from field and add the name of the sender as a comment, not that easy, needs some Python code * manipulating the from files and replacing the @ with something else, not that easy, needs some Python code * . . . More important: None of these would allow a simple click on the reply bottom to send the email to the original sender. I am thinking of running mailman on-premise and use our email relay, which we have full control on. But really, there is no elegant solution for this? I already opened a ticket with AWS support and they just insisted on their policy of verification. Best regards Mohsen Masoudfar Lead System Analyst, IT Operation American Association for the Advancement of Science 1200 New York Ave, NW, Washington, DC 20005 202-326-7087

2 3

Recipient address rejected: User unknown in local recipient table
by Mohsen Masoudfar May 1, 2020

May 1, 2020

Hi, I created a list called list_b@newlistserv.<tld<mailto:list_b@newlistserv.%3ctld>> , and added a user to it and invited the user. The user got a welcome email, when the user replies with help, The email gets rejected with the message: list_b wasn't found at newlistserv.<tld> and I see this entry in the postfix log on the server: postfix/smtpd[6757]: NOQUEUE: reject: RCPT from mail-eopbgr750113.outbound.xxx: 550 5.1.1 <list_b(a)newlistserv.xxx>: Recipient address rejected: User unknown in local recipient table; from=<xxx> to=<list_b(a)newlistserv.xxx> proto=ESMTP helo=<NAM02-BL2-obe.outbound.protection.outlook.com> I am new to mailman3, my understanding was, maybe wrong, that when I create a list, mailman3 adds that to the local list of users. I think , I am missing something . . . Or probably this is related to a postfix setting? Best regards Mohsen

3 6