> OK - thanks - got it working. Thanks for your patience! [more inline]

Welcome.  :-)

> > As I have said, the entire message flow is traced for you so that you
can
> > debug configuration issues.  You just need to read it.

> And understand it :( Sorry - I am new to this stuff (mail and Avalon).

I understand.  But it really is very simple to follow if you relax, and just
read it.  Hey, I've been there, too.  Right now I'm working my way through a
Perl script that I'm planning to convert into ... probably a servlet filter.

> > (a) move the list configuration to the transport processor.

> First, I thought I read documentation somewhere that said to put it in the
> root processor (can't remember where).

If you find out, let us know.  The documentation,
http://james.apache.org/mailing_lists_2_1.html, mentions "at the top of the
transport processor."

> my misunderstanding of the fact(?) that you need to have a
> correct order in the processors.

There is no order.  Processors are standalone, effectively linked by
ToProcessor mailets.  New messages start at the root processor.  Within a
processor, <mailet> tags are evaluated in order.

> I first tried moving the list elements to the transport processor *under*
> the existing match="RecipientIsLocal" and match="HostIsLocal" and it still
> did not work.

Recipient would have taken off the valid local addresses, and HostIsLocal
would have taken the remainder, and sent them to another processor as an
error.

> I put it at the top (first child under <processor name="transport">)
> of the transport processor and everything worked.

Yup.  :-)

> >  (b) figure out why it thinks that your IP address is bonded.

> I have no idea why it thinks that.

It isn't your domain, it is the IP of the mail agent that is talking to
James that matters.  Definitely something to figure out because otherwise
messages will bypass the anti-spam checks.

        --- Noel


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

Reply via email to