Bruce, I'm a Network Administrator for a company in the Midwest. I'm having an issue where emails sent via n_cpp_smtp are not triggering a non-delivery report when sent to an invalid recipient. I can telnet to the mail server on 25 and manually send an email using mail from:, rcpt to:, etc, and trigger the NDR, so I'm sort of at a loss. Can you shed any light on why this might occur when using PB to send mail? One would assume PB uses the same SMTP commands that I'm using when telneting to the mail server.
Hi Bruce, The pbnismtp105.pbx works great from PowerBuilder and the deployed application when it runs on a workstation with PowerBuilder 12.5 installed, but when one of our test PC runs our application we get a bad runtime function reference when the instanciated n_cpp_smtp object is referenced. My thoughts are we are missing deployment file(s). Am I correct? If so, can you tell me what we are missing.
You are deploying the pbx with your app, correct? Also, it's dependent on the openssl libraries (libeay32, ssleay32). You might want to use Dependency Walker on the machine you are deploying to in order to verify all the required files are available.
PBNISMTP is a wrapper around the CPJNSMTPConnection library (http://www.naughter.com/smtp.html). It appears there is an issue in that library prior to their v3.41 update in September of 2020 that would throw errors on Windows version earlier than Windows 8. The version I have available is based on v3.28, and so experiences the error.
Fortunately, the version of the library tha Roland Smith maintains (https://www.topwizprogramming.com/pbnismtp.html) has been updated to v3.45 (the latest available). If you switch to that version of PBNISMTP, you should not experience the error.
14 comments:
Bruce, I'm a Network Administrator for a company in the Midwest. I'm having an issue where emails sent via n_cpp_smtp are not triggering a non-delivery report when sent to an invalid recipient. I can telnet to the mail server on 25 and manually send an email using mail from:, rcpt to:, etc, and trigger the NDR, so I'm sort of at a loss. Can you shed any light on why this might occur when using PB to send mail? One would assume PB uses the same SMTP commands that I'm using when telneting to the mail server.
Hi Bruce,
The pbnismtp105.pbx works great from PowerBuilder and the deployed application when it runs on a workstation with PowerBuilder 12.5 installed, but when one of our test PC runs our application we get a bad runtime function reference when the instanciated n_cpp_smtp object is referenced. My thoughts are we are missing deployment file(s). Am I correct? If so, can you tell me what we are missing.
Thank-you,
John
You are deploying the pbx with your app, correct? Also, it's dependent on the openssl libraries (libeay32, ssleay32). You might want to use Dependency Walker on the machine you are deploying to in order to verify all the required files are available.
Hi Bruce,
I was wondering if the pbnismtp125.pbx needs to be updated for 12.5.1? It seems to work properly but I just wanted to make sure.
Thanks,
Chris
No, it shouldn't need updating. Should work fine as is.
OK - Thanks Bruce.
Hi Bruce, is there any chance to get the mail sending error as a text, not as a message box?
There's some functions in the object that toggle the messageboxes on and off. They're only meant for debugging.
dear sir.
what 's your email address.
i need your help, about powerbuilder ,data from json to datawindow
I suggest you post your questions in the Appeon PowerBuilder forum, and then myself and a number of other people can look at it and respond there.
https://community.appeon.com/home
estimado Bruce consulto , hay alguna limitante con el uso del objeto n_cpp_smtp, en sistema operativo windows 7?
Not that I'm aware of. It should work fine on Windows 7.
ayudame por favor , cuando intento implementar en equipos que coincidentemente que tienen windows7 me devuelve, error -5, marcas no validas
PBNISMTP is a wrapper around the CPJNSMTPConnection library (http://www.naughter.com/smtp.html). It appears there is an issue in that library prior to their v3.41 update in September of 2020 that would throw errors on Windows version earlier than Windows 8. The version I have available is based on v3.28, and so experiences the error.
Fortunately, the version of the library tha Roland Smith maintains (https://www.topwizprogramming.com/pbnismtp.html) has been updated to v3.45 (the latest available). If you switch to that version of PBNISMTP, you should not experience the error.
Post a Comment