HomeHomeSupportSupportFeedback Design...Feedback Design...There is a problem with the configuration of your SMTP Server. Mail was not sent. There is a problem with the configuration of your SMTP Server. Mail was not sent.
New Post
4/23/2010 7:43 PM
Hi guys,
Getting this error (before and after upgrading to latest version) however, I can send email fine through the core feedback module fine - plus running eTailer which is emailing fine.
Any hints?
New Post
4/24/2010 12:06 PM
Sending email tests from the host settings is not a true test as it is likely on the same server and not requiring authentication.
DNN SMTP settings
DNN Websites have the ability to configure in the host settings an SMTP server. When a DNN email is generated from the DNN website, it will attempt to send mail through this SMTP server.

In order that your DNN website can successfully send the email, the SMTP server must allow the email message to be received. Typically this is done in one of four ways.
  1. The SMTP server is configured for Open Relay (This should NEVER be done unless you have an external firewall blocking all external SMTP connections. Otherwise your mail server will become a spam server within hours)
  2. SMTP Authentication – Typically SMTP servers are configured to allow users with a valid username and password to authenticate themselves. Once they have been authenticated, they can communicate email messages through the SMTP server. This is the same way most ISP’s work their mail servers. The idea is that only users who are customers of the ISP will allow email to be sent from their SMTP servers.
  3. Selective Open Relay. The administrator of the SMTP server can also allow Open Relay (same as 1 above) from selective IP addresses. Any communication from an IP address that is configured to allow open relay will be accepted by the SMTP server.
  4. Local Host – If your website has it’s own SMTP server configured, typically it will allow email message to be sent form it’s self.
To correctly configure your DNN SMTP settings, you need to understand what method of communication has been configured in the SMTP server you are trying to set DNN to access.
Here is the process you would configure from above.
  1. Enter the IP address or valid domain name for the SMTP server, nothing more to do if open relay is allowed. (Still not recommended)
  2. Enter the IP address or valid domain name for the SMTP server, and the valid user name and password as would be used to communicate with the SMTP server. This is where you get to use the user name and password setting in DNN.
  3. Ensure that the SMTP administrator has allowed the IP address your DNN website uses to have open relay status. Then just enter the IP address or domain name of the SMTP server in your DNN host settings.
  4. Configure your DNN host settings to have “localhost” in the DNN SMTP server settings are.

There can be some issues that get confusing with the different methods.
  1. Open relay mail servers will be attacked by spammers very quickly. They are always on the lookout for mail servers that they can abuse. It is never recommended to have your mail server on the internet and in open relay. Additionally your mail server will be blacklisted by other mail servers if found to be in open relay.
  2. SMTP Authentication  can still be restricted to certain IP addresses. Many ISP’s will allow you only to use their mail servers while you are a client of their AND connecting to their mail server from an IP address they own. So thing will work in your Email applications while you are connecting to the internet via their dialup or high speed connection, but as soon as you move away from a connection provided by them, you will not be allows to connect to their servers, let alone Authenticate.
  3. Even if your ISP has allowed relay from the address that your mail server is run form, there may be a firewall or block on the normal port that the SMTP servers are typically configured to use. Port 25. If a firewall exists between your web server and the mail server, it must be configured to allow traffic over port 25.
  4. You may have web server configured with an SMTP server on the same system. Yet have it be blocked over port 25 for outbound communications. Some ISP’s block port 25 to curb the flow of virus email messages. You need to be sure that your ISP that provides connection to the internet for your web and SMTP server is not blocking port 25.
How to get really confused.

Often mail servers will allow you to send email messages to email addresses on that SMTP server, even though they do not allow you to send mail out. So if you have a web application configured to send email to yourself, and the SMTP settings you use in the DNN host settings are for the SMTP server that runs the same email address you will have success.
Yet when you change the email address in the web application, you can no longer send email, and the web application appears to fail. This is still an SMTP configuration error on your website. You will need to find a method above to solve the issue. 
New Post
4/25/2010 9:34 AM
Thanks for that, but like I said, the core feedback module is working and sending email, so is the 3rd party eTailer module. So I can assume that the SMTP settings are correct and working?
New Post
4/25/2010 9:39 PM
No, if the core module is sending to an email address hosted on the same server, it does not require authentication. So it may not be correct, but only shows now.
New Post
4/26/2010 8:59 AM
It has basic SMTP auth setup for an email account on the server.
All other modules appear to be sending emails without issue.
New Post
4/26/2010 12:47 PM
Please contact us through the contact us from on this site, make reference to this post and provide HOST login details and SMTP authentication details. We will take a look.
You should alos double check your settings are we have many Feedback Designers being used by people, and the only problems like this have only been related to SMTP settings.
New Post
4/27/2010 12:10 PM
Ive just spoken with PowerDNN (the hosts) and their reply is..
I have investigated the cause of your issue and the problem that you are having is caused by a misconfiguration in the module's mail settings.  When it sends, it is trying to send email from the user's email address and not the email address specified under the DotNetnuke host settings.  In order for the mail sending to work correctly, you will need to configure the module to send using the same username that is specified in the DotNetNuke HOST settings."
Am I able to specify an email address for the sender of the email?
New Post
4/27/2010 5:10 PM
This is not actually a miss configuration of the module, but is by design. When an email arrives in your inbox, and you reply, there is no point in having the reply go to the site admin. So the messsages are sent with the "from" address of the user who sent them.  Naturally.
In order for this to work, you only need a valid SMTP server that alllows either open relay (NOT recommended unless protected from the net)
Allso relay from certain IP addresses, and your website IP is enabled.
Allows relay with sucessful authentication (basic authentication normally)
If your host does not allow relay with Authentication (most unusual) then you should probably use a third party SMTP server, like gmail, hotmail, ymail, or your local ISP. All of these SMTP servers and every host company we have ever heard of will allow Authenticated SMTP relay. Some have limits like no more than 400 a day (gmail). but they alll allow it.
If could well be that power DNN allows it too, but the user name and pass being used is wrong, and this is tricking you into thinking that they only allow local delivery.
As for filtering to allow SEND FROM to only be an address hosted by Power DNN. That would be most unusual too, and is likely some Unix security guy getting all excited about what he learned at university. The realy world allows authenticated relay... just ask Microsoft or Google!
HomeHomeSupportSupportFeedback Design...Feedback Design...There is a problem with the configuration of your SMTP Server. Mail was not sent. There is a problem with the configuration of your SMTP Server. Mail was not sent.