John, Did you check the headers of the returned message to see where it came from? Did you check the James logs to see if the mail reached your mail server? If it did the logs will probably give you the best clues about why it was rejected.
Ian 2007/10/14, John Rose <[EMAIL PROTECTED]>: > I do understand this is not a James email message. > > These two messages are from two different end-user's email systems. If I'm > interpreting this correctly, they sent and email from (lets say for the > sake of discussion their Outlook system) to their user box in our > application which is processed by James. Somewhere that email is getting > rejected either by another mailserver in between or finally by James. That > rejection is being sent back to Outlook and Outlook is reporting the > rejection using Outlook's error handling. > > I do appreciate the suggestion of looking at another mail server in > between the end user mail system and our James mail server. I will > explore than angle. I still don't understand the randomness of the > relay-denied message. I would think it would always fail or always be > delivered. > > Thanks again for your response, Stefano. > > John Rose > > > > > Stefano Bagnara <[EMAIL PROTECTED]> > 10/13/2007 03:32 PM > Please respond to > "James Users List" <[email protected]> > > > To > James Users List <[email protected]> > cc > > Subject > Re: James is rejecting emails sporadically with a relay-denied error > > > > > > > John Rose ha scritto: > > 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> > > > This is not an error from JAMES Server. JAMES Server never use that > error format. So you probably have a misconfigured DNS or anyway the > mail land a bad mailserver before JAMES Server. > > Stefano > > > 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 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > ******************************************************************************** > 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. > ******************************************************************************** > -- Ian Lewis [EMAIL PROTECTED] http://www.ianlewis.org/ http://jsxe.sourceforge.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
