Failing to start instance of Email Listener (without configuration for Sender in Email Account)
For my use case I'm trying to have an Email Listener without handling any outbound emails (in other words, in the Email Account rule, Receiver configured and Sender left blank). In the rule section for the Email Account, these values are not required. The rule can be saved without mapping the sender values. This works as expected.
However, when restarting the Email Listener in Admin Studio, the following error is triggered: "Start operation failed for CSEmailAccount (Failed to launch listener, java.lang.IllegalArgumentException: Provided email account instance do not have sender details configured)."
Clear and easy to fix. But the interesting part is that after the sender details have been configured and the Email Listener is succesfully up and running again, I am free to retroactively remove the Sender and have the Email Listener still work as I would expect it to - handling the receiving of emails exclusively.
Since these rules allow room for this workaround, I'm starting to wonder whether I'm facing a bug somewhere in these series of actions.
Found this thread which essentially asks the same question, but unfortunately without an answer: https://support.pega.com/question/email-listener-doesnt-start
Accepted Solution
Updated: 7 Mar 2024 6:53 EST
Proximus
BE
Hello,
It makes sense that Sender is required.
Your listener is defined against an email account and it sounds technically logic that an email account should be properly set up to send email.
Changes you mention are done in mailbox definition (sender/receiver) while process running is the listener, connected to the mailbox.
Technically, the process which runs won't re-validate any change in the mailbox since validations have been done at startup.
Your listener will then just fail if it looks for some info which is no more available.
At next restart it will fail also.
More or less same "non-issue" with a node level DP. You can delete the rule while the data page in is memory.
It will work until refresh is needed
Regards
Anthony
Pegasystems Inc.
GB
@BKaan please log a support issue via the MSP if you can replicate the issue consistently.
Based on the information provided, it seems like you've encountered a behavior where the Email Listener requires sender details to start, but continues to function without them once started. This could be due to the initial validation checks performed when starting the listener. However, once the listener is running, these checks may not be performed again, allowing the listener to continue functioning even after the sender details are removed. If this behavior is causing issues or if you believe it's a bug, I recommend raising a support request with Pega for further investigation.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
More about MQ Listener data instances > Listener restart after service rule chang
Please provide the INC id here so that we can help track it.
Accepted Solution
Updated: 7 Mar 2024 6:53 EST
Proximus
BE
Hello,
It makes sense that Sender is required.
Your listener is defined against an email account and it sounds technically logic that an email account should be properly set up to send email.
Changes you mention are done in mailbox definition (sender/receiver) while process running is the listener, connected to the mailbox.
Technically, the process which runs won't re-validate any change in the mailbox since validations have been done at startup.
Your listener will then just fail if it looks for some info which is no more available.
At next restart it will fail also.
More or less same "non-issue" with a node level DP. You can delete the rule while the data page in is memory.
It will work until refresh is needed
Regards
Anthony