We have a Windows Server 2003 installation with multiple SMTP Virtual Servers (using IIS, not Exchange). Each SMTP Virtual Server is bound to a unique public IP Address. This system works just fine for incoming mail.
However, our problem is that for outgoing mail, the IIS / Windows uses ONLY the primary IP Address that is associated with the NIC (this is a known limitation).
We need someone to develop a solution to get around this limitation and force each SMTP Virtual Server to use the unique IP Address for Outbound mail as well as incoming.
Some possible solutions that we have considered:
- SMTP Event Sink
- SMTP Proxy
- Third party software
- Custom Development (Any code should be in C#.NET)
Please provide a brief synopsis of what you would do to solve the problem, as well as your timeline to complete it.
Please do your own research before bidding. This issue does not have a 'cut & paste' solution, so we need someone with some common sense and expertise.
Have you considered running an actual SMTP server instead of the SMTP virtual servers ?
Something like Mdaemon (commercial, with all features) or Hmailserver (Open source, with basic features) will solve your issue and give you a real SMTP (and pop3/imap as well) server that you can bind IP/Domain wise.
Hello
What you need to do is you the host file to create IP relays and then manual routes that you want for Mail routing this can be done with the Route ADD command on windows. If they is an internal IP that you are using then the internal IP should be able to multicast the IP to the specific domain I am assuming that Virtual SMTP server has a domain name. Let me know what you think