Re: [qmailadmin] QmailAdmin 1.2.0-pre1

2003-12-10 Thread John Johnson



I know this one is getting old, but did you 
fix it so my tmda stuff will not get removed from the .qmail files?

  - Original Message - 
  From: 
  Tom Collins 

  To: [EMAIL PROTECTED] ; [EMAIL PROTECTED] 
  
  Sent: Tuesday, December 09, 2003 10:40 
  PM
  Subject: [qmailadmin] QmailAdmin 
  1.2.0-pre1
  Well, it's about time to make a stable release. There are still 
  important thing that need to be added, but it's more important to get a stable 
  release out to match the forthcoming stable release of vpopmail 
  5.4.http://qmailadmin.sf.net/1.2.0-pre1 
  - released 9-Dec-03This is the first pre-release of what will be the 
  firststable release of QmailAdmin since 1.0.6. Pleasetest extensively 
  and report bugs to SourceForge.We are aware that configure runs twice 
  duringthe build process. This will be fixed in the 
  finalrelease.Tom Collins- More updates related to build 
  process. [826594]- Fix HTML formatting on display subscribers page.- 
  Convert HTTP_ACCEPT_LANGUAGE entries to lowercase, rename pt-BRto pt-br. 
  [852963]- Major cleanup of hooks code (fix call to execl, allow 
  blanklines, don't require entries for all hooks, pass proper 
  parameters to hook program, update documentation). [855707]- Use 
  VPOPMAIL_UMASK instead of hardcoded 0077.- Better lstat() error messages 
  in template.c.--Tom Collins - [EMAIL PROTECTED]QmailAdmin: 
  http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the 
  Sniffter hand-held Network Tester: 
http://sniffter.com/


Re: [qmailadmin] QmailAdmin 1.2.0-pre1

2003-12-10 Thread Tom Collins
On Wednesday, December 10, 2003, at 12:00  AM, John Johnson wrote:
 I know this one is getting old, but did you fix it so my tmda stuff will not get removed from the .qmail files?

I'm sorry, but that didn't make the cut for this release.  It's been 16 months since the last stable release (1.0.6), and the fix to preserve TMDA entries in .qmail files will require a significant rewrite of the code that reads and writes .qmail files.  While we're at it, the call to autorespond for vacations will go at the END of the .qmail file to avoid as many problems as possible.  We might also support qmail-autorespond as a better replacement.

I do plan to put your fix at the top of development for 1.3, and backport it to 1.2 once it's proven itself.

If anyone wants to sponsor the fix, I can make it an even higher priority.  :-)

--
Tom Collins  -  [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/ 
Info on the Sniffter hand-held Network Tester: http://sniffter.com/



Re: [qmailadmin] QmailAdmin 1.2.0-pre1

2003-12-10 Thread John Johnson



This is not good.. This makes it so you have 
to select to use the new qmailadmin
and not use tmda or use tmda and not the new 
qmailadmin. This has broken qmailadmin for me and to call it a stable 
release when something is broken is just
not fare. I am not attacking anyone just 
voicing my frustration.

-John


  - Original Message - 
  From: 
  Tom Collins 

  To: [EMAIL PROTECTED] 
  Sent: Tuesday, December 09, 2003 11:06 
  PM
  Subject: Re: [qmailadmin] QmailAdmin 
  1.2.0-pre1
  On Wednesday, December 10, 2003, at 12:00 AM, John Johnson 
  wrote:
  I know this one is 
getting old, but did you fix it so my tmda stuff will not get removed from 
the .qmail files?I'm sorry, but 
  that didn't make the cut for this release. It's been 16 months since the last 
  stable release (1.0.6), and the fix to preserve TMDA entries in .qmail files 
  will require a significant rewrite of the code that reads and writes .qmail 
  files. While we're at it, the call to autorespond for vacations will go at the 
  END of the .qmail file to avoid as many problems as possible. We might also 
  support qmail-autorespond as a better replacement.I do plan to put 
  your fix at the top of development for 1.3, and backport it to 1.2 once it's 
  proven itself.If anyone wants to sponsor the fix, I can make it an 
  even higher priority. :-)--Tom Collins - 
  [EMAIL PROTECTED]QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: 
  http://vpopmail.sf.net/ Info on the Sniffter hand-held Network 
  Tester: http://sniffter.com/


RE: [qmailadmin] QmailAdmin 1.2.0-pre1

2003-12-10 Thread Rietsch Thierry
I share the opinion from John. It would be nice if you're going to implement
the tmda-bug or however you're going to call this. This is just a wish, as
John also said, I'm not attacking anyone and I'll use qmailadmin. You've
done a great work with this product.

thx
thierry


-Original Message-
From: John Johnson [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 10. Dezember 2003 08:11
To: Tom Collins; [EMAIL PROTECTED]
Subject: Re: [qmailadmin] QmailAdmin 1.2.0-pre1


 This is not good.. This makes it so you have to select to use the new
qmailadmin
and not use tmda or use tmda and not the new qmailadmin.  This has broken
qmailadmin for me and to call it a stable release when something is broken
is just
not fare.  I am not attacking anyone just voicing my frustration.
 
-John

- Original Message - 
From: Tom Collins 
To: [EMAIL PROTECTED] 
Sent: Tuesday, December 09, 2003 11:06 PM
Subject: Re: [qmailadmin] QmailAdmin 1.2.0-pre1


On Wednesday, December 10, 2003, at 12:00 AM, John Johnson wrote:

 I know this one is getting old, but did you fix it so my tmda stuff will
not get removed from the .qmail files?


I'm sorry, but that didn't make the cut for this release. It's been 16
months since the last stable release (1.0.6), and the fix to preserve TMDA
entries in .qmail files will require a significant rewrite of the code that
reads and writes .qmail files. While we're at it, the call to autorespond
for vacations will go at the END of the .qmail file to avoid as many
problems as possible. We might also support qmail-autorespond as a better
replacement.

I do plan to put your fix at the top of development for 1.3, and backport it
to 1.2 once it's proven itself.

If anyone wants to sponsor the fix, I can make it an even higher priority.
:-)

--
Tom Collins - [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ 
Info on the Sniffter hand-held Network Tester: http://sniffter.com/



Re: [qmailadmin] QmailAdmin 1.2.0-pre1

2003-12-10 Thread Jeremy Kitchen
On Wed, 2003-12-10 at 01:10, John Johnson wrote:
  This is not good.. This makes it so you have to select to use the new
 qmailadmin
 and not use tmda or use tmda and not the new qmailadmin.  This has
 broken qmailadmin for me and to call it a stable release when
 something is broken is just
 not fare.  I am not attacking anyone just voicing my frustration.
  
 -John

Well, it's not broken.  As far as I know, qmailadmin doesn't support
TMDA functionality.  If you manually edit the .qmail files to make it
work with TMDA, then you've gone above and beyond qmailadmin's
authority.

Just like say, you edit an apache configuration you made with a gui or
web-based interface and it breaks, you can't really blame the makers of
the software, because you're doing something they didn't intend.

Also, I don't see you paying Tom or anyone else to fix the problem you
have with qmailadmin, so I don't think it's fair that you can really
whine about the fact that your needs weren't catered to personally. (I
could be mistaken, you may have paid Tom, but I'm guessing not).

Anyways, it's free software, if you want it fixed, I'm sure he'd be
happy to look at a patch that you provide :)

-Jeremy

-- 
Jeremy Kitchen
Systems Administrator
[EMAIL PROTECTED]
Kitchen @ #qmail on EFNet - Join the party!
.
Inter7 Internet Technologies, Inc.
www.inter7.com
866.528.3530 toll free
847.492.0470 int'l
847.492.0632 fax
GNUPG key ID: 93BDD6CE




Re: [qmailadmin] QmailAdmin 1.2.0-pre1

2003-12-10 Thread Jeremy Kitchen
On Wed, 2003-12-10 at 01:06, Tom Collins wrote:
 While we'reat it, the call to autorespond for vacations will go at the
 END of the.qmail file to avoid as many problems as possible.

the patch that I provided fixes autorespond so it isn't broken, and
shouldn't cause any stupid bounces.  I made it act more like Bruce's
qmail-autoresponder.  You can find the patch on the sourceforge page.

However, I also mentioned there that my patch breaks the mail robot
functionality in a way.  I will bring that up here:

autoresponders in use as vacation replies are generally supposed to
allow everything through and reply to only a few things.  That makes
sense, because you don't want to lose any mail, just make it so Jenny in
accounting knows you're at lunch when she emails you that big finance
report.  Surely you don't want that being lost in the mail :)

Auto-respond robots that exist to simply reply to incoming mail should
act differently.  They SHOULD bounce mailing list messages, because they
should try to get removed from them.  They should bounce Precendence:
bulk messages (who ever sends those anymore, eh? :) because that
shouldn't be being sent to an autoresponder anyways.  They SHOULD bounce
the message when someone emails too fast, so they know it's working.

My patch was for the vacation replies, as with the current (stable, if
you must) autoresponder, they were entirely broken.

 We might alsosupport qmail-autorespond as a better replacement.

that sounds good, but that is also 'broken' for the 'mail robot'
functionality.  Also, backwards compatibility isn't there, and having to
install two different autoresponder packages to install qmailadmin would
be kind of daunting for a new user.

Also, and as much as I love bruce and his software, his autoresponder
package is slightly more of a pain to install.  You must install his
bglibs, and if you don't want mysql support, or don't have mysql
installed or anything, you have to edit the Makefile so it'll actually
build!  

Just dropping my two cents :)


 If anyone wants to sponsor the fix, I can make it an even
 higherpriority.  :-)

as always ;)

-Jeremy
-- 
Jeremy Kitchen
Systems Administrator
[EMAIL PROTECTED]
Kitchen @ #qmail on EFNet - Join the party!
.
Inter7 Internet Technologies, Inc.
www.inter7.com
866.528.3530 toll free
847.492.0470 int'l
847.492.0632 fax
GNUPG key ID: 93BDD6CE




Re: [qmailadmin] QmailAdmin 1.2.0-pre1

2003-12-10 Thread Paul Theodoropoulos
At 08:10 AM 12/10/2003, Jeremy Kitchen wrote:
On Wed, 2003-12-10 at 01:10, John Johnson wrote:
  This is not good.. This makes it so you have to select to use the new
 qmailadmin
 and not use tmda or use tmda and not the new qmailadmin.  This has
 broken qmailadmin for me and to call it a stable release when
 something is broken is just
 not fare.  I am not attacking anyone just voicing my frustration.
Also, I don't see you paying Tom or anyone else to fix the problem you
have with qmailadmin, so I don't think it's fair that you can really
whine about the fact that your needs weren't catered to personally. (I
could be mistaken, you may have paid Tom, but I'm guessing not).
um, you might want to lighten up. he has a reasonable gripe, and he 
stipulated at the end that he was just voicing frustration. that's 
perfectly legitimate. part of what spurs a development community is voices 
from the community that uses the software. if nobody cares, then what's the 
point?

i don't use tmda, but with the absurd, horrendous volume of spam that we're 
all confronted with, i think it's a matter of time before my customers 
demand it. i'd like to see the option there, though i don't have the 
urgency of someone who is currently using it.

Anyways, it's free software, if you want it fixed, I'm sure he'd be
happy to look at a patch that you provide :)
not all of us are programmers. we appreciate the effort that goes into 
writing software. we ask for features. it's great when their implemented, 
frustrating when not, wouldn't you agree?

he voiced frustration. chill.

Paul Theodoropoulos
http://www.anastrophe.com



[qmailadmin] help:Is there a per domain enable-spam option

2003-12-10 Thread Joe Young
Question:

   Is there a per domain enable-spam option... I

thanks!

joe




Re: [qmailadmin] QmailAdmin 1.2.0-pre1

2003-12-10 Thread John Johnson

- Original Message - 
From: Jeremy Kitchen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 8:10 AM
Subject: Re: [qmailadmin] QmailAdmin 1.2.0-pre1

 Well, it's not broken.  As far as I know, qmailadmin doesn't support
 TMDA functionality.  If you manually edit the .qmail files to make it
 work with TMDA, then you've gone above and beyond qmailadmin's
 authority.

 Just like say, you edit an apache configuration you made with a gui or
 web-based interface and it breaks, you can't really blame the makers of
 the software, because you're doing something they didn't intend.

 Also, I don't see you paying Tom or anyone else to fix the problem you
 have with qmailadmin, so I don't think it's fair that you can really
 whine about the fact that your needs weren't catered to personally. (I
 could be mistaken, you may have paid Tom, but I'm guessing not).

 Anyways, it's free software, if you want it fixed, I'm sure he'd be
 happy to look at a patch that you provide :)

 It worked just fine before the code was changed. Now it's a problem it was
not in the older versions so
this tells me that there is no big chore to not break tmda in the .qmail
files and you don't have to be a smart
a$$ about it.

-John




Re: [qmailadmin] QmailAdmin 1.2.0-pre1

2003-12-10 Thread Tom Collins
On Wednesday, December 10, 2003, at 07:29  PM, John Johnson wrote:
It worked just fine before the code was changed. Now it's a problem it 
was
not in the older versions so
this tells me that there is no big chore to not break tmda in the 
.qmail
files
I can't recall if or how it worked in 1.0.6.  I do know that when it 
worked in the development releases, it allowed users to put ANYTHING in 
their .qmail file which is a bit of a security problem.  vdelivermail 
is running as vpopmail, so it would be possible for a malicious user to 
do things up to and including deleting ~vpopmail.

How do normal qmail installs handle this?  I assume that qmail-local 
usually runs as root and does a setuid() to the user's account before 
processing their .qmail file.

--
Tom Collins  -  [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/



Re: [qmailadmin] QmailAdmin 1.2.0-pre1

2003-12-10 Thread John Johnson

- Original Message - 
From: Tom Collins [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 7:34 PM
Subject: Re: [qmailadmin] QmailAdmin 1.2.0-pre1



 I can't recall if or how it worked in 1.0.6.  I do know that when it
 worked in the development releases, it allowed users to put ANYTHING in
 their .qmail file which is a bit of a security problem.  vdelivermail
 is running as vpopmail, so it would be possible for a malicious user to
 do things up to and including deleting ~vpopmail.

 How do normal qmail installs handle this?  I assume that qmail-local
 usually runs as root and does a setuid() to the user's account before
 processing their .qmail file.

  I don't need qmailadmin to allow me to put tmda settings in my .qmail
files
there is a cgi for tmda that does all that for me, I just need qmailadmin to
let the settings be and not remove them. I never have used qmailadmin in
anyway for editing settings to the .qmail files for tmda because of the nice
cgi that comes with tmda.  I have never had a problem with qmailadmin
removing
my tmda settings from the .qmail files, but I also have not upgraded now
that
qmailadmin will remove this stuff.

-John




Re: [qmailadmin] QmailAdmin 1.2.0-pre1 TMDA compatability

2003-12-10 Thread Tom Collins
[please don't cc me, the list copy is enough]

On Wednesday, December 10, 2003, at 09:35  PM, John Johnson wrote:
I don't need qmailadmin to allow me to put tmda settings in my .qmail
files
there is a cgi for tmda that does all that for me, I just need 
qmailadmin to
let the settings be and not remove them.
I understand this.

 I never have used qmailadmin in
anyway for editing settings to the .qmail files for tmda because of 
the nice
cgi that comes with tmda.  I have never had a problem with qmailadmin
removing
my tmda settings from the .qmail files, but I also have not upgraded 
now
that
qmailadmin will remove this stuff.
What version are you using?

What I'm saying is that versions 1.0.13 through 1.0.24 may have been 
good in that they didn't remove your tmda settings.  Those versions 
are bad in that they allow any user to put possibly malicious 
settings into their .qmail file.

The proper solution to all of this is to write new code to write out 
the .qmail file.  It will need to read in the old .qmail file, perhaps 
copying TMDA settings to a tmp.qmail file, then all of the new 
settings, and finally replacing .qmail with tmp.qmail.

At the same time, we'll probably replace the code that parses .qmail 
files since (as I recall), it couldn't handle the autoreponder line 
coming at the end of the file.

--
Tom Collins  -  [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/



Re: [qmailadmin] QmailAdmin 1.2.0-pre1 TMDA compatability

2003-12-10 Thread John Johnson

- Original Message - 
From: Tom Collins [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 10:22 PM
Subject: Re: [qmailadmin] QmailAdmin 1.2.0-pre1 TMDA compatability



 What version are you using?

1.0.24


 What I'm saying is that versions 1.0.13 through 1.0.24 may have been
 good in that they didn't remove your tmda settings.  Those versions
 are bad in that they allow any user to put possibly malicious
 settings into their .qmail file.

 The proper solution to all of this is to write new code to write out
 the .qmail file.  It will need to read in the old .qmail file, perhaps
 copying TMDA settings to a tmp.qmail file, then all of the new
 settings, and finally replacing .qmail with tmp.qmail.

 At the same time, we'll probably replace the code that parses .qmail
 files since (as I recall), it couldn't handle the autoreponder line
 coming at the end of the file.

Well maybe you can have it look for the word tmda and if it's there then
tell it to not mess
with that line or something like that... That's the only thing I can think
of myself, but again I
am not a programmer.

-John