Spike-
Monday, February 24, 2003, 7:20:26 PM, you wrote:
a lot of snippage occurs throughout...
S See above, as it only grabs the whole link if you select copy LINK. It
S won't paste properly in ANY application I could find to try it in.
I pasted it into my text editor of choice, Edit Plus,
Marck-
Monday, February 24, 2003, 4:15:58 PM, you wrote:
MDP know. The place to have this discussion is surely TBBETA where
MDP Stefan can chip in with the facts.
I'll take this as a tame dead horse.
-Mark Wieder
Using The Bat! v1.63 Beta/4 on Windows 2000 5.0 Build 2195 Service Pack 2
--
Hello Marck D Pearlstone,
On or about Sunday, February 23, 2003 at 03:31:17GMT + (which was
10:31 PM in the tropics where I live) Marck D Pearlstone posted:
MDP -BEGIN PGP SIGNED MESSAGE-
MDP Hash: SHA1
S Where EXACTLY in the registry is this entry?
MDP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Spike,
@24-Feb-2003, 09:07 -0500 (14:07 UK time) Spike [S] in
mid:[EMAIL PROTECTED] said:
S Has absolutely no effect in WIN-XP Home. Still get only the
S first word in the subject line of;
S mailto:[EMAIL PROTECTED] - Las Vegas Website Feedback
Hello Marck D Pearlstone,
On or about Monday, February 24, 2003 at 14:19:39GMT + (which was
9:19 AM in the tropics where I live) Marck D Pearlstone posted:
S mailto:[EMAIL PROTECTED] - Las Vegas Website Feedback
MDP Aha - are you talking about links in emails? That's different. The
MDP fix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Spike,
@24-Feb-2003, 09:57 -0500 (14:57 UK time) Spike [S] in
mid:[EMAIL PROTECTED] said:
S http://komp.com/web/feature/home_page.php
S FEEDBACK link near top-right.
You are quite right. That doesn't work at all. Why not use the link
to explain
Marck-
Monday, February 24, 2003, 7:30:00 AM, you wrote:
MDP You are quite right. That doesn't work at all. Why not use the link
MDP to explain the RFC to the webmaster? ;-)
grin One point for Marck.
But that *does* get us back on track. Here's what I (currently) think
about this:
Yes, the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mark,
@24-Feb-2003, 15:47 -0800 (23:47 UK time) Mark Wieder [MW] in
mid:[EMAIL PROTECTED] said:
MW If the next version of TB were modified to act on the whole link
MW instead of just the strict-interpretation subset I don't think
MW it would
Hello Mark Wieder,
On or about Monday, February 24, 2003 at 15:47:09GMT -0800 (which was
6:47 PM in the tropics where I live) Mark Wieder posted:
MW Marck-
MW Monday, February 24, 2003, 7:30:00 AM, you wrote:
MDP You are quite right. That doesn't work at all. Why not use the link
MDP to
Hello Marck D Pearlstone,
On or about Saturday, November 30, 2002 at 09:46:55GMT + (which
was 4:46 AM in the tropics where I live) Marck D Pearlstone posted:
MDP In the definition lies the solution. There is a simple fix to all of
MDP this that involves neither TB nor the web site author:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Spike,
23-Feb-2003, 11:08 -0500 (16:08 UK time) Spike [S] in
mid:[EMAIL PROTECTED] said:
MDP This is process is handled by the defined mailto: handler as
MDP specified in the registry. All you have to do is to add
MDP delimiting quotes to the %1
Hello Marck D Pearlstone,
On or about Sunday, February 23, 2003 at 16:30:39GMT + (which was
11:30 AM in the tropics where I live) Marck D Pearlstone posted:
S Where EXACTLY in the registry is this entry?
MDP HKCR/mailto/shell/open/command
Does this change require a reboot? I've had the
Hello Spike,
Sunday, February 23, 2003, 5:40:59 PM, you wrote:
S Where EXACTLY in the registry is this entry?
MDP HKCR/mailto/shell/open/command
S Does this change require a reboot? I've had the other changes take
S place immediately, such as the 'broken' mailto's with other changes I
S
Marck-
Sunday, February 23, 2003, 8:30:39 AM, you wrote:
S Where EXACTLY in the registry is this entry?
MDP HKCR/mailto/shell/open/command
However, as I've mentioned before, this has absolutely *no* effect on
my Win2k system. I posted the question earlier to see if anyone else
could confirm or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mark,
@23-Feb-2003, 17:24 -0800 (01:24 UK time) Mark Wieder [MW] in
mid:[EMAIL PROTECTED] said:
S Where EXACTLY in the registry is this entry?
MDP HKCR/mailto/shell/open/command
MW However, as I've mentioned before, this has absolutely *no*
MW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mark,
@1-Dec-2002, 17:52 -0800 (01:52 UK time) Mark Wieder [MW] in
[EMAIL PROTECTED]">mid:[EMAIL PROTECTED] said:
MDP ... enclose the %1 parameter at the end of TB command line to
MDP be enclosed in double quotes.
MW No, that's what I was
Hallo Marck,
On Sun, 1 Dec 2002 01:59:30 +GMT (1-12-02, 2:59 +0100GMT, where I
live), you wrote:
MDP If you are confident with RegEdit, find the mailto key in
MDP HK_CLASSES. Navigate to the Command sub-key and edit the default
MDP to enclose the %1 parameter at the end of TB command line to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Roelof,
@2-Dec-2002, 12:16 +0100 (11:16 UK time) Roelof Otten [RO] in
[EMAIL PROTECTED]">mid:[EMAIL PROTECTED] said:
MDP If you are confident with RegEdit, find the mailto key in
MDP HK_CLASSES. Navigate to the Command sub-key and edit the
MDP
Hello Mark,
On Sun, 1 Dec 2002 17:52:27 -0800 GMT (02/12/02, 08:52 +0700 GMT),
Mark Wieder wrote:
MDP If you are confident with RegEdit, find the mailto key in
MDP HK_CLASSES. Navigate to the Command sub-key and edit the default to
MDP enclose the %1 parameter at the end of TB command line to be
Marck-
I tested this with IE 5.00.3315.1000. I would have tried it with
Netscape as well, but I can't remember the javascript hack to get it
to launch an external mail client. Getting the double-quote thing to
work isn't a big priority for me, but it's a good trick to know about
if it works. I'm
Thomas-
Monday, December 2, 2002, 7:12:36 AM, you wrote:
TF Just a silly question: Did you close TB when you doctored the
TF registry?
Good point. I hadn't (I almost never do). Now I have, in fact I had
that machine off overnight. Brought it up this morning and still no
effect. Has anyone else
Marck-
Saturday, November 30, 2002, 5:59:30 PM, you wrote:
MDP If you are confident with RegEdit, find the mailto key in
MDP HK_CLASSES. Navigate to the Command sub-key and edit the default to
MDP enclose the %1 parameter at the end of TB command line to be
MDP enclosed in double quotes.
No,
Jonathan-
The quotes *aren't* passed on to TB, it's true. But look at the second
url on the web page - it's formatted correctly with %20 in between the
words instead of spaces. TB does pick up the entire string. It just
doesn't handle the %20s properly.
Try this: right-click on the hi url and
Marck-
Saturday, November 30, 2002, 1:46:55 AM, you wrote:
MDP Malformed Mailto links work perfectly if the definition of mailto is
MDP changed in the registry to enclose %1 in double quotes.
Didn't change anything on my systems. I haven't seen this hack before
- can you be more specific about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mark,
@30-Nov-2002, 10:06 -0800 (18:06 UK time) Mark Wieder [MW] in
[EMAIL PROTECTED]">mid:[EMAIL PROTECTED] said:
MDP Malformed Mailto links work perfectly if the definition of
MDP mailto is changed in the registry to enclose %1 in double
MDP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, November 29, 2002, Nathan J. Yoder wrote...
JA It's almost this kind of thinking (no offence) that starts
JA getting programs in trouble. I know mailto: URLs won't cause any
JA halm (unless you do permit certain headers to be set), but
Hello Nathan!
On Friday, November 29, 2002 at 8:21:30 AM you wrote:
The be lenient in what you accept, strict in what you send
So, TB should send mailto links correctly coded and accept (in
other mails) them wrong?
First, I am not sure what that means in this context.
Second, how the
In [EMAIL PROTECTED]">mid:[EMAIL PROTECTED],
Dierk Haasis [DH] wrote:'
DH So, TB should send mailto links correctly coded and accept (in
DH other mails) them wrong?
DH First, I am not sure what that means in this context.
DH Second, how the hell should TB know what part after a mailto:
DH
Hello Allie!
On Friday, November 29, 2002 at 12:52:20 PM you wrote:
You ask the question. How is TB! to know when the mail-to link
ends???
You can't compare an incorrectly formatted mailto link embedded in
text to an incorrectly formatted url or other link put in a browsers
address field.
Hello Nathan,
On Thu, 28 Nov 2002 22:13:50 -0500 GMT (29/11/02, 10:13 +0700 GMT),
Nathan J. Yoder wrote:
JA I think that is correct behavior per RFCs. Special characters such as
JA spaces, , and such are supposed to converted to the hex version.
...
JA So TB! is only behaving as per the rules.
Hello Jonathan,
On Thu, 28 Nov 2002 23:38:04 -0600 GMT (29/11/02, 12:38 +0700 GMT),
Jonathan Angliss wrote:
Case in point ;) IE is very buggy, and has security holes in it that'd
scare a lot of people if they knew about them. Maybe if they
considered following the RFCs, rules and standards
Hello Nathan,
On Fri, 29 Nov 2002 02:21:30 -0500 GMT (29/11/02, 14:21 +0700 GMT),
Nathan J. Yoder wrote:
JA I think RitLabs have done the correct thing in following the RFCs
JA correctly. The more compliance you have with standards, the more
JA likely you are to do well. Start changing things,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, November 29, 2002, Dierk Haasis wrote...
The be lenient in what you accept, strict in what you send
So, TB should send mailto links correctly coded and accept (in
other mails) them wrong?
First, I am not sure what that means in this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, November 29, 2002, Thomas Fernandez wrote...
JA I think RitLabs have done the correct thing in following the
JA RFCs correctly. The more compliance you have with standards, the
JA more likely you are to do well. Start changing things, or
In [EMAIL PROTECTED]">mid:[EMAIL PROTECTED],
Dierk Haasis [DH] wrote:'
DH Yes, I see what you mean. But, AIUI, the original poster asked
DH about a bug in TB - the application not recognising a space in
DH a link correctly. As my example showed, there is a good reason
DH to *not* have spaces in a
I'm going to respond to a bunch of e-mails from different people, so
in order to avoid sending a bunch of replies I've combined them into
this one. Also please read it all, including my previous lengthy post
on other software that uses the be lenient in what you receive...
policy. Also, I'm
Bats-
Bringing this back on topic again:
Friday, November 29, 2002, 5:45:50 PM, you wrote:
NJY You can see http://www.gummibears.nu/test.html for an example of one
NJY correct mailto, and one incorrect if you'd like to test for yourself.
The correctly formed url still is not handled correctly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, November 29, 2002, Mark Wieder wrote...
Bats-
Bringing this back on topic again:
Friday, November 29, 2002, 5:45:50 PM, you wrote:
NJY You can see http://www.gummibears.nu/test.html for an example of one
NJY correct mailto, and one
On Fri, 29 Nov 2002 22:23:07 -0600
Jonathan Angliss [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, November 29, 2002, Mark Wieder wrote...
Bats-
Bringing this back on topic again:
Friday, November 29, 2002, 5:45:50 PM, you wrote:
NJY You can
Hello Nathan!
On Thursday, November 28, 2002 at 8:03:53 AM you wrote:
I think I've found a minor, but annoying mailto: bug.
This is not actually a bug, simply a malformed value for the protocol
used. There are no blanks allowed in such links unless they are
correctly encoded as %20 (without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, November 28, 2002, Nathan J. Yoder wrote...
I think I've found a minor, but annoying mailto: bug. With an HTML
link that uses the mailto: and a subject line (i.e. a
href=mailto:[EMAIL PROTECTED]?subject=hello how are you) The Bat! may
Thursday, November 28, 2002, 9:37:47 AM, you wrote:
JA I think that is correct behavior per RFCs. Special characters such as
JA spaces, , and such are supposed to converted to the hex version.
...
JA So TB! is only behaving as per the rules. You'll find it is the other
JA mail clients that are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, November 28, 2002, Nathan J. Yoder wrote...
JA I think that is correct behavior per RFCs. Special characters
JA such as spaces, , and such are supposed to converted to the hex
JA version.
...
JA So TB! is only behaving as per the rules.
Hello Jonathan,
Thu, 28 Nov 2002 at 23:18:10[GMT -0600](05:18 where I live) you wrote
in [EMAIL PROTECTED]">mid:[EMAIL PROTECTED] :
Start changing things, or flexing the rules slightly, and you end up
having all kinds of problems.
Unless you're Microsnort in which case you can design a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, November 28, 2002, Richard Wakeford wrote...
Start changing things, or flexing the rules slightly, and you end
up having all kinds of problems.
Unless you're Microsnort in which case you can design a browser that
doesn't conform to
It's long, I know, I'm sorry :(
Friday, November 29, 2002, 12:18:10 AM, you wrote:
JA It's almost this kind of thinking (no offence) that starts getting
JA programs in trouble. I know mailto: URLs won't cause any halm (unless
JA you do permit certain headers to be set), but saying well, just let
I think I've found a minor, but annoying mailto: bug. With an HTML
link that uses the mailto: and a subject line (i.e. a
href=mailto:[EMAIL PROTECTED]?subject=hello how are you) The Bat! may not
properly insert the subject line into the message composing window. If
the subject line contains
47 matches
Mail list logo
