This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM has previously requested more clarifying information. Because the additional information was not provided within 30 days, the request has been closed.
I tried on 7.2 system, the sender email address is converted to lower case even the characters of domain name are upper case in the wrknamsmtp.
So, when the email is sent out by SNDSMTPEMM, the characters of sender email address are all lower case. But if the email is sent by SNDDST, the sender address is something like abc@DOMAIN.COM. I think, it is not described accurately about the sender address in the page https://www.ibm.com/support/pages/lowercase-e-mail-addresses .
This is also true for email system with *SDD diretory type since 7.2.
Hope this can help to address your business needs.
Thanks for your comments. I agree that moving to the new *SMTP support, would satisfy my requirements given the better support of RFC. Due to the SDD solution currently being used in many legacy programs, it will however require significant development efforts to migrate to the *SMTP solution, but I will leave it to your assessment whether mixed case should be also supported by the *SDD implementation - probably depending on the development costs involved.
This limitation applies to the SMTP server with directory type *SDD. Since v7r2m0, IBM i added directory type *SMTP, which follows RFC more strictly. And the email address can be lower case. Api QtmmSendMail and CL SNDSMTPEMM can be used to send emails from IBM i system to other email servers. SNDDST also works with some limitation, such as only long message can be sent out to smtp server outside.
IBM i alsp provides a tool STRIMPSMTP to enroll SDD users to SMTP. For more information, please refer to knowledge center, such as https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzair/rzaircrtup.htm .
Does this satisfy your requirements?
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Networking
Operating system - IBM i
Source - COMMON
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Work Management and Messaging
Operating system - IBM i
Source - COMMON
The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. Although there are commercial alternatives and potential to do it as a wrapper, it seems like this would not be hard to implement, and e-mails do need to be able to be sent in mixed case.
Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.
For more information about CAAC, see www.common.org/caac
For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/
Nancy Uthke-Schmucki - CAAC Program Manager
The COMMON Europe Advisory Council (CEAC) has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed.
Background: The CEAC members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.
To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT
Therese Eaton – CEAC Program Manager, IBM
Have a look at the QtmmSendMail API.
You can find several (commercial) implementations of it on internet.