We use mDaemon in exactly this way with Exchange 5.5
We do this for 3 main reasons -
1. mDaemon strips attachments for us (.bat, .exe, .com, .pif, etc, etc)
2. mDaemon goes out and retrieves mail from a POP3 account we have (no need for MX records, static IP, perm. connect etc)
3. We used to...
Think I am right in saying only if you use your existing mail server as a staging post for mDaemon. i.e. Get your existing system to place all test users mail into a single POP3 account then get mdaemon to open that account. Hope that makes sense.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.