Can't argue with that!
Here's a long shot... On the Privacy Options page of the web Admin, try
putting in the complete name of the mailing list into the field:
"Alias names (regexps) which qualify as explicit to
or cc destination names for this list"
From the example below "[EMAIL PROTECTED]"
It doesn't make any sense, but then neither does the error...
On Monday 22 October 2001 23:42, Moacir wrote:
> Jon Carnes wrote on 22 October 01:
> > Your DNS is improperly setup. There is no MX record for
> > zuikis.uchicago.edu.
>
> Could be. Yet it worked before--and it wasn't a new version of mailman
> that caused the problem.
>
> I tried again using "[EMAIL PROTECTED]" as the sending address,
> and the errors are identical. It seems like DNS can't be the problem if
> a midway.uchicago.edu address works fine.
>
> (2001-10-22 22:33:53 15vsK9-0002Uj-00 <= [EMAIL PROTECTED]
> H=midway.uchicago.edu [128.135.12.12] P=esmtp S=701
> [EMAIL PROTECTED] 2001-10-22 22:33:54
> 15vsK9-0002Uj-00 => test <[EMAIL PROTECTED]> D=list_director
> T=list_transport 2001-10-22 22:33:54 15vsK9-0002Uj-00 Completed)
>
> > nslookup
>
> Default Server: ns2.uchicago.edu
> Address: 128.135.12.73
>
> > set query=mx
> > midway.uchicago.edu
>
> Server: ns2.uchicago.edu
> Address: 128.135.12.73
>
> midway.uchicago.edu preference = 0, mail exchanger =
> midway.uchicago.edu
>
> [etc.]
>
> --m
>
> ------------------------------------------------------
> Mailman-Users maillist - [EMAIL PROTECTED]
> http://mail.python.org/mailman/listinfo/mailman-users
------------------------------------------------------
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
