Lucio Chiappetti wrote:
- all our e-mail are of the form user@domain NOT user@host.domain
OK
- all outgoing mail is masqueraded as user@domain by sendmail
OK
- the DNS advertises two MX's for the domain. We do not advertise MX's for particular hosts. Hosts other than MX's should have the SMTP port blocked by a firewall on the boundary router (we are several institutes in the same building, the boundary router is not managed by ours).
OK
[...]
- mailman will be installed on a given host (I call it mmhost for the purposes of this mail, but the real name will be different). Most likely it will be our www server (www.domain where www is a CNAME for its real host name), NOT the MXs (the two MXs are redundant, and are also the primary and secondary DNS and NIS servers).
If it is not the www server, you can use one of the methods in FAQ 4.84
I know now that DEFAULT_URL_HOST shall point to www.domain (or perhaps a dedicated virtual www server)
I know now that DEFAULT_EMAIL_HOST can be set to "domain" to make lists and service addresses of the form "list@domain" (preferred to list@mmhost.domain)
I know from my tests how to coerce sendmail and mailman to use (and automatically create) LOCAL aliases of the form
listname: "|/usr/lib/mailman/mail/mailman post listname"
but of course THESE aliases are not suitable to be NIS aliases. /usr/lib/mailman/mail/mailman won't exist on the MXs and on the clients !
But it is trivial to augment your script that copies Mailman's aliases for sendmail by adding something like
sed -r -e "s/^(.*):.*$/\1: \1@mmhost.domain/" < /path/data/aliases > ...
plus the command(s) necessary to install those in NIS.
[...]
PS I read also FAQs 4.84 and 4.72. Any more suitable for our configuration ?
I think those are good.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan