I have successfully sent email using the command SNDSMTPEMM.

I had to work to get to understand that at least in my shop I had to use the CHGSMTPA command.

The MAILROUTER() parameter and the FWDHUBSVR() parameter had to be the same, to point to our local network's Internet Exchange server DNS.

With the SNDSMTPEMM command, another thing was the CHARSET() parameter. When I create the CSV file in the IFS, I create it usually with the CCSID = 1252, a Windows standard. That's so some of the users can get it "as is" from the file share directory we set up, since that's where they're using these files.

So first times using the SNDSMTPEMM command with the attachment I used CHARSET( *WINDOWS_1252 ). But that got me some funny characters in the Inbox attachment when opening the email. Since it was already CCSID = 1252, I changed the parameter to CHARSET(*BIN).

That worked.

Gonna upgrade my TCPIP skills.

Confidentiality Notice: This email may contain confidential information or information covered under the Privacy Act, 5 USC 552(a), and/or the Health Insurance Portability and Accountability Act (PL 104-191) and its various implementing regulations and must be protected in accordance with those provisions. It contains information that is legally privileged, confidential or otherwise protected from use or disclosure. This e-mail message, including any attachments, is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Thank you.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].