[qmailadmin] 1.2.0rc2: bug report
Hi, here are some bugs in 1.2.0rc2: - Selecting a character in the char list at the bottom of POP accounts will not display all of the accounts starting with that character, but only the ones that fit on the screen. This is confusing (IMHO), becaus you have to go to 'i' to list the rest of the accounts that start with h. - Deleting a POP account, but creating a forward for that POP account, will make qmailadmin create a .qmail-user file. There is no way (that I've seen) to _delete_ that forward and _recreate_ the POP account from the web interface. -- Jens Benecke (jens at spamfreemail.de) http://www.hitchhikers.de - Europaweite kostenlose Mitfahrzentrale http://www.spamfreemail.de - 100% saubere Postfächer - garantiert! http://www.rb-hosting.de - PHP ab 9? - SSH ab 19? - günstiger Traffic
Re: [qmailadmin] 1.2.0rc2: bug report
On Jan 13, 2004, at 1:46 AM, Jens Benecke wrote: here are some bugs in 1.2.0rc2: - Selecting a character in the char list at the bottom of POP accounts will not display all of the accounts starting with that character, but only the ones that fit on the screen. This is confusing (IMHO), becaus you have to go to 'i' to list the rest of the accounts that start with h. - Deleting a POP account, but creating a forward for that POP account, will make qmailadmin create a .qmail-user file. There is no way (that I've seen) to _delete_ that forward and _recreate_ the POP account from the web interface. I've added your requests to the SourceForge trackers, and they'll be considered during the 1.3 development cycle (which will hopefully start soon). -- 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/
[qmailadmin] Re: /open/ in qmailadmin's url
On Saturday, January 03, 2004 at 23:43 (which was Sunday, January 4, 2004 at 7:43 where I am) Philipp Wagner wrote: font color=red 3 Are that errormessages? I would say, simply using a div tag like div class=error and an declaration of how that should look in the template would be enough. Hmm, shouldn't that be span class=errorerrormessage/span or do these include blocklevel text in p or ul. The same would go for replacing i; or would using span break XHTML conformity (I'm not familiar with XHTML). -- Greetings, Maurice
Re: [qmailadmin] Re: /open/ in qmailadmin's url
Maurice Snellen wrote:
On Saturday, January 03, 2004 at 23:43 (which was Sunday, January 4,
2004 at 7:43 where I am) Philipp Wagner wrote:
font color=red 3
Are that errormessages? I would say, simply using a div tag like div
class=error and an declaration of how that should look in the
template would be enough.
Hmm, shouldn't that be span class=errorerrormessage/span or do
these include blocklevel text in p or ul. The same would go for
replacing i; or would using span break XHTML conformity (I'm not
familiar with XHTML).
Both of those tags are legal (x)html. div has display:block property and spam has display:inline property. On the other hand the font tag has been deprecated for many years.
If the error message is to be displayed inline without leading or trailing newlines then use span; if the error message is to be displayed as a block with its own 4-way margins and paddings and/or positioning use div.
Define a class errorMessage { color: red; } Now either tag can be used depending on
the display desired:
div class='errorMessage'/div
span class='errorMessage'/span
[qmailadmin] MORE Still invalid login
Hi all, I am experiencing the same invalid login problems as the previous thread. I have been running a vpopmail setup for a few years now, and am familiar with setup and administration. This new installation is on a SuSE 8.2 box running apache 2.0.48 and I have attempted both vpopmail 5.2.2 w/ qmailadmin 1.0.6 AND vpopmail 5.4.0-rc1 w/ qmailadmin -1.2.0-rc1. I use the mysql authentication, clear passwords, and have double and triple checked usernames and passwords. I have also tried this on several domains. I have checked how the disk volume is mounted, and realizing that apache 2.0 doesn not have suexec compiled/installed by default, I attenpted to recompile apache with suEXEC enabled tonight. Alas, with all my might, I am out of options and ideas, and ask for your assistance. If anyone might be able to point me in a new direction, I would be grateful! Thanks for your time, --Ted
