Improper token substitution? Or something else?
I've noticed that in our Mailman installations here we're getting some odd addresses showing up in different places. For instance, the "Welcome" web page contains:
"If you are having trouble using the lists, please contact mailman@list_hostname.tld." [list_hostname.tld is any list's FQDN]
"mailman" is not the name of the list for which "list_hostname.tld" is the FQDN of the list, and this address will bounce.
A similar situation happens with the monthly reminder messages for which userpass.txt is the template. The text going out contains:
"If you have questions, problems, comments, etc, send them to mailman-owner@list_hostname.tld."
Again, this bounces - "listname-owner@list_hostname.tld" would not.
This is happening on two different Mailman installations, running 2.1.18 and 2.1.18-1.
Do I have a misconfiguration here? The comments in the source indicate that these token replacements insert _site_ information rather than _list_ information, so maybe this is the expected behavior. Do I need to set up a "mailman" address alias for _each_ virtual host on the system so that these addresses will work? This is doable, but is it documented?
--
Lindsay Haisley | "The first casualty when
FMP Computer Services | war comes is truth."
512-259-1190 |
http://www.fmp.com | -- Hiram W Johnson
On 02/09/2016 04:32 PM, Lindsay Haisley wrote:
...
If you are using Postfix, see the bug at <https://bugs.launchpad.net/mailman/+bug/1459236>.
I.e., in the latest 2.1.21rc2 release, Postfix/Mailman integration will create these virtual mappings. You may need to run bin/genaliases after upgrade. The NEWS file says
- Mailman-Postfix integration will now add mailman@domain entries in data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS which is a host_name of a list. This is so the addresses which are exposed on admin and listinfo overview pages of virtual domains will be deliverable. (LP: #1459236)
For other MTAs or Postfix without Mailman-Postfix integration, you're on your own for virtual mappings anyway. The need should probably be documented, but where? The two places that come to mind are in Defaults.py in the "Virtual domains" section or in the FAQ. Thoughts?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, 2016-02-09 at 17:07 -0800, Mark Sapiro wrote:
Hmmm. The MTA here is Courier-MTA. The virtual domains structure is elegant in its simplicity, and very flexible.
~vmail/domains/list_hostname.tld/alias/.courier-listname - handles redirection for listname@list_hostname.tld. Similarly, ~vmail/domains/list_hosthame.tld/alias/.courier-listname-default handles everything else addressed to listname-whatever@list_hostname.tld, e.g. listname-request@list_hostname.tld. It does this by redirecting to ~mailman/bin/courier-to-mailman.py, which I wrote based on qmail-to-mailman.py and which is now part of the contrib section for Mailman 2.x.
I'm not conversant with Postfix, but perhaps I can use this feature to solve this problem.
Back to the drawing board ....... :(
--
Lindsay Haisley | "The first casualty when
FMP Computer Services | war comes is truth."
512-259-1190 |
http://www.fmp.com | -- Hiram W Johnson
On 02/09/2016 05:25 PM, Lindsay Haisley wrote:
Postfix is quite different in detail, but based on what you've said above, the equivalent of what Postfix will now do would be to just create
~vmail/domains/list_hostname.tld/alias/.courier-mailman
with the appropriate
|/usr/bin/preline @prefix@/bin/courier-to-mailman.py
content for each list_hostname.tld. As I understand it, this wouldn't require any courrier-to-mailman.py changes as it already knows how to deliver to the 'mailman' list.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, 2016-02-09 at 17:55 -0800, Mark Sapiro wrote:
Brilliant, Mark!!
This was pretty much the result of my own thinking, too ;)
I shall make it so.
The only issue here is that in a few cases we have multiple lists using the virtual domain list_hostname.tld, so the alias will have to reference _all_ the lists using this virtual domain. This is doable.
--
Lindsay Haisley | "The first casualty when
FMP Computer Services | war comes is truth."
512-259-1190 |
http://www.fmp.com | -- Hiram W Johnson
On 02/09/2016 04:32 PM, Lindsay Haisley wrote:
...
If you are using Postfix, see the bug at <https://bugs.launchpad.net/mailman/+bug/1459236>.
I.e., in the latest 2.1.21rc2 release, Postfix/Mailman integration will create these virtual mappings. You may need to run bin/genaliases after upgrade. The NEWS file says
- Mailman-Postfix integration will now add mailman@domain entries in data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS which is a host_name of a list. This is so the addresses which are exposed on admin and listinfo overview pages of virtual domains will be deliverable. (LP: #1459236)
For other MTAs or Postfix without Mailman-Postfix integration, you're on your own for virtual mappings anyway. The need should probably be documented, but where? The two places that come to mind are in Defaults.py in the "Virtual domains" section or in the FAQ. Thoughts?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, 2016-02-09 at 17:07 -0800, Mark Sapiro wrote:
Hmmm. The MTA here is Courier-MTA. The virtual domains structure is elegant in its simplicity, and very flexible.
~vmail/domains/list_hostname.tld/alias/.courier-listname - handles redirection for listname@list_hostname.tld. Similarly, ~vmail/domains/list_hosthame.tld/alias/.courier-listname-default handles everything else addressed to listname-whatever@list_hostname.tld, e.g. listname-request@list_hostname.tld. It does this by redirecting to ~mailman/bin/courier-to-mailman.py, which I wrote based on qmail-to-mailman.py and which is now part of the contrib section for Mailman 2.x.
I'm not conversant with Postfix, but perhaps I can use this feature to solve this problem.
Back to the drawing board ....... :(
--
Lindsay Haisley | "The first casualty when
FMP Computer Services | war comes is truth."
512-259-1190 |
http://www.fmp.com | -- Hiram W Johnson
On 02/09/2016 05:25 PM, Lindsay Haisley wrote:
Postfix is quite different in detail, but based on what you've said above, the equivalent of what Postfix will now do would be to just create
~vmail/domains/list_hostname.tld/alias/.courier-mailman
with the appropriate
|/usr/bin/preline @prefix@/bin/courier-to-mailman.py
content for each list_hostname.tld. As I understand it, this wouldn't require any courrier-to-mailman.py changes as it already knows how to deliver to the 'mailman' list.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, 2016-02-09 at 17:55 -0800, Mark Sapiro wrote:
Brilliant, Mark!!
This was pretty much the result of my own thinking, too ;)
I shall make it so.
The only issue here is that in a few cases we have multiple lists using the virtual domain list_hostname.tld, so the alias will have to reference _all_ the lists using this virtual domain. This is doable.
--
Lindsay Haisley | "The first casualty when
FMP Computer Services | war comes is truth."
512-259-1190 |
http://www.fmp.com | -- Hiram W Johnson
participants (2)
-
Lindsay Haisley -
Mark Sapiro