Thanks. I'll keep that filed for future reference.
This particular project needs to have everything kept server-side, so processing the NDRs through Outlook isn't going to be very practical. ________________________________ From: Davies,Matt [mailto:[EMAIL PROTECTED] Sent: Sunday, March 16, 2008 3:43 PM To: MS-Exchange Admin Issues Subject: RE: How to programmitically capture delivery failures. You could look at Genius Connect, it allows outlook to sync with a sql database, we use it to keep our mailing lists up to date. http://www.geniusconnect.com/geniusconnect.asp Cheers Matt From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: 14 March 2008 21:27 To: MS-Exchange Admin Issues Subject: RE: How to programmitically capture delivery failures. I'll look into them. I have to get anything that's not from an already approved vendor through an approval and risk assessment process before I can install it on a production machine. Right now I'm just trying to get something reasonably reliable in place and working as soon as possible. Running them to the queue seemed like the quickest way to be able to do that. I understand this is more of an "administrators solution" to the problem, than a "developoer's solution", but for the moment I don't have the luxury of getting to wear that hat for as long as it will take to do it the "right" way. ________________________________ From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2008 4:07 PM To: MS-Exchange Admin Issues Subject: RE: How to programmitically capture delivery failures. I gotta go back and recommend the Lumisoft library. You can pull those messages down using either POP-3 or IMAP and process them. The library also has easy ways to deal with MIME encoding (which I've found invaluable). All that being said, the Exchange 2007 libraries for dealing with MIME are well documented and slightly easier to use than Lumisoft's library. However, by using the Lumisoft solution you can develop a solution NOW that will work on both versions of Exchange Server. ObDisclaimer: I am not associated with Lumisoft in any way. He fixed a bug in his library for me once, and that's the only contact I've ever had with the author. I've just had great luck with the solution - especially when building applications in PowerShell and C#. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2008 8:19 AM To: MS-Exchange Admin Issues Subject: RE: How to programmitically capture delivery failures. Well, I can pull the delivery failures out of the mailbox using the \\.\backoffice <file:///\\.\backoffice> file path, but it's not pretty. Using it also means I have to find another solution soon because I'm in the process of getting rid of those E2K3 servers. It seems like the hard part is getting them out of the mailbox. I'm considering sending them to a dead-end queue, and pulling them out of there as .eml files using the EMS export-message cmdlet. As far as getting them to the queue, I was thinking of either sending them from (or just re-directing the returns to) a non-authoritative domain, setting up a send connector for that namespace, and dead-end it (maybe smarthost it to an unreachable address). All the returns should collect in that connector's queue, and then it's just a matter of using the EMS cmdlets to export them, and keep the queue cleaned up. Thoughts? ________________________________ From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2008 7:56 PM To: MS-Exchange Admin Issues Subject: RE: How to programmitically capture delivery failures. Actually, what you want is the M: drive. I am one of the few that regret that that capability was removed from Exchange 2007 (in Exchange 2003, it was available as \\.\BackOfficeStorage\<primary-domain>) Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2008 8:54 PM To: MS-Exchange Admin Issues Subject: RE: How to programmitically capture delivery failures. Forget that idea. I was thinking a journal report was stored outside of a mailbox. I'm no better off trying to get that than the original email. Seems like this ought to be easier. I wish exmerge had an option to export to .txt. ________________________________ From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2008 7:48 PM To: MS-Exchange Admin Issues Subject: RE: How to programmitically capture delivery failures. I was hoping you'd drop in. I was just considering the possibility of setting up a mailbox to receive the DSNs, journaling the mailbox and extracting the data out of the journal reports. ________________________________ From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2008 7:38 PM To: MS-Exchange Admin Issues Subject: RE: How to programmitically capture delivery failures. I programmed this for a client using a PowerShell script based on the DSNs they received. I don't own the code, so I can't post it, but I can share that the Lumisoft NET library is a godsend for doing this kind-of stuff. It doesn't make it "easy", because you've got to program around a few bugs in their MIME implementation, but it makes it quite feasible and not extraordinarily difficult. And if you use the POP-3 interface or the IMAP interface, the Exchange version doesn't matter (and you can use various 3rd party mail servers as well). Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2008 7:39 PM To: MS-Exchange Admin Issues Subject: How to programmitically capture delivery failures. Problem: An application has a user database with email addresses. The application will send an email to the users in the database periodically. The application developers want the emails addresses from any of these that came back undeliverable captured and sent back to them to clean up the database. Environment - Exchange 2007 Edge and Hub Transport servers. Exchange 2003 servers on the back end with the mailboxes. (No 2007 mailbox servers yet). We're using an outsourced mail host (Message Labs) for delivery, so the protocol logs aren't much help. All outbound email will initially be accepted by the servers at Message Labs, so there won't be any delivery failures reported in the protocol logs on the Edge servers. Any email returned to the sending address should be a DSN. There shouldn't be any replies or other inbound email to that address. If I can get the incoming DSN's routed to a text file, I can parse out the information I need. Originally I was thinking about just letting them go to BADMAIL, but it seems that Exchange 2007 doesn't give you that option. Any ideas? ************************************************************************************************** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ************************************************************************************************** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
