[qmailadmin] Possible additions
Hello, We are finally getting around to rolling out the new QmailAdmin/Vpopmail to all of our clients and we have received some suggestions on the QmailAdmin interface. I wanted to run them by the people on the list to see if these are features that others would like to see or not. If they are, I will release a patch. The first feature is the ability for a non-postmaster user to be able to see their disk usage when the log into the QmailAdmin interface. When I had wrote the quota patch for version 1.0.4, I had included this functionality along with the other quota code. Most of the quota code is intact in 1.2.1, but it seems that the non-postmaster section of the interface was dramatically changed and the ability for the user to see their quota usage was removed. It would be very easy to add it back in. I'm thinking it would go nicely under the present Quota field and would be present only on the non-postmaster section of the interface, since the postmaster interface adequately shows the disk usage. The second feature is just a simple modification. It has been brought to my attention that some people do not like putting in NOQUOTA when they wish a user to not have a quota set. I had chosen to use NOQUOTA in the 1.0.4 patch out of pure laziness, so I take full blame. It would be just as easy to have the users just leave the quota field blank for no quota. It's a minor thing, but I could see how it would get annoying to have to type in NOQUOTA when leaving it blank makes better sense. The last feature would be to clean up my old quota conversion functions and have them allocate their own memory, which could then be released once the calling code is done with it. Since it's only a script, this isn't critical, but it would be cleaner. I meant to clean it up at some point, then thought somebody else would, so it seems time. Let me know what people think of these proposed changes and whether anyone outside of our network would like to see/use them. -- Justin Hopper [EMAIL PROTECTED] UNIX Systems Engineer BSDHosting.net Hosting Division of Digital Oasys Inc. http://www.bsdhosting.net
[qmailadmin] Apache Config/Install Errors
Hello, This is my first post and at the cost of getting some nasty replies I have a question about the installation. I have been following the install guide from www.qmailrocks.org and have ran into a problem. qmail admin compiles and installs just fine. I have already installed and tested vqadmin but everytime I access http://myserver.com/cgi-bin/qmailadmin is just sends me a text file. the server was accessed 1 time before a domain and domain user was created but I cannot find the answer to my question anywhere. I am thinking apache is not rendering this file as a cgi program because it lacks an extension. I have googled for hours and tried about 50 different configs for apache and nothing seems to work. qmailadmin will only serve me a text file that looks like binary or machine language. I am very confused at this point. Please refrain from telling me how dumb this question is :), I know it's dumb but I had to ask. thank you for your help sincerely, Adam Ossenford
Re: [qmailadmin] Apache Config/Install Errors
On Monday 05 April 2004 10:07 am, Adam Ossenford wrote: Hello, [snip apache is sending me the qmailadmin binary rather than executing it] do you have your qmailadmin in a /cgi-bin or similar that is either set up as a ScriptAlias or with Options +ExecCGI in apache config? -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] Apache Config/Install Errors
A text file of binary garbage, I hope. If it is legible text, you need to find out where make install put the real QmailAdmin binary. If it is sending the program file as text data, check to make sure you have something like: ServerAlias /cgi-bin/ /path/to/cgi-bin in your Apache configuration? I may have the parm order backwards... Rick Adam Ossenford wrote: Hello, This is my first post and at the cost of getting some nasty replies I have a question about the installation. I have been following the install guide from www.qmailrocks.org and have ran into a problem. qmail admin compiles and installs just fine. I have already installed and tested vqadmin but everytime I access http://myserver.com/cgi-bin/qmailadmin is just sends me a text file. the server was accessed 1 time before a domain and domain user was created but I cannot find the answer to my question anywhere. I am thinking apache is not rendering this file as a cgi program because it lacks an extension. I have googled for hours and tried about 50 different configs for apache and nothing seems to work. qmailadmin will only serve me a text file that looks like binary or machine language. I am very confused at this point. Please refrain from telling me how dumb this question is :), I know it's dumb but I had to ask. thank you for your help sincerely, Adam Ossenford
Re: [qmailadmin] Apache Config/Install Errors
On Monday 05 April 2004 04:27 pm, Rick Widmer wrote: A text file of binary garbage, I hope. If it is legible text, you need to find out where make install put the real QmailAdmin binary. If it is sending the program file as text data, check to make sure you have something like: ServerAlias /cgi-bin/ /path/to/cgi-bin s/Server/Script/ at least, I assume that's what you mean :) -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] Possible additions
Justin Hopper wrote: Hello, We are finally getting around to rolling out the new QmailAdmin/Vpopmail to all of our clients and we have received some suggestions on the QmailAdmin interface. I wanted to run them by the people on the list to see if these are features that others would like to see or not. If they are, I will release a patch. They all sound like good ideas. Please post your patch to the SourceForge tracker: http://sourceforge.net/tracker/?group_id=6691atid=306691 I am in the process of releasing a program right now, so it may be a week or two before I have time to merge it with 1.3.0. Rick
[qmailadmin] Re: Apache Config/Install Errors
First of all, Thank you for the quick response. I have tried many combinations of configurations. I set up mime.types with a blank extension for application/x-httpd-cgi, I have changed the servers DefaultType to be application/x-httpd-cgi instead of text. Added +ExecCGI to the directory, installed to other directories and configured correctly. but to no avail, I still only receive a binary text file of the qmailadmin cgi script. I think it has to be an apache problem. I have tried script alias, setting it's own Directory container. Using the current cgi-bin directory and still the same thing happens. for some reason apache will not serve it as a cgi script. I will keep trying but no luck yet, /cgi-bin/ .cgi files work because I have tested them. for some reason it just doesn't like me. slackware 9.1, apache 1.3.29 sincerely, Adam Ossenford
Re: [qmailadmin] Re: Apache Config/Install Errors
Adam Ossenford wrote: First of all, Thank you for the quick response. I have tried many combinations of configurations. I set up mime.types with a blank extension for application/x-httpd-cgi, I have changed the servers DefaultType to be application/x-httpd-cgi instead of text. Added +ExecCGI to the directory, installed to other directories and configured correctly. but to no avail, I still only receive a binary text file of the qmailadmin cgi script. I think it has to be an apache problem. I have tried script alias, setting it's own Directory container. Using the current cgi-bin directory and still the same thing happens. for some reason apache will not serve it as a cgi script. I will keep trying but no luck yet, /cgi-bin/ .cgi files work because I have tested them. for some reason it just doesn't like me. Mine works with ScriptAlias (Yes you were right Jeremy.) With that you can expect every program in the directory to be executed rather than sent. Several of your other choices should too. I suggest you use one of them and put another executable program in cgi-bin and see if it gets executed. That will confirm if it is an Apache problem. You do have exec permission allowed for the web user, and reload or restart Apache after all config file changes, right? Rick
Re: [qmailadmin] Possible additions
Hello, We are finally getting around to rolling out the new QmailAdmin/Vpopmail to all of our clients and we have received some suggestions on the QmailAdmin interface. I wanted to run them by the people on the list to see if these are features that others would like to see or not. If they are, I will release a patch. The first feature is the ability for a non-postmaster user to be able to see their disk usage when the log into the QmailAdmin interface. I have had this question too, great. The second feature is just a simple modification. It has been brought to my attention that some people do not like putting in NOQUOTA when they wish a user to not have a quota set. I had chosen to use NOQUOTA in the 1.0.4 patch out of pure laziness, so I take full blame. It would be just as easy to have the users just leave the quota field blank for no quota. It's a minor thing, but I could see how it would get annoying to have to type in NOQUOTA when leaving it blank makes better sense. INHO leaving this field blank should default to the default quota. Anything else would mean extra work for the postmasters, as 100% of the users use the default quota. In my opinion a N instead of NOQUOTA in this field, would be nice for no quota. Another thing the postmasters have mentioned is the location of the quota field. They think it should be placed below the real name field. They never put anything in the quota field, so this would save them a TAB. One last thing, which I think is quite funny. Some users have complained about not being able to log in to Qmailadmin. As the default User account in the login window is postmaster, they think they are about to log in as postmaster for their own account, supplying only their password. Luckily there are not many users who are this clueless ;-) Personally I think it would be more logical with the domain name as the uppermost field in the login window. I have also had requests for a link to the help-files in the add mailinglist window. -- JKvalvaag
