- Jun 24, 2006
- 3,248
- 1
- 81
Sorry if this is the wrong forum, this seems like the best category to post this question.
I need to set up a way to capture bounced-back email (non-delivery reports aka NDR's). My plan is to set up a special subdomain (e.g. noreply@bounce.mycompany.com) so all NDR's go to that domain. I'd create an MX record pointing to my servers (or other external facing MTA's provided by my ISP, and then have those forwarded to my machines, depends on what my ISP decides about security with regard to having incoming connections to my machines). I want to run each NDR through a process to take action based on the reason for non-delivery.
What I need to do is kind of not that specific to NDR reports, just need to be able to access emails to a certain domain:
The reason I'm setting up the separate domain is I want this to run completely outside of the rest of my company's email infrastructure. I have two servers available that run other custom apps. I'd rather not install exchange. I need to basically access the emails (the NDR's themselves are emails) via either file system, or a POP3 account. What's the best way to do that (windows 2003 on these machines)? What software would I need, can IIS 6.0 SMTP handle this itself?
Further requirements are that if something were to go wrong on my two servers (i.e. disk fills up and they stop accepting emails, or the servers explode), i don't want my systems sending out NDR's about the NDR's (i.e. "double-bounce"). Is there a way to ensure this?
I need to set up a way to capture bounced-back email (non-delivery reports aka NDR's). My plan is to set up a special subdomain (e.g. noreply@bounce.mycompany.com) so all NDR's go to that domain. I'd create an MX record pointing to my servers (or other external facing MTA's provided by my ISP, and then have those forwarded to my machines, depends on what my ISP decides about security with regard to having incoming connections to my machines). I want to run each NDR through a process to take action based on the reason for non-delivery.
What I need to do is kind of not that specific to NDR reports, just need to be able to access emails to a certain domain:
The reason I'm setting up the separate domain is I want this to run completely outside of the rest of my company's email infrastructure. I have two servers available that run other custom apps. I'd rather not install exchange. I need to basically access the emails (the NDR's themselves are emails) via either file system, or a POP3 account. What's the best way to do that (windows 2003 on these machines)? What software would I need, can IIS 6.0 SMTP handle this itself?
Further requirements are that if something were to go wrong on my two servers (i.e. disk fills up and they stop accepting emails, or the servers explode), i don't want my systems sending out NDR's about the NDR's (i.e. "double-bounce"). Is there a way to ensure this?