On Friday, October 25, 2002, 8:05:44 AM, Marcus Ohlström <[EMAIL PROTECTED]> wrote:
MO> On Friday, October 25, 2002, 13:37, Marck D Pearlstone wrote: MO>>> Could it be that TB! for some reason tries to log on to one account MO>>> but tries to send the message from another? It would indeed be a MO>>> strange behaviour, but it's my last shot. >> Actually, yes - that's a thought. "This account is the default for >> mailto:"; is the key there. MO> I'm not sure about that (even if "This account is the default for MO> mailto:"; must be involved). I think the key is bad programming by RIT MO> Labs. MO> My guess is that TB! interpret account settings in the wrong order. When MO> launched through a mailto: link, it first checks for "This account is MO> the default for mailto:"; and tries to send the message through the MO> corresponding account, thus putting up the dialog asking for account MO> password. It then realize there are accounts set up as user and not MO> admin and asks for log on. MO> If TB! instead first checked for the presence of user accounts, it could MO> present only the log on box and dismiss the account password dialog. MO> I think this should be reported to the bugtraq, but since I don't have MO> my username/password at hand, anyone else feel like reporting? MO> Jonathan, have you seen this thread? Any thoughts? Interesting. I removed the "default for mailto" option on my password-protected account. Closed TB. Then clicked on a mailto: URL. The "password only" dialog did NOT come up. The "Logon" did. I then entered another account name and no password (as there was no password for this account) and TB started up. It did NOT start a new message, however, but gave me a TB view of that account only. (That is, as if I had started TB with a non-admin account name.) I could not do ANYTHING in TB, nor could I even close TB! I had to End Task on the TB process; however TB gave me an Access Violation message and I force an abort via the W2K "Not responding" message. At this point there was NO account with a "default for mailto" option enabled. I then started TB normally, enabled the "default for mailto" option on the non-password protected account and closed TB. Then clicked on a mailto: URL again. This time, the "Logon" dialog flashed on the screen and TB started up with a new message, using that default mailto account. I was limited to that message, however, until I entered something in the Logon dialog. These errors are reproducible in my environment. I'm surprised that other folks have not experienced them. To me, it only reaffirms my opinion that the whole "Network and Administration" methodology of TB needs to be revamped and then properly documented. It seems more of an afterthought, and really is not that administerable. (My needs are not demanding, but I'd prefer a simple security database for managing accounts: creating, granting rights, changing passwords, etc.) jon -- jwayne [EMAIL PROTECTED] ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
