[vchkpw] RFC 3514
I know its not list related, but it could affect all of us...lol -Chris -- From: ftp://ftp.rfc-editor.org/in-notes/rfc3514.txt Network Working GroupS. Bellovin Request for Comments: 3514AT&T Labs Research Category: Informational 1 April 2003 The Security Flag in the IPv4 Header Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. Abstract Firewalls, packet filters, intrusion detection systems, and the like often have difficulty distinguishing between packets that have malicious intent and those that are merely unusual. We define a security flag in the IPv4 header as a means of distinguishing the two cases. 1. Introduction Firewalls [CBR03], packet filters, intrusion detection systems, and the like often have difficulty distinguishing between packets that have malicious intent and those that are merely unusual. The problem is that making such determinations is hard. To solve this problem, we define a security flag, known as the "evil" bit, in the IPv4 [RFC791] header. Benign packets have this bit set to 0; those that are used for an attack will have the bit set to 1. 1.1. Terminology The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in [RFC2119]. 2. Syntax The high-order bit of the IP fragment offset field is the only unused bit in the IP header. Accordingly, the selection of the bit position is not left to IANA. Bellovin Informational [Page 1] RFC 3514 The Security Flag in the IPv4 Header 1 April 2003 The bit field is laid out as follows: 0 +-+ |E| +-+ Currently-assigned values are defined as follows: 0x0 If the bit is set to 0, the packet has no evil intent. Hosts, network elements, etc., SHOULD assume that the packet is harmless, and SHOULD NOT take any defensive measures. (We note that this part of the spec is already implemented by many common desktop operating systems.) 0x1 If the bit is set to 1, the packet has evil intent. Secure systems SHOULD try to defend themselves against such packets. Insecure systems MAY chose to crash, be penetrated, etc. 3. Setting the Evil Bit There are a number of ways in which the evil bit may be set. Attack applications may use a suitable API to request that it be set. Systems that do not have other mechanisms MUST provide such an API; attack programs MUST use it. Multi-level insecure operating systems may have special levels for attack programs; the evil bit MUST be set by default on packets emanating from programs running at such levels. However, the system MAY provide an API to allow it to be cleared for non-malicious activity by users who normally engage in attack behavior. Fragments that by themselves are dangerous MUST have the evil bit set. If a packet with the evil bit set is fragmented by an intermediate router and the fragments themselves are not dangerous, the evil bit MUST be cleared in the fragments, and MUST be turned back on in the reassembled packet. Intermediate systems are sometimes used to launder attack connections. Packets to such systems that are intended to be relayed to a target SHOULD have the evil bit set. Some applications hand-craft their own packets. If these packets are part of an attack, the application MUST set the evil bit by itself. In networks protected by firewalls, it is axiomatic that all attackers are on the outside of the firewall. Therefore, hosts inside the firewall MUST NOT set the evil bit on any packets. Bellovin Informational [Page 2] RFC 3514 The Security Flag in the IPv4 Header 1 April 2003 Because NAT [RFC3022] boxes modify packets, they SHOULD set the evil bit on such packets. "Transparent" http and email proxies SHOULD set the evil bit on their reply packets to the innocent client host. Some hosts scan other hosts in a fashion that can alert intrusion detection systems. If the scanning is part of a benign research project, the evil bit MUST NOT be set. If the scanning per se is innocent, but the ultimate intent is evil and the destination site has such an intrusion detection system, the evil bit SHOULD be set. 4. Pr
RE: [vchkpw] Courier IMAP & vchkpw problem
This problem has been covered many many times. Check archives. Hint = --with-authvchkpw \ --without-explicitsync \ --without-authpwd \ --without-authshadow \ --without-authpam \ --without-authuserdb \ --without-authcram \ --without-authldap \ --without-authmysql \ --without-authpgsql \ --without-authdaemon \ --without-authcustom Good luck. On Tuesday, May 27, 2003, at 08:33 PM, Rob Francis wrote: > Hi, > > I was happily using vpopmail 5.2.1 and qmailadmin. Everything was fine. > > However, our clients demanded some form of webmail access, so after > trying a > few packages, I settled for SquirrelMail (PHP pages that we could set > to our > needs). SquirrelMail requires an IMAP server for authentication and > Courier-IMAP seems to be the fastest around and recommended by most > groups. > > Everything worked wonderfully EXCEPT for the fact that you could only > authenticate about 3 times before getting a username/password unknown > error. > If I restart the Courier authentication daemon it works for another 3 > times. > I even tried setting up a cron job to run a script as root that > restarts the > Courier authentication daemon every minute. > > The Courier IMAP list was the first place I searched for help but they > were > adamant that the problem is with vchkpw and that I should upgrade to > version > 5.3.20. I have done this but still have the same problem. > > Any suggestions? Has anyone else had this problem? > >
RE: [vchkpw] Courier IMAP & vchkpw problem
uummm...isn't squirrelmail php? Did you mean recompile courier-imap minus all the authentication modules aside from vchkpw? -Chris -Original Message- From: Rick Root [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2003 9:27 AM Cc: [EMAIL PROTECTED] Subject: Re: [vchkpw] Courier IMAP & vchkpw problem On Tuesday, May 27, 2003, at 08:33 PM, Rob Francis wrote: > >Any suggestions? Has anyone else had this problem? Recompile squirrelmail and make sure it ONLY uses authvchkpw... get rid of tha authdaemon and all the other crap... see the previous response in this thread. that authdaemon is nothing but trouble... I had the same problem with sqwebmail. It creates more problems than it solves for most users, if you ask me. - Rick
cdb files
once the vpasswd database starts gathering thousands and hundreds of thousands of users...is it divided up into smaller counterparts?
pop trouble
i have recently installed latest versions of qmail, vpopmail, sqwebmail, tcpserver, qmailadmin. all aspects of email operation seem to be working fine except pop authentication. no trouble doing sending and recieving via webmail...however...if i try to use an email client like outlook or eudora...my user info is rejected. here are my compile options. ./configure --enable-roaming-users=y --enable-tcprules-prog=/usr/local/bin/t cprules --enable-logging=e --enable-auth-logging=y --enable-tcpserver-file=/ etc/tcprules/tcp.smtp --enable-hardquota=1000
RE: pop trouble
/var/log/messages - no errors found anywhere in the logs
May 14 17:00:21 que qmail: qmail-send shutdown succeeded
May 14 17:00:21 que qmail: rc startup succeeded
May 14 17:00:59 que qmail: qmail-send shutdown succeeded
May 14 17:00:59 que qmail: rc startup succeeded
/var/log/maillog - delivery to and from email addresses works fine...using
sqwebmail
May 14 20:46:02 que qmail: 989844362.830558 info msg 327056: bytes 1135 from
<[EMAIL PROTECTED]> qp 7776 uid 51
May 14 20:46:02 que qmail: 989844362.835234 starting delivery 3: msg 327056
to local [EMAIL PROTECTED]
May 14 20:46:02 que qmail: 989844362.835317 status: local 1/10 remote 0/20
May 14 20:46:02 que qmail: 989844362.847662 delivery 3: success: did_0+0+1/
May 14 20:46:02 que qmail: 989844362.847771 status: local 0/10 remote 0/20
May 14 20:46:02 que qmail: 989844362.847798 end msg 327056
May 15 10:12:23 que qmail: 989892743.652691 new msg 327061
May 15 10:12:23 que qmail: 989892743.652887 info msg 327061: bytes 386 from
<[EMAIL PROTECTED]> qp 8430 uid 60
May 15 10:12:23 que qmail: 989892743.657339 starting delivery 4: msg 327061
to remote [EMAIL PROTECTED]
May 15 10:12:23 que qmail: 989892743.657439 status: local 0/10 remote 1/20
May 15 10:12:25 que qmail: 989892745.422955 delivery 4: success:
209.124.144.153_accepted_message./Remote_host_said:_250_ok_989967911_qp_2985
2/
May 15 10:12:25 que qmail: 989892745.423070 status: local 0/10 remote 0/20
May 15 10:12:25 que qmail: 989892745.423097 end msg 327061
/etc/rc.d/init.d/qmail simple startup script
start() {
# Start daemons.
echo -n $"Starting $prog: "
daemon /var/qmail/rc
/usr/local/bin/tcpserver -v -p -x /etc/tcprules/tcp.smtp.cdb -u
51 -g 50 0 smtp /var/qmail/bin/qmail-smtpd &
/usr/local/bin/tcpserver -H -R -u 51 -g 55 0 pop-3
/var/qmail/bin/qmail-popup teknistar.com /var/qmail/bin/vchkpw
/var/qmail/bin/qmail-pop3d Maildir &
RETVAL=$?
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/qmail
echo
return $RETVAL
}
stop() {
# Stop daemons.
echo -n $"Stopping $prog: "
killproc qmail-send
killall tcpserver
RETVAL=$?
[ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/qmail
echo
return $RETVAL
}
-Original Message-
From: Bill Shupp [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 14, 2001 9:43 PM
To: Chris Ochap; Mailing List Vchkpw
Subject: Re: pop trouble
on 5/14/01 11:48 PM, Chris Ochap at [EMAIL PROTECTED] spake:
> i have recently installed latest versions of qmail, vpopmail, sqwebmail,
> tcpserver, qmailadmin. all aspects of email operation seem to be working
> fine except pop authentication. no trouble doing sending and recieving
via
> webmail...however...if i try to use an email client like outlook or
> eudora...my user info is rejected. here are my compile options.
>
>
./configure --enable-roaming-users=y --enable-tcprules-prog=/usr/local/bin/t
>
cprules --enable-logging=e --enable-auth-logging=y --enable-tcpserver-file=/
> etc/tcprules/tcp.smtp --enable-hardquota=1000
What's in your logs? Please post excerpts.
-Bill
pop authentication solved
i recently posted because i was having trouble getting vpop to authenticate and couldn't for the life of me figure where my problem was. fresh installations of the latest software following instructions and reading all the literature i could find didn't seem to help. in the end it turned out to be the user i was starting pop3 with. /usr/local/bin/tcpserver -u 51 -g 50 0 smtp /var/qmail/bin/qmail-smtpd & /usr/local/bin/tcpserver -u 51 -g 55 0 pop3 /var/qmail/bin/qmail-popup host.domain.com /var/vpopmail/bin/vchkpw /var/qmail /bin/qmail-pop3d Maildir & vpopmail.vchkpw user.group = -u 60 -g 60 i had been starting pop3 using a member in the qmail user pool and didn't realize that vpopmail user is the only one who has access to the password files. all the times i recompiled and re-read could have been averted had i just checked my startup closely. i have heard some debate here and there on this mailing list about whether simple questions should be outright answered or hints/nudges should be given...and i don't know if people just ignored my earlier posting...but i am glad because i learned a lot during this whole ordeal. thanx.
mysql blues
having trouble getting mysql to work (i am quite a newbie to mysql and how it works). i can log into the server using vpopmail user and the password i chose. when logged into mysql as vpopmail user i can create and destroy databases (only ones vpopmail created). here are my compile options and settings after configure. below that is the output when i try add a test domain. everything works great using cdb auth module but i would like to learn to use mysql. any hints would be appreciated. thanx. ./configure --enable-mysql=y --enable-auth-logging=y --enable-logging=p --en able-roaming-users=y --enable-hardquota=31457280 --enable-sqwebmail-pass=y - -enable-tcprules-prog=/usr/local/bin/tcprules --enable-tcpserver-file=/var/v popmail/etc/tcp.smtp vpopmail 4.10.18 Current settings --- vpopmail directory = /var/vpopmail uid = 60 gid = 60 ip alias = OFF --enable-ip-alias-domains=n (default) address extentions = OFF --enable-qmail-ext=n (default) roaming users = ON --enable-roaming-users=y tcpserver file = /var/vpopmail/etc/tcp.smtp open_smtp file = /var/vpopmail/etc/open-smtp user quota = 31457280 -enable-hardquota=31457280 auth module = mysql --enable-mysql=y mysql replication = OFF --enable-mysql-replication=n default table optimization = many domains --enable-large-site=n default system passwords = OFF --enable-passwd=n file locking = ON --enable-file-locking=y default auth logging = ON --enable-auth-logging=y mysql clear passwd = OFF --enable-clear-passwd=n default valias processing = OFF --enable-valias=n pop syslog = show failure attempts with clear text password --enable-logging=p default domain = --enable-default-domain= auth inc = -I/usr/include/mysql auth lib = -L/usr/lib/mysql -lmysqlclient -lz [root@que vpopmail-4.10.18]# vadddomain testing.com Please enter password for postmaster: enter password again: could not connect to mysql update server could not create dir control table create table dir_control ( domain varchar(255) not null, cur_users int, level_cur int, level_max int, level_start0 int, level_start1 int, level_start2 int, level_end0 int, level_end1 int, level_end2 int, level_mod0 int, level_mod1 int, level_mod2 int, level_index0 int , level_index1 int, level_index2 int, the_dir varchar(255), primary key (domain) ) could not replace dir control table 2 replace into dir_control ( domain, cur_users, level_cur, level_max, level_start0, level_start1, level_start2, level_end0, level_end1, level_end2, level_mod0, level_mod1, level_mod2, level_index0, level_index1, level_index2, the_dir ) values ( 'dom_60', 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, '') vsql_getpw: failed select could not create dir control table create table dir_control ( domain varchar(255) not null, cur_users int, level_cur int, level_max int, level_start0 int, level_start1 int, level_start2 int, level_end0 int, level_end1 int, level_end2 int, level_mod0 int, level_mod1 int, level_mod2 int, level_index0 int , level_index1 int, level_index2 int, the_dir varchar(255), primary key (domain) ) could not create dir control table create table dir_control ( domain varchar(255) not null, cur_users int, level_cur int, level_max int, level_start0 int, level_start1 int, level_start2 int, level_end0 int, level_end1 int, level_end2 int, level_mod0 int, level_mod1 int, level_mod2 int, level_index0 int , level_index1 int, level_index2 int, the_dir varchar(255), primary key (domain) ) could not replace dir control table 2 replace into dir_control ( domain, cur_users, level_cur, level_max, level_start0, level_start1, level_start2, level_end0, level_end1, level_end2, level_mod0, level_mod1, level_mod2, level_index0, level_index1, level_index2, the_dir ) values ( 'testing.com', 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, '') vsql_getpw: failed select MySQL server has gone away mysql adduser failed Error: Unable to chdir to vpopmail/users directory
RE: another compile problem
had same problem...zlib or libz is library you need to install. -Original Message- From: Trey Nolen [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 14, 2001 8:20 AM To: [EMAIL PROTECTED] Subject: another compile problem I'm getting this when compiling the new vpopmail: gcc -I. -I/usr/include/mysql -g -O2 -Wall -c vchkpw.c gcc -g -O2 -Wall -o vchkpw vchkpw.o libvpopmail.a -L/usr/lib/mysql -lmysqlcli ent -lz -lnsl -lcrypt -lm /usr/bin/ld: cannot find -lz collect2: ld returned 1 exit status make[2]: *** [vchkpw] Error 1 make[2]: Leaving directory `/usr/local/src/vpopmail-4.10.19' make[1]: *** [all-recursive] Error 1 This is on Debian 2.3. Does anyone know where lz could be found or what package it might be in? This server was originally 2.2, and vpopmail compiled, but I had to upgrade it so that I could use the new MySQL, and it seems to have broken some libraries. Trey Nolen [EMAIL PROTECTED]
RE: mysql blues
ok false alarm...i had vpopmail as user in vmysql.h and that user didn't have rights to create database or modify existing one. everything is working good. having problem recompiling sqwebmail but that is for another list. thanx all. -Original Message- From: inter7 [mailto:inter7]On Behalf Of Ken Jones Sent: Thursday, June 14, 2001 11:03 PM To: Chris Ochap Subject: Re: mysql blues What are the contents of your vmysql.h file? Did you edit that? What OS are you using? have you tried to log into mysql from a non root shell account? Ken Jones Chris Ochap wrote: > > having trouble getting mysql to work (i am quite a newbie to mysql and how > it works). i can log into the server using vpopmail user and the password i > chose. when logged into mysql as vpopmail user i can create and destroy > databases (only ones vpopmail created). here are my compile options and > settings after configure. below that is the output when i try add a test > domain. everything works great using cdb auth module but i would like to > learn to use mysql. any hints would be appreciated. thanx. > > ./configure --enable-mysql=y --enable-auth-logging=y --enable-logging=p --en > able-roaming-users=y --enable-hardquota=31457280 --enable-sqwebmail-pass=y - > -enable-tcprules-prog=/usr/local/bin/tcprules --enable-tcpserver-file=/var /v > popmail/etc/tcp.smtp > >vpopmail 4.10.18 > Current settings > --- > > vpopmail directory = /var/vpopmail >uid = 60 >gid = 60 > ip alias = OFF --enable-ip-alias-domains=n (default) > address extentions = OFF --enable-qmail-ext=n (default) > roaming users = ON --enable-roaming-users=y > tcpserver file = /var/vpopmail/etc/tcp.smtp > open_smtp file = /var/vpopmail/etc/open-smtp > user quota = 31457280 -enable-hardquota=31457280 >auth module = mysql --enable-mysql=y > mysql replication = OFF --enable-mysql-replication=n default > table optimization = many domains --enable-large-site=n default > system passwords = OFF --enable-passwd=n > file locking = ON --enable-file-locking=y default > auth logging = ON --enable-auth-logging=y > mysql clear passwd = OFF --enable-clear-passwd=n default > valias processing = OFF --enable-valias=n > pop syslog = show failure attempts with clear text password > --enable-logging=p > default domain = --enable-default-domain= > auth inc = -I/usr/include/mysql > auth lib = -L/usr/lib/mysql -lmysqlclient -lz > > [root@que vpopmail-4.10.18]# vadddomain testing.com > Please enter password for postmaster: > enter password again: > could not connect to mysql update server > could not create dir control table create table dir_control ( domain > varchar(255) not null, cur_users int, level_cur int, level_max int, > level_start0 int, level_start1 int, level_start2 int, level_end0 int, > level_end1 int, level_end2 int, level_mod0 int, level_mod1 int, level_mod2 > int, level_index0 int , level_index1 int, level_index2 int, the_dir > varchar(255), primary key (domain) ) > could not replace dir control table 2 replace into dir_control ( domain, > cur_users, level_cur, level_max, level_start0, level_start1, level_start2, > level_end0, level_end1, level_end2, level_mod0, level_mod1, level_mod2, > level_index0, level_index1, level_index2, the_dir ) values ( 'dom_60', 1, 0, > 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, '') > > vsql_getpw: failed select > could not create dir control table create table dir_control ( domain > varchar(255) not null, cur_users int, level_cur int, level_max int, > level_start0 int, level_start1 int, level_start2 int, level_end0 int, > level_end1 int, level_end2 int, level_mod0 int, level_mod1 int, level_mod2 > int, level_index0 int , level_index1 int, level_index2 int, the_dir > varchar(255), primary key (domain) ) > could not create dir control table create table dir_control ( domain > varchar(255) not null, cur_users int, level_cur int, level_max int, > level_start0 int, level_start1 int, level_start2 int, level_end0 int, > level_end1 int, level_end2 int, level_mod0 int, level_mod1 int, level_mod2 > int, level_index0 int , level_index1 int, level_index2 int, the_dir > varchar(255), primary key (domain) ) > could not replace dir control table 2 replace into dir_control ( domain, > cur_users, level_cur, level_max, level_start0, level_start1, level_start2, > level_end0, level_end1, level_end2, level_mod0, level_mod1, level_mod2, > level_index0, level_index1, level_index2, the_dir ) values ( 'testing.com', > 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, '') > > vsql_getpw: failed select > MySQL server has gone away > mysql adduser failed > Error: Unable to chdir to vpopmail/users directory
[vchkpw] duplicate valias entries
I have noticed that you can create the same alias multiple times. [EMAIL PROTECTED] root]# valias -s aptedtech.com [EMAIL PROTECTED] -> [EMAIL PROTECTED] [EMAIL PROTECTED] -> [EMAIL PROTECTED] [EMAIL PROTECTED] -> [EMAIL PROTECTED] When a message is delivered to [EMAIL PROTECTED], 3 copies show up for [EMAIL PROTECTED] I do not know if there is some logic behind this, but it makes sense to me to disallow creating an alias that already exists just the same as you would disallow creation of an e-mail address that already exists. I guess this is a feature request or even a bug report. Thanks all. -Chris
[vchkpw] Can't We All Just Get Along
Wow, this list is beginning to look like the qmail list. Why is there so much pointless arguing and disagreement over something as simple as giving Inter7 admin access to the project on SourceForge? I don't know the staff @ Inter7 personally, but I am sure they would never do anything to hurt the development of this software. To be frank, I don't know anyone on this list, but all seem geared towards its successful progression. What is the big deal? Give them admin access, that way the user community does not have to deal with forking projects. It's ridiculous. If anything, it will form a bond between the development efforts of all parties involved and the project can flourish. I can understand that Tom is spearheading the new super-charged development effort for the project, and that is wonderfull. I simply suggested that there should be a change in the valias code, and it was done a few days later. A small testament to the power of open source development. However, if I had begun a project, worked on it for years, and then gotten busy with other things (as life often does to us), I would have a certain feeling of authority or status over the fruits of my labor, just as Inter7 obviously does. I am confident that if Inter7 is given admin rights, they will not demote anyone. I would not be so kind in my reply to Tom, as Inter7 has been, had I been told that I could not have the same level of access as he to the very project that I started & raised. True, it is a GPL project, and Tom, or whoever else, can fork away to their hearts content. But honestly people, is that really necessary? Are there any actual algorithm or implementation disagreements that would warrant a fork on this or any other related project? Everybody wants stable, fast, feature-rich, quality software. The vpopmail/vchkpw project is a suite of small, *VERY* usefull programs. Please all, can we keep this simple and pure. Tom, I mean no insult, but I do believe that you are being a little childish about this. Give the creators of the suite access, and lets see some posts on this list that actually have something to do with anything besides politics. -Chris
RE: [vchkpw] Re: Tom's fork of vpopmail (and qmailadmin)
I completely agree with every syllable. I would also love for this thread to end. -Chris > -Original Message- > From: Michael Bowe [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 09, 2003 3:35 PM > To: vpopmail list > Subject: Re: [vchkpw] Re: Tom's fork of vpopmail (and qmailadmin) > > > Ken and Inter7 deserve credit for all the work they have put > into vpopmail and the associated admin packages. > > Sourceforge is a great place for hosting open source software. > The tracker system allows bugs, patches, feature requests etc > to be handled in an orderly fashion. > > Tom deserves credit for the large amount of work he has put > into both packages since their relocation to Sourceforge. > > It is not in anyone's interests to fork these projects into > "Kens version" and "Toms version". > > So surely the best compromise/solution would be for all > parties to agree that getting a 5.4-stable out the door is the > #1 goal > > To achieve this we could : > > * Grant Ken admin privileges on Sourceforge. Even if Ken isn't > actively contributing to the development at the moment, his past > efforts warrant him to be included as an admin if he wishes > > * Tom remains also as admin, and it be confirmed that he is in > charge of releasing new 5.3.x development builds with the goal > of getting 5.4 out the door > > * Leave the project home page set as the Inter7 site. But update > the Inter7 so it refers any development downloads link back > to the Sourceforge page > > Michael. > > >
RE: [vchkpw] qmail installation script 1.3.6 final release
You're a little bit of a jerk there mister. The guy has something to contribute, let him contribute. -Chris > -Original Message- > From: Davide Giunchi [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 29, 2003 4:59 AM > To: [EMAIL PROTECTED]; Mailing Vpopmail > Subject: Re: [vchkpw] qmail installation script 1.3.6 final release > > > You must bother all the mailing lists > (vpopmail,qmailadmin,vqadmin) with your > announcement for every release??? > Please notice your update on freshmeat and doesn't bother the > mailing lists > with your "yet another qmail installation script". > > Regards > > Il 14:35, mercoledì 29 ottobre 2003, Franck ha scritto: > > Hello, > > > > A new version of the installing's script for qmail are released. > > > > All feedback are welcome for this final 1.3.6 :) > > > > > http://www.linuxpourtous.com/download/qmail/in> stall_qmail-1.3.6.tar.gz > > http://www.linuxpourtous.com/download/qmail/README > > http://www.linuxpourtous.com/download/qmail/CHANGELOG > > > > Changelog since 1.3.6-rc6 : > > > > * Testing installation script on Debian testing without error. > > * Added values.suse and values.debian for both installation. > > * This script works fine on SuSE Linux and Debian testing. > > * Added apt-debian.sh for installing all needed > softwares on Debian. > > * Minor bug fix > > > > Best regards > > -- > Davide Giunchi > > > >
RE: [vchkpw] Re: qmail installation script 1.3.6 final release
Lol...you all realize that you are generating more noise than the noise that is the root of the discussion. The installation script release updates on a vpopmail list are debateable if you really like being AAAP (As Anal As Possible). But the fact that it is a simple post about a qmail project someone is working on, which (arguably) does very much relate to vpopmail makes me believe it shouldn't be ridiculed. If you really feel the need to tell someone to post to another list, you don't have to be a terrible asshole about it right from the get-go. I think a few people on this list need to get a punching bag and/or a girl friend. PS. Franck, I say post on man. I'm gonna be setting up another MX for my company, and I'm gonna give your script a try. Peaz. -Chris > -Original Message- > From: Nick Harring [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 04, 2003 6:31 AM > Cc: [EMAIL PROTECTED] > Subject: Re: [vchkpw] Re: qmail installation script 1.3.6 > final release > > > Raboo Treed wrote: > > >>Congratulations. You've been here longer than I have. The > only thing > >>is that, even with my notoriously-poor memory, I remember > seeing MANY > >>announcements from him. At least more than one a month. > >> > >> > > > >Well lets make it a rule of tumb, only put out releases > every 3 months or > >so... > > > >Like me, I've sometimes put my releases here, but I never > put a release post > >if it's a small typo fix, and I've never heard anyone > complaining about my > >releases... > > > >Cause I would like to see releases like that, but not so > much like 2-5 times > >in a month from the same dude... this list isn't for advertising!! > > > > > > > I must say, I did go back and search and discovered that this > person did > in fact post announcements about a ridiculous number of "rc" > releases, > some of which were trivial fixes that the general public > wouldn't have > cared about. > Apparently I'm better at ignoring noise than even I'd thought. > I would think that only at major releases, with major releases being > something sane like new features and massive bugfixes, would > notification be reasonable. Even then people have pointed out it is > terribly off-topic. What I suppose would be truly nice would > be a sort > of meta qmail/vpopmail/courier/sqwebmail/squirrelmail/etc > list just for > new version announcements so that anything related to the cluster of > packages that many of use some group of would have one place to be > announced at. > -- > Nick > > >
