> I finally got RC3 to work.
> I think the problem was that I had some files in the inbox.
> I had mad a copy of one (including object and stream) under 2.1.3.
> So instead of filename, it contained "Copy of filename".

That is why I told you to make sure that EVERY file matched the pattern I
gave you.  When you listed the files that were in that directory, you did
not list the "Copy of ..." filename.  If you had, I would have told you
right away that it was the cause of your troubles.

> The following might be useful for faq or release notes or something
> as it affects the transition form a working 2.1.3 to a working RC3.

> I run a 172.21x.x. behind my firewall so I have a minimal DNS server for
> internal use.  With 2.2.0 RC3, the config also has:
>       <autodiscover>true</autodiscover>
> So I guess it discovered this server and the lack of an MX record caused
> error messages that I think were no relay allowed.

> Perhaps a line or two that says "if you want to process emails for
> [EMAIL PROTECTED] and [EMAIL PROTECTED] that you should entries:
>          <servername>abc.com</servername>
>          <servername>abd.net</servername>

> I don't understand the new SenderInFakeDomain

Ah ... already attended to in the MAIN (James v3) branch, but I can copy the
comment back to James 2.2.0.

See
http://news.netcraft.com/archives/2003/10/01/wildcard_tlds_and_the_web_serve
r_survey.html for an explanation of the IP address list.  Basically, if you
do a lookup of a non-existent domain, rather than return NXDOMAIN, certain
domain registrars give you a generic address, e.g.,
http://www.bogus.museum/.

See also: www.isc.org/products/BIND/delegation-only.html
          http://tinydns.org/

One problem with these wildcard DNS entries is that they are www-centric,
and don't take other services, such as mail, into account.  Just because a
wildcard is useful to take you to the museum list, doesn't make it useful
when trying to decide if mail from @bugus.museum is from a valid domain.

        --- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to