>Can i use WWIPSTUFF on VFP6 to send authenticated email?
>Does Base64Encode (for VFP6) require MSXML3 ?
I verified that wwIPStuff works with Verizon on both VFP 8 and 6 with a login thanks to the logins you sent me to work with.
There is a bug in the VFP 6 code though.
#IF wwVFPVersion < 7
lcUsername = IIF(!EMPTY(this.cUsername),this.Base64encode(THIS.cUsername),"" )
lcpassword = IIF(!EMPTY(this.cPassword),this.Base64encode(THIS.cPassword),"" )
#ELSE
lcUsername = IIF(!EMPTY(this.cUsername),STRCONV(THIS.cUsername,13),"")
lcpassword = IIF(!EMPTY(this.cPassword),STRCONV(This.cPassword,13),"")
#ENDIF
the empty strings were missing for some reason in the IIF() clause.
You do need MSXML 3 if you use authentication with VFP 6 to provide the Base64 encoding.
Make sure you recompile all the classes if you're using VFP 6... the code is compiled for VFP 8 by default and if you don't recompile it runs the 8.0 code which will fail on 6.
Chris, time to upgrade to VFP 8... <g>
+++ Rick ---
>
>>Chris and Larry,
>>
>>>Can u post the sample code u are using to send authenticated email w/ WWIPstuff? What is the version/date of WWIPstuff?
>>>
>>>I am having the same problem and am getting nowhere.
>>>
>>>thanks.
>>
>>For authentication all you should need to do is fill in the cUsername and cPassword properties.
>>
>>Several people have reported problems with Verizon's SMTP server - specifically the authentication. It appears Verizon is doing something non-standard with their auth, but I can't really check it out since I don't have an account with them.
>>
>>OTOH, Verizon is the only provider that I've heard problems about with SMTP so I suspect it's something in their protocol handling. It is possible that they don't support basic auth or have it disabled so that hte login fails.
>>
>>What is the error message you get? Is it a login error or what?
>>
>>If anybody wants to pass me account info temporarily I'll take a look at it. Send me private email if you want to do this...
>>
>>+++ Rick ---
>>
>>
>>>
>>>
>>>>Here's the fix that worked for me:
>>>>
>>>>Turns out, I was using an older version of wwIpstuff.dll (file dated 20-Jan-02) which I had restored from a backup disk after a hard drive problem. Once I upgraded to the newer version (file dated 5-Dec-02), sendmail() worked fine with authentication, and I did not need to mess with making a pop connection first.
>>>>
>>>>FYI. I was put on the right track by a message I found in the West-Wind message board: "Make sure you are using the appropriate wwIPStuff.dll. If you have upgraded from a prior version, you might not be using the right .DLL. Double-check it. Then triple-check it." - Guy Pardoe
>>>>
>>>>Thanks Guy!
>>>>
>>>>- Larry
>>>>
>>>>
>>>>
>>>>[original post]:
>>>>I'm using wwIPstuff’s sendmail()from a VFP app. This has worked fine until I changed my email provider from Earthlink to Verizon. Testing with my email client and talking to Verizon I verified that Verizon requires authentication whereas Earthlink does not. So I added the cUsername and cPassword properties (plus, of course, the new cMailServer property) for Verizon, but sendmail() still failed - giving a 'relay' error. I've read the relevant UT threads on this, plus Rick Strahl's Wiki post (
http://www.west-wind.com/wiki/kb.wiki?wc~EmailRelayingDenied), but am still having problems.
>>>>
>>>>(a) If I must make a POP3 connection first, how would I best do this and can this be done using wwIPstuff? Would I be making a pop3 connection to the smtp server?
>>>>
>>>>(b) Is it possible that wwIPstuff's sendmail() simply won't work with the Verizon mail server?
>>>>
>>>>Thanks!
>>>>- Larry
