Can you append this lines to logger
<logger name="com.solarwinds.oncall.email.EmailPollerImpl" level="TRACE" />
<logger name="com.solarwinds.oncall.workflow.WorkflowControllerImpl" level="TRACE" />
<logger name="com.solarwinds.oncall.email.parser.MessageParserEngineImpl" level="TRACE" />
loggin into appliance >> SolarWinds Management tab >> Edit Configuration >> logback-config.xml
- restart app
- reproduce both bugs
- bundle logs
There is some problems with your input mails.
Can you tell what mail client (and version) you use and specific details (maybe signatures, images, calendars, business cards, etc) of output mail?
It composes multipart mail with part that is actually claim to be plain/text, but without any value (empty).
Thank you for answering.
I have made the changes you asked, tried afterwards to send a "close" a re-assigned alarm which was in acknowledge state.
As before, the alarm did not close(I tried sending the reply as default Outlook html and plain text).
This exact same procedure worked without issue before the upgrade.
It does not matter if i send the "close" from Outlook 2013(html/plain text) or a Android mail client. These are the ones I have tried from.
The test close e-mail I sent as plain text from my Outlook 2013 was stripped for everything else except the Subject line and body contained the word close.
My college has tried from his Outlook as well, with the same result as me.
Please let me know if you want me to try anything else or you would prefer a remote session.
1 of 1 people found this helpful
Yes, it look like we have issue with v.591
All your messages will be trashed if you don't change mail server configurations (or change mail server; to GMail for example).
Right now your mail server don't include return-path header property in mail and we treat it like bounce message (more info here: Email Not Processing)
I'll raise this issue like severe and recurrent. It looks like we need release patch...
Ok, thank you.
Hopefully there will be a patch available very soon then
When you say that the Return-Path info is missing, I would just like to point out that if I send a test mail from my work Outlook 2013 to my privet Gmail address and choose to look at the header info(Show original), the Return-Path is there!
I will have a talk with our Exchange guru tomorrow. But I think my simple test above, should prove that the header info, does contain the Return-Path.
Or am I misunderstanding something?
Thank you again.
Yes, I think.
You can just connect to GMail (as your integration AC account) and validate that all works good.
Also, return-path value can be any non empty value (not necessary real return path of sender).
Any update on this issue as I am facing it as well with any Acknowledgements, assuming it's the same issue.
Any day soon, I believe (or so I was told).
Don't want misinformate nobody (we have no influence on release process), but 7th is the date that we expect new version to be available for download.
It fixed it, thank you!
Kevin M Reddish, CISSP, CEH