You searched for the word(s): userid:282164

More Search Options

RSS Available

• Re: DNS names planning

  And on this topic, I wonder what the general consensus is about the .local suffix? My Active Directory name is "mydomain.local" because, when I installed Server 2003 for the very first time and promoted it to a Domain Controller I had to provide a domain name...and I simply typed "mydomain" and Windows appended the ".local" suffix automatically. Is the ".local" suffix common? Is it good practice? Regards

  Posted to Microsoft Solution for Hosted Exchange (Forum) by sabine on 1/27/2007
  Filed under: .local

• Re: How to specify SMTP server port under Host Settings

  Hi Arie, Yes your questions are definately related to this discussion. Unfortunately, I think that the only solutions available to you are: a) either modify the DNN core code to support SSL on a non-standard port using CDO, b) or to modify the core code to support ASP.NetMail (which presumably supports SLL on a non-standard port). Using ASP.NetMail doesn't really solve any problems though. CDO is excellent (and already part of DNN's code) so I'd probably suggest option 'A' above. c) or to move DNN

  Posted to Core Framework (Forum) by sabine on 10/5/2005

• Re: How to specify SMTP server port under Host Settings

  Hi Jeff, Point well taken. I'll be back in a few days (or weeks) to tell this thread how things go. I have one issue to resolve in my DNS configuration, then I'll be installing Mail Enable and -- with all this discussion in mind -- I'm hopeful that the most logical solutions will present themselves. Ultimately, if I install Mail Enable and have it listening at port 25 and DNN doesn't choke, then perhaps your recent post presents the wisest option. I'll let you know how it all turns out. Many thanks

  Posted to Core Framework (Forum) by sabine on 9/18/2005

• Re: How to specify SMTP server port under Host Settings

  Hi Jeff Currently, the SMTP Server Name in DNN is "127.0.0.1". MailEnable will handle relaying from the IIS SMTP -- the recommendation from Mail Enable's forums is to smarthost all IIS SMTP messages to the Mail Enable SMTP. (So actually, I guess IIS isn't 'relaying' to Mail Enable at all but rather the messages are passed from one service to the other directly -- have I understood this correctly?) Mail Enable will handle relaying from "localhost" or 127.0.0.1. I believe you're right that I'll have

  Posted to Core Framework (Forum) by sabine on 9/18/2005

• Re: How to specify SMTP server port under Host Settings

  Hello Nina, Jeff, Non-DNN sites on my server are written either in asp.net or classic asp (the majority). Yes, many have email forms or user registration and are driven by databases. All of the non-DNN sites (about 15) I will modify to use CDOSYS on port 26 (or 587 - I haven't really decided yet but I've been using port 26 in this discussion as my example). They won't be adversely effected at all if I move the IIS SMTP to a non-standard port and install the more robust MailEnable SMTP in its place

  Posted to Core Framework (Forum) by sabine on 9/15/2005

• Re: How to specify SMTP server port under Host Settings

  Hi Jeff, Hmm.... so by doing as you suggest, I should expect that DNN will communicate directly with which one of the SMTP services? The IIS SMTP service (on a non-standard port) or the other one (at port 25)? Here's where I get confused...as I've said, on my server it appears that DNN's email service stops working and I get a CDO.Message error if I set the IIS STMP service inbound to a non-standard port. This makes me believe that CDO defaults to cdoSendUsingPort(25) rather than cdoSendUsingPickup

  Posted to Core Framework (Forum) by sabine on 9/13/2005

• Re: How to specify SMTP server port under Host Settings

  Okay, perhaps we need to get to the bottom of this. I've grabbed the relevant code from "Globals.vb". Public Function SendMail(ByVal MailFrom As String, ByVal MailTo As String, ByVal Cc As String, ByVal Bcc As String, ByVal Priority As MailPriority, ByVal Subject As String, ByVal BodyFormat As MailFormat, ByVal BodyEncoding As System.Text.Encoding, ByVal Body As String, ByVal Attachment As String, ByVal SMTPServer As String, ByVal SMTPAuthentication As String, ByVal SMTPUsername As String, ByVal

  Posted to Core Framework (Forum) by sabine on 9/13/2005

• Re: SMTP

  I too have been having difficulty with DotNetNuke's SMTP settings. So, if you're using DNN 2 you should have three available settings. (sorry I'm not looking at the Host Settings page right now so the terminology in DNN might be different than I've written here.) SMTP Server: - I use either the word "localhost" or the address "127.0.0.1" (which is the IP address of the localhost!) Both of these work in my installation. - If these do not work in your installation then you'll need to find out from

  Posted to Core Framework (Forum) by sabine on 9/13/2005

• Re: 8 Modest Suggestions from a frustrated user since 1.0

  Hello Wendy, I hope that you've received some helpful advice on this topic and are better prepared than you were before asking your initial question. Hello all, I'd like to comment, not about the issues she raised, but about the way that her comments were received by the other members of this forum. Let's reflect upon the responses she received: codegalaxy began by telling wendyb she was wrong. DNN 'is' fast enough; that the 'skinning engine IS great and easy to use; then intimated that she should

  Posted to DotNetNuke (Forum) by sabine on 9/12/2005

• Re: How to specify SMTP server port under Host Settings

  As suggested, I've entered this issue into Gemini. http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=1901 Fingers crossed.

  Posted to Core Framework (Forum) by sabine on 9/12/2005