Hi,
Indeed I'm not responsible for the GSoC project, but there were some
discussions on this topic that may help you:
As far as I understood, the purpose of the GSoC project is to provide
social interaction / synchronization between page comments and emails, the
mail archive project purpose is more to really create an archive of emails,
something close to nabble, markmail ... but inside xwiki.
Of course both projects may have similarities while they are in fact quite
different.
My purpose was only to give you some piece of information about the mail
archive project, but in no way to influence you to use whatever technology
/ plugin, or to promote a particular architecture, this is your
responsibility and the one of xwiki dev team ;-)
BR,
Jeremie
2013/4/22 Sushil Kumar <0120sushil(a)gmail.com>
Hi Jeremie ,
Thanks for reply. But i'm still confused about the goal of the project. Is
it using the plugin code and make it more robust or adding some
email server with the xWiki.
Thanks and Regards
Sushil Kumar
On Mon, Apr 22, 2013 at 3:49 PM, Jeremie BOUSQUET <
jeremie.bousquet(a)gmail.com> wrote:
Hello,
Some comments,
2013/4/21 Sushil Kumar <0120sushil(a)gmail.com>
Hi , my name is Sushil Kumar and i'm an
undergraduate student at JIIT ,
Noida (India) . I would like to work on the project Advanced Email
Integration via GSOC 2013 . I consulted about the work that need to be
done
in this project on IRC channel and got a nice
explanation . But there
was a
> dilemma between what have to be done in this project and what has
already
That project is divided in some components, one of them being in charge
of
reading emails from a server connection (IMAP or
whatever, but I only
tested on IMAP). It uses Javamail under the hood.
https://github.com/xwiki-contrib/xwiki-application-mailarchive/tree/feature…
This is the link to that component, on a feature
branch because I
refactored it a lot for the import feature. So currently it aims at
"loading" emails from mail servers, or from archives in MBOX format.
I wouldn't say I'm satisfied currently of its design or API (well any
help
welcome of course ;-) ), and event if not tagged
like that (yet), it's
pretty much @Unstable ... But it might help you at least as a sample, of
course if you use James it's redundant.
Currently the components does mainly 2 things: "load" emails from a
server/an archive, and parses them to create a non-javamail object
(MailItem/MailContent).
>
> Well here are the bullet points which i have understood after two days
of
> talks on IRC .
>
> - A SMTP server is required to receive mails and then to attach
them
as
XWikiComments object to a document.
For my culture, why only SMTP ?
> - sdumitriu suggested me to use Apache James , but he said that its
a
full
blown mail server and we only need receiving part hence we need
to
> slice that part out.
> - I found it very hard to slice the SMTP part and embed it with
Jetty
(
> its hard without rewriting the code from scratch and taking help
from
James
and MailArchive plugin )
I don't know how James and MailArchive would go together, I think they're
pretty much redundant as I noticed above ... I don't know James very well
though.
>
> Now after all these i have certain doubts regarding what exactly needs
to
> be done in this project .
>
> - Do we have to integrate a mail server or have to write our own
SMTP
receiver ?
- If we have to integrate a mail server do we have to slice out the
SMTP
> part only?
> - Or is it something entirely different from these two points.
>
>
> P.S. The same dilemma exists for the Jabber part too. But will figure
it
out once
Email Integration is well understood.
Thanks and Regards
Sushil Kumar
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs