Re: OF! Why not KDE in Debian
Hi, On Thu, 17 Aug 2000, J.H.M. Dassen (Ray) wrote: On Thu, Aug 17, 2000 at 14:01:55 +0100, Pontus Ullgren wrote: After this matter I decided to try KDE out and found out that KDE is not in the Debian dist. Any reason why or is it just lack of package matainers ? A conflict exists between KDE's license and the license of the Qt library KDE uses; as a result of this, the Debian project cannot distribute KDE. Nevertheless - there are Debian Packages out there. Just add deb http://kde.tdyc.com woody kde contrib to your /etc/apt.sources.list . Regards Torsten Krueger -- Media Online Internet Services Marketing GmbH Torsten Krueger [EMAIL PROTECTED] fon: 49-231-5575100fax: 49-231-55751098 Ruhrallee 39 D-44137 Dortmund -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: very long passwd
On Fri, Aug 04, 2000 at 11:39:51AM +0200, Joaquin Ferrero wrote: I have 200.000 users. The most part only have email service. The file /etc/passwd es very, very long... but es necessary for IMAP server to check the home directory for every user. i'm surprised you get that many users in a passwd file. the passwd uid field is a 16 bit integer, which only allows for 65536 users total. i guess you must be sharing uidsprobably a bad idea. debian, btw, allows you to convert your passwd and group files into a hashed db files (stored in /var/lib/misc). to enable it, edit /etc/nsswitch.conf and change the lines: passwd:compat group: compat shadow:compat to passwd:db files group: db files shadow:db files then remember to run the Makefile in /var/lib/misc every time you add/change/delete a user. or set up a cron job to do it every 5 or 10 minutes: */10 * * * * cd /var/lib/misc ; make /dev/null 21 i'd say that this would scale up to 2^16 users. any more than that and you want to look for a better tool. this will probably work for you - looking up an entry in a db file is a LOT faster than sequentially searching a flat text file - but you have more users than can really be supported by 16bit uids so you should look into something designed to do the job like cyrus (see below). nss_mysql is the only solution? Now, I have mysql to auth users for proftpd apache via PAM (pam_mysql) Sendmail can't delivery emails to not existents users (it check /etc/passwd). IMAP server need /etc/passwd for check user home dir. With pam_mysql check the user but not the home dir. Any solution for only-email users without /etc/passwd file??? How can to have many users easy? you probably want to look at the cyrus mail system (which is packaged for debian). don't be put off by the "non-free" status, the license is free enough for most practical purposes, but doesn't quite meet the debian free software guidelines. you will need at least the cyrus-common, cyrus-admin, and cyrus-imapd packages. Package: cyrus-admin Priority: extra Section: non-free/mail Installed-Size: 76 Maintainer: Michael-John Turner [EMAIL PROTECTED] Architecture: i386 Source: cyrus-imapd Version: 1.5.19-3 Depends: libc6 (= 2.1.2), libdb2 (= 1:2.4.14-7), tcl8.0 (= 8.0.4) Filename: dists/unstable/non-free/binary-i386/mail/cyrus-admin_1.5.19-3.deb Size: 38252 MD5sum: b5fa894cf5b47389abb873d1c4d10bc2 Description: CMU Cyrus mail system (administration tool) Cyrus is a fully-featured IMAP daemon, with a number of features not found in other IMAP implementations, including: o Designed to handle massive quantities of mail o No need for users to have login accounts o Support for POP3 in addition to IMAP o Servers don't run as root o Easy support for mail quotas . Note: Cyrus doesn't support reading from and storing mail in your standard mail spool - it stores mail in a separate directory in its own MH-like format. . This package contains the cyradm tool which can be used to administer both local and remote Cyrus mail systems. cyrus' mailbox format is similar to the Maildir format so should be NFS safe (or at least as safe as anything is likely to be under NFS). i haven't used cyrus myself yet in any serious way, just played with it a bit. it looks good, i'm impressed. cyrus will work with sendmail or exim or most other mailers (dunno if it works with qmail). i'd recommend using it with postfix, because postfix is about the best mailer available - it's fast, secure, and backwards compatible with sendmail. from what i've read on the postfix-users list, cyrus + postfix makes an excellent combination. postfix scales extremely well. i would guess that your mail server is straining under an extremely high load average with 200,000 users on sendmail. under postfix it would just chug along barely breaking a sweat. craig -- craig sanders -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
More than 65K users..
Hello We are risking to pass this magic number in a short while.. Is there any neat way to handle more than this as I recall you can only have 2^16 UIDS?? /Roger - Roger Abrahamsson, Sys/Net Admin Obbit AB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Inherited ISP host configuration nightmare
Upon reviewing host configurations created by my predecessor, I inherited a nightmare. DNS was misconfigured from the start, causing dial-up clients to use a SMTP/POP3 hostname of "domain.com" instead of "mail.domain.com". We need "domain.com" to resolve to the NT web server for "http://domain.com" requests and to the Linux mail server for mail client software. It will take a few months to migrate clients to a new SMTP/POP3 host name. Does anyone know how to best handle this on the Linux host in the interim? Many thanks in advance for any assistance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inherited ISP host configuration nightmare
Gene, i dont think this is possible. There may be some tricks you can do with ipchains to forward packets from one port to another IP/port and get the job done, but it would probably be a kludge. You could also do this on your cisco, kinda like redirecting all traffic through the router to a squid server, or similar. Why dont you put up a simple web server on the linux box and then have them automatically transferred to the NT box (where the real web server/pages are located?) This would be very simple and could be done in a number of ways, and ways in which they were meant to be used? On Fri, 18 Aug 2000, Gene Grimm wrote: | Upon reviewing host configurations created by my predecessor, I | inherited a nightmare. DNS was misconfigured from the start, causing | dial-up clients to use a SMTP/POP3 hostname of "domain.com" instead of | "mail.domain.com". We need "domain.com" to resolve to the NT web server | for "http://domain.com" requests and to the Linux mail server for mail | client software. It will take a few months to migrate clients to a new | SMTP/POP3 host name. Does anyone know how to best handle this on the | Linux host in the interim? Many thanks in advance for any assistance. | | | -- | To UNSUBSCRIBE, email to [EMAIL PROTECTED] | with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] | | -- ___ _ __ _ __ /___ ___ /__ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [-[system info]---] 8:20am up 99 days, 14:23, 4 users, load average: 0.24, 0.17, 0.11 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inherited ISP host configuration nightmare
Upon reviewing host configurations created by my predecessor, I inherited a nightmare. I almost forgot to mention, we have about 40-60 virtual domains hosted via for both email and web services on these two machines. Is there some script that will handle this for all domains without having to configure each one individually? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inherited ISP host configuration nightmare
Gene, you need to be a little bit more specific. It sounds like you might be getting in a little over your head. You should probably do a little bit of reading before you go changing alot of stuff around, or you could have some pissed off customers to deal with... i know how much that sucks, trust me, you dont want to be there. I'll give you some links, and then you can tell me what you might be looking to do. Some questions first. Are the virtual domains on linux machine(s) or NT machine(s)? We host all our virtual domains on a linux box. Apache has virtual domain support built in, and you can even setup a virtual domain without using an IP with apache. We dont currently do this, but we plan to in the future. Currently we still setup our virtual domains with IP addresses. For the email, we use qmail, which works beautifully, securely, efficiently, and VERY easily with virtual domains. (as you can tell, i'm a qmail bigot) http://www.linux.org/docs/ldp/howto/Virtual-Services-HOWTO.html http://www.linux.org/docs/ldp/howto/VMailMgr-HOWTO.html On Fri, 18 Aug 2000, Gene Grimm wrote: | Upon reviewing host configurations created by my predecessor, I | inherited a nightmare. | | I almost forgot to mention, we have about 40-60 virtual domains hosted via for | both email and web services on these two machines. Is there some script that will | handle this for all domains without having to configure each one individually? | | | -- | To UNSUBSCRIBE, email to [EMAIL PROTECTED] | with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] | | -- ___ _ __ _ __ /___ ___ /__ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [-[system info]---] 8:30am up 99 days, 14:33, 4 users, load average: 0.35, 0.21, 0.15 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Inherited ISP host configuration nightmare
GG [...] DNS was misconfigured from the start, GG causing dial-up clients to use a SMTP/POP3 hostname of GG "domain.com" instead of "mail.domain.com". We need GG "domain.com" to resolve to the NT web server for GG "http://domain.com" requests and to the Linux mail server for GG mail client software. [...] No problem, (I alluded to this yesterday). Just run a web server on the linux machine and have it issue HTTP redirects from domain.com to www.domain.com. You could also port-forward, but I think the redirect is easier to get right (and less disruptive as you are getting it right). Apache would do just fine. The bigger picture: Maybe you want to bring in an experienced firefighter for while, learn from him and then take over? Good bosses usually like 'this is new, I'll need to learn' almost as much as they like 'sure, I can do it.' Yours in particular should by now. BM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inherited ISP host configuration nightmare
Gene, From what I understand here, you need a simple webserver on the Linux mail server (domain.com) that will redirect clients to www.domain.com, at least until you can get the customer base reconfigured. Stick Apache on there and set your index.html with this tag in the header. META HTTP-EQUIV="refresh" CONTENT="0;URL=http://www.domain.com" -- Kevin Blackham 801-539-0852 Domains Administrator, XMission Internet 877-XMISSION [EMAIL PROTECTED]877-964-7746 http://www.xmission.com/help On Fri, Aug 18, 2000 at 10:16:46AM -0400, Gene Grimm wrote: Upon reviewing host configurations created by my predecessor, I inherited a nightmare. DNS was misconfigured from the start, causing dial-up clients to use a SMTP/POP3 hostname of "domain.com" instead of "mail.domain.com". We need "domain.com" to resolve to the NT web server for "http://domain.com" requests and to the Linux mail server for mail client software. It will take a few months to migrate clients to a new SMTP/POP3 host name. Does anyone know how to best handle this on the Linux host in the interim? Many thanks in advance for any assistance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inherited ISP host configuration nightmare
On Fri, 18 Aug 2000, Gene Grimm wrote: The easiest thing I can think of is ipportfw. Why not just forward the mail or http ports to the other machine. (probably the http in this case). Maybe setup a simple ip chain on the mail ports to keep track of how much data goes through them, or even logging the ips of the users who go through. (cross reference with access logs and you should have an idea of which clients to have your support department contact when they aren't too busy). Puts a little extra load on the linux box, but I am sure it can handle it. Upon reviewing host configurations created by my predecessor, I inherited a nightmare. DNS was misconfigured from the start, causing dial-up clients to use a SMTP/POP3 hostname of "domain.com" instead of "mail.domain.com". We need "domain.com" to resolve to the NT web server for "http://domain.com" requests and to the Linux mail server for mail client software. It will take a few months to migrate clients to a new SMTP/POP3 host name. Does anyone know how to best handle this on the Linux host in the interim? Many thanks in advance for any assistance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] --- J.R. Blain [EMAIL PROTECTED] http://www.top100.org [EMAIL PROTECTED] http://www.2kservices.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OF! Why not KDE in Debian
Hi, On Thu, 17 Aug 2000, J.H.M. Dassen (Ray) wrote: On Thu, Aug 17, 2000 at 14:01:55 +0100, Pontus Ullgren wrote: After this matter I decided to try KDE out and found out that KDE is not in the Debian dist. Any reason why or is it just lack of package matainers ? A conflict exists between KDE's license and the license of the Qt library KDE uses; as a result of this, the Debian project cannot distribute KDE. Nevertheless - there are Debian Packages out there. Just add deb http://kde.tdyc.com woody kde contrib to your /etc/apt.sources.list . Regards Torsten Krueger -- Media Online Internet Services Marketing GmbH Torsten Krueger [EMAIL PROTECTED] fon: 49-231-5575100fax: 49-231-55751098 Ruhrallee 39 D-44137 Dortmund
Re: very long passwd
On Fri, Aug 04, 2000 at 11:39:51AM +0200, Joaquin Ferrero wrote: I have 200.000 users. The most part only have email service. The file /etc/passwd es very, very long... but es necessary for IMAP server to check the home directory for every user. i'm surprised you get that many users in a passwd file. the passwd uid field is a 16 bit integer, which only allows for 65536 users total. i guess you must be sharing uidsprobably a bad idea. debian, btw, allows you to convert your passwd and group files into a hashed db files (stored in /var/lib/misc). to enable it, edit /etc/nsswitch.conf and change the lines: passwd:compat group: compat shadow:compat to passwd:db files group: db files shadow:db files then remember to run the Makefile in /var/lib/misc every time you add/change/delete a user. or set up a cron job to do it every 5 or 10 minutes: */10 * * * * cd /var/lib/misc ; make /dev/null 21 i'd say that this would scale up to 2^16 users. any more than that and you want to look for a better tool. this will probably work for you - looking up an entry in a db file is a LOT faster than sequentially searching a flat text file - but you have more users than can really be supported by 16bit uids so you should look into something designed to do the job like cyrus (see below). nss_mysql is the only solution? Now, I have mysql to auth users for proftpd apache via PAM (pam_mysql) Sendmail can't delivery emails to not existents users (it check /etc/passwd). IMAP server need /etc/passwd for check user home dir. With pam_mysql check the user but not the home dir. Any solution for only-email users without /etc/passwd file??? How can to have many users easy? you probably want to look at the cyrus mail system (which is packaged for debian). don't be put off by the non-free status, the license is free enough for most practical purposes, but doesn't quite meet the debian free software guidelines. you will need at least the cyrus-common, cyrus-admin, and cyrus-imapd packages. Package: cyrus-admin Priority: extra Section: non-free/mail Installed-Size: 76 Maintainer: Michael-John Turner [EMAIL PROTECTED] Architecture: i386 Source: cyrus-imapd Version: 1.5.19-3 Depends: libc6 (= 2.1.2), libdb2 (= 1:2.4.14-7), tcl8.0 (= 8.0.4) Filename: dists/unstable/non-free/binary-i386/mail/cyrus-admin_1.5.19-3.deb Size: 38252 MD5sum: b5fa894cf5b47389abb873d1c4d10bc2 Description: CMU Cyrus mail system (administration tool) Cyrus is a fully-featured IMAP daemon, with a number of features not found in other IMAP implementations, including: o Designed to handle massive quantities of mail o No need for users to have login accounts o Support for POP3 in addition to IMAP o Servers don't run as root o Easy support for mail quotas . Note: Cyrus doesn't support reading from and storing mail in your standard mail spool - it stores mail in a separate directory in its own MH-like format. . This package contains the cyradm tool which can be used to administer both local and remote Cyrus mail systems. cyrus' mailbox format is similar to the Maildir format so should be NFS safe (or at least as safe as anything is likely to be under NFS). i haven't used cyrus myself yet in any serious way, just played with it a bit. it looks good, i'm impressed. cyrus will work with sendmail or exim or most other mailers (dunno if it works with qmail). i'd recommend using it with postfix, because postfix is about the best mailer available - it's fast, secure, and backwards compatible with sendmail. from what i've read on the postfix-users list, cyrus + postfix makes an excellent combination. postfix scales extremely well. i would guess that your mail server is straining under an extremely high load average with 200,000 users on sendmail. under postfix it would just chug along barely breaking a sweat. craig -- craig sanders
Re: mailman error
On Fri, 18 Aug 2000, Ed Kai wrote: I'm not sure why mailman is trying to use a majordomo script...Any help is you're using sendmail with smrsh enabled look at the smrsh root dir, and modify the ``wrapper'' link to point to mailman's wrapper instead of majordomo's wrapper -- [-] ``And there are plenty of other innovative pieces of software such as Napster and ICQ.'' -- comment on ``Systems Software Research is Irrelevant'' at http://freshmeat.net/news/2000/08/05/965534399.html
More than 65K users..
Hello We are risking to pass this magic number in a short while.. Is there any neat way to handle more than this as I recall you can only have 2^16 UIDS?? /Roger - Roger Abrahamsson, Sys/Net Admin Obbit AB
Inherited ISP host configuration nightmare
Upon reviewing host configurations created by my predecessor, I inherited a nightmare. DNS was misconfigured from the start, causing dial-up clients to use a SMTP/POP3 hostname of domain.com instead of mail.domain.com. We need domain.com to resolve to the NT web server for http://domain.com; requests and to the Linux mail server for mail client software. It will take a few months to migrate clients to a new SMTP/POP3 host name. Does anyone know how to best handle this on the Linux host in the interim? Many thanks in advance for any assistance.
Re: Inherited ISP host configuration nightmare
Gene, i dont think this is possible. There may be some tricks you can do with ipchains to forward packets from one port to another IP/port and get the job done, but it would probably be a kludge. You could also do this on your cisco, kinda like redirecting all traffic through the router to a squid server, or similar. Why dont you put up a simple web server on the linux box and then have them automatically transferred to the NT box (where the real web server/pages are located?) This would be very simple and could be done in a number of ways, and ways in which they were meant to be used? On Fri, 18 Aug 2000, Gene Grimm wrote: | Upon reviewing host configurations created by my predecessor, I | inherited a nightmare. DNS was misconfigured from the start, causing | dial-up clients to use a SMTP/POP3 hostname of domain.com instead of | mail.domain.com. We need domain.com to resolve to the NT web server | for http://domain.com; requests and to the Linux mail server for mail | client software. It will take a few months to migrate clients to a new | SMTP/POP3 host name. Does anyone know how to best handle this on the | Linux host in the interim? Many thanks in advance for any assistance. | | | -- | To UNSUBSCRIBE, email to [EMAIL PROTECTED] | with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] | | -- ___ _ __ _ __ /___ ___ /__ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [-[system info]---] 8:20am up 99 days, 14:23, 4 users, load average: 0.24, 0.17, 0.11
Re: Inherited ISP host configuration nightmare
Upon reviewing host configurations created by my predecessor, I inherited a nightmare. I almost forgot to mention, we have about 40-60 virtual domains hosted via for both email and web services on these two machines. Is there some script that will handle this for all domains without having to configure each one individually?
Re: Inherited ISP host configuration nightmare
Gene, you need to be a little bit more specific. It sounds like you might be getting in a little over your head. You should probably do a little bit of reading before you go changing alot of stuff around, or you could have some pissed off customers to deal with... i know how much that sucks, trust me, you dont want to be there. I'll give you some links, and then you can tell me what you might be looking to do. Some questions first. Are the virtual domains on linux machine(s) or NT machine(s)? We host all our virtual domains on a linux box. Apache has virtual domain support built in, and you can even setup a virtual domain without using an IP with apache. We dont currently do this, but we plan to in the future. Currently we still setup our virtual domains with IP addresses. For the email, we use qmail, which works beautifully, securely, efficiently, and VERY easily with virtual domains. (as you can tell, i'm a qmail bigot) http://www.linux.org/docs/ldp/howto/Virtual-Services-HOWTO.html http://www.linux.org/docs/ldp/howto/VMailMgr-HOWTO.html On Fri, 18 Aug 2000, Gene Grimm wrote: | Upon reviewing host configurations created by my predecessor, I | inherited a nightmare. | | I almost forgot to mention, we have about 40-60 virtual domains hosted via for | both email and web services on these two machines. Is there some script that will | handle this for all domains without having to configure each one individually? | | | -- | To UNSUBSCRIBE, email to [EMAIL PROTECTED] | with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] | | -- ___ _ __ _ __ /___ ___ /__ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [-[system info]---] 8:30am up 99 days, 14:33, 4 users, load average: 0.35, 0.21, 0.15
Re: Inherited ISP host configuration nightmare
On Fri, 18 Aug 2000, Gene Grimm wrote: The easiest thing I can think of is ipportfw. Why not just forward the mail or http ports to the other machine. (probably the http in this case). Maybe setup a simple ip chain on the mail ports to keep track of how much data goes through them, or even logging the ips of the users who go through. (cross reference with access logs and you should have an idea of which clients to have your support department contact when they aren't too busy). Puts a little extra load on the linux box, but I am sure it can handle it. Upon reviewing host configurations created by my predecessor, I inherited a nightmare. DNS was misconfigured from the start, causing dial-up clients to use a SMTP/POP3 hostname of domain.com instead of mail.domain.com. We need domain.com to resolve to the NT web server for http://domain.com; requests and to the Linux mail server for mail client software. It will take a few months to migrate clients to a new SMTP/POP3 host name. Does anyone know how to best handle this on the Linux host in the interim? Many thanks in advance for any assistance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] --- J.R. Blain [EMAIL PROTECTED] http://www.top100.org [EMAIL PROTECTED] http://www.2kservices.com
