[
https://issues.apache.org/jira/browse/JAMES-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219543#comment-17219543
]
ASF GitHub Bot commented on JAMES-3389:
---------------------------------------
chibenwa commented on a change in pull request #256:
URL: https://github.com/apache/james-project/pull/256#discussion_r510707090
##########
File path:
server/protocols/webadmin/webadmin-mail-over-web/src/test/resources/json/mail.json
##########
@@ -0,0 +1,13 @@
+{
Review comment:
> After that i will try to implement the request payload as the
emailSubmission object.
Don't. I points it to show you this is a complex topic.
I would prefer passing the mail envelope via URL query parameters, and
having the request payload being the raw MIME message. (I think having the raw
MIME EML submission format is really easy to use). The client system could be
as simple as a curl command (good inter-operability, but client system have to
generate mime messages itself).
If we want to support another format, JSON based, we could use the Accept
header to specify the Mail to be sent, and could be friendlier to modern
application (but we won't have a one format fit all use cases without some
over-engineering - we should rather start with something simple). The client
system would need to be adapted to this format (limited inter-operability).
I propose you write an API proposition, with examples, in the JIRA ticket
before implementing more things.
(You can of course take care of stylish and location issues).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> New API endpoint to accept incoming message
> -------------------------------------------
>
> Key: JAMES-3389
> URL: https://issues.apache.org/jira/browse/JAMES-3389
> Project: James Server
> Issue Type: Improvement
> Reporter: Juhan Aasaru
> Priority: Major
>
> We have messages arriving over a web service (not SMPT). For this we need a
> new API endpoint that would accept the message and insert it into the queue
> (ActiveMQ / rabbitMQ) for the email to be processed and stored.
> This new code would be placed to webadmin where all of the REST API-s live.
> Since the underlying queues are a bit different (ActiveMQ vs RabbitMQ) it
> needs to be designed in a way that it works for all configurations.
> Original discussion:
> [https://www.mail-archive.com/server-user@james.apache.org/msg16399.html]
> I would like to work on this myself but it will take me some weeks before I
> can start. Feel free to discuss under this task how to design it best. All
> the ideas how to solve this technically are taken from the thread in the
> mailing list - I haven't looked at the code myself yet.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
