Hmm.. users do type in [EMAIL PROTECTED] which resolves to same name. So it might be going out and trying to come back in. Our MX record at the ISP points to our firewall which forwards emails to our Exchange 5.5 server. Is there a setting where I can tell it that all internal emails to xxx.com shouldn't go outside?
But I'm still don't understanding why it wouldn't just deliver like it was doing for the last 4 years since the only change was that the public folder was rehomed to the new Exchange 2k server. There shouldn't have been any address change since no one is allowed to modify it. Wilson Varghese NT Systems Manager KMV, LLC Office: (415)229-0726 Email: [EMAIL PROTECTED] -----Original Message----- From: Dupler, Craig [mailto:[EMAIL PROTECTED]] Sent: Monday, February 18, 2002 2:31 PM To: Exchange Discussions Subject: RE: Help with mail enabled Public folder Perhaps. Are you then also saying that your Outlook users are using the external form of address ( [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>) and thus forcing it out through you SMTP gateway for routing by your relay host, and then back in again? You see, I am convinced that if they were mailing to the folder as an AD addressable object from within, then an delivery failure should not be possible. Another possibility comes to mind. Cached but obsolete addresses gathered in the Outlook Contacts list. In either case, or perhaps another which has not yet suggested itself, an addressing change has occurred. There are but two general possibilities: either the address being used is truly valid and the resolution of it is failing, or the address is not valid. Is Sir John around here someplace? -----Original Message----- From: Varghese, Wilson [mailto:[EMAIL PROTECTED]] Sent: Monday, February 18, 2002 2:14 PM To: Exchange Discussions Subject: RE: Help with mail enabled Public folder Sorry, but internal I mean our normal outlook users in the domain that connect to the Exchange servers. All the other email works, I can send to other users fine. I didn't do any MX record changes since the site was still the same, we still have the 5.5 server as our primary until all the users are migrated over. Hope that helps? Wilson -----Original Message----- From: Dupler, Craig [mailto:[EMAIL PROTECTED]] Sent: Monday, February 18, 2002 2:09 PM To: Exchange Discussions Subject: RE: Help with mail enabled Public folder When you say "internal users" what do you mean? The way you laid out the problem, it rather sounds like these users are not using Exchange, but some other SMTP mailer and then relying on your internal DNS to point it toward Exchange - yes? If this be the case, did your true DNS domain names and/ or MX records change during your upgrade? I think you have an address resolution issue at the DNS level. -----Original Message----- From: Varghese, Wilson [mailto:[EMAIL PROTECTED]] Sent: Monday, February 18, 2002 1:41 PM To: Exchange Discussions Subject: Help with mail enabled Public folder Importance: High Hello everyone, Current setup.. One site, with Exchange 5.5 and Exchange 2000 server. Public folders are replicated across both servers but all are homed on Exchange 2000 server. Exchange 2000 is in a child domain that is native for DL reasons. We have a public folder called [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> with an email address of [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> so when you send an email to [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> , it get put in the public folder. This has been working fine for over 4 years, but lately after the Exchange 2000 addition, we are having issues from internal users that send email to this. They get the following NDR. Your message did not reach some or all of the intended recipients. Subject: test Sent: 2/18/2002 12:47 PM The following recipient(s) could not be reached: [EMAIL PROTECTED] on 2/18/2002 12:47 PM The message was undeliverable because the recipient specified has changed address permanently and forwarding was not applicable <sf1-its-exc-001.Exchange.kmv.com #5.1.6> Emails from a test yahoo account went to the folder fine after about 15 minutes so I am assuming that it's being sent to one of the servers then being replicated to the other. (our replication is set to 15 minutes) What I want to know is why the internal users are getting NDRs when the external clients can send to it fine. Please any info you have would be great. I have checked technet and support and can't find this error referenced anywhere. Thank you, Wilson _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
