Iavor Raytchev wrote: (on the wiki)
* brief idea - combination of extension and daemon
I think that should be changed. 'Extension' implies C code that is
compiled into PHP. With a daemon there is no need for such drastic
measures. 'Module' or 'library' would be better since the whole
Doug Clements wrote:
Iavor Raytchev wrote:
[snip]
X-Istence wrote:
Now what i want to ask is, could we write it efficiently. As i would
want to deploy this over multiple servers, and having everything
written out in normal ASCII would be a waste of bandwidth (all bytes
count), i think that we shou
Paul Oehler wrote:
There is a function that provides authentication:
vpasswd( user, domain, password, is_apop )
that returns the user's password info if valid, or 0.
The problem is, if you can execute the vpopmail library at all, you can
execute every function within it. This is how Qmail
Alejandro Borges wrote:
>> That woudl be the best way. However, then we'd need a PHP API to use
>> in web-apps
>>
>> [snip]
>>
>> Ken, actually how do you imagine php to talk to the daemon?
>>
>>
>>
> With XML-RPC or SOAP!
Or super-simple: over sockets using tcpserver. tcpserver is built for makin
Iavor Raytchev wrote:
> [snip]
> X-Istence wrote:
>
> Now what i want to ask is, could we write it efficiently. As i would
> want to deploy this over multiple servers, and having everything
> written out in normal ASCII would be a waste of bandwidth (all bytes
> count), i think that we should make
> There is a function that provides authentication:
>
> vpasswd( user, domain, password, is_apop )
>
> that returns the user's password info if valid, or 0.
>
> The problem is, if you can execute the vpopmail library at all, you can
> execute every function within it. This is how QmailAdmin ch
Paul Oehler wrote:
Is this something related to how qmailadmin (which
I know the least about re: vpopmail) does authentication?
There is a function that provides authentication:
vpasswd( user, domain, password, is_apop )
that returns the user's password info if valid, or 0.
The problem
> >>The daemon MUST require all connections to be authenticated, preferably
> >>against the vpopmail user base.
> >>
> >>user rwidmer ok
> >>password mypassword ok
> >
> >
> > This is only slightly related to Rick's comments (which
> > The daemon MUST require all connections to be authenticated, preferably
> > against the vpopmail user base.
> >
> > user rwidmer ok
> > password mypassword ok
>
> This is only slightly related to Rick's comments (which I think a
Paul Oehler wrote:
The daemon MUST require all connections to be authenticated, preferably
against the vpopmail user base.
user rwidmer ok
password mypassword ok
This is only slightly related to Rick's comments (which I think a
X-Istence wrote:
I'd like to keep it in the vpopmail project. The daemon could be part of
the regular code and the php client module could be part of contrib?
Ken
This would cause problems. Then it would not be in PHP releases, and
only in the contrib directory, thus making it still an "remote
Ken Jones wrote:
On Friday 02 April 2004 2:32 pm, Iavor Raytchev wrote:
Hello everybody,
As it seems that the daemon idea prevails - what about a 'home' for the
daemon?
When I spoke to Boian Bonev (one of the authors of the php vpopmail
extension) he was absolutely for the daemon idea, but he sai
Rick Macdougall wrote:
Ken Jones wrote:
On Friday 02 April 2004 1:27 pm, Rick Macdougall wrote:
That sounds good. Of course as a C programmer I'd prefer it be written
in C linking in the vpopmail API. I'd like to take a swing
at building it in C over the weekend. vmailmgr has something
like thi
Rick Widmer wrote:
[1] Maybe it is my age showing, but it seems to me you want daemons lean
and mean, and having to load the whole PHP interpreter just doesn't do
it for me. (This is from someone who usually prefers to do everything
in PHP.)
I agree.
X-istence
> The daemon MUST require all connections to be authenticated, preferably
> against the vpopmail user base.
>
> user rwidmer ok
> password mypassword ok
This is only slightly related to Rick's comments (which I think are very
good
On Friday 02 April 2004 08:21 pm, Ken Jones wrote:
> > How about security? If we got it secures by SSL we coiuld use it on
> > multiple servers from one console. Rick, could you post a URL to the
> > code?
>
> I was talking this over with Jeremy and he recommended running it
> under tcpserver. So w
X-Istence wrote:
why? We could talk to it using normal sockets. I dont see why it would
require a special API to talk to a normal deamon on a TCP/IP. Even Unix
sockets.
Here is my $0.02 on how to best implement a daemon...
The daemon is in C [1] and runs under tcpserver. It opens a unix s
[snip]
Rick Macdougall:
Ken Jones wrote:
> I'd like to keep it in the vpopmail project. The daemon could be part of
> the regular code and the php client module could be part of contrib?
> I really like the idea of a wiki, too bad we don't have one for vpopmail.
Hi,
My only problem with that so
[snip]
Ken Jones
On Friday 02 April 2004 2:32 pm, Iavor Raytchev wrote:
> Would be best to open a Sourceforge.net project and open a wiki for an easy
> white board?
I'd like to keep it in the vpopmail project. The daemon could be part of
the regular code and the php client module could be part o
That woudl be the best way. However, then we'd need a PHP API to use in
web-apps
[snip]
Ken, actually how do you imagine php to talk to the daemon?
With XML-RPC or SOAP!
Ken Jones wrote:
I'd like to keep it in the vpopmail project. The daemon could be part of
the regular code and the php client module could be part of contrib?
I really like the idea of a wiki, too bad we don't have one for vpopmail.
Hi,
My only problem with that solution is that I wouldn't want
I dont think implementing an independent tcp transport (even if its a
very simple protocol) is a good idea nowdays.
I would do it in a soap or xmlrpc wrappers, over an already well made,
very lean, http server library. So then the clients could be made in any
language without having to implemen
[snip]
X-Istence:
why? We could talk to it using normal sockets. I dont see why it would
require a special API to talk to a normal deamon on a TCP/IP. Even Unix
sockets.
[snip]
I heard this idea several times and I think I like it.
[snip]
Marcin Soltysiak:
> Ken:
>
> That sounds good. Of course as a C programmer I'd prefer it be
> written in C linking in the vpopmail API. I'd like to take a swing
> at building it in C over the weekend. vmailmgr has something
> like this already, including a php module to talk to it. Perhaps
[snip]
X-Istence wrote:
Now what i want to ask is, could we write it efficiently. As i would
want to deploy this over multiple servers, and having everything written
out in normal ASCII would be a waste of bandwidth (all bytes count), i
think that we should make it binary communication, just like
[snip]
Ken Jones wrote:
That sounds good. Of course as a C programmer I'd prefer it be
written in C linking in the vpopmail API. I'd like to take a swing
at building it in C over the weekend. vmailmgr has something
like this already, including a php module to talk to it. Perhaps
we can re-use som
On Friday 02 April 2004 2:32 pm, Iavor Raytchev wrote:
> Hello everybody,
>
> As it seems that the daemon idea prevails - what about a 'home' for the
> daemon?
>
> When I spoke to Boian Bonev (one of the authors of the php vpopmail
> extension) he was absolutely for the daemon idea, but he said tha
Hello everybody,
As it seems that the daemon idea prevails - what about a 'home' for the daemon?
When I spoke to Boian Bonev (one of the authors of the php vpopmail extension) he was
absolutely for the daemon idea, but he said that it is very important to decide about
its home -
Is it going to
> >>That sounds good. Of course as a C programmer I'd prefer it be
> >>written in C linking in the vpopmail API. I'd like to take a swing
> >>at building it in C over the weekend. vmailmgr has something
> >>like this already, including a php module to talk to it. Perhaps
> >>we can re-use some of
Hi,
Ken Jones wrote:
On Friday 02 April 2004 2:15 pm, Marcin Soltysiak wrote:
I was talking this over with Jeremy and he recommended running it
under tcpserver. So we could run it over ssl with the ssl patch to tcpserver.
Yup, that's what we were doing. It was originally written to handle
reque
Ken Jones wrote:
On Friday 02 April 2004 1:27 pm, Rick Macdougall wrote:
That sounds good. Of course as a C programmer I'd prefer it be
written in C linking in the vpopmail API. I'd like to take a swing
at building it in C over the weekend. vmailmgr has something
like this already, including a
On Friday 02 April 2004 2:15 pm, Marcin Soltysiak wrote:
>
> How about security? If we got it secures by SSL we coiuld use it on
> multiple servers from one console. Rick, could you post a URL to the code?
I was talking this over with Jeremy and he recommended running it
under tcpserver. So we co
Marcin Soltysiak wrote:
Ken Jones wrote:
I've been thinking about this and I think the daemon is definitly the
way to go. If Rick can't release the code I can write one. I think
the protocol could be like this:
I found the code and although it is not as pretty as I remember it is
available for rel
> > Ken Jones wrote:
> > > I've been thinking about this and I think the daemon is definitly the
> > > way to go. If Rick can't release the code I can write one. I think
> > > the protocol could be like this:
> >
> > I found the code and although it is not as pretty as I remember it is
> > availabl
Rick Macdougall wrote:
Hi,
Ken Jones wrote:
I've been thinking about this and I think the daemon is definitly the
way to go. If Rick can't release the code I can write one. I think
the protocol could be like this:
I found the code and although it is not as pretty as I remember it is
available
On Friday 02 April 2004 1:27 pm, Rick Macdougall wrote:
> Hi,
>
> Ken Jones wrote:
> > I've been thinking about this and I think the daemon is definitly the
> > way to go. If Rick can't release the code I can write one. I think
> > the protocol could be like this:
>
> I found the code and although
Hi,
Ken Jones wrote:
I've been thinking about this and I think the daemon is definitly the
way to go. If Rick can't release the code I can write one. I think
the protocol could be like this:
I found the code and although it is not as pretty as I remember it is
available for release. It's in php
On Friday 02 April 2004 7:11 am, Iavor Raytchev wrote:
[snip]
> First code
> --
>
> Rick Macdougall has written a daemon for somebody and this somebody has
> agreed to open the source. This might be a starting point. Waiting from
> Rick to write back with details.
[snip]
I've been thinking
38 matches
Mail list logo
