I have set this up successfully in the past.

- compare in JetspeedResources.properties (in the WEB-INF/conf dir) the
value of

[EMAIL PROTECTED]

- to the James.conf value

<servernames>
    <servername> mydomain.com</servername>
    <servername> other valid domains to handle </servername>
</servernames>

- if domain is not included in the servernames of james.conf, all the emails
will be dumped into James' spam folder.

Steve B.

----- Original Message -----
From: "Charles Benett" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 16, 2001 1:02 AM
Subject: Re: James not receiving confirmation email from Jetpseed when
adding users.


> As your Outlook clients can send email via James, your problem probably
> lies with Jetspeed. So I'd ask them.
> Charles
>
> scott wrote:
> >
> > Dear all
> >
> > My James is running. and I can use Outlook client to send out and
receive
> > mail among users that I added to the  James mailserver (in my case is
> > localhost).
> >
> > My problem is that I tried to add users to Jetspeed, but after adding
the
> > user, Jetspeed moves to next page asking for my confirmation key which
was
> > supposed to sent out to an email address created within James.  But the
user
> > didn;t receive any single mail.
> >
> > At Jetpseed, inside the TurbineResource.properties file, I locate the
> > following variable and set it to my localhost. Can any body let me know
> > whether the setting is correct and is this the only setting I need to
> > change.
> >
> > mail.server=localhost
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


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

Reply via email to