Page History
| Devstatus | ||||
|---|---|---|---|---|
| ||||
* Primary target: our own forum with our own nntp-archived mailing lists.
Observation (exporter) and scheduled task (importer)
By observing creation of new mgnl:message nodes, we should be able to push those to the mailing list.
By polling the mailing list archive (or an account that is subscribed to the list), we should be able to add mgnl:message nodes to the forum.
Other suggestion: setup a mail server, get mails delivered to it and have a listener process those mails. (probably could be done with maillets)
Mail clients do not (necessarily) keep custom headers, so we can't rely on using custom headers to mark forum threads etc.
When sending a message to the mailing-list, we keep track of the mail's Message-Id, so we can match responses to the thread.
When fetching new messages from the list, we check if there is a forum:message with the same Message-Id (in which case it means the message was already exported); if this email has an In-Reply-To field with a known Message-Id, we know which thread to attach this message to,
User matching
We need to be able to find users by email. This is currently not possible via the UserManager API.
Proposed custom mail headers
Email clients dont propagate such headers (when responding), but we could still want to send email with custom headers:
X-Magnolia-Forum-ThreadID: the UUID of the threadX-Magnolia-Forum-ServerID: a unique identifier to make sure we're pushing data to/from the correct Magnolia instance ?- how to generate such a server id? (Jira has such an id for example, when registering a license)
Configuration
...
- One forum <-> one list
- nntp host, credentials etc
- our mailing lists nntp-group-names are in the form of
com.magnolia-cms.test1-list
...
- Possibility
...
- certain
...
...
- senders
...
- (typically
...
- Jira
...
- or
...
- Hudson)
...
- filter
...
...
- signatures
...
- and
...
- quotes
...
- (some
...
- regex
...
- work
...
- should
...
- help,
...
- but
...
- what
...
- do
...
- we
...
- do
...
- with
...
- inlined
...
- quotes?)
...
Libs
I've
...
had
...
some
...
reasonable
...
success
...
at
...
using
...
Kerio's
...
NNTP
...
with
...
commons-net:
...
http://commons.apache.org/net/
...
Still
...
looking
...
for
...
alternatives
...
as
...
commons-net's
...
api
...
isn't
...
superb,
...
and
...
has
...
some
...
scary
...
longstanding
...
issues:
...
https://issues.apache.org/jira/browse/NET-298
...
https://issues.apache.org/jira/browse/NET-276
...
->
...
will
...
use
...
...
instead,
...
as
...
Kerio's
...
NNTP
...
implementation
...
does
...
not
...
support
...
the
...
NEWNEWS
...
command.
...
Open
...
questions
...
- Implement
...
- an
...
- observer/listener
...
- pattern
...
- on
...
- forum
...
- instead
...
- of
...
- relying
...
- on
...
- jcr
...
- ?
...
- would
...
- match
...
- the
...
- idea
...
- of
...
- having
...
ForumManager
...
- return
...
Forum
...
- ,
...
Thread
...
- and
...
Message
...
- bean
...
- instances
...
- instead
...
- of
...
- exposing
...
- jcr
...
- nodes.
...
- jcr
...
- observation
...
- can
...
- filter
...
- per
...
- node
...
- type
...
- but
...
- it
...
- filters
...
- on
...
- the
...
- parent
...
- node
...
- type,
...
- ie
...
- we
...
- need
...
- to
...
- filter
...
- for
...
mgnl:thread
...
- and
...
mgnl:message
...
- (the
...
- latter,
...
- because
...
- messages
...
- can
...
- be
...
- nested),
...
- and
...
- thus
...
- we
...
- can't
...
- use
...
ForumManager.getMessage()
...
- directly
...
- from
...
- the
...
- EventListener.
...
- The
...
- EventListener
...
- would
...
- have
...
- to
...
- 1)
...
- fetch
...
- the
...
- node
...
- and
...
- check
...
- its
...
- type
...
- 2)
...
- either
...
- bypass
...
- ForumManager
...
- altogether
...
- or
...
- let
...
- ForumManager
...
- re-fetch
...
- the
...
- node
...
- we
...
- still
...
- need
...
- deferred
...
- and
...
- buffered
...
- execution
...
- of
...
- events
...
- if
...
- possible,
...
- so
...
- I
...
- need
...
- to
...
- look
...
- into
...
- reusing
...
info.magnolia.cms.util.DelayedExecutor
...
- or
...
- the
...
java.util.concurrent
...
- package.
...
This
...
- has
...
- not
...
- been
...
- implemented
...
- yet,
...
- but
...
- is
...
- still
...
- an
...
- open
...
- option
...
- for
...
- the
...
- future.
...
Links
- NNTP RFC: http://tools.ietf.org/html/rfc977
...
- Arpa
...
- text
...
- messages:
...
...
- More
...
- human-friendly
...
- description
...
- of
...
- the
...
- protocol:
...
...
...
Overview
Content Tools