All of the emails sent by our server out to the mailing lists were using the host name instead of the DNS A record for the Mailman VirtualHost. I tried for days to fix this and eventually got the feeling that it was DNS related. However, I still couldn't see why Sendmail would force the To-header back to the canonical name when Mailman was setting it correctly. Eventually, I happened across this email ( http://mail.python.org/pipermail/mailman-developers/1998-August/004971.html) on the dev list that solved the problem by manually editting sendmail.cf's rulesets to bypass canonicalization. I'm sure this violates some RFC. Although, the hack does indeed solve the problem. The actual wizardry was to comment out the following line in sendmail.cf.
# pass to name server to make hostname canonical # R$* $| $* < @ $* > $* $: $2 < @ $[ $3 $] > $4 It's absolutely wrong to do this because if you edit sendmail.mc, and restart sendmail, the cf file gets regenerated automatically which obliterates the change. Is there a better way to fix this without violating RFCs and changing sendmail rulesets? Note: I don't have access to the DNS server. Tony Perrie Engineer, STI Convergence Team, BQQA 11501 Burnet Rd, Building 906/3007C Austin, TX, 78759 Phone: 512-838-1402, T/L: 678-1402 Fax: 512-838-2132 ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
