I tried posting this twice at the website and it appears to blackholed both times, don’t know whether it’s a new-user moderating thing or what. So apologies if this is a duplicate
Hopefully, this is simple. I know nothing about the innards of Mailman -- I've been just using it as a black box for a decade and it's been working fine.
Today, in the process of handling a subscriber's non-delivery complaint, I came across this error message in WHM's Mail Delivery Reports:
From Address: mailman-loop(a)server.wickenburg.us
Sender:
Sent Time: Feb 22, 2025, 6:48:18 PM
Sender Host: server.wickenburg.us
Sender IP: 127.0.0.1
Authentication: unauthorized
Spam Score: 0
Recipient: root(a)cloud-ci.unifiedlayer.com
Delivered To:
Delivery User:
Delivery Domain: cloud-ci.unifiedlayer.com
Router: reject
Transport: **rejected**
Out Time: Feb 22, 2025, 6:48:18 PM
ID: 1tm16p-00000000BOG-aS00
Delivery Host: server.wickenburg.us
Delivery IP: 127.0.0.1
Size: 0 bytes
Result: The mail server could not deliver mail to root(a)cloud-ci.unifiedlayer.com. The account or domain may not exist, they may be blacklisted, or missing the proper dns entries.
The recipient identified is not anything I ever set up. "unifiedlayer" belongs to my hosting provider, so this may be some sort of default or unset value. I've scoured the Mailman configuration screens for anything resembling this, or any field I should have provided but left blank, and I'm buffaloed.
Where is Mailman getting this value from, and how to I change it to something more useful?
I want to set up two anouncement-only lists, call them U and P with the
following linked conditions.
* Posts by the authorized poster to list U will go to members of BOTH
lists U and P.
* Posts by the authorized poster to list P will go ONLY to members of
list P.
* If a subscriber's address is on BOTH lists U and P, said subscriber
will only receive ONE copy of an authorized post to list U.
Is this possible, and if so, how? I'm running Mailman 2.1.18-1.
--
Lindsay Haisley | "The arc of the moral universe is long,
FMP Computer Services | but it bends toward justice"
512-496-7118 |
http://www.fmp.com | - Martin Luther King, Jr.
In 25 years of operation one in-house working-group FINALLY decided to
activate the "topics" feature in a list on our MM2 instance.
Questions:
* when a user is added, no topics are automatically chosen.
Is there a way of (for example) enabling ALL/CERTAIN topics by default?
Rationale behind this: If it becomes "too much" for a member he or
she can simply opt out of certain uninteresting topics.
* Is there a way of setting a default for "Do you want to receive
messages that do not match any topic filter?" for every (new) member?
Rationale behind this: Uncategorized topics should not be lost or invisible.
--
Ralf Hildebrandt
Charité - Universitätsmedizin Berlin
Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration
Invalidenstraße 120/121 | D-10115 Berlin
Tel. +49 30 450 570 155
ralf.hildebrandt(a)charite.de
https://www.charite.de
