webmail.abc.com IN A 200.200.200.26
lists.codewan.com. IN A 200.200.200.30
www IN CNAME webmail.abc.com
doing an nslookup/dig on the following ip/fqdn gave a correct result.
when browsing using ip address only point me to the correct website,
though on
200.200.200.30 point me to /mailman/listinfo of that ip address.
could it be an apache problem?
wdyt,
--Lito
neuroticimbecile wrote:
On Friday 11 January 2002 19:22, you wrote:
> Hi Jijo,
>
> happy that mailman is working, i can see the page in my lists.abc.com but
> the problem is abc.com now points to lists.abc.com also. Even though
> lists.abc.com and abc.com has different ip address. abc.com is not
> virtually hosted
>
> so i dont need to create a virtualhost entry for it in my httpd.conf.
> Desperately, i removed the index.html you recommend in my mailman
> directory and even remove the virtualhost entry for lists.abc.com in my
> httpd.conf., restart the services. but nothing happened,
> it still points me to my /mailman/listinfo page.if lists.abc.com and abc.com do not have the same ip address, and they both
point to the same site, then it may be a dns issue?> Federico Sevilla III wrote:
> > On Thu, 10 Jan 2002 at 15:04, Lito A. Lampitoc wrote:
> > > Tried your suggestion, and it WORKED!
> >
> > Over lunch I was also thinking about the new MailMan setup and about how
> > I can improve security. I thought of one. Instead of pointing
> > DocumentRoot to /var/lib/mailman, I created a directory
> > /var/lib/mailman/html (or anywhere, actually) where I put the index.html
> > file the code of which I recommended in my earlier reply. Then I set this
> > as DocumentRoot. This way a person with proper MailMan know-how cannot
> > view things like your mm_cfg.py by simply going to
> > <http://lists.abc.com/Mailman/mm_cfg.py>. The ScriptAlias definition that
> > redirects /mailman to /usr/lib/cgi-bin/mailman makes everything work as
> > it should, no matter what your DocumentRoot is. I also have Alias
> > definitions for /pipermail and /images. :)... another way to skin that cat:
with apache, you can just create an .htaccess file in the directories where
you want to store those files which shouldn't be accessed by browsers:
<Options -Indexes
<Files ~ "*.py">
Order allow,deny
Deny from all
</Files>hth,
-eric
--
.--. Enrique D. Rosel II
( () ) Q Linux Solutions, Inc.
`--\\ A Philippine Open Source Solutions Co. http://www.q-linux.com/
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
-- Lito A. Lampitoc Foundation for Communication Initiatives phone:+63(2)8941345 CodeWAN Project http://www.codewan.com.ph -- "If you think you're good, you're not."
