REST API is good. It has all necessary methods e.g. create an answer or a question. The problem is authorization process. Each call has an authorization header and credentials have to be the same as for the confluence user. Original idea was to listen inbox folder, get id of topic/question and with our own service call on Questions plugin REST API. But in this case we don't have user's credentials. And if we create e.g. answer with admin user we will lose such functionality as voting, notifications for that user and so on. Looks like it is critical issue in this case. If anyone has solved such problem please share this knowledge.

Any progress on this? If not, any add-ons that can do this? How about something custom utilizing the REST API? Would be a huge boost to adoption of the platform.

This could be a killer feature.

I have voted for this feature as well. In an organization that constantly sends out and replies to emails. Having this feature would be much more efficient and increase productivity.

I follow the use case, but being able to email Confluence Questions and create a question sounds like a lesser, poorer version of the external email listener/connector already present in JIRA. Rather than be able to ask questions via email, it may make more sense to add an external email address to a Jira project and incoming emails are created as technical question issues. This works very well with external customers or devices you wouldn't bring in to your Jira or Confluence instance.

Now answering questions via email - https://jira.atlassian.com/browse/CQ-542 - that feature request I just upvoted and watched. I would think the number of times field support engineers ask questions via SMTP emails because they aren't on the internal network would actually be far lower than answering questions or replying to possible answers via SMTP email (out in the field).

-Kelly Schoenhofen

I agree. We are thinking about using CQ to replace mailing-lists. Our Field Support Engineers absolutely need to be able to interact via email.

This is important to support engagement for mobile workers. They need to be able to ask questions when offline.