>
> Hi Roger,
>
> There is a <mailet> tag in the config.xml file that contains
> a <gateway>
> tag and a <gatewayPort> tag.
>
> Set the <gateway> tag to the IP address of the remote
> mailserver through
> which to route all the mail and set the <gatewayPort> tag to whatever
> the SMTP port on that machine is, 25 being the default.
>
Hi Darryl
I've done that. James doesn't want to know. If I have any DNS servers defined
then James sends directly to that domain, if I don't have any DNS servers
defined then James complains in the logs that it can't find a DNS entry for the
remote domain and doesn't know where to send the message.
24/11/04 13:21:19 INFO James.Mailet: RemoteDelivery: Storing message
Mail1101302073823-0-to-atosorigin.com into outgoing after 1 retries
24/11/04 13:31:50 INFO James.Mailet: RemoteDelivery: No mail server found for:
atosorigin.com
24/11/04 13:31:50 INFO James.Mailet: RemoteDelivery: Temporary exception
delivering mail (Mail1101302073823-0-to-atosorigin.com:
javax.mail.MessagingException: There are no DNS entries for the hostname
atosorigin.com. I cannot determine where to send this message.
at
org.apache.james.transport.mailets.RemoteDelivery.deliver(RemoteDelivery.java:398)
at
org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.java:912)
at java.lang.Thread.run(Thread.java:536)
Regards
Roger
> I've never relayed through an exchange server before so I have no idea
> of what sort of authentication issues you may run into, but
> if there are
> any the james smtp and mailet logs should give you enough
> information to
> identify what else will have to be done.
>
> Darryl.
>
> -----Original Message-----
> From: Varley, Roger [mailto:[EMAIL PROTECTED]
> Sent: 24 November 2004 04:31 PM
> To: [EMAIL PROTECTED]
> Subject: Configuring James to route all outgoing mail to an Exchange
> Server
>
> Hi
>
> I'm new to james so if I've missed some obvious documentation please
> accept my apologies and point me to what I've missed.
>
> I have a Tomcat Server who's servlets currently send e-mails using the
> Mail API via a remote Exchange server. Obviously, when the
> remote server
> is either down or very busy mails do not get sent. It has
> been suggested
> that I install James on the Tomcat server and let James take care of
> sending/re-sending the mail to the Exchange server.
>
> James will be used one-way only, in that the servlets send the e-mails
> to James and James forwards to Exchange, there will be no
> incoming mail
> to the James server either from the Exchange server or from
> the outside
> world (Port 25 is closed on the Tomcat server).
>
> I've downloaded James and tried to set the config.xml as documented on
> the Apache James site. I have set the IP address of the
> remote Exchange
> server in the <mailet match="All" class="RemoteDelivery"> block - but
> thereafter I get stuck. If I specify any sort of DNS server,
> James sends
> the mails directly to the mailserver for the remote domain, if I don't
> define any DNS servers and set autodetect to false, then James doesn't
> send the emails and complains in the log files about the lack of DNS
> servers. I've found this question asked before in the list
> archives but
> I've beeen unable to find the answer.
>
> Any assistance would be gratefully received.
>
> Regards
> Roger
>
>
> ______________________________________________________________
> __________
> __
> This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you
> receive this
>
> e-mail in error, please notify the sender immediately and destroy it.
> As its integrity cannot be secured on the Internet, the Atos Origin
> group
> liability cannot be triggered for the message content. Although the
> sender endeavours to maintain a computer virus-free network,
> the sender
> does not warrant that this transmission is virus-free and will not be
> liable for any damages resulting from any virus transmitted.
> ______________________________________________________________
> __________
> __
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.799 / Virus Database: 543 - Release Date: 2004/11/19
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
__________________________________________________________________________
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive this
e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender
does not warrant that this transmission is virus-free and will not be
liable for any damages resulting from any virus transmitted.
__________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
