We head already configured creating issues or adding comments to an issue by E-mail. It worked for some time, but then it stopped to work.
Analyzing the problem I've checked the configuration of the POP7IMAP-Server and the configured Mail-Handler. Everything looks fine and when I press "TEST"-Button, Test succeeds.
When I have the details shown, it shows:
To examine this, I have configurd another POP-Server and another Mail-Handler for another project. Click on "Test"-Button succeeds as well
.
So I thought, the configuration of this Mail-Handler looks fine, but it doesn't work either.
Hi @wvogtel
I suggest looking into the incoming mail logs for any errors.
the logs are located in the JIRA_HOME/log directory.
Thank you for that hint. I found two kinds of log-Files, all named following the two patterns
access_log.yyyy-mm-dd
and
catalina.yyyy-mm-dd.log
in which yyyy-mm-dd means year-month date.
Which kind do you mean by writing "mail logs"? Anyway, I'll have a look into both and see, if I can figure something out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, ... here we go:
On 15-Jan-2020 at 17:35 I sent a mail to create an issue for the project oms.
After that time, I find the following log entries:
15-Jan-2020 17:39:52.011 WARNUNG [http-nio-8080-exec-11] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://omsdev.awk.de:8080/rest/jira-mail-plugin/1.0/message-handlers/validate?atl_token=BQ4G-JNCV-W9AN-F4JZ%7C203dd8c9df5c65e3bab38a44b706ed4d4b4e1770%7Clin, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
15-Jan-2020 17:39:55.394 WARNUNG [http-nio-8080-exec-26] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://omsdev.awk.de:8080/rest/jira-mail-plugin/1.0/message-handlers/test?atl_token=BQ4G-JNCV-W9AN-F4JZ%7C203dd8c9df5c65e3bab38a44b706ed4d4b4e1770%7Clin, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the
After these two entries more entries can be found, all of the same pattern.
Presuming that sending an e-mail to the Jira-Project triggers a REST-request, it seems to me, that the content of the e-mail is not correct.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm also having a problem with creating issues or adding comments to an issue by E-mail. We're on server v 8.4. Is it possible it is not working because we are managing users via Crowd? Has anyone seen or heard the root cause can be using an external user management tool even when the configuration is correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.