Re: [qmailadmin] Login....
On Jun 13, 2005, at 8:12 AM, dopry wrote: One thing I've always wanted with qmailadmin... IS there a convenient way to drop the domain option and just use a full email address for the username/domain? my users use [EMAIL PROTECTED] for every other login on my network, but explaining why qmail admin is different is always a hassle. Yep. Here's the patch: http://sourceforge.net/tracker/index.php? func=detailaid=1018476group_id=6691atid=306691 I guess I should be trying to work this into qmailadmin, perhaps as a compile option. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ You don't need a laptop to troubleshoot high-speed Internet: sniffter.com
Re: [qmailadmin] Login....
that would be ideal. :) I don't like using code that is not fully accepted into the distribution you guys maintain. Mainly because I have a couple thousand people using this system, and I somehow feel more secure when project maintainers merge patches like this into the project. ;) On Mon, 2005-06-13 at 08:19 -0700, Tom Collins wrote: On Jun 13, 2005, at 8:12 AM, dopry wrote: One thing I've always wanted with qmailadmin... IS there a convenient way to drop the domain option and just use a full email address for the username/domain? my users use [EMAIL PROTECTED] for every other login on my network, but explaining why qmail admin is different is always a hassle. Yep. Here's the patch: http://sourceforge.net/tracker/index.php? func=detailaid=1018476group_id=6691atid=306691 I guess I should be trying to work this into qmailadmin, perhaps as a compile option. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ You don't need a laptop to troubleshoot high-speed Internet: sniffter.com
Re: [qmailadmin] Login....
I've reviewed it, and it looks like a good patch. I haven't integrated it yet because it doesn't include a ./configure option for turning it on or off. On Jun 13, 2005, at 8:37 AM, dopry wrote: that would be ideal. :) I don't like using code that is not fully accepted into the distribution you guys maintain. Mainly because I have a couple thousand people using this system, and I somehow feel more secure when project maintainers merge patches like this into the project. ;) On Mon, 2005-06-13 at 08:19 -0700, Tom Collins wrote: On Jun 13, 2005, at 8:12 AM, dopry wrote: One thing I've always wanted with qmailadmin... IS there a convenient way to drop the domain option and just use a full email address for the username/domain? my users use [EMAIL PROTECTED] for every other login on my network, but explaining why qmail admin is different is always a hassle. Yep. Here's the patch: http://sourceforge.net/tracker/index.php? func=detailaid=1018476group_id=6691atid=306691 I guess I should be trying to work this into qmailadmin, perhaps as a compile option. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ You don't need a laptop to troubleshoot high-speed Internet: sniffter.com
Re: [qmailadmin] Login Incorrect Message
On Thu, 2004-02-19 at 21:19, [EMAIL PROTECTED] wrote: Hi, I am new to qmail/qmailadmin. I installed everything according to the instructions on qmailrocks.org and everything is working great. I can relay out and accept mail in. I am however unable to login to qmailadmin, it always tells me login incorrect, even though I am logging in with the correct settings. I am running mandrake, anybody know why this might happen? Thanks in advance, any assistance is much appreciated! $5 says msec took the setuid bit off of the qmailadmin binary for you. Isn't it so nice? :) -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 -- 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] login problem
Qmailadmin doesn't support MySQL. Since when? Supports it fine from my end. Giacomo, Check that your /cgi-bin/qmailadmin is chmod 4755 and that it is owned by root:wheel or whatever your root equivelent is on your system. Also make sure that user vpopmail has access to the ~vpopmail/domains directory and those domains below it. Usually chmod 700 for security reasons. Since Qmailadmin runs under Apache you can also check the error_log for Apache usually under apache/logs/ Wil -Original Message- From: HONTI Miklos [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 4:14 PM To: Capitano Cc: [EMAIL PROTECTED] Subject: Re: [qmailadmin] login problem as you an read in all doc, faq, archive, qmailadmin do not support mysql. maybe there is an other web interface for vpopmail+mysql, or you can write one easily for example in php. bye Miki On Tue, 25 Mar 2003, Capitano wrote: Hi all I've installed a mailserver that give me a strange problem: Qmailadmin doesn't permit me to login, like when the password is wrong. Mysql log shows me that vadddomain and vadduser work well. Where could I found some hints to resolve this problem (logs) ? thanks Giacomo
Re: [qmailadmin] login problem
- Original Message - From: Wil Hatfield - HVHM Customer Care [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 11:25 PM Subject: RE: [qmailadmin] login problem Check that your /cgi-bin/qmailadmin is chmod 4755 and that it is owned by root:wheel or whatever your root equivelent is on your system. you are right the prob was the sticky! for the owner I use vpopmail:vchkpw like the tutorial that I've followed say. thank you very much for the help! Giacomo
RE: [qmailadmin] login problem
Capitano, Your welcome. I use mine owned by root:wheel so that if I have a postoffice located under a user's home directory owned by that user it will step down and setuid to that user. But if you are using stock Vpopmail then you can leave it at vpopmail:vchkpw. Wil -Original Message- From: Capitano [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 4:21 PM To: Wil Hatfield - HVHM Customer Care; [EMAIL PROTECTED] Subject: Re: [qmailadmin] login problem - Original Message - From: Wil Hatfield - HVHM Customer Care [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 11:25 PM Subject: RE: [qmailadmin] login problem Check that your /cgi-bin/qmailadmin is chmod 4755 and that it is owned by root:wheel or whatever your root equivelent is on your system. you are right the prob was the sticky! for the owner I use vpopmail:vchkpw like the tutorial that I've followed say. thank you very much for the help! Giacomo
Re: [qmailadmin] login problem
as you an read in all doc, faq, archive, qmailadmin do not support mysql. maybe there is an other web interface for vpopmail+mysql, or you can write one easily for example in php. bye Miki On Tue, 25 Mar 2003, Capitano wrote: Hi all I've installed a mailserver that give me a strange problem: Qmailadmin doesn't permit me to login, like when the password is wrong. Mysql log shows me that vadddomain and vadduser work well. Where could I found some hints to resolve this problem (logs) ? thanks Giacomo
Re: [qmailadmin] Login form
At 10:21 AM 03-13-2003, Rick Romero wrote: Easy. Just change your qmailadmin-1.12/html/show_login.html: trtdDomain Name /tdtd SELECT name=domain option value=domain1.comdomain1.com option value=domain2.comdomain2.com option value=domain3.comdomain3.com /select !-- input type=hidden size=14 name=domain value=orginaldomain1.com maxlength=128-- /td/tr okay, this isn't a qmailadmin related query - more of a general html/cgi query so i apologize in advance. we have a signup page on our service, and we offer addresses at a dozen or so domains. we've tried setting it up so that the user enters their desired email name in one box, then chooses a domain from a drop-down list. but it just won't work - when the values are put together, there's always a space between them, creating an invalid address, e.g. paul @smileglobal.com. so we have to stick with just one larger text entry box where the customer spells out the entire address they want. the problem is - that allows misspelling of the domain name part, so every so often, we get some poor soul who drops a letter from a domain, and can't understand why they don't have their email account. hey - like i said, unrelated to qmailadmin, so feel free to tell me to go take a jump in a lake! ;^) Paul Theodoropoulos http://www.anastrophe.com http://folding.stanford.edu The Nicest Misanthrope on the Net
Re: [qmailadmin] Login form
On Thu, 2003-03-13 at 12:12, Ajai Khattri wrote: We are currently setting up qmailadmin. I was wondering if anyone had written any patches to qmailadmin so that the Domain Name field on the login page displays a pulldown of domain-names instead of just a text field? Maybe pulling the domains from vpopmail at runtime? ;-) Easy. Just change your qmailadmin-1.12/html/show_login.html: trtdDomain Name /tdtd SELECT name=domain option value=domain1.comdomain1.com option value=domain2.comdomain2.com option value=domain3.comdomain3.com /select !-- input type=hidden size=14 name=domain value=orginaldomain1.com maxlength=128-- /td/tr And make install. (or just change it where it's installed) Rick (No customers will ever see qmailadmin so this is OK for us ).
Re: [qmailadmin] Login form
Janning Vygen wrote: drop down field is not a good idea or do you want somebody might see all your domains?? Ajai Khattri wrote: (No customers will ever see qmailadmin so this is OK for us). Would be better if this could be done programmatically so I don't have to edit a template every time we add a domain. Maybe I will write a script that pulls from the MySQL database and generates the pulldown ;-) -- Aj. Systems Administrator / Developer
Re: [qmailadmin] Login form
On Thursday 13 March 2003 13:12, Ajai Khattri wrote: We are currently setting up qmailadmin. I was wondering if anyone had written any patches to qmailadmin so that the Domain Name field on the login page displays a pulldown of domain-names instead of just a text field? Maybe pulling the domains from vpopmail at runtime? ;-) (No customers will ever see qmailadmin so this is OK for us). Hi Ajai. I have written a patch for Sqwebmail that does exactly what you want and much MUCH more. I will soon port this patch to qmailadmin. I plan to begin the porting process late next week. It shouldn't take more than an hour or two, so if you can wait until then, you'll have what you need. (and hopefully it will be included in the next release.) Attached is documentation for the 'logindomainlist' file that my patch reads before generating it's drop down menu, or hidden field. Take a look, and let me know if it's what you're looking for. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net We are actively looking for companies that do a lot of long distance faxing and want to cut their long distance bill by up to 50%. Contact [EMAIL PROTECTED] for more info. /usr/local/share/sqwebmail/logindomainlist - this file can be used in a vast number of ways to fine tune the user login experience. In sqwebmail version prior to 3.5.0.20030304, logindomainlist had much more limited functionality. You could only specify a list of domains, one per line. The user would then see a drop down list to the right of the user id field on login.html. This drop down list was of limited usefulness because it always defaulted to an empty (non-existant) domain. The user would then have to search through the drop down to find the domain he wanted to log in under. In addition, the drop down had no access controls, and it showed EACH user ALL of the domains listed in the logindomainlist file. However, now the logindomainlist file is MUCH more useful. Among the new logindomainlist functionality is the ability to specify a group field for each drop down menu record, and the ability to specify default domains so that the user doesn't have to go searching for his domain in the drop down list. Also, you can do away with the drop down menu all together if you wish. You can now specify records that generate hidden fields in login.html, allowing you to show only one domain to the user per URL or IP address. This can greatly reduce confusion for first time web mail users. And finally, the new logindomainlist functionality allows you to use wildcards to rewrite the domain portion of the calling URL to the mail domain equivalent. For example, the following record can rewrite the URL mail.*.com to the mail domain *.com *.com:mail.*.com:* This powerful wildcard functionality can often automate most of your server's default domains with just one or two logindomainlist records. Let's take a look at the NEW logindomainlist file format: firstfield:secondfield:thirdfield Above, we can see that the new logindomainlist records are made up of three fields delimited by colons. But what does each field do? First Field - the first field contains the MAIL login domain. This is the part of an email address after the @ symbol. For example, in the email address [EMAIL PROTECTED], domain.com is the mail login domain. Second Field - the second field contains the URL or IP address that is used to figure out which mail domain to use by default. For example, in the following logindomainlist record: domain1.com:domain2.com domain2.com is the default domain and domain1.com is the mail domain. If the user logs into the following URL: http://domain2.com/cgi-bin/sqwebmail His default domain will be domain1.com. Third Field - the third field may contain a modifier. The modifier may be either a single character modifier, or a group string. The individual modifiers and their functions are listed below: * - the asterisk modifier tells sqwebmail that the first and second fields _MAY_ contain wildcards. It also explicitly turns off the drop down list, since wildcards are technically incompatible with drop downs. And finally, IPs are not allowed in the second field with this modifier since wildcarding would have to be implemented differently for IP addresses. When using wildcarding, whatever the asterisk (*) represents in the second field will be substituted for the asterisk (if it exists) in the first field. For example, given the following logindomainlist record: *.com:mail.*.com:* And the user logs into sqwebmail with the following URL: http://mail.mydomain.com/cgi-bin/sqwebmail The asterisk in the second field will represents the string mydomain. This string
