NetTalk Central

Author Topic: Settings.ini vs embed in NT6/SecWin6 app  (Read 2661 times)

jking

  • Sr. Member
  • ****
  • Posts: 419
    • View Profile
    • Email
Settings.ini vs embed in NT6/SecWin6 app
« on: January 15, 2012, 01:30:57 PM »
I'm still struggling to get email notification to work in my NT6/SW6 app.  I have been working with the web51 example and actually got it to say it sent a password to my email account but nothing ever came through.  I have checked my spam filter.

I have set EmailServer, Port, EmailFrom and hostaddress in the settings.ini file.  These are duplicated in the SendEmail procedure Accepted embed (except the host address).  I deleted the dssw5.tps file and got the message that I was adding a new user with supervisor level access when I tried the Create a Login tab.  It also gave a message about sending the password to the email address given.  Nothing has come to my email account.  The new user does appear in the secwin_operators.tps file, but i cannot use it to log in since I don't have the password.  When I try to add more new users I get the message "This user could not be added".  I can't get any further.  This is a C8 ABC app with NT6.14 and SW 6.03.

Thanks,

Jeff King

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: Settings.ini vs embed in NT6/SecWin6 app
« Reply #1 on: January 15, 2012, 09:20:02 PM »
There are a variety of reasons email does not arrive;

a) it's simply filtered out somewhere along the line. Usually it's best to test with a local server, one you control, to determine what is the "sending side" and what is the "server side".

b) Some servers require, or prefer, you to log on before _sending_ mail. The send mail object has properties for this, if you have them, and your server will accept them, then it's a good idea to send them.

When in doubt use the _trace method to send the conversation between the client and the server to debugview. Adding calls to ._trace in the SEND and PROCESS methods in the SendEmail object is the way to do this.

cheers
Bruce