OK - thanks - got it working. Thanks for your patience! [more inline]
> -----Original Message-----
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: Saturday, July 05, 2003 1:21 PM
> To: James Users List
>
> Robert,
>
> 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).
<snip/>
>
> That is your root processor. By the way, you don't need the fully-
> qualified
> package names.
OK
>
> So what happens? Again, let's read the log file:
>
> DEBUG spoolmanager: Processing Mail1057429170468-0 through root
> DEBUG spoolmanager.root: Servicing mail: Mail1057429170468-0
> DEBUG spoolmanager.root: Checking Mail1057429170468-0 with
> [EMAIL PROTECTED]
> DEBUG spoolmanager.root: Servicing Mail1057429170468-0 by Postmaster
> aliasing mailet
> DEBUG spoolmanager.root: Checking Mail1057429170468-0 with
> [EMAIL PROTECTED]
> DEBUG spoolmanager.root: Checking Mail1057429170468-0 with
> [EMAIL PROTECTED]
> DEBUG spoolmanager.root: Servicing Mail1057429170468-0 by ToProcessor
> Mailet
> DEBUG spoolmanager: Processed Mail1057429170468-0 through root
> DEBUG spoolmanager: Result was transport
>
> Just match that up with your config file. The All/PostmasterAlias is
> internal. Then you have RelayLimit, followed by InSpammerBlacklist. We
> see
> that InSpammerBlacklist matches, causing ToProcessor to be invoked,
> sending
> the message to the transport processor. That bypasses your mailing list
> configuration (which is one reason why it isn't a good idea to put it in
> the
> root processor). An interesting question is why it thinks that your IP
> address is in the Bonded Senders registry.
>
> (a) move the list configuration to the transport processor.
Thanks for taking the time to explain!
First, I thought I read documentation somewhere that said to put it in the
root processor (can't remember where).
/I will try to summarize what I did wrong/
I am using the default config.xml from the binary distribution.
When I was in the root proc:
It was mainly my misunderstanding of the fact(?) that you need to have a
correct order in the processors. I did not see anything in the docs that
said you need to have a specific order of things to occur so maybe I am
describing something completely wrong. Conversely, I assumed there was an
order - just, the list should be after all others and before the catchall.
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.
Next, I put it at the top (first child under <processor name="transport">)
of the transport processor and everything worked. Hooray for Rob :)
Is this correct? I would have thought I wanted all other processing to occur
first then James would get to the list.
> (b) figure out why it thinks that your IP address is bonded.
After looking up what that means... I have no idea why it thinks that. I
mainly use the domain to test things. It is registered through register.com
- perhaps it is a default service they offer? Do you think this is a James
problem? If so, do have any ideas on how I can determine what the problem
is? Perhaps all ${number}.com domains get this for free :)
Isn't it a good thing (if not a James problem)?
Thanks again,
-Rob
p.s. Coming up next: questions concerning virtual hosts :) (I know, v3)
>
> --- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
