Serge Knystautas wrote:
>
> ----- Original Message -----
> From: "Charles Benett" <[EMAIL PROTECTED]>
> To: "JAMES" <[EMAIL PROTECTED]>
> Sent: Wednesday, September 13, 2000 11:26 AM
> Subject: New Mailet API
>
> > 2) Something seems to have gone amiss in the mailet processing. James
> > appears to be trying to remotely deliver when it should be locally
> > delivering and it is munging the sender and therefore failing to send (I
> > think - still trying to get to grips with new API!). I think the first
> > issue means RecipientIsLocal is not working, and is related to the
> > implementation of the new MailetContext and how it interacts with
> > UserManager. I've no ideas on the second problem.
>
> Patched! Ironically, RecipientIsLocal was written incorrectly in the first
> place... it was retrieving the list of possible users during init, rather
> than during each call. This means when you added your accounts and then
> sent the messages without restarting, RecipientIsLocal wasn't aware of the
> new accounts. I say ironic because JAMES 1.1 is actually instantiating and
> init'ing each mailet and matcher *for every message*. In 1.2, I've got it
> properly keeping these matchers and mailets in memory, so the bug in the
> matcher appeared.
>
> Anyway, that's patched and I was able to successfully retrieve my message
> through POP3. I'm also changing the default conf file to bounce messages
> that have HostIsLocal (but didn't mean the RecipientIsLocal) as otherwise
> the mail server just SMTPs the messages back to itself.
Works for me too!
C
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
