Re: [qmailadmin] QmailAdmin 1.2.0-rc2 released
Tom Collins wrote (at Mon, Jan 05, 2004 at 06:30:28PM -0700): On Jan 4, 2004, at 1:21 PM, Philipp Wagner wrote: But I found something else, I don't know if that is going to be a bug or only a display-error: I ran configure with --enable-htmldir=/customer/, and the image dir seems to be set wrong. I didn't install it yet, I only ran configure and make. Probably it'd a good idea to remove all ending slashes from the paths in configure. html dir = /customer/ image dir = /customer//images/qmailadmin I don't think doubled slashes are a problem. I don't know enough shell scripting to strip a trailing / off of html dir. If anyone has a simple method (sed? awk?) we can throw it in. We could also use a check for someone starting a path with ~ instead of /. path=`echo $path | sed -e 's#//#/#g'` will at least remove double-slashes, but I also don't see it as a problem. If you see that happen, reconfigure it without the trailing slash. -- Casey Zacek Senior Engineer NeoSpire, Inc.
Re: [qmailadmin] Re: Please take a look...
me too Jonathan Shaw wrote (at Wed, Dec 31, 2003 at 11:28:34AM -0700): I like it. -Jonathan Rick Widmer writes: I would apreciate if anyone interested in QmailAdmin would take a look at the following URL, and tell me how you would feel if that was the administrator's main menu in a future version of QmailAdmin. http://www.developersdesk.com/qmailadmin/ QmailAdmin would only generate the table of email account information. The heading, left side menu and copyright notice are in my header and footer files. I like the idea of seeing all types of accounts in one place rather than having to know what [EMAIL PROTECTED] is before you can edit/view its properties. This is currently just a static page. I realize it will need page breaks, first letter links and a search function, but my domain is pretty small. Anyway... is it worth more work? Rick -- Casey Zacek Senior Engineer NeoSpire, Inc.
Re: non-postmaster administrators
Hubbard, David spoke forth with the blessed manuscript: If anything, I'd like that as a configurable option on a per-domain basis. I fully agree there. -Original Message- From: Bill Shupp [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 26, 2001 5:59 PM Subject: non-postmaster administrators Now that the multiple administrator idea is integrated, seems to me the next logical step would be to allow the postmaster (and other admins?) the right to grant admin privileges to others. What do you folks think? Should this be the function only of the system administrator? Or maybe an option in the qmailadmin-limits file so that it's turned off by default, but can be turned on on a per domain basis? -- -- Casey Zacek Senior Staff Engineer NeoSpire, Inc.
Re: 0.83 patch
I totally agree with this. I am going to have a real bitch of a time migrating my current email system to vpopmail because of the current limitation. Brad Dameron spoke forth with the blessed manuscript: Speaking of MySQL. There is one feature that should be implemented. There should no longer be a requirement to use postmaster as the admininistrator. There should be an additional entry in the database that says if a user is a admin or not. This would allow different usernames as well as multiple admin's as requested from some of my users. --- Brad Dameron Network Account Executive TSCNet Inc. www.tscnet.com Silverdale, WA. 1-888-8TSCNET -Original Message- From: Bill Shupp [mailto:[EMAIL PROTECTED]] Sent: Saturday, September 22, 2001 9:00 PM To: [EMAIL PROTECTED] Subject: 0.83 patch Ken, all: I've posted a patch that brings qmailadmin 0.82 to a 0.83 candidate: ChangeLog: http://shupp.org/patches/ChangeLog INSTALL: cd qmailadmin-0.82 lynx --source http://shupp.org/patches/0.83-patch.gz | patch -p0 ./configure options make ; make install-strip I've tested it with both cdb and mysql modules, and seems to work. Please report any issues to the list. Cheers, Bill Shupp -- -- Casey Zacek Senior Staff Engineer NeoSpire, Inc.
