[qmailadmin] qmailadmin in russian
Hello, When I tried to use qmailadmin, a strange problem occurred: most of the webpage was displayed in Russian. No matter what language I set anything on my computer to, I can't manage to get the pages displayed in English. Does anyone know what is the cause of this problem, or what to do about it? Thanks, Dorenda Snieder
Re: [qmailadmin] qmailadmin in russian
When I tried to use qmailadmin, a strange problem occurred: most of the webpage was displayed in Russian. No matter what language I set anything on my computer to, I can't manage to get the pages displayed in English. Does anyone know what is the cause of this problem, or what to do about it? I think that qmailadmin can't access languagefile. -- Eero
Re: [qmailadmin] qmailadmin in russian
On Jan 19, 2004, at 4:36 AM, Dorenda wrote: When I tried to use qmailadmin, a strange problem occurred: most of the webpage was displayed in Russian. No matter what language I set anything on my computer to, I can't manage to get the pages displayed in English. Does anyone know what is the cause of this problem, or what to do about it? Check the settings of your web browser -- that's where QmailAdmin gets its language setting. What version of QmailAdmin? Earlier versions had trouble parsing the language preferences sent by the web browser, and could end up using a less-preferred language. Upgrading to the latest QmailAdmin should take care of the problem, or you could entirely remove Russian from you language list in your browser. -- 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] Stable version
Hi all, What is the stable version for Qmailadmin, Vpopmail Vqadmin. -- Saravanan - This mail sent through IMP: http://horde.org/imp/
Re: [qmailadmin] Qmail Admin Missing Graphics
I did have this problem actually...the odd thing was when I ended up upgrading my kernel is went back fine. Stephen Harmon [EMAIL PROTECTED] wrote: Hi, I installed Qmailadmin the other day and it was working just fine. Since installing VQAdmin I no longer have my graphics in QMailAdmin. QmailAdmin still works, I just don't have the any of the graphics. I am running QmailAdmin Version 1.2.0-rc2. I did recomplile - reinstall QmailAdmin but have the same results. I searched the Mail Archives and couldn't find anything either. Any help would be appreciated. Thanks, Stephen Harmon Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing
Re: [qmailadmin] qmailadmin-rww -- md5 session ID
You might be able to piggy-back off the md5 code in vpopmail... Yes, it looks very close to a drop-in replacement to the one I found. I don't even have to change the build process again. The file names match. Wish I would have seen that sooner! I have added three defines in qmailadmin.h, that should actually be set by ./configure options: I think we should also add a probability how often the garbage collector is executed and deletes the expired session files. Executing it every time QmailAdmin is executed is IMO to much and slows it only down. I already garbage collect only after a successful login, so it doesn't run with every hit, but probability testing won't be hard to add. I should also make it so the page paints before the garbage collection starts so it doesn't slow the user. You could read from /dev/random or /dev/urandom, if present. There's a patch pending for vpopmail that uses that device for random data. I guess if vpopmail uses it it should be safe for QmailAdmin. I know that should work on my Linux boxes... How do you tell if it is present? ./configure? What happens if it is not there? I suspect the whole block of code and configure.in(?) can be stolen from vpopmail. Random numbers are more or less always generated out of the current time, but I think we perhaps could generate the SESSION_SECRET string randomly, too. Or repeat the hashing a random time (1-10 for example). If you always have a good random generator avialble that is much better than a preset secret. I don't know enough about c portability to decide. One thing I've heard is that /dev/?random can sometimes block if there isn't enough enthropy available. That could be bad on a lightly loaded machine. I don't need to retain the random input values for anything, I am just trying to make it very hard to predict SessionID values. Why get the things messed up? I would do a logout like 1) Delete the cookie/no more sids in the urls 2) Delete the session file on the server On a relogin you create everything new as it would be the first login. What it does now... in get_session_id() The first time you hit QmailAdmin the program checks for a cookie. There is none, so it sets SessionFromCookie = 0. Then it checks for SessionID in Request.(Get/Put) Again there is none so it generates a new SessionID. in paint_headers() Since SessionFromCookie is 0 (false) and SessionID is set a Set-cookie header for SessionID will be sent. Since there is no session file associated with the new SessionID and the [Login] button was not clicked, you are only allowed to login. show_login() calls send_template() and paints the login page, then the progran is done. Since SessionFromCookie is 0 a hidden field is included in the page containing SessionID. -- the user enters user/domain/password then clicks [login] -- This time through... in get_session_id() SessionID is found in Cookie, so SessionFromCookie = 1, and SessionID is set. in paint_headers SessionFromCookie is 1, so do not send a SetCookie header. Still no session file matching your SessionID, but this time [Login] was clicked so verify the login. If the login is good create the session file then call show_menu -- else call show_login, with the fields still filled in the way the user left them. (I hate having to re-enter everything even more than I hate being dropped into an error page that tells me to hit [Back] and try again.) As long as a cookie is found, the SessionID will not be appended to link URLS, and the hidden field may not be added to forms. Right now it is always added, and that does not hurt anything. Mere mortals will never see it. A ##t? could be used to hide the hidden SessionID field. On the other hand it might be nice to be able to view the SessionID with View Source if you have a problem. I don't have to decide yet... -- the user does whatever, then clicks the exit link -- in get_session_id() SessionID is found in Cookie, so SessionFromCookie = 1, and SessionID is set. in main() Since exit was selected, delete the session file, set SessionFromCookie to 0, and set SessionID = . in paint_headers() Since SessionFromCookie is 0 and SessionID is blank, send a Set-cookie header with an old Expires value. The browser will delete the cookie. Then we need to paint something to the browser... But what? Things I have considered... o Delay setting the cookie until there is a valid login. I very much like setting the SessionID cookie the first time I paint the show_login.html template. This way I know that the next operation will be a form entry. If I wait until I have a valid login the next operation will be a menu, and every link will have to have the SessionID appended in case cookies are off. That looks uggly... o Don't worry about leaving the cookie in the browser. Things worked well right up to the time I decided it wasn't cool to do a logout without cleaning up the cookie. That is tacky... o Have an exit page that tells you that
Re: [qmailadmin] Qmailadmin 1.2.0 Release Candidate 3 released
Still no Fix so this will not remove my tmda settings from the .qmail files? -John - Original Message - From: Tom Collins [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, January 19, 2004 2:49 PM Subject: [qmailadmin] Qmailadmin 1.2.0 Release Candidate 3 released We are getting closer to a stable release, and we need everyone's help in testing this release. Even if you don't want to run it, at least try downloading, configuring and compiling it on your system. We've been making changes to the build-related files, and need feedback on any problems that might still exist. Take a look at the documentation, and feel free to offer any suggestions for improvement (or better yet, post patches with your changes to SourceForge). As you can see in the ChangeLog, we've been fixing a lot of small bugs and improving the documentation. Please post any bug reports to SourceForge. ChangeLog: Tom Collins - Minor formatting changes to configure.in for consistency. - Make function buffers static when returning pointers to them. - More updates to build files. - Properly format autoresponder names with '.' in them. [872721] - Remove old code and redundant quota setting code from user.c. - Switch to using new pw_flags field in auth.c. - Set permissions on html templates and lang files to 644 (not 755). Jussi Siponen - Add Finnish translation. [879032]
[qmailadmin] Re: [qmailadmin-devel] Re: [qmailadmin] Qmailadmin 1.2.0 Release Candidate 3 released
John Johnson wrote: Still no Fix so this will not remove my tmda settings from the .qmail files? No. Sorry, QmailAdmin is in a feature freeze until 1.2.0 goes out the door. Your request is high on the list for things to add to the next version. It will requite major changes that would push the release of the current version out WAY too far. (IMHO it has been way too long since the last stable release!) I assure you the next stable release will be faster. I know, I'm already working on it... Rick
Re: [qmailadmin] Re: [qmailadmin-devel] Re: [qmailadmin] Qmailadmin 1.2.0 Release Candidate 3 released
OK, I am just a little upset because this was not a problem with the last stable release and now it's broken for someone elses idea of spam reduction. -John - Original Message - From: Rick Widmer [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, January 19, 2004 4:10 PM Subject: [qmailadmin] Re: [qmailadmin-devel] Re: [qmailadmin] Qmailadmin 1.2.0 Release Candidate 3 released John Johnson wrote: Still no Fix so this will not remove my tmda settings from the .qmail files? No. Sorry, QmailAdmin is in a feature freeze until 1.2.0 goes out the door. Your request is high on the list for things to add to the next version. It will requite major changes that would push the release of the current version out WAY too far. (IMHO it has been way too long since the last stable release!) I assure you the next stable release will be faster. I know, I'm already working on it... Rick
Re: [qmailadmin] Qmailadmin 1.2.0 Release Candidate 3 released
Tom Collins wrote: We are getting closer to a stable release, and we need everyone's help in testing this release. More WARNINGS! After compiling the RC2 vpopmail and the RC3 QmailAdmin I get the following block of errors: In file included from qmailadmin.c:31: /mail/include/vpopmail_config.h:221:1: warning: PACKAGE_NAME redefined In file included from qmailadmin.c:28: config.h:131:1: warning: this is the location of the previous definition In file included from qmailadmin.c:31: /mail/include/vpopmail_config.h:224:1: warning: PACKAGE_STRING redefined In file included from qmailadmin.c:28: config.h:134:1: warning: this is the location of the previous definition In file included from qmailadmin.c:31: /mail/include/vpopmail_config.h:227:1: warning: PACKAGE_TARNAME redefined In file included from qmailadmin.c:28: config.h:137:1: warning: this is the location of the previous definition In file included from qmailadmin.c:31: /mail/include/vpopmail_config.h:230:1: warning: PACKAGE_VERSION redefined In file included from qmailadmin.c:28: config.h:140:1: warning: this is the location of the previous definition source='alias.c' object='alias.o' libtool=no \ for each of the following files: qmailadmin.c, user.c, template.c qmailadmin.c doesn't actually use anything from vpopmail_config.h, so the #include can just be removed. user.c uses VPOPMAILDIR template.c uses the following values: PACKAGE and VERSION. It also uses QA_PACKAGE and QA_VERSION which look like they might be standard autoconf variables that have been alterd to make them unique so both can be displayed from the ##V tag. The actual duplicated variables are not used anywhere in QmailAdmin. Rick
[qmailadmin] vpopmail - qmailadmin = KO with e-mails beginning with p-z
Hello, I'm using vpopmail 5.2.1 as POP3 daemon, courier-imap as IMAP daemon and qmail as MTA, qmailadmin 1.0.6 as Administration Web Interface on linux redhat 7.2 When I create an e-mail account by the way of the qmailadmin web interface, and if this e-mails begins with p,q,r,s,t,u,v,w,x,y,z this e-mail account is created but not listed in the e-mail accounts list of qmailadmin. The e-mail is working correctly. If I want to create again this e-mail, qmailadmin says that this e-mail is already active (so qmailadmin have a way to check presence but can't list the e-mail accounts...) sometimes = if I create [EMAIL PROTECTED] = it works [EMAIL PROTECTED] = it does'nt work [EMAIL PROTECTED] = it does'nt work
Re: [qmailadmin] vpopmail - qmailadmin = KO with e-mailsbeginningwithp-z
Please **close** this thread I found my mistake : in /home/vpopmail/include/vpopmail_config.h /* #undef CLEAR_PASS */ I forgot to compile with --enable-clear-passwd=y option All lines after postmaster line are not read by qmailadmin in /home/vpopmail/domains/adomain.com/vpasswd because when adding a domain with vpopmail without enable clear passwd It looks like that postmaster:CRYPTPASS.:2:0:Postmaster:/home/vpopmail/domains/adomain.com/post master:NOQUOTA without enable clear passwd, it have a better look :) postmaster:CRYPTPASS.:2:0:Postmaster:/home/vpopmail/domains/adomain.com/post master:NOQUOTA:CLEARPASS and it works...
Re: [qmailadmin] Qmailadmin 1.2.0 Release Candidate 3 released
Despite the warnings vpopmail rc2 and QmailAdmin RC3 appear to be working on my test server. I can add/remove/edit accounts, but can not test mail delivery. Rick
