Our situation is thus:
1. We have *one* virtual dedicated server
2. We are running *two* applications over it in ASP.Net
3. Each application is running over a separate IP and a separate domain name
Let us call the applications: abc.com andn xyz.com
4. We have created reverse pointers to the domain names to the respective IP addresses.
5. Each application needs to send the regular emails to the users (password reset, updates, etc)
6. We do not expect any incoming email on either domains.
7. We have one email server running - MailEnable which is currently using the IP of abc.com and that domain to send email
However, MailEnable does not support sending email over multiple IPs and domains - nor do a lot other email servers that we checked.
The problem which happens is that when we try sending emails from xyz.com, they go through the IP mapped to abc.com. This creates some problems with being able to create strong SPF records and thus a lot of mail might end up in SPAM. (It already does on Hotmail and a couple of other servers, bounce of the email)
What is the best practice to do this?
As in how do other multiple websites running on the same server fix this? In our research, we figured that the multiple outbound email sending is not supported by many servers - even though it is a much requested feature.
One way that we thought off was to get another IP and a Domain name - say - abcemail.com - and send mails for both applications via this. However, I would just like to find out whether this is actually a good practice - and if not, what are our other alternatives?
Thanks.
Start Free Trial