|
First, the "AS/400-native" applications. The problem was that the 400 couldn't do domain-name resolutions. It turned out that was a firewall problem; when the port the 400 was trying to use for DNS resolutions (evidently not what the WinDoze boxes are using) was opened up, we could immediately start sending email through the native SMTP.
Then there's the JavaMail application. As it turned out, I was making a wrong assumption: I'd forgotten that I'd made a jar, and (seeing the classes just sitting in an IFS directory) thought it was running from loose class files. THAT's why nothing I did was having any effect. Once I started making jars with each test revision, the exceptions started to change, and when I got it identifying itself properly to the server (I didn't know you had to set another property to have it do that!), it started working.
As to the bounce messages involving the native SMTP, they turned out to be red herrings, evidently from some native application test I'd forgotten about.
Thanks to everybody who helped with this. -- JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
