On Monday, November 12, 2001, at 04:39 PM, Tom Collins wrote:
> At 7:15 PM -0600 11/11/01, Bill Shupp wrote:
>> Since the session id would need to be stored in all URLs and form,
>> this is where most of the work would be in converting qmailadmin to
>> use session ids rather than IP addresses.
On Monday, November 12, 2001, at 04:21 PM, Ken Jones wrote:
> The final qmailadmin 1.0 canidate is available now
> http://www.inter7.com/devel/qmailadmin-1.0.tar.gz
>
> There are no known problems with this release. If
> no problems are reported in the next two days we will
> release this version
At 7:15 PM -0600 11/11/01, Bill Shupp wrote:
>Since the session id would need to be stored in all URLs and form,
>this is where most of the work would be in converting qmailadmin to
>use session ids rather than IP addresses.
>
>The good news is that qmailadmin would remain cookie free. I just
The final qmailadmin 1.0 canidate is available now
http://www.inter7.com/devel/qmailadmin-1.0.tar.gz
There are no known problems with this release. If
no problems are reported in the next two days we will
release this version as 1.0 to work with vpopmail-5.0.
Please test it.
Ken Jones
On Monday, November 12, 2001, at 09:20 AM, Gabriel Ambuehl wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> Hello Bill,
>
> Monday, November 12, 2001, 2:15:52 AM, you wrote:
>
>> The good news is that qmailadmin would remain cookie free. I just
>> implemented a similar scenario in PHP4 with its n
> -Original Message-
> From: Ross Davis - DataAnywhere.net [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 12, 2001 12:17 PM
> To: Brian Ipsen; [EMAIL PROTECTED]
> Subject: Re: ezmlm/ezmlm-idx with (full) MySQL Support ?
>
>
> and to add to that, I don't want my users to be able to kno
On Monday, November 12, 2001, at 01:16 PM, Ross Davis - DataAnywhere.net
wrote:
> and to add to that, I don't want my users to be able to know the
> password
> and username to the database. Why can't we have an option that disables
> that portion on screen and then reads that data from a conf
and to add to that, I don't want my users to be able to know the password
and username to the database. Why can't we have an option that disables
that portion on screen and then reads that data from a config file or
something.
- Original Message -
From: "Brian Ipsen" <[EMAIL PROTECTED]>
On Monday, November 12, 2001, at 12:44 PM, Brian Ipsen wrote:
> Hi!
>
> I wonder why qmailadmin can't create the needed tables in a MySQL
> database
> to be used for a mailinglist - if MySQL support is checked. Why is it
> needed
> to run ezmlm-mktab, when this task just as well can be perfor
Hi!
I wonder why qmailadmin can't create the needed tables in a MySQL database
to be used for a mailinglist - if MySQL support is checked. Why is it needed
to run ezmlm-mktab, when this task just as well can be performed by
qmailadmin (or qmailadmin can create the needed tables) ??
Regards,
/B
I finally stupidly found my problem. qmailadmin wasn't properly
sticky.
Given that, does anyone know the purpose of the (test ! -w /etc) in
the Makefile (ref:
install-exec-local:
test ! -w /etc || chown vpopuser $(DESTDIR)$(bindir)/qmailadmin
test ! -w /etc || chgrp vchkpw $(DE
On Monday, November 12, 2001, at 11:48 AM, Guillaume Monfort wrote:
> Hello there,
>
> my users create mailing lists with qmailadmin.
> the point is i do not wish to allow them to use
> list archival. is there any way to force qmailadmin
> to create list with this attribute ? or any kind of
> gl
Hello there,
my users create mailing lists with qmailadmin.
the point is i do not wish to allow them to use
list archival. is there any way to force qmailadmin
to create list with this attribute ? or any kind of
global setting that can override this creation ?
thanks for your help.
-BEGIN PGP SIGNED MESSAGE-
Hello Bill,
Monday, November 12, 2001, 2:15:52 AM, you wrote:
> The good news is that qmailadmin would remain cookie free. I just
> implemented a similar scenario in PHP4 with its new session
> support. Seems to work pretty well.
> Thoughts? Better ideas?
14 matches
Mail list logo