What attribute is actually getting passed into the parameter of the Decrypt subflow?
As an aside, for the Decrypt java action. Set the prefix to empty. The prefix is only needed for encrypting.
This is assuming an actual encrypted value is getting passed into the microflow. If there isnt an encrypted value to decrypt, you would have to check the $emailsettings object again. The EmailAccount object gets used in this case (but named Emailsettings) and that uses the password. Breakpoint the decrypt flow; see if the password going in starts with AES. If so, you have an encrypted password. Then check if it works with the above settings.
If not sure: breakpoint the saving of the emailaccount object and see what happens there.
Thanks for asking your question on the forum and adding your additional research. A few notes which might help you:
- You noticed that the EmailSettings object is empty. This is indeed required to send an e-mail. Did you use the Administration snippet provided by the module? When navigating to this snippet/page, you can see that the DS microflow will create the settings object for you. When configured correctly (with the correct SMTP details), you should be able to use it.
- Did you consider migrating to the new Email Connector? The module you're using will be deprecated when moving to Mendix 10. The new module will be supported in a more decent way; https://marketplace.mendix.com/link/component/120739