[Mailman-Users] mailman domain error

Mark Sapiro msapiro at value.net
Tue Jan 23 07:53:49 CET 2007

Christopher Glanville wrote:

>The /var/log/exim4/mainlog file shows no difference between a.com and 
>b.com but yet b.com doesn't arrive??

Are you saying that mail to list at b.com produces an exim log entry like

2007-01-22 22:38:05 JCB6FF-0001N0-GS => list <list at b.com>
R=mailman_router T=mailman_transport

If so, that message got delivered to Mailman's 'in' queue (or at least
got piped to the wrapper, but if list at a.com works, we can assume that
the wrapper does the same thing because it's called the same way).

Lot's of things can happen to the message after that, but the most
likely is the message is held because require_explicit_destination is
yes, and Mailman is looking for list at a.com and list at b.com is not in
acceptable_aliases. What's in the admindb interface waiting for
moderator action? What's in Mailman's vette log? What's in Mailman's
other logs?

Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

More information about the Mailman-Users mailing list