Question
Capgemini
SE
Last activity: 21 Nov 2023 10:54 EST
EMail Listener Service sporadically not getting triggered and blank reply mails getting triggered to the sender
Sporadically Email listener service is not getting triggered while the listener runs and the sender of the mail to the Listener Mail Box gets a blank Reply mail without any details.
The response configuration of the service itself is stopped in our scenario and ideally there should not be any response mail triggered by the service. Also on tracing the Listener runtime, there is no trace of the Service and its underlying activity getting triggered at times. This scenario is happening sometimes during the Email listener execution, and other times the same mail content is processed successfully and the service is also running
Can anybody suggest what can be the underlying root cause for Email listener Service itself not getting triggered sometimes and working fine in other times. Has it something to do with the Node on which it is configured to execute ?? Please suggest any analytical steps other than tracing for getting an RCA for this scenario,.
Thanks in advance.
Proximus
BE
Hello,
How many nodes have this listener running? Are all nodes able to properly connect to the mail server?
"the sender of the mail to the Listener Mail Box gets a blank Reply mail without any details" and "response configuration of the service itself is stopped": Are you sure that the blank reply is well sent by your application. This can also come from email server.
If it works from time to time, check on which server it works. Then I would suggest to have only one listener instances running at a time so that you can validate each of your servers.
You can also connect directly on each server and perform an email account test connection from each of them. You'll see if they're all well connected.
If you use a a variable/datapage for any of your parameters, make sure that it's well loaded on any of these servers. For testing this you could also hardcode any of your values.
This should already give a view on the technical path from all servers to email account. Then, you should also ideally make a technical connectivity check between your servers & all email servers since I guess it's not a single one.
Regards
Anthony
Capgemini
SE
Hi @Anthony_Gourtay thank you so much for your response !!
Answering to your questions:
1) Are you sure that the blank reply is well sent by your application? The answer is - I am very sure that the response is not getting triggered from the EMail Service Response since we have not configured any response mailer to the sender from Service level.
2) How many nodes have this listener running? - In our current test environment, We are running on one Node, which is a shared node for browser/end user level requestors as well as used for background processing of all our listeners, etc.
3) Are all nodes able to properly connect to the mail server? - Mostly yes, because our Listener is working fine in most cases except for certain timestamps when its failing to execute the Service and underlying activity logic, etc.
4) Are you sure that the blank reply is well sent by your application. This can also come from email server. - We are also suspecting that its coming from email server, but how to confirm this can you please guide.
Thanks in advance...
Proximus
BE
What you can try:
- Stop the listener. Push a message to this email account and start manually the listener. Do that several times (stop, put a message, start, then stop, push, start, etc..) and if each time it works then the technical path looks good. - You can also do it with few emails to be picked-up
- Then, if this works, stop listener, push a message, start the listener (this should work) and let the listener running. Wait for some minutes (more than defined latency period) and push a new email to be picked up.
Please also make sure that your email account is well defined without expiry period or your connection will technically be cut after some time. This means you'll need to authenticate again and this will happen only with manual restart (listener or application, I don't remember :))
This last point is maybe the first thing to check actually.
regards
Anthony