PD43 replied...

On Mar 14, 3:00=A0pm, Andy David  {MVP}


To expand...

1) the recipient of your email can easily disable the sending of such
receipts.
2) such receipts are not supported in many email situations.

Lesson: stop obsessing about whether or not your emails are being read.

  Ed Crowley [MVP] replied...

They're not completely useless; they're a positive indicator only.  If you
get one, you can be pretty sure the message was delivered, but if you don't
get one you essentially know nothing about the delivery status.
--
Ed Crowley
MVP - Exchange

  Andy David {MVP} replied...

Delivered where? A relay can send back a delivery receipt - doesnt
mean it correctly routed that message to its final destination.

  Ed Crowley [MVP] replied...

Delivered to the relay!
--
Ed Crowley
MVP - Exchange

  Andy David {MVP} replied...

Doh!

Using Outlook 2003 with Exchange 2003.

If a user requests a "Delivery Receipt" when she sends  emails to an outside
address, and then does NOT receive any notification that her email has been
delivered, is that conclusive evidence that her email has in fact NOT been
delivered?

  Andy David {MVP} replied...

Nope. Its conclusive evidence that delivery receipts and read receipts
can be pretty useless.

and should send all email for domain.com to the external service (unless you adjust recipient policy to include domain.com, which you may have done so that email from users one of the alternate domains for SBS Exchange (by running the CEICW and ensuring our recipient policy does not include domain.com) we don't have to do the shared SMTP peruse this Monday evening and post the outcome when I get there. D.Sweet Hi David, Thank you for your post and let's also thanks for SuperGumby's great input with the new email domain name. If CEICW is successful, it will add a new recipient policy as address for external mail flow. However, the default recipient policy For more information about how and what CEICW wizard will do to your domain Recipient Policy, please see: Q&A from Configure and Manage Exchange Server 2003 on Windows SBS appreciated. = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = This posting is provided "AS IS" with no warranties, and confers no rights. Hello David, Thanks for your response. Hope you had a good weekend. From the last mail I would like to explain that running CEICW clean up will not clear up the previous recipient policies if you have ever defined like "@local.domain1.com" or "@domain1.local" for Exchange

see that these are all set correctly. My issue is that my internal clients are getting a password prompt. The password prompt is for access to the external URL supplied by pointless). I hope I have explained this clearly. Any pointers would be greatly appreciated! Cheers, David Exchange Admin Discussions Microsoft Exchange (1) Active Directory (1) Outlook 2007 (1) AutodiscoverInternalURI (1) IIS Elan Shudnow http: / / www.shudnow.net On Sun, 9 Nov 2008 03:42:24 +1100, "David Chadwick" It depends how they connect. MAPI, they get the internal URL HTTPS over RPC the external URL regardless of whether the AutodiscoverInternalURI or autodiscover.domain.com was used. Regards, David Hi Andy, All of my clients get prompted (500 of them) - it's not only configured and I get the credential prompt regardless (when the client is connecting internally). Cheers, David [ snip ] Do you have RPC-over-HTTPS configured for BOTH high- and low-speed connections Outlook. I would have thought that this completely rules it out as the cause. Regards, David On Sun, 9 Nov 2008 14:35:57 +1100, "David Chadwick" It does. I mention it only because you were asking about it. As to in every environment. :) Thanks so much for your responses so far, I appreciate it! Cheers, David On Mon, 10 Nov 2008 00:18:23 +1100, "David Chadwick" [ snip ] Do you have

SMTP getting hijacked Exchange Server I'm getting thousands of msgs queued up from all sorts of random senders. I got some advice following the KB article on how to empty the queue of those msgs. But still getting tons. The good news is this exchange was only being prepared for use, isn't use yet. We are still on POP3. So I am able to turn off outbound delivery so none of this junk is actually getting out. By the way, the "recipient filtering" described in MS docs seems counter-intuitive. I would think I would want to messages wholesale and then determining after the fact that it cannot deliver them because the recipient does not exist. This only has to do with accepting mail that is destined for set up Exchange and realize that they can receive mail but cannot send mail anywhere, getting an "unable to relay" error message when they try to do so. They dig around

incoming mail Exchange Server We have exchange 2003 and recently I (as administrator) have been getting over 600 administrator non delivery emails that are being sent to our domain name but not to legitimate names in get emails from the email addresses in our SMTP settings in active directory users? Thanks. David Exchange Admin Discussions Exchange Server 2003 (1) Report (1) SMTP (1) Sunbelt (1) Sender (1) Ninja (1) Undeliverables (1) Recipients (1) Implement Recipient Filtering. http: / / www.msexchange.org / tutorials / Sender Recipient-Filtering.html Once you've enabled it at the Org level, remember to enable it though the email address on the incoming emails to me are the System Administrator non delivery emails and I don't know why they are all of a sudden coming in. We have a spam filter (GFI) but somehow these are getting through as undeliverables and showing up in my inbox. Is there any place else that I can check? Thank you. David If they are NDR's to addresses you haven't sent to then your email

domain [11:16:54] Leaving ScIsComputerMemberOfDomain [11:16:54] Entering CDirectoryManager::ScGetLocalDomainInformation [11:16:54] Getting information about the local domain [11:16:54] m_strLocalServer = "ms-srv-2" [11:16:54 11:16:55] Looking for server groups [11:16:55] Entering ScGetExchangeServerGroups [11:16:55] Getting DOB for group 0 [11:16:55] Getting string GUID for group 0 [11:16:55] Getting string SID for group 0 [11:16:55] Getting DOB for group 1 [11:16:55 Getting string GUID for group 1 [11:16:55] Getting string SID for group 1 [11:16:55] Leaving ScGetExchangeServerGroups [11:16:55] Server groups been set [11:17:06] Leaving ScDetermineIfLocalDomainServerGroupHasAlreadyBeenACLedOnExchangeCT [11:17:06] Entering ScGetExchangeServerGroups [11:17:06] Getting DOB for group 0 [11:17:06] Getting string GUID for group 0 [11:17