-
1
- #1
Spent a significant amount of time trying to get the MWI to clear from Message Forwarding.
Platform is BCM450 6.0. I diligently searched the archives and found the advice to correct the DNS settings in element manager. Also checked my DNS server to verify FQDN (bcm.company-name.org) was pointing to correct IP. Then verified the SMTP server was set properly. I was consistenly receiving the message forwards from the BCM but acknowledging the read receipt wouldn't clear the extension's MWI.
In my organization we are active directory integrated with Exchange 2010. We have a "send connector" programmed into Exchange that routes all our email though third-party filtering company (Message Labs) unless it is an internal user in which case Exchange will deliver the message itself.
All the advice I'd read here about how to fix message forwarding MWI just didn't sit right with what I know as an IT Tech. The email originates from the BCM's internal SMTP server which is bcm.company-name.org. So for a read receipt to get back to MAILER-DAEMON@bcm.company-name.org my exchange server needs to know how to send that read receipt back to the BCM's SMTP server. Without a specific send connector for the bcm.company-name.org it's just going to throw it out onto the internet and let MessageLabs figure out what to do with it which it won't know how to either. Just having the right A record in the DNS server for my BCM isn't enough for me.
So... the solution: I added a second smart host entry in Exchange for address space "bcm.company-name.org". Then I programmed this smart host to route these messages through bcm.company-name.org which is the FQDN for the BCM. The BCM's smtp server will now receive the read receipt and clear the MWI immediately once I acknoledge the read receipt.
Problem solved.
Note that you need each individual user's "Original Message" setting in their Message Forwarding configuration of Mailbox Manager set to "Mark As Read When Opened By Recipient." And you need your company's SMTP server programmed into CallPilot Manager under "System Properties." I chose to leave the "From" email address field clear. Finally, make sure your DNS records are solid and that you have your IP subsystem settings correct in Element Manager. It's a necessary step but not always sufficient.
Hope this helps someone else in my situation.
Platform is BCM450 6.0. I diligently searched the archives and found the advice to correct the DNS settings in element manager. Also checked my DNS server to verify FQDN (bcm.company-name.org) was pointing to correct IP. Then verified the SMTP server was set properly. I was consistenly receiving the message forwards from the BCM but acknowledging the read receipt wouldn't clear the extension's MWI.
In my organization we are active directory integrated with Exchange 2010. We have a "send connector" programmed into Exchange that routes all our email though third-party filtering company (Message Labs) unless it is an internal user in which case Exchange will deliver the message itself.
All the advice I'd read here about how to fix message forwarding MWI just didn't sit right with what I know as an IT Tech. The email originates from the BCM's internal SMTP server which is bcm.company-name.org. So for a read receipt to get back to MAILER-DAEMON@bcm.company-name.org my exchange server needs to know how to send that read receipt back to the BCM's SMTP server. Without a specific send connector for the bcm.company-name.org it's just going to throw it out onto the internet and let MessageLabs figure out what to do with it which it won't know how to either. Just having the right A record in the DNS server for my BCM isn't enough for me.
So... the solution: I added a second smart host entry in Exchange for address space "bcm.company-name.org". Then I programmed this smart host to route these messages through bcm.company-name.org which is the FQDN for the BCM. The BCM's smtp server will now receive the read receipt and clear the MWI immediately once I acknoledge the read receipt.
Problem solved.
Note that you need each individual user's "Original Message" setting in their Message Forwarding configuration of Mailbox Manager set to "Mark As Read When Opened By Recipient." And you need your company's SMTP server programmed into CallPilot Manager under "System Properties." I chose to leave the "From" email address field clear. Finally, make sure your DNS records are solid and that you have your IP subsystem settings correct in Element Manager. It's a necessary step but not always sufficient.
Hope this helps someone else in my situation.
