Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Verification emails not being receivedVerification emails not being received
Previous
 
Next
New Post
9/23/2006 5:04 PM
 

Hi

I'm not getting any verification code emails sent from my portal, nor password reminders.

The actual error is:

Mailbox unavailable. The server response was: not local host <dom.com>, not a gateway

i.e. I cant send to any mailbox outside of the current domain, as the smtp server wont act as a relay (see expanded err msg below)

Any ideas how i can get around this problem? My ISP requires smtp authentication

cheers in advance

ian

 

 

AssemblyVersion: 04.03.04
PortalID: 3
PortalName: The Landlords Club
UserID: -1
UserName:
ActiveTabID: 70
ActiveTabName: Home
RawURL: /llcforum/Home/tabid/70/ctl/SendPassword/Default.aspx
AbsoluteURL: /LLCForum/Default.aspx
AbsoluteURLReferrer: http://www.thelandlordsclub.co.uk/llcforum/Home/tabid/70/ctl/SendPassword/Default.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 90fbdb2e-eabc-4377-8633-96d057dfa028
InnerException: Mailbox unavailable. The server response was: not local host tiktaktoe.co.uk, not a gateway
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Net.Mail.SmtpTransport.SendMail
StackTrace:
Message: System.Net.Mail.SmtpFailedRecipientException: Mailbox unavailable. The server response was: not local host tiktaktoe.co.uk, not a gateway at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, SmtpFailedRecipientException& exception) at System.Net.Mail.SmtpClient.Send(MailMessage message) at DotNetNuke.Services.Mail.Mail.SendMail(String MailFrom, String MailTo, String Cc, String Bcc, MailPriority Priority, String Subject, MailFormat BodyFormat, Encoding BodyEncoding, String Body, String Attachment, String SMTPServer, String SMTPAuthentication, String SMTPUsername, String SMTPPassword)
Source:
Server Name: MAXVPS007

 
New Post
9/23/2006 6:33 PM
 

My guess is that your FROM address ( which is the portal admin ) is not a legit address on the SMTP server you are using.  The configuration in the Host Settings for the SMTP Authentication establishes the CONNECTION to the mail server, but once the mail gets there... it is subject to the mail servers rules.  This is where I would look.

Remember that you can create a separate Admin User ( with a proper email address ) and specify them as the "Portal Administrator".  This won't affect your ability to administer the site, but will ensure that a specific email address ( not your personal one ) is used as the FROM address for all portal-sent email.

Cheers,
Scott


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
New Post
9/24/2006 12:29 PM
 

Hi

Thanks, that worked, seeting the admin mail account to be a valid one set in the host settings.

I do have a further question though - given that the host smtp settings are the ones used to specify the mail server, the problem is that all portals I create, no matter what domain name, will have emails coming from the host domain email server.

eg.

my main domain would be www.maindomain.com, plus I'd have a couple of portals for customers, www.customer1.com and www.customer2.com. If I create the setup as indicated, all automatic emails will come from mail@maindomain.com, rather than mail@customer1.com (and so on for all other portals I create) - it would be nice for the emails to come from the portal domain, rather than the host. Any ideas on how I'd overcome this problem, given that my smtp server does not allow relaying, for obvious reasons!

thanks in advance

regards

ian

 
New Post
9/24/2006 9:20 PM
 
goolag2006 wrote

I do have a further question though - given that the host smtp settings are the ones used to specify the mail server, the problem is that all portals I create, no matter what domain name, will have emails coming from the host domain email server.

The "FROM" address on any email sent by a portal is taken from the Portal Administrator specified for the portal.  If the SMTP server you are using requires that outbound email contain a known address in the FROM field, then YES, this is going to be an issue.

The issue can be avoided in a number of procedural ways that don't require an application change:

  • Setup an email address of client@host.com ( and provide routing for replies ).
  • Configure a rule for your clients admin address ( presuming you have some authority on your email server )
  • Utilize separate instances for clients that require it.
  • Provide email services for your client as well ( most reseller accounts include email capability ).
  • + I'm sure there are other suggestions as well.

The case for supporting multiple SMTP servers is as you appropriately identify, multiple clients which don't use the SMTP server you provide.  Such a configuration option ( even under host control ) exposes all of the DNN host, other clients in the instance, and hosting company to potential spam abuse, etc.  This is a request in our enhancement log and is under consideration for an appropriate way to implement... however, as long as their are a number of workarounds ( as indicated above ) it will probably be prioritized accordingly.


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
New Post
10/4/2006 9:30 PM
 

Getting similar error, but the suggestions above don't seem to resolve.  Can you make any other suggestions?

System.Net.Mail.SmtpException: Failure sending mail. ---> System.IO.IOException: Unable to read data from the transport connection: net_io_connectionclosed. at System.Net.Mail.SmtpReplyReaderFactory.ProcessRead(Byte[] buffer, Int32 offset, Int32 read, Boolean readLine) at System.Net.Mail.SmtpReplyReaderFactory.ReadLines(SmtpReplyReader caller, Boolean oneLine) at System.Net.Mail.SmtpReplyReaderFactory.ReadLine(SmtpReplyReader caller) at System.Net.Mail.SmtpReplyReader.ReadLine() at System.Net.Mail.SmtpConnection.GetConnection(String host, Int32 port) at System.Net.Mail.SmtpTransport.GetConnection(String host, Int32 port) at System.Net.Mail.SmtpClient.GetConnection() at System.Net.Mail.SmtpClient.Send(MailMessage message) --- End of inner exception stack trace --- at System.Net.Mail.SmtpClient.Send(MailMessage message) at DotNetNuke.Services.Mail.Mail.SendMail(String MailFrom, String MailTo, String Cc, String Bcc, MailPriority Priority, String Subject, MailFormat BodyFormat, Encoding BodyEncoding, String Body, String Attachment, String SMTPServer, String SMTPAuthentication, String SMTPUsername, String SMTPPassword)

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Verification emails not being receivedVerification emails not being received


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out