Mailman within VHOST

2001-11-04 Thread A.Sleep
Hello all,

I'm attempting to setup Mailman for just one vhosted user.

Once mailman was installed (via apt) I edited the mm_cfg.py to reflect the
default url and host.

I created a lists. subdomain vhost and made the DocumentRoot the mailman
root (/usr/lib/mailman/cgi-bin). Then restarted Apache.

When I went to lists./listinfo I get a garbled output. Inbetween the
mess I can see it complaining about the UIG/GID but alas the script doesn't
tell me what gid/uid it's getting (looks like the script isn't being run
correctly to me).

Below is the vhost entry and it's corresponding Directory directive. Please
forgive the dropping of domain/ip data, it's not needed.

Note that I've attempted to use User and Group directives to set the uid/gid
to: www-data (should be the default for any host w/o a user/group directive
anyway) and the list user.

I also set the MAILMAN_UID and MAILMAN_GID to list and www-data to no avail.

Any insight would be wonderful.


# User list - Also tried manually setting to www-data
# Group list - Same as above
DocumentRoot /usr/lib/mailman/cgi-bin
ServerName lists.[domain]



    Options ExecCGI


---
A.Sleep




Mailman within VHOST

2001-11-04 Thread A.Sleep

Hello all,

I'm attempting to setup Mailman for just one vhosted user.

Once mailman was installed (via apt) I edited the mm_cfg.py to reflect the
default url and host.

I created a lists. subdomain vhost and made the DocumentRoot the mailman
root (/usr/lib/mailman/cgi-bin). Then restarted Apache.

When I went to lists./listinfo I get a garbled output. Inbetween the
mess I can see it complaining about the UIG/GID but alas the script doesn't
tell me what gid/uid it's getting (looks like the script isn't being run
correctly to me).

Below is the vhost entry and it's corresponding Directory directive. Please
forgive the dropping of domain/ip data, it's not needed.

Note that I've attempted to use User and Group directives to set the uid/gid
to: www-data (should be the default for any host w/o a user/group directive
anyway) and the list user.

I also set the MAILMAN_UID and MAILMAN_GID to list and www-data to no avail.

Any insight would be wonderful.


# User list - Also tried manually setting to www-data
# Group list - Same as above
DocumentRoot /usr/lib/mailman/cgi-bin
ServerName lists.[domain]



    Options ExecCGI


---
A.Sleep


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Virtual web hosting best practice?

2001-10-29 Thread A.Sleep
On Tue, Oct 30, 2001 at 12:56:18PM +1000, Andrew Pollock wrote:
> I'm just wondering what methods different people are using to provision 
> multiple
> websites under Apache?
> I'm after a method that's scaleable, as neat as possible, and most of all as
> secure as possible.
> e.g.
> Where do people shove their content roots?
> How do you securely allow individual sites to have CGI access?
> Directory structures, permission structures, account structures etc etc

I'm kinda new at commercal vhosting but...

Since all the users on my main box are vhosts I'v kept my users in
/home/LETTER/NAME and setup public_html for html/non-exec and added a
directory inside of that named cgi for exec scripts.

Below is my general ~/ layout for each user.

I've added each user to the www-data group (but enabled other mesures to
hopefully stop scripts from lurking around other dir's and chmoded their
home dir's 770.

I setup 3 vhosts (standard) for each user, www.domain.com/domain.com,
webalizer.domain.com and mail.domain.com, the latter of witch is simply a
pointer to my local TWIG install I've modded for vhosting.
The webalizer domain points to the webalizer dir and a cronjob runs under
each users account that updates their information.

The logs for their www domain (both combined and errors) go into ~/logs and
have the following format:
Error log: /home/f/foo/logs/error.log
Access Log (type Combined): /home/f/foo/logs/

The reason for the  as the name of the access log is that I have
quite a few clients that have multiple vhosts.

If the user wants an ftp server I set them up with a ProFTPD virtualhost and
that domain and ProFTPD directive points to their ~/ftp directory.

I'm working on a PHP script that will add my vhost directives for me but
currently I'm adding them by hand. Take a look at the User/Group directives
they come in handy.

There is also a way to setup "macros" to use w/ vhosts that would cut the
hand-workload down a bit I'm just opting for a script-based approach.


example username "foo":

layout of /home/f/foo
-rw---1 foo   foo   2888 Oct 28 12:54 README
drwxrws---2 foo   foo   4096 Oct 28 20:59 ftp
drwxrws---2 foo   foo   4096 Oct 28 15:55 logs
drwxrws---   13 foo   foo   4096 Oct 28 15:12 public_html
drwxrws---2 foo   foo   4096 Oct 29 12:28 webalizer




Re: Virtual web hosting best practice?

2001-10-29 Thread A.Sleep

On Tue, Oct 30, 2001 at 12:56:18PM +1000, Andrew Pollock wrote:
> I'm just wondering what methods different people are using to provision multiple
> websites under Apache?
> I'm after a method that's scaleable, as neat as possible, and most of all as
> secure as possible.
> e.g.
> Where do people shove their content roots?
> How do you securely allow individual sites to have CGI access?
> Directory structures, permission structures, account structures etc etc

I'm kinda new at commercal vhosting but...

Since all the users on my main box are vhosts I'v kept my users in
/home/LETTER/NAME and setup public_html for html/non-exec and added a
directory inside of that named cgi for exec scripts.

Below is my general ~/ layout for each user.

I've added each user to the www-data group (but enabled other mesures to
hopefully stop scripts from lurking around other dir's and chmoded their
home dir's 770.

I setup 3 vhosts (standard) for each user, www.domain.com/domain.com,
webalizer.domain.com and mail.domain.com, the latter of witch is simply a
pointer to my local TWIG install I've modded for vhosting.
The webalizer domain points to the webalizer dir and a cronjob runs under
each users account that updates their information.

The logs for their www domain (both combined and errors) go into ~/logs and
have the following format:
Error log: /home/f/foo/logs/error.log
Access Log (type Combined): /home/f/foo/logs/

The reason for the  as the name of the access log is that I have
quite a few clients that have multiple vhosts.

If the user wants an ftp server I set them up with a ProFTPD virtualhost and
that domain and ProFTPD directive points to their ~/ftp directory.

I'm working on a PHP script that will add my vhost directives for me but
currently I'm adding them by hand. Take a look at the User/Group directives
they come in handy.

There is also a way to setup "macros" to use w/ vhosts that would cut the
hand-workload down a bit I'm just opting for a script-based approach.


example username "foo":

layout of /home/f/foo
-rw---1 foo   foo   2888 Oct 28 12:54 README
drwxrws---2 foo   foo   4096 Oct 28 20:59 ftp
drwxrws---2 foo   foo   4096 Oct 28 15:55 logs
drwxrws---   13 foo   foo   4096 Oct 28 15:12 public_html
drwxrws---2 foo   foo   4096 Oct 29 12:28 webalizer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Apache suEXEC Question

2001-10-13 Thread A.Sleep
On Sat, Oct 13, 2001 at 02:09:03PM +1000, Craig Sanders wrote:
> dunno if this is already what you were doing, but why not use proftpd
> which can restrict users to their own home directory? it's not quite the
> same as chroot (because you don't need to copy /etc, /usr/bin, /lib, and
> so on into each home dir) but it gives a similar affect.

For ftp I already do that. This box does provide shell access though. That's
the reason I was looking at things like FreeVSD (looks good and they 'say'
they are working on a Debian port but no developer has ever answered my
questions about it).

The apache problem has been solved so the home dir's can be 700'ed the users
and I don't want to make them use rbash (since many of the users are
programmers this would be silly) so I'll have to devise some other means of
securing the box a bit more.

I know for one I'll be changing php to run in SAFE_MODE :)

Thanks for all the help.

A.Sleep




Re: Apache suEXEC Question

2001-10-13 Thread A.Sleep

On Sat, Oct 13, 2001 at 02:09:03PM +1000, Craig Sanders wrote:
> dunno if this is already what you were doing, but why not use proftpd
> which can restrict users to their own home directory? it's not quite the
> same as chroot (because you don't need to copy /etc, /usr/bin, /lib, and
> so on into each home dir) but it gives a similar affect.

For ftp I already do that. This box does provide shell access though. That's
the reason I was looking at things like FreeVSD (looks good and they 'say'
they are working on a Debian port but no developer has ever answered my
questions about it).

The apache problem has been solved so the home dir's can be 700'ed the users
and I don't want to make them use rbash (since many of the users are
programmers this would be silly) so I'll have to devise some other means of
securing the box a bit more.

I know for one I'll be changing php to run in SAFE_MODE :)

Thanks for all the help.

A.Sleep


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Apache suEXEC Question

2001-10-12 Thread A.Sleep
On Fri, Oct 12, 2001 at 11:38:32AM -0700, Jeremy C. Reed wrote:
> > I've added my User and Group directives in the vhosts in my vhost.conf and
> > I'm getting Forbidden errors.
> Look at your error and suexec logs. Maybe at /var/log/apache/suexec.log or
> /var/log/apache/cgi.log.

I forgot all about the suexec log... thanks, that's quite helpfull.

> Also, have you changed your suexec document root to cover /home? (By
> default it covers /var/www.)

Actually no I didn't. AAMOF I didn't think I needed to... I'm running the
box's domain (simple pages and mrtg output) out of /var/www so I left the
docroot as it was. Would that make a differance?

All of the other boxen I've worked on had a setup like - normal - w/
/var/vhosts/ etc... and the docroot was always /var/vhosts so I didn't need
to play with it.

A.Sleep




Re: Apache suEXEC Question

2001-10-12 Thread A.Sleep

On Fri, Oct 12, 2001 at 11:38:32AM -0700, Jeremy C. Reed wrote:
> > I've added my User and Group directives in the vhosts in my vhost.conf and
> > I'm getting Forbidden errors.
> Look at your error and suexec logs. Maybe at /var/log/apache/suexec.log or
> /var/log/apache/cgi.log.

I forgot all about the suexec log... thanks, that's quite helpfull.

> Also, have you changed your suexec document root to cover /home? (By
> default it covers /var/www.)

Actually no I didn't. AAMOF I didn't think I needed to... I'm running the
box's domain (simple pages and mrtg output) out of /var/www so I left the
docroot as it was. Would that make a differance?

All of the other boxen I've worked on had a setup like - normal - w/
/var/vhosts/ etc... and the docroot was always /var/vhosts so I didn't need
to play with it.

A.Sleep


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Apache suEXEC Question

2001-10-12 Thread A.Sleep
On Fri, Oct 12, 2001 at 09:17:57AM -0700, Tim Moss wrote:
> > I've added my User and Group directives in the vhosts in my vhost.conf
> > and
> > I'm getting Forbidden errors.
> > Here's an example:
> > The User and Group directives are set to foo
> > Here's an -ls -l of /home/f/ and /home/f/foo/
> > ls -l /home/
> > drwxr-xr-x2 root root 4096 Oct 11 09:51 f
> > ls -l /home/f/
> > drwxrwx---7 foo  foo  4096 Oct 12 08:37 foo
> Seems like this directory should be mode 755. Setting the User and Group
> in a VirtualHost section only affects what user and group CGI programs
> run as. The main webserver User & Group don't have any access to this
> directory unless those happen to be foo & foo.

That's what I was thinking but this is also the first time the box hasn't
been chroot'ed for users. The idea was to have non-world readable home dir's.

There must be some way to do this. Is adding the www-data user into each new
uesrs group the way to go? I'm still against NOT having a chroot'ed jail for
the users but it's not my choice.

A.Sleep.




Apache suEXEC Question

2001-10-12 Thread A.Sleep
Oddly, this is the first time I've had this issue...

I've added my User and Group directives in the vhosts in my vhost.conf and
I'm getting Forbidden errors.
Here's an example:

The User and Group directives are set to foo
Here's an -ls -l of /home/f/ and /home/f/foo/

ls -l /home/

drwxr-xr-x2 root root 4096 Oct 11 09:51 f


ls -l /home/f/

drwxrwx---7 foo  foo  4096 Oct 12 08:37 foo


ls -l /home/f/foo/

drwxr-sr-x2 foo  foo  4096 Oct 12 08:37 logs
drwxr-sr-x   24 foo  foo  4096 Oct 12 08:37 public_html


Any ideas why I'm getting forbidden errors? I've never gotten errors before
when setting this up, but I've never used the /home//
setup before either, is this an issue?

A.Sleep




Apache suEXEC Question

2001-10-12 Thread A.Sleep

Oddly, this is the first time I've had this issue...

I've added my User and Group directives in the vhosts in my vhost.conf and
I'm getting Forbidden errors.
Here's an example:

The User and Group directives are set to foo
Here's an -ls -l of /home/f/ and /home/f/foo/

ls -l /home/

drwxr-xr-x2 root root 4096 Oct 11 09:51 f


ls -l /home/f/

drwxrwx---7 foo  foo  4096 Oct 12 08:37 foo


ls -l /home/f/foo/

drwxr-sr-x2 foo  foo  4096 Oct 12 08:37 logs
drwxr-sr-x   24 foo  foo  4096 Oct 12 08:37 public_html


Any ideas why I'm getting forbidden errors? I've never gotten errors before
when setting this up, but I've never used the /home//
setup before either, is this an issue?

A.Sleep


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: vmailmgr issue

2001-09-28 Thread A.Sleep

On Sat, Sep 29, 2001 at 04:53:09PM +1000, Jeff Waugh wrote:
> Might want to revise your motto. :)

No, it's fine with me...

I can't admin email... I have already admitted that and have no issues doing
it again.

Thanks anyway...

A.Sleep

P.S.: It was a project motto, the whole group adopted it... and I am smart ;)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: vmailmgr issue

2001-09-28 Thread A.Sleep

On Fri, Sep 28, 2001 at 12:00:11PM -0700, Loopshot Operator wrote:
> I don't know about vmailmgr, but from what I remember, vpopmail was 
> the newer version of vmailmgr (I *think*), and I have vpopmail 

>From what I can find you are correct, thanks for the heads up.

This time I got qmail, vpopmail AND qmail admin working AND I can USE it :)
kindof

When attempting to start qmail I get:
alert: cannot start: unable to read controls

A search on google mainly returns the manpage for qmail-log ... not really
any help.

Looking at some other issues I checked the perms for both /var/lib/qmail and
/var/qmail, etc. and made sure they were all the same (alias.qmail).

Any ideas? qmail was installed from apt (qmail-src, build-qmail, etc.)

I hate admining email... no wonder I've never had to do this before.

A.Sleep


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Webmin

2001-09-28 Thread A.Sleep

On Fri, Sep 28, 2001 at 09:52:22AM +0200, Craig wrote:
> Does anyone know how to install new modules in webmin ?
> I have download the exim plug in and placed it in the
> webmin dir but it's not displaying it in webmin ...

Webmin modules can be installed right through the webmin interface using HTTP.

I don't have a box w/ webmin on it right now, but I last used it two weeks
ago.

No downloading is needed unless the module isn't packaged correctly (e.g.
needs some compiling, etc.).

A.Sleep


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




vmailmgr issue

2001-09-28 Thread A.Sleep

I'm sure there is a way... I'm just bashing my head against the wall now...

I'm attempting to setup vmailmgr on my Sid box and I can't get it to run.

I first installed from source but I wasn't sure of the install so I alien'ed
the RPMs and now I feel - slighly - more confedent. I had to move some files
around but it _looks_ right.

I've also installed ucspi-tcp but this did not give me a needed file
"unixserver".

Has anyone gotten vmailmgr to run on a Debian box? Is there some deb's
anywhere? I couldn't find any.

A.Sleep


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Still Messing With Mail...

2001-09-24 Thread A.Sleep

Oh Kay...

I've gone back to postfix and courier beacuse every other solution just
didn't seem to work quite right. Since I havn't the time (nor the patiance)
to get a better system in place it's gonna stay this way :)

Hopefully final questions from me about vhost mail:

1. Am I right in setting postfix up this way?
  I currently (and previously) have had to edit the virtual file for every
user then run postmap. I'm going to add this action into an adduser script
but I'm wondering if there isn't a better way to do it.
  I attempted postfix+mysql for mapping but the lack of documentation I
could find just confused the heck outta me.

2. How can I set the users default domain when the send mail via mutt/xmailer?

If there was an anti-mail-admin it would be me.

A.Sleep


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




VHost/hosting Administration System

2001-09-15 Thread A.Sleep

I've found a few 'control panel' or 'vhosting administration' systesm out
there but they have two major flaws.

1. They are RHAT specific
2. They are sorely incomplete

I've always done vhosting/virt-users admin by hand but this is getting quite
tedious.

If anyone has any hints as to a mail-admin system or complete control system
please send `em my way.

I'm currently using postfix but I have seen there will be many more options
if I use Qmail (this may or may not be true).

Thanks for the advise in advance...

A.Sleep


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: VHost Question

2001-09-10 Thread A.Sleep

On Sun, Sep 09, 2001 at 11:11:48AM +0200, Russell Coker wrote:
> > e.g. DEFAULT: www.theirdomain.com ADDED DIR (test): test.theirdomain.com
> > I've been attempting this with mod_alias and mod_rewrite and I'm quite
> > exasperated. :)
> Use something like the following in the Apache httpd.conf file:
> VirtualDocumentRoot /home/hosting/%-1/%-2/%-3/%-4+
> Then use my logtools package for managing the logs (it has documentation 
> explaining what to do).
> Do a search for VirtualDocumentRoot and my name, I've posted more information 
> on this topic previously.

Bah! Searching for the above turned out useless. No results found and for
VirtualDocumentRoot only one result was found.

I'll keep testing until I get this right, if anyone has any more pointers
please send them my way.

-- 
  .-"""-.   A.Sleep (Jeraimee Hughes) of NESIT (www.nesit.org)
 /* * * *\F r e e  S o f t w a r e  E v a n g e l i s t
:_.-:`:-._; Home: www.asleep.net - [EMAIL PROTECTED]
(_)CT2600: www.ct2600.org - [EMAIL PROTECTED]
_\|/(_)\|/
"from hell's heart I stab at thee"


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




VHost Question

2001-09-08 Thread A.Sleep

Hello all, I'm new to the list, the Geocrawler search (I'm being kind)
provided null for this topic so I'm hoping someone may have an idea of how
this is done:

An associate of mine has is system setup so that a users public_html dir has
(by default) two dirs. one www and one _ (linked to www).

When that user adds another dir (say test) it becomes a subdomain of their
domain.

e.g. DEFAULT: www.theirdomain.com ADDED DIR (test): test.theirdomain.com

I've been attempting this with mod_alias and mod_rewrite and I'm quite
exasperated. :)

Any pointers?

A.Sleep


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]