james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sheldon Jackson (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-2539) Need assistance with setting up James Server 3.0 to use Camel
Date Wed, 05 Sep 2018 11:14:00 GMT

    [ https://issues.apache.org/jira/browse/JAMES-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604283#comment-16604283
] 

Sheldon Jackson commented on JAMES-2539:
----------------------------------------

Thanks for the information. Since the entire email is not being stored in the MQ as part of
James Server 3.0 does the 3.0 version still have the option to queue emails in the DB spool
table like James Server 2.3 version. 

> Need assistance with setting up James Server 3.0 to use Camel
> -------------------------------------------------------------
>
>                 Key: JAMES-2539
>                 URL: https://issues.apache.org/jira/browse/JAMES-2539
>             Project: James Server
>          Issue Type: Task
>          Components: James Core
>    Affects Versions: 3.1.0
>            Reporter: Sheldon Jackson
>            Priority: Major
>
> I hope this is the correct forum. I need some assistance with getting James Server 3.0
+ camel to route incoming emails to use another MQ(like Websphere MQ) to store message(spooling)
for processing. I don't want message stored on local disk for spooling or if the inbound smtp
message error out it should be stored in websphere MQ.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message