We are running James 2.3.1 on a Windows 2003 server. The email interfaces
with our Apache Tomcat application where the emails coming in thru the
James server get posted to a user's mailbox in our application.
There are several complaints coming in from our users indicating email
that they send from their external or outside email network to the their
email address within our application get rejected with an relay-denied
error. This is happening sporadically. Not all emails get rejected. Some
days email goes through into our application fine, other days it gets
rejected. Here is an example of the message being received by the user's
external email system:
Your message did not reach some or all of the intended recipients.
Subject: FW: Our Ref.: xxxxxxx/xxxxx - Your Ref.: yyyy/yyyyyy
Sent: 10/12/2007 9:27 AM
The following recipient(s) could not be reached:
[EMAIL PROTECTED] on 10/12/2007 9:27 AM
There was a SMTP communication problem with the recipient's
email server. Please contact your system administrator.
<netmail.nnnnnn.com #5.5.0 smtp;554 <
[EMAIL PROTECTED]>: Relay access denied>
Another example from another client of ours:
The following message to <[EMAIL PROTECTED]> was
undeliverable.
The reason for the problem:
5.1.0 - Unknown address error 554-'<[EMAIL PROTECTED]>:
Relay access denied'
Here is what I think is the relevant section of the config.xml settings
(replaced our actual ip address with 33.55.77....):
<!-- If you are using this matcher/mailet you will probably want to -->
<!-- update the configuration to include your own
network/addresses. The -->
<!-- matcher can be configured with a comma separated list of IP
addresses -->
<!-- wildcarded IP subnets, and wildcarded hostname subnets. -->
<!-- e.g. "RemoteAddrNotInNetwork=127.0.0.1, abc.de.*,
192.168.0.*" -->
<!-- -->
<!-- If you are using SMTP authentication then you can (and
generally -->
<!-- should) disable this matcher/mailet pair. -->
<mailet match="RemoteAddrNotInNetwork=127.0.0.1,33.55.77.*"
class="Null">
<processor> relay-denied </processor>
<notice>550 - Requested action not taken: relaying
denied</notice>
</mailet>
Any assistance would be greatly appreciated. Just don't know why a given
client can get emails to our application fine and on other days the email
gets rejected.
Thank you.
John Rose
********************************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorized.
If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.
********************************************************************************
