FTP Proxy
Can anyone recommend to me a good (non-transparent by preference) FTP proxy? I've never managed to get SOCKS and active FTP to work well together, so I've always needed PASV, and I'm encountering problems with misconfigured sites that can't use passive connections. Any help would be appreciated. Please CC replies to me. __ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com
FTP Proxy
Can anyone recommend to me a good (non-transparent by preference) FTP proxy? I've never managed to get SOCKS and active FTP to work well together, so I've always needed PASV, and I'm encountering problems with misconfigured sites that can't use passive connections. Any help would be appreciated. Please CC replies to me. __ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
金蜘蛛电子商务频道网站
Title: Untitled Document ¹ó¹«Ë¾£¬ÆóÒµ»òÍøÕ¾£ºÈ«ÇòÊ×´´eÃûƬµÄ½ðÖ©Öëµç×ÓÉÌÎñƵµÀÍøÕ¾ÔÚÕâÀïÏòÄã°Ý¸öÄ꣡ÎÒÃÇΪÁËÖ§³Ö¸öÈËÍøÕ¾µÄ·¢Õ¹£¬Ïò¸öÈËÍøÕ¾ÍƳöÁË¡°´úÀíÏúÊÛ¡±·þÎñ¡£²¢ÇÒ³éÈ¡35%µÄÌá³É×÷Ϊ֧³Ö¸öÈËÍøÕ¾·¢Õ¹»ù½ð¡£Ï£Íû¹ó¹«Ë¾£¬ÆóÒµ»òÍøÕ¾Äܹ»¶¦Á¦Ö§³Ö£¡ ÏÖÔÚ£¬ºÜ¶à¶«Î÷¶¼Àë²»¿ª»¥ÁªÍø£¬°üÀ¨£ºÉÌÎñ£¬½»ÓÑ£¬ÓÎÏ·£¬Í¨ÐÅ£¬¹ºÎï.¶øEÃûƬҲÊÇÐÂʱ´úÍøÂçµÄ²úÎï¡£ ×÷ΪҪ½øÐÐÒµÎñµÄÄ㣬EÃûƬ¸üÊDZز»¿ÉÉÙ£¡ËüÊÇÄãÓë¿Í»§ÁªÏµµÄ×îºÃ¹¤¾ß£¡£¨µã»÷ÒÔÉϹã¸æ£¬²Î¹ÛÎÒÃǵÄÍøÕ¾£© ÓÐemail,ÔõÄÜûÓÐeÃûƬ! ½ðÖ©Öëµç×ÓÉÌÎñƵµÀÍøÕ¾2002.2.16
金蜘蛛电子商务频道网站
Title: Untitled Document ¹ó¹«Ë¾£¬ÆóÒµ»òÍøÕ¾£ºÈ«ÇòÊ×´´eÃûƬµÄ½ðÖ©Öëµç×ÓÉÌÎñƵµÀÍøÕ¾ÔÚÕâÀïÏòÄã°Ý¸öÄ꣡ÎÒÃÇΪÁËÖ§³Ö¸öÈËÍøÕ¾µÄ·¢Õ¹£¬Ïò¸öÈËÍøÕ¾ÍƳöÁË¡°´úÀíÏúÊÛ¡±·þÎñ¡£²¢ÇÒ³éÈ¡35%µÄÌá³É×÷Ϊ֧³Ö¸öÈËÍøÕ¾·¢Õ¹»ù½ð¡£Ï£Íû¹ó¹«Ë¾£¬ÆóÒµ»òÍøÕ¾Äܹ»¶¦Á¦Ö§³Ö£¡ ÏÖÔÚ£¬ºÜ¶à¶«Î÷¶¼Àë²»¿ª»¥ÁªÍø£¬°üÀ¨£ºÉÌÎñ£¬½»ÓÑ£¬ÓÎÏ·£¬Í¨ÐÅ£¬¹ºÎï.¶øEÃûƬҲÊÇÐÂʱ´úÍøÂçµÄ²úÎï¡£ ×÷ΪҪ½øÐÐÒµÎñµÄÄ㣬EÃûƬ¸üÊDZز»¿ÉÉÙ£¡ËüÊÇÄãÓë¿Í»§ÁªÏµµÄ×îºÃ¹¤¾ß£¡£¨µã»÷ÒÔÉϹã¸æ£¬²Î¹ÛÎÒÃǵÄÍøÕ¾£© ÓÐemail,ÔõÄÜûÓÐeÃûƬ! ½ðÖ©Öëµç×ÓÉÌÎñƵµÀÍøÕ¾2002.2.16 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SNMPD package (Vulnerabilities)
On Thu, Feb 14, 2002 at 10:12:34AM +0100, James wrote: > > For potato (?) of course. This should be pretty trivial.. Since you're in potato, it might be easier to simply download the 3 source files from the /pool directory on a debian mirror. There will be a .dsc file, a .diff file and a .orig.tar.gz file :) dpkg-source -x snmp-4.3.2_2.dsc (or whatever the filename is) cd snmp-4.3.2 debian/rules binary-arch It should tell you if you're missing any packages to complete the compile :) This is a common procedure, e.g. I use it to build recent samba packages for potato.. Cheers, Gavin.
RE: vpopmail?
take a look http://inter7.com/vpopmail/ _ Sebastian Ezequiel Ovide
Re: Upgrade a mail server
On Thu, Feb 14, 2002 at 10:33:49AM +0100, Javier Castillo Alcibar wrote: > Hi all!! > > I have a debian 2.1 email server, with sendmail as smtp server, and > qpopper as POP3 server. This box hosts several domains (about 100 different > domains, using virtual hosting), with a total of 1300 users. Because the > auth method is based on /etc/passwd, I have 1300 unix user accounts, one per > mailbox, of course. > > This is becomming not scalable, and I want to start to use a mail > server with auth based on sql, using MySQL for example. I am thinking in use > a debian woody( I'll wait till woody becomes stable), with sendmail as smtp > server, but I am not sure about the pop3 daemon I have to use. Why isn't it scalable? If the getpwent() calls are getting slow look at using libnss-db: This package supports using the "db" mechanism for Name Service Switch. Glibc 2.1.92 and before included this module, but it has been since been split and is now a separate package. If you use .db files for your passwd, shadow, group or other naming databases, then you need this module. Looking things up in db files is simple, fast, and reliable. (An SQL server is complex, slow for small data sets [ie, has a far higher startup cost than a flat file], and the complexity can jeapordize the reliability.) Keeping the db file sync'd is done via 'make'. (See the 'pam_make' module for fun.) > My questions are: > > 1? what POP3 server do you recomend me to use, in order to use sql > method for auth.?? If you still insist on SQL, use something like nss-mysql: This package provides a Name Service Switch that allows your MySQL server act as a name service. It currently features full account support (shadow,passwd and group). Installing nscd will make lookups much faster. (Ie, nscd may cover up some of the startup costs by caching results.) Then you can use whatever servers you want. > 2? what's is the way to "transfer" the info (users, passwords, > emails, etc) from my old box to my new box and database?? A bit of perl to parse /etc/shadow into the database? I'd still (and do) use libnss-db. Simple is good. I love MySQL, but things like /etc/(passwd|shadow) are too critical to trust to something as complex as MySQL when the db libraries are much much more reliable.
RE: exim.conf
fyi: I was able to chmod 755 my root directory and my web server directory...
so I can get shell access and my web serber seems to be working now
bernie
-Original Message-
From: Bernie Berg
Sent: Friday, February 15, 2002 3:36 PM
To: Michael Merritt
Cc: debian-isp@lists.debian.org
Subject: RE: exim.conf
I ran the convert-and-create script, and it seemed to do the trick. The only
problem is that is must have also reset some permissions, becuase I cant get a
shell with any user besides root now, and I got "forbidden" when accessing my
web server.
any ideas on what happended?
bernie
-Original Message-
From: Michael Merritt [mailto:[EMAIL PROTECTED]
Sent: Friday, February 15, 2002 2:30 PM
To: Bernie Berg
Cc: debian-isp@lists.debian.org
Subject: Fwd: exim.conf
The main things to look at are maildir_delivery: in the TRANSPORTS section.
Copy that verbatim into your /etc/exim/exim.conf file.
Then look for this (or modify it) at the end of the DIRECTORS section:
localuser:
driver = localuser
transport = maildir_delivery
You'll see I've got some virtual domain stuff that may or may not apply to
you, but this should at least give you the general idea.
If you're delivering mail into /var/spool/mail/$USER now, you'll need to get
the convert-and-create.pl script from qmail.org and run it to convert your
existing user mailboxes from mbox to maildir.
Hope this gets you started. Hopefull I'll have the time RSN to detail my
setup on my site. I've done some other stuff w/ exim+courier as well that
may help some other ppl.
-Michael
-- Forwarded Message --
Subject: exim.conf
Date: Fri, 15 Feb 2002 14:24:42 -0600
From: Michael Merritt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
# This is the main exim configuration file.
# It was originally generated by `eximconfig', part of the exim package
# distributed with Debian, but it may edited by the mail system
administrator. # This file originally generated by eximconfig at Fri Feb 1
17:06:40 CST 2002 # See exim info section for details of the things that can
be configured here.
# Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file.
# This file is divided into several parts, all but the last of which are
# terminated by a line containing the word "end". The parts must appear
# in the correct order, and all must be present (even if some of them are
# in fact empty). Blank lines, and lines starting with # are ignored.
##
#MAIN CONFIGURATION SETTINGS #
##
# Specify the domain you want to be added to all unqualified addresses
# here. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.
qualify_domain = miklm.com
# If you want unqualified recipient addresses to be qualified with a
different # domain to unqualified sender addresses, specify the recipient
domain here. # If this option is not set, the qualify_domain value is used.
# qualify_recipient =
# Specify your local domains as a colon-separated list here. If this option
# is not set (i.e. not mentioned in the configuration file), the
# qualify_recipient value is used as the only local domain. If you do not
want # to do any local deliveries, uncomment the following line, but do not
supply # any data for it. This sets local_domains to an empty string, which
is not # the same as not mentioning it at all. An empty string specifies
that there # are no local domains; not setting it at all causes the default
value (the # setting of qualify_recipient) to be used.
local_domains = /etc/exim/aliases.conf:/etc/exim/virtuals.conf
# Allow mail addressed to our hostname, or to our IP address.
local_domains_include_host = true
local_domains_include_host_literals = true
# Domains we relay for; that is domains that aren't considered local but we
# accept mail for them.
relay_domains =
/etc/exim/aliases.conf:/etc/exim/virtuals.conf:/etc/exim/relays.conf
# If this is uncommented, we accept and relay mail for all domains we are
# in the DNS as an MX for.
#relay_domains_include_local_mx = true
# No local deliveries will ever be run under the uids of these users (a
colon- # separated list). An attempt to do so gets changed so that it runs
under the # uid of "nobody" instead. This is a paranoic safety catch. Note
the default # setting means you cannot deliver mail addressed to root as if
it were a # normal user. This isn't usually a problem, as most sites have an
alias for # root that redirects such mail to a human administrator.
never_users = root
# The setting below causes Exim to do a re
Re: 3dmd and kernel 2.4.17
> > You create your file systems with a label, for example > mke2fs -L data1 /dev/sdb1 > > You can then mount /dev/sdb1 by using mount -L data1 > or LABEL=data1 in /etc/fstab. > Okay, I see what you are saying. We already put labels on our filesystems (not for mounting, but for clarity so we know what each partition is for). But what would happen if (for example) sda1, sdb5, and sdc3 all have the label "boot". If you do "mount -L boot", which would it load? > Of course, this works only for filesystems, not raw > devices. > It would not be very useful if it referred to raw devices anyway. > I am using this on our 160 file servers equipped with > a total of 390 3ware boards and more than 2000 disks. So you probably already have a proven way to get around the problem... Or else you'd have a HUGE headache any time an array goes funny ;-) > > -Original Message- > From: Jason Lim [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 14, 2002 10:27 PM > To: fabien; Peter L. Ashford > Cc: Timothy Demarest; [EMAIL PROTECTED] > Subject: Re: 3dmd and kernel 2.4.17 > > > > To overcome this "problem" you can mount your file > > systems using labels instead of physical disks/volumes (aka /dev/sdX) > > > > See mke2fs -L option, and mount -L option. > > > > Great advice... but is it really that useful? > > in man mount: > >-L label > Mount the partition that has the specified label. > > in man mke2fs > >-L Set the volume label for the filesystem. > > > That would suggest that if we gave it "/dev/sda" and told it to mount a > partition called "boot", then it would load, for example, /dev/sda2. > > But that doesn't really solve the problem that /dev/sda may NOT be the > actual disk/array you want loaded. We're not talking about the > partitions... because that is one thing we can get right. Its the problem > is sda becoming sdb if whatever is on port0 (the preceding port) fails or > becomes independent. > > the 3ware bios does not seem to have the intelligence or ability to set > the "array order", so that a arrays will ALWAYS load up in a particular > order, regardless of whatever changes are made, or what ports the drives > are on ,etc. > > Does this make sense? Or is there already a way to do this? > > > >
RE: exim.conf
I ran the convert-and-create script, and it seemed to do the trick. The only
problem is that is must have also reset some permissions, becuase I cant get a
shell with any user besides root now, and I got "forbidden" when accessing my
web server.
any ideas on what happended?
bernie
-Original Message-
From: Michael Merritt [mailto:[EMAIL PROTECTED]
Sent: Friday, February 15, 2002 2:30 PM
To: Bernie Berg
Cc: debian-isp@lists.debian.org
Subject: Fwd: exim.conf
The main things to look at are maildir_delivery: in the TRANSPORTS section.
Copy that verbatim into your /etc/exim/exim.conf file.
Then look for this (or modify it) at the end of the DIRECTORS section:
localuser:
driver = localuser
transport = maildir_delivery
You'll see I've got some virtual domain stuff that may or may not apply to
you, but this should at least give you the general idea.
If you're delivering mail into /var/spool/mail/$USER now, you'll need to get
the convert-and-create.pl script from qmail.org and run it to convert your
existing user mailboxes from mbox to maildir.
Hope this gets you started. Hopefull I'll have the time RSN to detail my
setup on my site. I've done some other stuff w/ exim+courier as well that
may help some other ppl.
-Michael
-- Forwarded Message --
Subject: exim.conf
Date: Fri, 15 Feb 2002 14:24:42 -0600
From: Michael Merritt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
# This is the main exim configuration file.
# It was originally generated by `eximconfig', part of the exim package
# distributed with Debian, but it may edited by the mail system
administrator. # This file originally generated by eximconfig at Fri Feb 1
17:06:40 CST 2002 # See exim info section for details of the things that can
be configured here.
# Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file.
# This file is divided into several parts, all but the last of which are
# terminated by a line containing the word "end". The parts must appear
# in the correct order, and all must be present (even if some of them are
# in fact empty). Blank lines, and lines starting with # are ignored.
##
#MAIN CONFIGURATION SETTINGS #
##
# Specify the domain you want to be added to all unqualified addresses
# here. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.
qualify_domain = miklm.com
# If you want unqualified recipient addresses to be qualified with a
different # domain to unqualified sender addresses, specify the recipient
domain here. # If this option is not set, the qualify_domain value is used.
# qualify_recipient =
# Specify your local domains as a colon-separated list here. If this option
# is not set (i.e. not mentioned in the configuration file), the
# qualify_recipient value is used as the only local domain. If you do not
want # to do any local deliveries, uncomment the following line, but do not
supply # any data for it. This sets local_domains to an empty string, which
is not # the same as not mentioning it at all. An empty string specifies
that there # are no local domains; not setting it at all causes the default
value (the # setting of qualify_recipient) to be used.
local_domains = /etc/exim/aliases.conf:/etc/exim/virtuals.conf
# Allow mail addressed to our hostname, or to our IP address.
local_domains_include_host = true
local_domains_include_host_literals = true
# Domains we relay for; that is domains that aren't considered local but we
# accept mail for them.
relay_domains =
/etc/exim/aliases.conf:/etc/exim/virtuals.conf:/etc/exim/relays.conf
# If this is uncommented, we accept and relay mail for all domains we are
# in the DNS as an MX for.
#relay_domains_include_local_mx = true
# No local deliveries will ever be run under the uids of these users (a
colon- # separated list). An attempt to do so gets changed so that it runs
under the # uid of "nobody" instead. This is a paranoic safety catch. Note
the default # setting means you cannot deliver mail addressed to root as if
it were a # normal user. This isn't usually a problem, as most sites have an
alias for # root that redirects such mail to a human administrator.
never_users = root
# The setting below causes Exim to do a reverse DNS lookup on all incoming
# IP calls, in order to get the true host name. If you feel this is too
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.
host_lookup = *
# The setting below would, if uncommented, cause Exim to check the syntax of
# all the header
Re: SNMPD package (Vulnerabilities)
On Thu, Feb 14, 2002 at 10:12:34AM +0100, James wrote: > > For potato (?) of course. This should be pretty trivial.. Since you're in potato, it might be easier to simply download the 3 source files from the /pool directory on a debian mirror. There will be a .dsc file, a .diff file and a .orig.tar.gz file :) dpkg-source -x snmp-4.3.2_2.dsc (or whatever the filename is) cd snmp-4.3.2 debian/rules binary-arch It should tell you if you're missing any packages to complete the compile :) This is a common procedure, e.g. I use it to build recent samba packages for potato.. Cheers, Gavin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: vpopmail?
take a look http://inter7.com/vpopmail/ _ Sebastian Ezequiel Ovide -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Fwd: exim.conf
The main things to look at are maildir_delivery: in the TRANSPORTS section.
Copy that verbatim into your /etc/exim/exim.conf file.
Then look for this (or modify it) at the end of the DIRECTORS section:
localuser:
driver = localuser
transport = maildir_delivery
You'll see I've got some virtual domain stuff that may or may not apply to
you, but this should at least give you the general idea.
If you're delivering mail into /var/spool/mail/$USER now, you'll need to get
the convert-and-create.pl script from qmail.org and run it to convert your
existing user mailboxes from mbox to maildir.
Hope this gets you started. Hopefull I'll have the time RSN to detail my
setup on my site. I've done some other stuff w/ exim+courier as well that
may help some other ppl.
-Michael
-- Forwarded Message --
Subject: exim.conf
Date: Fri, 15 Feb 2002 14:24:42 -0600
From: Michael Merritt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
# This is the main exim configuration file.
# It was originally generated by `eximconfig', part of the exim package
# distributed with Debian, but it may edited by the mail system
administrator. # This file originally generated by eximconfig at Fri Feb 1
17:06:40 CST 2002 # See exim info section for details of the things that can
be configured here.
# Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file.
# This file is divided into several parts, all but the last of which are
# terminated by a line containing the word "end". The parts must appear
# in the correct order, and all must be present (even if some of them are
# in fact empty). Blank lines, and lines starting with # are ignored.
##
#MAIN CONFIGURATION SETTINGS #
##
# Specify the domain you want to be added to all unqualified addresses
# here. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.
qualify_domain = miklm.com
# If you want unqualified recipient addresses to be qualified with a
different # domain to unqualified sender addresses, specify the recipient
domain here. # If this option is not set, the qualify_domain value is used.
# qualify_recipient =
# Specify your local domains as a colon-separated list here. If this option
# is not set (i.e. not mentioned in the configuration file), the
# qualify_recipient value is used as the only local domain. If you do not
want # to do any local deliveries, uncomment the following line, but do not
supply # any data for it. This sets local_domains to an empty string, which
is not # the same as not mentioning it at all. An empty string specifies
that there # are no local domains; not setting it at all causes the default
value (the # setting of qualify_recipient) to be used.
local_domains = /etc/exim/aliases.conf:/etc/exim/virtuals.conf
# Allow mail addressed to our hostname, or to our IP address.
local_domains_include_host = true
local_domains_include_host_literals = true
# Domains we relay for; that is domains that aren't considered local but we
# accept mail for them.
relay_domains =
/etc/exim/aliases.conf:/etc/exim/virtuals.conf:/etc/exim/relays.conf
# If this is uncommented, we accept and relay mail for all domains we are
# in the DNS as an MX for.
#relay_domains_include_local_mx = true
# No local deliveries will ever be run under the uids of these users (a
colon- # separated list). An attempt to do so gets changed so that it runs
under the # uid of "nobody" instead. This is a paranoic safety catch. Note
the default # setting means you cannot deliver mail addressed to root as if
it were a # normal user. This isn't usually a problem, as most sites have an
alias for # root that redirects such mail to a human administrator.
never_users = root
# The setting below causes Exim to do a reverse DNS lookup on all incoming
# IP calls, in order to get the true host name. If you feel this is too
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.
host_lookup = *
# The setting below would, if uncommented, cause Exim to check the syntax of
# all the headers that are supposed to contain email addresses (To:, From:,
# etc). This reduces the level of bounced bounces considerably.
# headers_check_syntax
# Exim contains support for the Realtime Blocking List (RBL) that is being
# maintained as part of the DNS. See http://maps.vix.com/rbl/ for
# background. Uncommenting the following line will make Exim reject mail
# from any host whose IP address is blacklisted in the RBL at maps.vix.com.
rbl_domains = rbl.maps.vix.com
rbl_re
Re: Upgrade a mail server
On Thu, Feb 14, 2002 at 10:33:49AM +0100, Javier Castillo Alcibar wrote: > Hi all!! > > I have a debian 2.1 email server, with sendmail as smtp server, and > qpopper as POP3 server. This box hosts several domains (about 100 different > domains, using virtual hosting), with a total of 1300 users. Because the > auth method is based on /etc/passwd, I have 1300 unix user accounts, one per > mailbox, of course. > > This is becomming not scalable, and I want to start to use a mail > server with auth based on sql, using MySQL for example. I am thinking in use > a debian woody( I'll wait till woody becomes stable), with sendmail as smtp > server, but I am not sure about the pop3 daemon I have to use. Why isn't it scalable? If the getpwent() calls are getting slow look at using libnss-db: This package supports using the "db" mechanism for Name Service Switch. Glibc 2.1.92 and before included this module, but it has been since been split and is now a separate package. If you use .db files for your passwd, shadow, group or other naming databases, then you need this module. Looking things up in db files is simple, fast, and reliable. (An SQL server is complex, slow for small data sets [ie, has a far higher startup cost than a flat file], and the complexity can jeapordize the reliability.) Keeping the db file sync'd is done via 'make'. (See the 'pam_make' module for fun.) > My questions are: > > 1? what POP3 server do you recomend me to use, in order to use sql > method for auth.?? If you still insist on SQL, use something like nss-mysql: This package provides a Name Service Switch that allows your MySQL server act as a name service. It currently features full account support (shadow,passwd and group). Installing nscd will make lookups much faster. (Ie, nscd may cover up some of the startup costs by caching results.) Then you can use whatever servers you want. > 2? what's is the way to "transfer" the info (users, passwords, > emails, etc) from my old box to my new box and database?? A bit of perl to parse /etc/shadow into the database? I'd still (and do) use libnss-db. Simple is good. I love MySQL, but things like /etc/(passwd|shadow) are too critical to trust to something as complex as MySQL when the db libraries are much much more reliable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Missing /proc/sys
Jacob, Thanks! I forgot the golden rule: "Use the Source." A quick grep through the source would have saved the public humiliation. :-/ Pete -- http://www.elbnet.com ELB Internet Service, Inc. Web Design, Computer Consulting, Internet Hosting > CONFIG_SYSCTL=y > > -- > Jacob Elder > http://www.lucidpark.net/
Re: configureing courier imap
On Friday 15 February 2002 13:55 pm, Bernie Berg wrote: > Hi, > I'm running potato with the unstable packages. I've been using exim and > cucipop for some time now. I wanted to get squirrelmail working so I > installed that and courier imap. I think I'm missing some sort of imap > configuration step. I scan my box and port 143 is open and courier seems > to be running but I can't check my mail with squirrel mail. I also set up > an imap mail client to check my mail on my server and it didn't work What > do I need to do to get courier to work with exim? Is exim set up to deliver to Maildir for your users? It has to be for courier to work. I can send you the applicable configs if you need them for exim.conf -- Michael MerrittO2/CO2 Conversion Specialist [o] [EMAIL PROTECTED] | www.miklm.com | (931) 205-1392 | AIM/MSN miklm "Piracy is not a technological issue. It's a behavior issue." --Steve Jobs
configureing courier imap
Hi, I'm running potato with the unstable packages. I've been using exim and cucipop for some time now. I wanted to get squirrelmail working so I installed that and courier imap. I think I'm missing some sort of imap configuration step. I scan my box and port 143 is open and courier seems to be running but I can't check my mail with squirrel mail. I also set up an imap mail client to check my mail on my server and it didn't work What do I need to do to get courier to work with exim? thanks!! bernie www.bernieberg.com
RE: exim.conf
fyi: I was able to chmod 755 my root directory and my web server directory... so I
can get shell access and my web serber seems to be working now
bernie
-Original Message-
From: Bernie Berg
Sent: Friday, February 15, 2002 3:36 PM
To: Michael Merritt
Cc: [EMAIL PROTECTED]
Subject: RE: exim.conf
I ran the convert-and-create script, and it seemed to do the trick. The only problem
is that is must have also reset some permissions, becuase I cant get a shell with any
user besides root now, and I got "forbidden" when accessing my web server.
any ideas on what happended?
bernie
-Original Message-
From: Michael Merritt [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 15, 2002 2:30 PM
To: Bernie Berg
Cc: [EMAIL PROTECTED]
Subject: Fwd: exim.conf
The main things to look at are maildir_delivery: in the TRANSPORTS section.
Copy that verbatim into your /etc/exim/exim.conf file.
Then look for this (or modify it) at the end of the DIRECTORS section:
localuser:
driver = localuser
transport = maildir_delivery
You'll see I've got some virtual domain stuff that may or may not apply to
you, but this should at least give you the general idea.
If you're delivering mail into /var/spool/mail/$USER now, you'll need to get
the convert-and-create.pl script from qmail.org and run it to convert your
existing user mailboxes from mbox to maildir.
Hope this gets you started. Hopefull I'll have the time RSN to detail my
setup on my site. I've done some other stuff w/ exim+courier as well that
may help some other ppl.
-Michael
-- Forwarded Message --
Subject: exim.conf
Date: Fri, 15 Feb 2002 14:24:42 -0600
From: Michael Merritt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
# This is the main exim configuration file.
# It was originally generated by `eximconfig', part of the exim package
# distributed with Debian, but it may edited by the mail system
administrator. # This file originally generated by eximconfig at Fri Feb 1
17:06:40 CST 2002 # See exim info section for details of the things that can
be configured here.
# Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file.
# This file is divided into several parts, all but the last of which are
# terminated by a line containing the word "end". The parts must appear
# in the correct order, and all must be present (even if some of them are
# in fact empty). Blank lines, and lines starting with # are ignored.
##
#MAIN CONFIGURATION SETTINGS #
##
# Specify the domain you want to be added to all unqualified addresses
# here. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.
qualify_domain = miklm.com
# If you want unqualified recipient addresses to be qualified with a
different # domain to unqualified sender addresses, specify the recipient
domain here. # If this option is not set, the qualify_domain value is used.
# qualify_recipient =
# Specify your local domains as a colon-separated list here. If this option
# is not set (i.e. not mentioned in the configuration file), the
# qualify_recipient value is used as the only local domain. If you do not
want # to do any local deliveries, uncomment the following line, but do not
supply # any data for it. This sets local_domains to an empty string, which
is not # the same as not mentioning it at all. An empty string specifies
that there # are no local domains; not setting it at all causes the default
value (the # setting of qualify_recipient) to be used.
local_domains = /etc/exim/aliases.conf:/etc/exim/virtuals.conf
# Allow mail addressed to our hostname, or to our IP address.
local_domains_include_host = true
local_domains_include_host_literals = true
# Domains we relay for; that is domains that aren't considered local but we
# accept mail for them.
relay_domains =
/etc/exim/aliases.conf:/etc/exim/virtuals.conf:/etc/exim/relays.conf
# If this is uncommented, we accept and relay mail for all domains we are
# in the DNS as an MX for.
#relay_domains_include_local_mx = true
# No local deliveries will ever be run under the uids of these users (a
colon- # separated list). An attempt to do so gets changed so that it runs
under the # uid of "nobody" instead. This is a paranoic safety catch. Note
the default # setting means you cannot deliver mail addressed to root as if
it were a # normal user. This isn't usually a problem, as most sites have an
alias for # root that redirects such mail to a human administrator.
never_users = root
# The setting below causes Exim to do a reverse DNS lookup on
Re: 3dmd and kernel 2.4.17
> > You create your file systems with a label, for example > mke2fs -L data1 /dev/sdb1 > > You can then mount /dev/sdb1 by using mount -L data1 > or LABEL=data1 in /etc/fstab. > Okay, I see what you are saying. We already put labels on our filesystems (not for mounting, but for clarity so we know what each partition is for). But what would happen if (for example) sda1, sdb5, and sdc3 all have the label "boot". If you do "mount -L boot", which would it load? > Of course, this works only for filesystems, not raw > devices. > It would not be very useful if it referred to raw devices anyway. > I am using this on our 160 file servers equipped with > a total of 390 3ware boards and more than 2000 disks. So you probably already have a proven way to get around the problem... Or else you'd have a HUGE headache any time an array goes funny ;-) > > -Original Message- > From: Jason Lim [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 14, 2002 10:27 PM > To: fabien; Peter L. Ashford > Cc: Timothy Demarest; [EMAIL PROTECTED] > Subject: Re: 3dmd and kernel 2.4.17 > > > > To overcome this "problem" you can mount your file > > systems using labels instead of physical disks/volumes (aka /dev/sdX) > > > > See mke2fs -L option, and mount -L option. > > > > Great advice... but is it really that useful? > > in man mount: > >-L label > Mount the partition that has the specified label. > > in man mke2fs > >-L Set the volume label for the filesystem. > > > That would suggest that if we gave it "/dev/sda" and told it to mount a > partition called "boot", then it would load, for example, /dev/sda2. > > But that doesn't really solve the problem that /dev/sda may NOT be the > actual disk/array you want loaded. We're not talking about the > partitions... because that is one thing we can get right. Its the problem > is sda becoming sdb if whatever is on port0 (the preceding port) fails or > becomes independent. > > the 3ware bios does not seem to have the intelligence or ability to set > the "array order", so that a arrays will ALWAYS load up in a particular > order, regardless of whatever changes are made, or what ports the drives > are on ,etc. > > Does this make sense? Or is there already a way to do this? > > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Missing /proc/sys
On Fri, Feb 15, 2002 at 07:39:06PM +, Peter Billson wrote: > Hello *, >I have a weird problem on a server, the /proc/sys directory is not there. > The > /proc filesystem is mounted and the rest of /proc seems to be fine, but > /proc/sys and it's sub-directories are MIA. CONFIG_SYSCTL=y -- Jacob Elder http://www.lucidpark.net/
Missing /proc/sys
Hello *, I have a weird problem on a server, the /proc/sys directory is not there. The /proc filesystem is mounted and the rest of /proc seems to be fine, but /proc/sys and it's sub-directories are MIA. I have turned up a few people that have had this problem, but no answers. I'm running a 2.4.9 kernel on a modified potato machine (I have a similar set up on half-a-dozen other machines without a problem) and discovered the problem after running out of file descriptors. The machine runs fine otherwise. Help? Pete -- http://www.elbnet.com ELB Internet Service, Inc. Web Design, Computer Consulting, Internet Hosting
RE: exim.conf
I ran the convert-and-create script, and it seemed to do the trick. The only problem
is that is must have also reset some permissions, becuase I cant get a shell with any
user besides root now, and I got "forbidden" when accessing my web server.
any ideas on what happended?
bernie
-Original Message-
From: Michael Merritt [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 15, 2002 2:30 PM
To: Bernie Berg
Cc: [EMAIL PROTECTED]
Subject: Fwd: exim.conf
The main things to look at are maildir_delivery: in the TRANSPORTS section.
Copy that verbatim into your /etc/exim/exim.conf file.
Then look for this (or modify it) at the end of the DIRECTORS section:
localuser:
driver = localuser
transport = maildir_delivery
You'll see I've got some virtual domain stuff that may or may not apply to
you, but this should at least give you the general idea.
If you're delivering mail into /var/spool/mail/$USER now, you'll need to get
the convert-and-create.pl script from qmail.org and run it to convert your
existing user mailboxes from mbox to maildir.
Hope this gets you started. Hopefull I'll have the time RSN to detail my
setup on my site. I've done some other stuff w/ exim+courier as well that
may help some other ppl.
-Michael
-- Forwarded Message --
Subject: exim.conf
Date: Fri, 15 Feb 2002 14:24:42 -0600
From: Michael Merritt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
# This is the main exim configuration file.
# It was originally generated by `eximconfig', part of the exim package
# distributed with Debian, but it may edited by the mail system
administrator. # This file originally generated by eximconfig at Fri Feb 1
17:06:40 CST 2002 # See exim info section for details of the things that can
be configured here.
# Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file.
# This file is divided into several parts, all but the last of which are
# terminated by a line containing the word "end". The parts must appear
# in the correct order, and all must be present (even if some of them are
# in fact empty). Blank lines, and lines starting with # are ignored.
##
#MAIN CONFIGURATION SETTINGS #
##
# Specify the domain you want to be added to all unqualified addresses
# here. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.
qualify_domain = miklm.com
# If you want unqualified recipient addresses to be qualified with a
different # domain to unqualified sender addresses, specify the recipient
domain here. # If this option is not set, the qualify_domain value is used.
# qualify_recipient =
# Specify your local domains as a colon-separated list here. If this option
# is not set (i.e. not mentioned in the configuration file), the
# qualify_recipient value is used as the only local domain. If you do not
want # to do any local deliveries, uncomment the following line, but do not
supply # any data for it. This sets local_domains to an empty string, which
is not # the same as not mentioning it at all. An empty string specifies
that there # are no local domains; not setting it at all causes the default
value (the # setting of qualify_recipient) to be used.
local_domains = /etc/exim/aliases.conf:/etc/exim/virtuals.conf
# Allow mail addressed to our hostname, or to our IP address.
local_domains_include_host = true
local_domains_include_host_literals = true
# Domains we relay for; that is domains that aren't considered local but we
# accept mail for them.
relay_domains =
/etc/exim/aliases.conf:/etc/exim/virtuals.conf:/etc/exim/relays.conf
# If this is uncommented, we accept and relay mail for all domains we are
# in the DNS as an MX for.
#relay_domains_include_local_mx = true
# No local deliveries will ever be run under the uids of these users (a
colon- # separated list). An attempt to do so gets changed so that it runs
under the # uid of "nobody" instead. This is a paranoic safety catch. Note
the default # setting means you cannot deliver mail addressed to root as if
it were a # normal user. This isn't usually a problem, as most sites have an
alias for # root that redirects such mail to a human administrator.
never_users = root
# The setting below causes Exim to do a reverse DNS lookup on all incoming
# IP calls, in order to get the true host name. If you feel this is too
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.
host_lookup = *
# The setting below would, if uncommented, cause Exim to check the syntax of
# all the headers that ar
RE: vpopmail?
Thought up some more... I always have used qmail (even when I used freebsd, but I love Debian more) Is there an easy to learn alternative that has a good deb file? For most isp's I would assume it would have to support virtual domains. I've tried using exim, and perhaps it's just me, but I'm not big on it... I've always like the security angle of qmail too, just not the license -- Matt Andreko On-Ramp Indiana (317)774-2100 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2002 1:27 PM To: Jason Lim Cc: debian-isp@lists.debian.org Subject: Re: vpopmail? changed name to vchkpw but i sugest to install the sources !!! On Fri, 15 Feb 2002, Jason Lim wrote: > Hi, > > I was just wondering, has anyone seen vpopmail? I didn't know it had been > completely removed. > > Does anyone know what happened? > > Sincerely, > Jason > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > _ Sebastian Ezequiel Ovide -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: vpopmail?
If you decide to install from source instead, what do you do to convince apt you did that? If you have a program that needs it as a dependency ? I just always did a Apt-get install qmail-src ucspi-tcp-src Build-qmail;build-ucspi-tcp Apt-get install vchkpw I have a working mail server, as for virtual domains, I have not been able to test that much yet. -- Matt Andreko On-Ramp Indiana (317)774-2100 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2002 1:27 PM To: Jason Lim Cc: debian-isp@lists.debian.org Subject: Re: vpopmail? changed name to vchkpw but i sugest to install the sources !!! On Fri, 15 Feb 2002, Jason Lim wrote: > Hi, > > I was just wondering, has anyone seen vpopmail? I didn't know it had been > completely removed. > > Does anyone know what happened? > > Sincerely, > Jason > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > _ Sebastian Ezequiel Ovide -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: vpopmail?
changed name to vchkpw but i sugest to install the sources !!! On Fri, 15 Feb 2002, Jason Lim wrote: > Hi, > > I was just wondering, has anyone seen vpopmail? I didn't know it had been > completely removed. > > Does anyone know what happened? > > Sincerely, > Jason > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > _ Sebastian Ezequiel Ovide
Re: qpopper as POP3 server
On Fri, 15 Feb 2002, Davi Leal wrote: > Feb 15 09:44:18 excalibur xinetd[316]: FAIL: pop-3 address > from=80.25.136.215 > Note: The client address 80.25.136.215 has not a DNS entry, neither direct > nor reverse. (nslookup, dig). The /etc/hosts.allow has _only_ the "ALL: ALL" > line. Have your tried by setting up some reverse lookup (in your /etc/hosts for example)? As far as I know, xinetd always does a lookup on the IP (even without libwrap). Also, do any other hosts fail? (Just the ones without reverse lookups?) Ask the xinetd mailing list if there is an archive, where "FAIL" error is documented or tell them your situation. (http://www.synack.net/xinetd/) Jeremy C. Reed BSD software, documentation, resources, news... http://bsd.reedmedia.net/
Fwd: exim.conf
The main things to look at are maildir_delivery: in the TRANSPORTS section.
Copy that verbatim into your /etc/exim/exim.conf file.
Then look for this (or modify it) at the end of the DIRECTORS section:
localuser:
driver = localuser
transport = maildir_delivery
You'll see I've got some virtual domain stuff that may or may not apply to
you, but this should at least give you the general idea.
If you're delivering mail into /var/spool/mail/$USER now, you'll need to get
the convert-and-create.pl script from qmail.org and run it to convert your
existing user mailboxes from mbox to maildir.
Hope this gets you started. Hopefull I'll have the time RSN to detail my
setup on my site. I've done some other stuff w/ exim+courier as well that
may help some other ppl.
-Michael
-- Forwarded Message --
Subject: exim.conf
Date: Fri, 15 Feb 2002 14:24:42 -0600
From: Michael Merritt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
# This is the main exim configuration file.
# It was originally generated by `eximconfig', part of the exim package
# distributed with Debian, but it may edited by the mail system
administrator. # This file originally generated by eximconfig at Fri Feb 1
17:06:40 CST 2002 # See exim info section for details of the things that can
be configured here.
# Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file.
# This file is divided into several parts, all but the last of which are
# terminated by a line containing the word "end". The parts must appear
# in the correct order, and all must be present (even if some of them are
# in fact empty). Blank lines, and lines starting with # are ignored.
##
#MAIN CONFIGURATION SETTINGS #
##
# Specify the domain you want to be added to all unqualified addresses
# here. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.
qualify_domain = miklm.com
# If you want unqualified recipient addresses to be qualified with a
different # domain to unqualified sender addresses, specify the recipient
domain here. # If this option is not set, the qualify_domain value is used.
# qualify_recipient =
# Specify your local domains as a colon-separated list here. If this option
# is not set (i.e. not mentioned in the configuration file), the
# qualify_recipient value is used as the only local domain. If you do not
want # to do any local deliveries, uncomment the following line, but do not
supply # any data for it. This sets local_domains to an empty string, which
is not # the same as not mentioning it at all. An empty string specifies
that there # are no local domains; not setting it at all causes the default
value (the # setting of qualify_recipient) to be used.
local_domains = /etc/exim/aliases.conf:/etc/exim/virtuals.conf
# Allow mail addressed to our hostname, or to our IP address.
local_domains_include_host = true
local_domains_include_host_literals = true
# Domains we relay for; that is domains that aren't considered local but we
# accept mail for them.
relay_domains =
/etc/exim/aliases.conf:/etc/exim/virtuals.conf:/etc/exim/relays.conf
# If this is uncommented, we accept and relay mail for all domains we are
# in the DNS as an MX for.
#relay_domains_include_local_mx = true
# No local deliveries will ever be run under the uids of these users (a
colon- # separated list). An attempt to do so gets changed so that it runs
under the # uid of "nobody" instead. This is a paranoic safety catch. Note
the default # setting means you cannot deliver mail addressed to root as if
it were a # normal user. This isn't usually a problem, as most sites have an
alias for # root that redirects such mail to a human administrator.
never_users = root
# The setting below causes Exim to do a reverse DNS lookup on all incoming
# IP calls, in order to get the true host name. If you feel this is too
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.
host_lookup = *
# The setting below would, if uncommented, cause Exim to check the syntax of
# all the headers that are supposed to contain email addresses (To:, From:,
# etc). This reduces the level of bounced bounces considerably.
# headers_check_syntax
# Exim contains support for the Realtime Blocking List (RBL) that is being
# maintained as part of the DNS. See http://maps.vix.com/rbl/ for
# background. Uncommenting the following line will make Exim reject mail
# from any host whose IP address is blacklisted in the RBL at maps.vix.com.
rbl_domains = rbl.maps.vix.com
rbl_r
Re: Missing /proc/sys
Jacob, Thanks! I forgot the golden rule: "Use the Source." A quick grep through the source would have saved the public humiliation. :-/ Pete -- http://www.elbnet.com ELB Internet Service, Inc. Web Design, Computer Consulting, Internet Hosting > CONFIG_SYSCTL=y > > -- > Jacob Elder > http://www.lucidpark.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: configureing courier imap
On Friday 15 February 2002 13:55 pm, Bernie Berg wrote: > Hi, > I'm running potato with the unstable packages. I've been using exim and > cucipop for some time now. I wanted to get squirrelmail working so I > installed that and courier imap. I think I'm missing some sort of imap > configuration step. I scan my box and port 143 is open and courier seems > to be running but I can't check my mail with squirrel mail. I also set up > an imap mail client to check my mail on my server and it didn't work What > do I need to do to get courier to work with exim? Is exim set up to deliver to Maildir for your users? It has to be for courier to work. I can send you the applicable configs if you need them for exim.conf -- Michael MerrittO2/CO2 Conversion Specialist [o] [EMAIL PROTECTED] | www.miklm.com | (931) 205-1392 | AIM/MSN miklm "Piracy is not a technological issue. It's a behavior issue." --Steve Jobs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
configureing courier imap
Hi, I'm running potato with the unstable packages. I've been using exim and cucipop for some time now. I wanted to get squirrelmail working so I installed that and courier imap. I think I'm missing some sort of imap configuration step. I scan my box and port 143 is open and courier seems to be running but I can't check my mail with squirrel mail. I also set up an imap mail client to check my mail on my server and it didn't work What do I need to do to get courier to work with exim? thanks!! bernie www.bernieberg.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Missing /proc/sys
On Fri, Feb 15, 2002 at 07:39:06PM +, Peter Billson wrote: > Hello *, >I have a weird problem on a server, the /proc/sys directory is not there. The > /proc filesystem is mounted and the rest of /proc seems to be fine, but > /proc/sys and it's sub-directories are MIA. CONFIG_SYSCTL=y -- Jacob Elder http://www.lucidpark.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Missing /proc/sys
Hello *, I have a weird problem on a server, the /proc/sys directory is not there. The /proc filesystem is mounted and the rest of /proc seems to be fine, but /proc/sys and it's sub-directories are MIA. I have turned up a few people that have had this problem, but no answers. I'm running a 2.4.9 kernel on a modified potato machine (I have a similar set up on half-a-dozen other machines without a problem) and discovered the problem after running out of file descriptors. The machine runs fine otherwise. Help? Pete -- http://www.elbnet.com ELB Internet Service, Inc. Web Design, Computer Consulting, Internet Hosting -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: vpopmail?
Thought up some more... I always have used qmail (even when I used freebsd, but I love Debian more) Is there an easy to learn alternative that has a good deb file? For most isp's I would assume it would have to support virtual domains. I've tried using exim, and perhaps it's just me, but I'm not big on it... I've always like the security angle of qmail too, just not the license -- Matt Andreko On-Ramp Indiana (317)774-2100 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, February 15, 2002 1:27 PM To: Jason Lim Cc: [EMAIL PROTECTED] Subject: Re: vpopmail? changed name to vchkpw but i sugest to install the sources !!! On Fri, 15 Feb 2002, Jason Lim wrote: > Hi, > > I was just wondering, has anyone seen vpopmail? I didn't know it had been > completely removed. > > Does anyone know what happened? > > Sincerely, > Jason > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > _ Sebastian Ezequiel Ovide -- 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: vpopmail?
If you decide to install from source instead, what do you do to convince apt you did that? If you have a program that needs it as a dependency ? I just always did a Apt-get install qmail-src ucspi-tcp-src Build-qmail;build-ucspi-tcp Apt-get install vchkpw I have a working mail server, as for virtual domains, I have not been able to test that much yet. -- Matt Andreko On-Ramp Indiana (317)774-2100 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, February 15, 2002 1:27 PM To: Jason Lim Cc: [EMAIL PROTECTED] Subject: Re: vpopmail? changed name to vchkpw but i sugest to install the sources !!! On Fri, 15 Feb 2002, Jason Lim wrote: > Hi, > > I was just wondering, has anyone seen vpopmail? I didn't know it had been > completely removed. > > Does anyone know what happened? > > Sincerely, > Jason > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > _ Sebastian Ezequiel Ovide -- 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: vpopmail?
On Fri, Feb 15, 2002 at 11:21:59AM -0500, Matt Andreko wrote: > I believe now it is in the package "vchkpw". I would wonder... vchpw you need just to check the passwords given to vpopmail. Why don't you just download it from qmail.org? You will anyway have to compile it yourself. The owner don't accept precompiled packages (why ever) - or can anybody explain that? > I have it installed, but haven't had enough time to play with it. > > > > -- > Matt Andreko > On-Ramp Indiana > (317)774-2100 > > > -Original Message- > From: Jason Lim [mailto:[EMAIL PROTECTED] > Sent: Friday, February 15, 2002 10:48 AM > To: debian-isp@lists.debian.org > Subject: vpopmail? > > Hi, > > I was just wondering, has anyone seen vpopmail? I didn't know it had > been > completely removed. > > Does anyone know what happened? > > Sincerely, > Jason > > > > -- > 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] -- "The software said it requires Windows 2000 or better, so I installed Linux"
RE: vpopmail?
I believe now it is in the package "vchkpw". I have it installed, but haven't had enough time to play with it. -- Matt Andreko On-Ramp Indiana (317)774-2100 -Original Message- From: Jason Lim [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2002 10:48 AM To: debian-isp@lists.debian.org Subject: vpopmail? Hi, I was just wondering, has anyone seen vpopmail? I didn't know it had been completely removed. Does anyone know what happened? Sincerely, Jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: vpopmail?
changed name to vchkpw but i sugest to install the sources !!! On Fri, 15 Feb 2002, Jason Lim wrote: > Hi, > > I was just wondering, has anyone seen vpopmail? I didn't know it had been > completely removed. > > Does anyone know what happened? > > Sincerely, > Jason > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > _ Sebastian Ezequiel Ovide -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: qpopper as POP3 server
On Fri, 15 Feb 2002, Davi Leal wrote: > Feb 15 09:44:18 excalibur xinetd[316]: FAIL: pop-3 address > from=80.25.136.215 > Note: The client address 80.25.136.215 has not a DNS entry, neither direct > nor reverse. (nslookup, dig). The /etc/hosts.allow has _only_ the "ALL: ALL" > line. Have your tried by setting up some reverse lookup (in your /etc/hosts for example)? As far as I know, xinetd always does a lookup on the IP (even without libwrap). Also, do any other hosts fail? (Just the ones without reverse lookups?) Ask the xinetd mailing list if there is an archive, where "FAIL" error is documented or tell them your situation. (http://www.synack.net/xinetd/) Jeremy C. Reed BSD software, documentation, resources, news... http://bsd.reedmedia.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
vpopmail?
Hi, I was just wondering, has anyone seen vpopmail? I didn't know it had been completely removed. Does anyone know what happened? Sincerely, Jason
Re: Diverting smtp traffic
Hello Jeremy On 14 Feb 2002, at 9:14, Jeremy C. Reed wrote: > > old server directly to the new one. I have tried "ipmasqadm -- > > portfw" but there is no masquerading involved and it does not work. > > Does not work? (Show us.) This machine has two network cards, one with masquerading onto a private LAN. However the second mail server is on the public side. There is already forwarding of certain ports to machines inside the LAN, which works perfectly. So the kernel must have all the correct options compiled into it. However > Try something like: > > ipmasqadm portfw -a -P tcp -L 192.168.0.1 25 -R 192.168.0.2 25 This is exactly what I am running, but it does not work. (It would work if the redirected IP was already being masqueraded.) >From /usr/share/doc/netbase/ipmasqadm/README.portfw.gz Port forwarding uses the existing masquerading scheme to do all the rewriting of packets. The masquerading table (what you see when you type netstat -M or ipfwadm -M -l) is setup as if the connection started internally. Which may give a clue why it does not work on IP's for which there is no masquerading configured. > Your remote interface needs to listen on the original IP too. Yes, I have checked that. It seems I will have to upgrade to kernel 2.4. I thought there might be an inetd replacement that could do this (with correction of the source address IP). As this is an old stable machine, and I don't want to fiddle too much, I think I will try another option - updating the mail server configuration to match that on our main server. Thanks Ian - Ian Forbes ZSD http://www.zsd.co.za Office: +27 21 683-1388 Fax: +27 21 674-1106 Snail Mail: P.O. Box 46827, Glosderry, 7702, South Africa -
Re: vpopmail?
On Fri, Feb 15, 2002 at 11:21:59AM -0500, Matt Andreko wrote: > I believe now it is in the package "vchkpw". I would wonder... vchpw you need just to check the passwords given to vpopmail. Why don't you just download it from qmail.org? You will anyway have to compile it yourself. The owner don't accept precompiled packages (why ever) - or can anybody explain that? > I have it installed, but haven't had enough time to play with it. > > > > -- > Matt Andreko > On-Ramp Indiana > (317)774-2100 > > > -Original Message- > From: Jason Lim [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 15, 2002 10:48 AM > To: [EMAIL PROTECTED] > Subject: vpopmail? > > Hi, > > I was just wondering, has anyone seen vpopmail? I didn't know it had > been > completely removed. > > Does anyone know what happened? > > Sincerely, > Jason > > > > -- > 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] -- "The software said it requires Windows 2000 or better, so I installed Linux" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: vpopmail?
I believe now it is in the package "vchkpw". I have it installed, but haven't had enough time to play with it. -- Matt Andreko On-Ramp Indiana (317)774-2100 -Original Message- From: Jason Lim [mailto:[EMAIL PROTECTED]] Sent: Friday, February 15, 2002 10:48 AM To: [EMAIL PROTECTED] Subject: vpopmail? Hi, I was just wondering, has anyone seen vpopmail? I didn't know it had been completely removed. Does anyone know what happened? Sincerely, Jason -- 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]
vpopmail?
Hi, I was just wondering, has anyone seen vpopmail? I didn't know it had been completely removed. Does anyone know what happened? Sincerely, Jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Diverting smtp traffic
Hello Jeremy On 14 Feb 2002, at 9:14, Jeremy C. Reed wrote: > > old server directly to the new one. I have tried "ipmasqadm -- > > portfw" but there is no masquerading involved and it does not work. > > Does not work? (Show us.) This machine has two network cards, one with masquerading onto a private LAN. However the second mail server is on the public side. There is already forwarding of certain ports to machines inside the LAN, which works perfectly. So the kernel must have all the correct options compiled into it. However > Try something like: > > ipmasqadm portfw -a -P tcp -L 192.168.0.1 25 -R 192.168.0.2 25 This is exactly what I am running, but it does not work. (It would work if the redirected IP was already being masqueraded.) >From /usr/share/doc/netbase/ipmasqadm/README.portfw.gz Port forwarding uses the existing masquerading scheme to do all the rewriting of packets. The masquerading table (what you see when you type netstat -M or ipfwadm -M -l) is setup as if the connection started internally. Which may give a clue why it does not work on IP's for which there is no masquerading configured. > Your remote interface needs to listen on the original IP too. Yes, I have checked that. It seems I will have to upgrade to kernel 2.4. I thought there might be an inetd replacement that could do this (with correction of the source address IP). As this is an old stable machine, and I don't want to fiddle too much, I think I will try another option - updating the mail server configuration to match that on our main server. Thanks Ian - Ian Forbes ZSD http://www.zsd.co.za Office: +27 21 683-1388 Fax: +27 21 674-1106 Snail Mail: P.O. Box 46827, Glosderry, 7702, South Africa - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: qpopper as POP3 server
From: "Jeremy C. Reed" <[EMAIL PROTECTED]>
> > qpopper 2.53-5 on xinetd.conf
>
> > $ telnet 194.224.7.3 110
> > Trying 194.224.7.3...
> > Connected to 194.224.7.3.
> > Escape character is '^]'.
> > Connection closed by foreign host.
> > $
> >
> > Though I am using the '-d' (debug) option of qpopper, it does not show
> > anything in the syslog or mail.log files due to the above try of
connection.
> > Is it posible that the qpopper daemon does not log the refused
connections?.
>
> Maybe qpopper is not even being ran.
>
> Configure your xinetd to give more logging; maybe like:
> log_type= SYSLOG local4 info
> log_on_success = PID HOST EXIT DURATION
> log_on_failure = HOST ATTEMPT
I have modified the xinetd.conf file:
service pop-3
{
socket_type = stream
protocol= tcp
wait= no
user= root
server = /usr/sbin/in.qpopper
server_args = -d
}
service pop-3
{
socket_type = stream
protocol= tcp
wait= no
user= root
server = /usr/sbin/in.qpopper
server_args = -d -t /var/log/pop3--trace-file.log -s
log_on_success = HOST USERID EXIT PID DURATION
log_on_failure = HOST ATTEMPT RECORD
log_type = SYSLOG local4 info
}
syslog
Feb 15 09:44:18 excalibur xinetd[316]: FAIL: pop-3 address
from=80.25.136.215
Feb 15 09:44:37 excalibur last message repeated 49 times
netstat --inet -n
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 1 194.224.7.3:110 80.25.136.215:42399 FIN_WAIT1
tcp 0 0 194.224.7.3:110 80.25.136.215:42398 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42397 TIME_WAIT
...
tcp 0 0 194.224.7.3:110 80.25.136.215:42337 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42336 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42335 TIME_WAIT
tcp 0 0 194.224.7.3:110 194.224.7.97:2049 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42334 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42333 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42332 TIME_WAIT
...
tcp 0 0 194.224.7.3:110 80.25.136.215:42033 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42032 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42031 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42030 TIME_WAIT
tcp 0 0 194.224.7.3:110 194.224.7.109:2057 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42400 SYN_RECV
/var/log/pop3--trace-file.log
Fri Feb 15 10:10:46 2002 [656] (v2.53) Servicing request from
"developer.ene.es" at 194.224.7.96
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] +OK QPOP (version 2.53) at excalibur.ene.es
starting. <[EMAIL PROTECTED]>
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Received: "USER jc"
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] +OK Password required for jc.
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Received: "pass x"
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Creating temporary maildrop
'/var/spool/pop/jc.pop'
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] uid = 1123, gid = 8
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Checking for old .jc.pop file
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Old .jc.pop file not found, errno (2)
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Unable to create .popbull file (20)
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] +OK jc has 0 messages (0 octets).
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Received: "STAT"
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] 0 message(s) (0 octets).
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] +OK 0 0
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Received: "QUIT"
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Performing maildrop update...
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Checking to see if all messages were deleted
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Stats: jc 0 0 0 0
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] +OK Pop server at excalibur.ene.es signing
off.
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] (v2.53) Ending request from "jc" at
(developer.ene.es) 194.224.7.96
Fri Feb 15 10:10:46 2002
> > I have checked the firewall between us and InterNet but it appears
> > accurate:
>
> What does netstat on your 194.224.7.3 system show?
> netstat --inet -n -c
>
> Maybe watch top(1) to see if qpopper is even started.
The 'top' and 'ps -el' commands show, some times, the 'in.qpopper' process
executing. I think it is due to the no-FAILed client connections. I have
used an infinite loop with 'telnet 194.224.7.3 110' from 80.25.136.215 and:
1.- the syslog shows the FAIL
2.- the /var/log/pop3--trace-file
UNSUBSCRIBE-REQUEST
Re: RAID Suggestion for webserver
Hi All RAID 0 gives the best read and write performace as the data is striped across the drives. RAID 1 gives the same write performace as a single drive but read performance is faster than a single drive (as there are always 2 drives that the data can be read from, hence the controller can choose the drive not being accessed / with it's head closest to the needed data. RAID5 give read performance a boost for the same reason as RAID0, but write performance is only slightly faster than a single drive as the array must 'stop' while the controller calculates the parity bit and writes that to a drive. Overall the chances of 2 drives failing at the same time a very small and if they do you look to your backup. Also running all your services on one box will be fine for a small setup, but if you have big plans you will quickly run our of processing power (especially with a database on the box). It would seem unlikley that the HDD transfer speed will be the bottleneck. At 02:53 14/02/2002 +0800, Jason Lim wrote: > It shouldn't be any worse write performance than RAID-5, and read performance > should be good! > With RAID 5, isn't the data distributed (along with parity data) to the various disks, while with RAID 1 the whole data is written to all disks? I'm guessing that each disk writing only part of the data to each disk would lead to faster performance (as long as the controller can handle sending the data to all the disks that fast). Read performance... if it is RAID 1 i suppose it would depend on how good the read algorithm is? Worst case it would be the same as a single disk. But if it is RAID 5, wouldn't it only need to read a bit of the data from each disk (to build up the complete data)? (I may be wrong with the above information, i'm no raid expert). > Instead of having one server for 50 accounts which does everything, why not > have different servers for different services? Then you could have three web > servers for several thousand domains instead of getting a new server for > every 50... > I could see a lot of headache doing it that way, including user authentication and how to tie all the services together in a nice neat package that is easy to manage/maintain. Virtually all the publically available solutions (Plesk, Hostplus, etc.) do it on a per-server basis, and that would include Cobalt's Raqs. I suppose if we have many thousands of accounts it would be more economical to do it your way (seperate mail server, ftp server, auth server, www server, database server, etc. each specialized in both software and hardware) but we don't have THAT many customers ;-) Mostly we put lower-end clients on servers with 100-200 or so clients, with higher end clients on servers with 50 or less. Works out pretty well that way, as you can then artificially "manage" the performance you give clients (of course, this is not direct control, but it achieves the same goal). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: qpopper as POP3 server
From: "Jeremy C. Reed" <[EMAIL PROTECTED]>
> > qpopper 2.53-5 on xinetd.conf
>
> > $ telnet 194.224.7.3 110
> > Trying 194.224.7.3...
> > Connected to 194.224.7.3.
> > Escape character is '^]'.
> > Connection closed by foreign host.
> > $
> >
> > Though I am using the '-d' (debug) option of qpopper, it does not show
> > anything in the syslog or mail.log files due to the above try of
connection.
> > Is it posible that the qpopper daemon does not log the refused
connections?.
>
> Maybe qpopper is not even being ran.
>
> Configure your xinetd to give more logging; maybe like:
> log_type= SYSLOG local4 info
> log_on_success = PID HOST EXIT DURATION
> log_on_failure = HOST ATTEMPT
I have modified the xinetd.conf file:
service pop-3
{
socket_type = stream
protocol= tcp
wait= no
user= root
server = /usr/sbin/in.qpopper
server_args = -d
}
service pop-3
{
socket_type = stream
protocol= tcp
wait= no
user= root
server = /usr/sbin/in.qpopper
server_args = -d -t /var/log/pop3--trace-file.log -s
log_on_success = HOST USERID EXIT PID DURATION
log_on_failure = HOST ATTEMPT RECORD
log_type = SYSLOG local4 info
}
syslog
Feb 15 09:44:18 excalibur xinetd[316]: FAIL: pop-3 address
from=80.25.136.215
Feb 15 09:44:37 excalibur last message repeated 49 times
netstat --inet -n
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 1 194.224.7.3:110 80.25.136.215:42399 FIN_WAIT1
tcp 0 0 194.224.7.3:110 80.25.136.215:42398 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42397 TIME_WAIT
...
tcp 0 0 194.224.7.3:110 80.25.136.215:42337 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42336 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42335 TIME_WAIT
tcp 0 0 194.224.7.3:110 194.224.7.97:2049 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42334 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42333 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42332 TIME_WAIT
...
tcp 0 0 194.224.7.3:110 80.25.136.215:42033 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42032 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42031 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42030 TIME_WAIT
tcp 0 0 194.224.7.3:110 194.224.7.109:2057 TIME_WAIT
tcp 0 0 194.224.7.3:110 80.25.136.215:42400 SYN_RECV
/var/log/pop3--trace-file.log
Fri Feb 15 10:10:46 2002 [656] (v2.53) Servicing request from
"developer.ene.es" at 194.224.7.96
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] +OK QPOP (version 2.53) at excalibur.ene.es
starting. <[EMAIL PROTECTED]>
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Received: "USER jc"
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] +OK Password required for jc.
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Received: "pass x"
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Creating temporary maildrop
'/var/spool/pop/jc.pop'
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] uid = 1123, gid = 8
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Checking for old .jc.pop file
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Old .jc.pop file not found, errno (2)
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Unable to create .popbull file (20)
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] +OK jc has 0 messages (0 octets).
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Received: "STAT"
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] 0 message(s) (0 octets).
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] +OK 0 0
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Received: "QUIT"
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Performing maildrop update...
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Checking to see if all messages were deleted
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] Stats: jc 0 0 0 0
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] +OK Pop server at excalibur.ene.es signing
off.
Fri Feb 15 10:10:46 2002
Fri Feb 15 10:10:46 2002 [656] (v2.53) Ending request from "jc" at
(developer.ene.es) 194.224.7.96
Fri Feb 15 10:10:46 2002
> > I have checked the firewall between us and InterNet but it appears
> > accurate:
>
> What does netstat on your 194.224.7.3 system show?
> netstat --inet -n -c
>
> Maybe watch top(1) to see if qpopper is even started.
The 'top' and 'ps -el' commands show, some times, the 'in.qpopper' process
executing. I think it is due to the no-FAILed client connections. I have
used an infinite loop with 'telnet 194.224.7.3 110' from 80.25.136.215 and:
1.- the syslog shows the FAIL
2.- the /var/log/pop3--trace-fil
UNSUBSCRIBE-REQUEST
Re: RAID Suggestion for webserver
Hi All RAID 0 gives the best read and write performace as the data is striped across the drives. RAID 1 gives the same write performace as a single drive but read performance is faster than a single drive (as there are always 2 drives that the data can be read from, hence the controller can choose the drive not being accessed / with it's head closest to the needed data. RAID5 give read performance a boost for the same reason as RAID0, but write performance is only slightly faster than a single drive as the array must 'stop' while the controller calculates the parity bit and writes that to a drive. Overall the chances of 2 drives failing at the same time a very small and if they do you look to your backup. Also running all your services on one box will be fine for a small setup, but if you have big plans you will quickly run our of processing power (especially with a database on the box). It would seem unlikley that the HDD transfer speed will be the bottleneck. At 02:53 14/02/2002 +0800, Jason Lim wrote: > > It shouldn't be any worse write performance than RAID-5, and read >performance > > should be good! > > > >With RAID 5, isn't the data distributed (along with parity data) to the >various disks, while with RAID 1 the whole data is written to all disks? >I'm guessing that each disk writing only part of the data to each disk >would lead to faster performance (as long as the controller can handle >sending the data to all the disks that fast). > >Read performance... if it is RAID 1 i suppose it would depend on how good >the read algorithm is? Worst case it would be the same as a single disk. >But if it is RAID 5, wouldn't it only need to read a bit of the data from >each disk (to build up the complete data)? > >(I may be wrong with the above information, i'm no raid expert). > > > Instead of having one server for 50 accounts which does everything, why >not > > have different servers for different services? Then you could have >three web > > servers for several thousand domains instead of getting a new server for > > every 50... > > > >I could see a lot of headache doing it that way, including user >authentication and how to tie all the services together in a nice neat >package that is easy to manage/maintain. Virtually all the publically >available solutions (Plesk, Hostplus, etc.) do it on a per-server basis, >and that would include Cobalt's Raqs. > >I suppose if we have many thousands of accounts it would be more >economical to do it your way (seperate mail server, ftp server, auth >server, www server, database server, etc. each specialized in both >software and hardware) but we don't have THAT many customers ;-) Mostly >we put lower-end clients on servers with 100-200 or so clients, with >higher end clients on servers with 50 or less. Works out pretty well that >way, as you can then artificially "manage" the performance you give >clients (of course, this is not direct control, but it achieves the same >goal). > > >-- >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]
You have been unsubscribed from SuperHouses
Hello, This is to inform you that your request to unsubscribe from SuperHouses has been completed. Regards, Yahoo! Groups Customer Care Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Please reply to unsubscribe from SuperHouses
Hello, We have received a request from you to unsubscribe from the SuperHouses group. Please confirm your request by replying to this message. If you do not wish to unsubscribe from SuperHouses, please ignore this message. Regards, Yahoo! Groups Customer Care Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Welcome to SuperHouses
Hello, Welcome to the SuperHouses group at Yahoo! Groups, a free, easy-to-use email group service. Please take a moment to review this message. To learn more about the SuperHouses group, please visit http://groups.yahoo.com/group/SuperHouses To start sending messages to members of this group, simply send email to [EMAIL PROTECTED] If you do not wish to belong to SuperHouses, you may unsubscribe by sending an email to [EMAIL PROTECTED] To see and modify all of your groups, go to http://groups.yahoo.com/mygroups Regards, Moderator, SuperHouses Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Please confirm your request to subscribe to SuperHouses
Hello, We have received your request to join the SuperHouses group at Yahoo! Groups, home to free, easy-to-use email groups. To become a member of the SuperHouses group, please confirm your request by replying to this message. If you did not request, or do not want, a membership in the SuperHouses group, please accept our apologies and ignore this message. Regards, Yahoo! Groups Customer Care P.S. If you would like to learn more about the SuperHouses group, please visit http://groups.yahoo.com/group/SuperHouses Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
