Ok, thanks - I'll see if I can get that set up when I get a moment and give
it a try.
Cheers,
Colin
On 16 November 2013 04:22, Aurélien Bompard wrote:
>
> > Thanks Aurélien! Is there some documentation (or code) somewhere I can
> > look at for that?
>
> Unfortunately there is no separate docum
> Thanks Aurélien! Is there some documentation (or code) somewhere I can
> look at for that?
Unfortunately there is no separate documentation for the REST API, but
if you install HyperKitty and browse the /api URL, there is an HTML
rendering that explains endpoints and their use.
Aurélien
--
h
Thanks Aurélien! Is there some documentation (or code) somewhere I can look
at for that?
On 14 November 2013 03:38, Aurélien Bompard wrote:
> Hey Colin, sorry for not replying earlier
>
> There is a REST interface in HyperKitty, that will give you access to
> the archives if you want to impleme
Hey Colin, sorry for not replying earlier
There is a REST interface in HyperKitty, that will give you access to
the archives if you want to implement another web interface on top of
it. The good thing is that I know someone who already did that, with
about the same needs as you, so it must be doab
Ah, I see - great, thanks for the clarification.
On 11 November 2013 04:36, Stephen J. Turnbull wrote:
> Colin Fleming writes:
>
> > Thanks for the comments, Steve - can you clarify what you mean by a
> > "write-only API"?
>
> "Mailman core has no way to retrieve those messages."
>
> For the
Colin Fleming writes:
> Thanks for the comments, Steve - can you clarify what you mean by a
> "write-only API"?
"Mailman core has no way to retrieve those messages."
For the rest, I think Barry's answer is clear and definitive.
___
Mailman-Developers
On Nov 09, 2013, at 06:10 PM, Colin Fleming wrote:
>Thanks for the comments, Steve - can you clarify what you mean by a
>"write-only API"? As far as I can tell I could use that to insert messages
>that Mailman now considers "posted to the list" into my own DBMS and then
>present them however I lik
Thanks for the comments, Steve - can you clarify what you mean by a
"write-only API"? As far as I can tell I could use that to insert messages
that Mailman now considers "posted to the list" into my own DBMS and then
present them however I like. I'll have a bunch of questions around
robustness and
Colin Fleming writes:
> Is there a way to create an archive view (i.e. present a view of
> all messages in a list and allow reading particular mails) using
> the current API?
No, and (sorry Barry, but I think you just added to the confusion --
IArchiver is really a write-only API) there won't
Ok, thanks Barry, I'll take a closer look at IArchiver then. I've seen a
little info about it but I'm not on a development machine at the moment
(moving cities) so I'll look when I get a chance.
Thanks,
Colin
On 8 November 2013 04:15, Barry Warsaw wrote:
> On Nov 07, 2013, at 02:50 PM, Colin F
On Nov 07, 2013, at 02:50 PM, Colin Fleming wrote:
>I'm interested in using Mailman to set up a mailing list for my product.
>I'd like to have it be fully integrated into my website, so I'm planning to
>use Mailman 3 and the REST API. I've checked out mailman.client and poked
>around, and also loo
Hi all,
I'm interested in using Mailman to set up a mailing list for my product.
I'd like to have it be fully integrated into my website, so I'm planning to
use Mailman 3 and the REST API. I've checked out mailman.client and poked
around, and also looked at
http://bazaar.launchpad.net/~mailman-cod
12 matches
Mail list logo
