Hi Lee,
I've already watched the videos suggested in other threads for SMTP configuration and have been setting up SMTP server for years. I have it sending emails just fine.
My problem is similar to the question posted in this thread
http://www.dnncreative.com/Forum/ta....aspx#7865
The way I use DNN is as such, I have my primary portal I consider HOST and then portals I create for all my clients. Each client however now wants emails to be sent from different email accounts (support@company1.com or sales@company999.com). Right now DNN only allows configuration for one SMTP server and thus sends all email from the same account.
My primary email server for HOST is Gmail, however it will not allow for domain alaising. So I can setup a locall SMTP service on the server and configure domain alaising for these other domains (company1.com company999.com) but that is a very poor solution.
The reason is because more and more the receiving SMTP server of an email delivery is using reverse DNS lookup to verify that the sender is really authorized to send mail from that domain. Yahoo is a big one on this. When an email is sent to Yahoo from support@company1.com, Yahoo does a reverse DNS lookup on the IP address of the sending SMTP server. If it does not match the domain name of the sender email address, it will refuse the mail. This is to keep spammers from delivering email to servers from domains they are not registered to send from. So the IP address of my SMTP server is my domain, so mail sent to Yahoo will get bounced. And of course will will never know this unless you check the logs.
So, yes, I can use domain alaising so my SMTP server will send email from the admin account for each portal, but it is really not a good solution because more and more major email services are requiring reverse IP DNS lookup for delivery. In fact I noticed that SmarterMail has added the option to their email server but disabled it by default.
Actually domain alaising would not even solve my problem completely. The reason is that the admin for say company1.com uses an email address of joe.smith@company1.com (that is the configuration in the admin account for their portal). However, when a new user signs up for that portal, company1 wants the welcome email to be send from support@company1.com and not joe.smith@company1.com. There is no where to specify this alternative email address. The same is true for lost passwords, it would be nice to configure a noreply@company1.com.
Does all this make sense?
So there are two solutions.
1. DNN can realize this issue and allow for SMTP settings to be configured on a PER PORTAL BASIS. I'm not sure why they have not done this already.
2. Create a new DNN installation for each of my companies. This will allow me to specify for each portal (in the HOST settings) the REAL companies SMTP server which has authority to send email from that domain. This is the correct method, but terrible in terms of multiple DNN installations.
Thanks for listening and I appreciate any input.
Paul