Hi to all.

I spent many hours on this problem, trying any kind of SMTP configuration and test.
This is my experience:

I have "two" parent portals,
Host Portal (domain1.com)
Parent Portal (domain2.com)

Configuration a)

Host Email: admin@domain1.com
Host SMPT: smtp.domain1.com
Type: Basic
User: admin
Password: xxxxxx
Parent Portal Admin Email: admin@domain2.com

With this configuration, all work fine for the Host Portal (domain1.com), but if I try to send an email from Parent Portal, I find this error in Mail Server's log file: admin@domain1.com prevented from sending email as admin@domain2.com

Configuration b)
Host Email: admin@domain1.com
Host SMPT: localhost
Type: anonymous
Parent Portal Admin Email: admin@domain2.com
SMTP Server relay: Allow relay from IP 127.0.0.1

With this configuration I not have problem to send mail from both the domains, but with certain mail address like yahoo, hotmail, etc. I receive this error: Sending unsolicited commercial or bulk e-mail to Microsoft or....
It mean that the message is not correctly authenticated.

I have tried any other kinds of settings and authentication, for example:IP in place of localhost, basic authentication to the SMTP; but with the same result.

I think that, the only way that all can works fine, would be that each portal could send email with its own SMTP authentication: domain1.com with smpt.domain1.com, domain2.com with smtp.domain2.com and so on...

This mean Core modifications...

Let me know yours opinions and or suggestions.

Please, excuse me for my trivial english.

Manzoni Fausto

I have noted that emails generated from DNN sites to a hotmail address often end up in the 'junk email' folder and are then also often missed by the person expecting to see a verification code in the inbox.

This is a response from the receiving domain, Yahoo or whomever.  It has nothing to do with authentication, and the fact that you got this messge means authentication is working.

Your problem might be that the sending domain and the domain in the email header don't match, but that shouldn't be an issue if your DNS correctly maps each domain back to the same server for a MX record and the reverse DNS resolves correctly.  Yahoo, Hotmail and several others have gotten extremely tight on SPAM and even if you do get past the filters you may get a response that you have to approve the message by replying to a message they sent.  You can either manually look for these or instruct your users to add your domain to their allowed domains list, but neitehr is fool proof.

Jeff