Hi Eric,
Thanks. I see that issue is fixed. I am going to use 2.3.2 which is the
stable version. I cannot use v3 at this moment as its not stable and I
cannot convince the people around here to go ahead with v3. Do you still
see I would encounter these kind of issues with 2.3.2 ? What other
For pure smtp relay, v2 is better tested and is known to work in various
production deployments.
It supports pop3 but not imap, so if you don't need imap and focus on
smtp, v2 is the best choice.
Simply be aware that if you face an issue and want a patch committed,
and released, you will get
I will definitely evaluate v3. But our use case doesn't need IMAP. Its not
a mail server which many users are going to access from their local mail
clients. What we are planning is an email application platform where when
an email is received over SMTP, call a web service and store the attachment
No limitation nor constraint at all to run your use case on V2, and even
maybe recommended as V3 mailetcontainer certainly still needs more
tuning, while V2 is stable and tested.
Benchmarking V2 vs V3 should give interesting figures, but we didn't do
anything yet.
You may also need support to
Thanks a lot Eric. That gives me more confidence on V2. I have built
Postage from source and did a sanity run for a minute. I downloaded the
source from
http://svn.apache.org/repos/asf/james/postage/tags/james-2_20120613/ as
opposed to the trunk mentioned in the wiki entry for Postage. Trunk
My pleasure.
tag/james-2_20120613 uses ant against V2, while trunk uses maven against
V3, that's why the jar are not in the lib folder.
On 08/10/2014 01:43 PM, Mahesh Sivarama Pillai wrote:
Thanks a lot Eric. That gives me more confidence on V2. I have built
Postage from source and did a
