Thanks A couple of people are also getting
Error 5.7.1. You do not have permission to send to this recipient. Unable to relay for. When sending mail from outlook attached to back end server through the front end. When I had one server (exchange 5.5) we didn't have this problem. Its not all email just a couple. Under advanced delivery options in the SMTP properties I tried changing the FQDN to the public mail server name (which is different than the internal one) Thanks for everyone's help. Been a week with exchange 2k3 from 5.5 and just trying to get the nuances right. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Scharff Sent: Thursday, January 22, 2004 5:14 PM To: Exchange Discussions Subject: RE: Relay message A user requested a delivery receipt and the receiving server doesn't support DSN, so your server is telling the sender, I handed it off, but don't construe that to mean it's been delivered. -----Original Message----- From: Montano, Greg [mailto:[EMAIL PROTECTED] Posted At: Thursday, January 22, 2004 3:10 PM Posted To: swynk Conversation: Relay message Subject: Relay message Every now and then a few of my users get this kind of email from the exchange server I have frontend and backend 2003. I have tried keeping the 'authenticated users' only in the relay tab check or unchecked. Depending on the checked status a few users will get this (if checked) or it if not checked will say relaying denied. I think part of the issue is that our external namespace is po1.gnyha.org while the internal AD domain is gnyha.com <=- I had to keep intenal .com due to legacy apps depending on it Anything I should be worried about or do? Thanks all From: POSTMASTER Sent: Thursday, January 22, 2004 3:29 PM To: Smith, John Subject: Delivery Status Notification (Relay) This is an automatically generated Delivery Status Notification. Your message has been successfully relayed to the following recipients, but the requested delivery status notifications may not be generated by the destination. This also attached Reporting-MTA: dns;EXEFE01.gnyha.com Received-From-MTA: dns;po2.gnyha.com Arrival-Date: Thu, 22 Jan 2004 15:14:40 -0500 Final-Recipient: rfc822;[EMAIL PROTECTED] Action: relayed Status: 2.5.0 _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
