Right. But how about in this case: The message is being originated from a web-app, being sent via an authenticated connection to my Exchange server. Failure NDRs do not seem to be landing back to the return-path (assigned to a public folder).
However, status delay NDRs do. Its just the failure replies that seem to not. I'm perplexed to say the least. If a PF can indeed accept a failure NDR, then my next guess is that the 'envelope sender' used by the .NET hook is perhaps different that what the web guys configured as the return-path... On Thu, Jun 12, 2008 at 3:07 PM, Steve Ens <[EMAIL PROTECTED]> wrote: > Are you talking mail enabled folders? usually it is the person who sends as > that gets the NDR... > > On Thu, Jun 12, 2008 at 1:50 PM, Micheal Espinola Jr > <[EMAIL PROTECTED]> wrote: >> >> ::Exchange 2003 >> >> From what I am seeing, the answer is no - but I never would have >> guesses this would be true. >> >> Is there a reghack I need to apply in order to receive >> server-generated NDR failures? Odd thing is that delay status >> messages appear to work fine, but failure messages do not. >> >> TIA! >> >> -- >> ME2 >> >> ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ >> ~ http://www.sunbeltsoftware.com/Ninja ~ > > -- ME2 ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
