Re: [qmailadmin] Authentication oddity in qmailadmin
On Tuesday, June 17, 2003, at 12:15 AM, Tom Collins wrote: On Monday, June 16, 2003, at 07:33 PM, Matt Simerson wrote: I can log in just fine as [EMAIL PROTECTED] but I cannot log in as [EMAIL PROTECTED], which is an aliasdomain of u-r-on.net. I've tried removing the aliasdomain avgisp.com and then re-adding it but still no luck. I wonder if the hyphens are messing anything up. What happens when you do: grep u-r-on.net /var/qmail/users/assign How about `~vpopmail/bin/vuserinfo [EMAIL PROTECTED] or better yet, `~vpopmail/bin/vdominfo avgisp.com`? mail# ~vpopmail/bin/vuserinfo [EMAIL PROTECTED] 1.txt mail# ~vpopmail/bin/vuserinfo [EMAIL PROTECTED] 2.txt mail# diff 1.txt 2.txt mail# more 1.txt name: matt passwd: * clear passwd: uid:0 gid:0 gecos: Matt Simerson all services available dir: /usr/local/vpopmail/domains/u-r-on.net/matt quota: 20971520 usage: 0% last auth: Tue Jun 17 07:39:35 2003 last auth ip: imap mail# mail# ~vpopmail/bin/vdominfo avgisp.com domain: avgisp.com uid:89 gid:89 dir:/usr/local/vpopmail/domains/u-r-on.net users: 0 I'm thinking that it might be a problem with the vget_assign function in vpopmail.c. Using the vuserinfo tool will help determine if it's a problem with the vpopmail library, or a problem with qmailadmin. Good question, I'm not certain. :) Matt
Re: [qmailadmin] Authentication oddity in qmailadmin
Hi Matt, However, qmailadmin does not appear to support this. Only [EMAIL PROTECTED] is able to log in via qmailadmin. Shouldn't the user also be able to authenticate as [EMAIL PROTECTED] I can't reproduce this behaviour (using vpopmail 5.2.1 with qmailadmin 1.0.6), however, qmailadmin always switches to the main domain, i.e. you log in as [EMAIL PROTECTED], qmailadmin shows bob.com at the main menu, not bobsmith.com. This may cause trouble. If you have had a customer with an-ugly-domain.com, having a zillion of alias domains, and then one day telling you, hey, I don't need an-ugly-domain.com anymore, you're in the bad situation that you can't kill an-ugly-domain.com because that would break every single alias domain. Furthermore, creation of ezmlm mailing lists will always succeed in creating listname@an-ugly-domain.com, even if you logged in as [EMAIL PROTECTED] To get rid of the the customers wants to close its main domain problem, I tried creating dummy hostnames for customers' accounts, e.g. login-id.internal, then having _all_ domains as aliasdomains for login-id.internal, thus being able to create and delete every single domain without trouble. Unfortunately, this creates more confusion - think about Hi. I'm the ezmlm program on login-id.internal.. Is anybody aware of this? Unfortunately I'm no C programmer, but I would highly appreciate if qmailadmin took the domain name from the customer's login instead of switching to the real domain right after login. Does anybody have a hint on this? Jonas
Re: [qmailadmin] Authentication oddity in qmailadmin
My server also runs the mysql backend I tried adding a aliasdomain (testme.com) and then logging into qmailadmin on the alias domain and it failed with an error : vmysql: sql error[3]: Table 'vpopmail.testme_com' doesn't exist I took a quick look through the code, and I think the problem may have something to do with line 358 from the vauth_getpw() function in vmysql.c /*vget_real_domain(in_domain, 100);*/ Shorly after this remarked line, an SQL command is built that contains a SELECT for the aliased domain name. Since the alised domain doesnt actually exist in SQL you get a nasty error. The SELECT should really contain a lookup on the real domain rather than the aliased domain. I wonder why that code was remarked out, because it seems to be the solution to this problem? Michael. - Original Message - From: Matt Simerson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 17, 2003 12:37 PM Subject: Fwd: [qmailadmin] Authentication oddity in qmailadmin (sorry for the personal reply Tom, I forgot to change the reply-to) OK, I've updated both my vpopmail and qmailadmin to the latest devel versions and it still doesn't work. Here's how I'm configured: vpopmail: ./configure --enable-mysql=y --enable-rebuild-tcpserver-file=n --enable-defaultquota=1S,1C --enable-roaming-users=y --enable-learn-passwords=y --enable-logging=v --enable-default-domain=u-r-on.net --enable-mysql-replication=y qmailadmin: ./configure --enable-domain-autofill=Y --enable-modify-spam=Y '--enable-spam-command=| /usr/local/bin/maildrop' --enable-modify-quota=y --enable-cgibindir=/usr/local/www/cgi-bin.mail I can't think of why any of the above would cause this to not work. I can authenticate via just fine via POP3 using all three domains (indicating that yea verily, it is set up in vpopmail correctly). But I can only log into qmailadmin using the main domain. The domains were added using qmailadmin 1.0.15 but I don't see anything particularly relevant in the ChangeLog. I can log in just fine as [EMAIL PROTECTED] but I cannot log in as [EMAIL PROTECTED], which is an aliasdomain of u-r-on.net. I've tried removing the aliasdomain avgisp.com and then re-adding it but still no luck. Matt On Monday, June 16, 2003, at 05:57 PM, Tom Collins wrote: On Monday, June 16, 2003, at 02:30 PM, Matt Simerson wrote: I can thus add bobsmith.com to vpopmail as an aliasdomain. Now any user in bob.com can also authenticate as user at bobsmith.com. I'm sure you're all with me so far. However, qmailadmin does not appear to support this. Only [EMAIL PROTECTED] is able to log in via qmailadmin. Shouldn't the user also be able to authenticate as [EMAIL PROTECTED] Works for me (qmailadmin 1.0.21, vpopmail 5.3.20). -- Tom Collins [EMAIL PROTECTED]
[qmailadmin] Authentication oddity in qmailadmin
OK, I think I found something that's a little odd, anyone feel free to smack with a LART if I'm wrong about this. With vpopmail, you can create valiasdomains. So, I could have: bob.com set up on my mail server. I can thus add bobsmith.com to vpopmail as an aliasdomain. Now any user in bob.com can also authenticate as user at bobsmith.com. I'm sure you're all with me so far. However, qmailadmin does not appear to support this. Only [EMAIL PROTECTED] is able to log in via qmailadmin. Shouldn't the user also be able to authenticate as [EMAIL PROTECTED] Matt
Re: [qmailadmin] Authentication oddity in qmailadmin
On Monday, June 16, 2003, at 02:30 PM, Matt Simerson wrote: I can thus add bobsmith.com to vpopmail as an aliasdomain. Now any user in bob.com can also authenticate as user at bobsmith.com. I'm sure you're all with me so far. However, qmailadmin does not appear to support this. Only [EMAIL PROTECTED] is able to log in via qmailadmin. Shouldn't the user also be able to authenticate as [EMAIL PROTECTED] Works for me (qmailadmin 1.0.21, vpopmail 5.3.20). -- Tom Collins [EMAIL PROTECTED]