Introduce an email reply processor

[asmecher]

...to:

• enable users to participate to discussions by answering emails
• enable reviewers to comment by answering emails
• ...possibly more.

[asmecher]

Proposal: Allow journal managers to optionally configure an email account (IMAP and/or POP), that OJS can periodically process. Use PHP's imap functions -- they can actually handle POP as well. Fetch unread messages as a batch job (to run via the normal scheduled tasks mechanisms) and delete the ones that have been successfully processed.

[asmecher]

Unknowns: how to authenticate received emails against the task (perhaps use AccessKey); where to put authentication information (we probably can't use one-time-generated email addresses, as most users won't have access to this); how to mix normal email content in with parseable content; whether there are support libraries/standard mechanisms to do this.

[NateWr]

how to authenticate received emails against the task (perhaps use AccessKey); where to put authentication information (we probably can't use one-time-generated email addresses, as most users won't have access to this);

Just a comment for later: we should be able to use the + syntax that is supported by most mail providers. So if the reply processor address is replies@example.com, the reply-to address could be replies+<access-key>@example.com. Most mail providers will put that into the replies@example.com mailbox. (This is how GitHub does it.)