From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_02EC_01C5CA9E.0E186350
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   It's not a work around.  That is how you specify an email address =
with special characters.  As you have made clear you prefer to whine and =
complain and will repeatedly do so.

Rich

  "Mike '/m'"  wrote in message =
news:vj4bk1p6lbo9umbic44q9kph80vbvqdb28{at}4ax.com...

  I read and saw a kludgy workaround.=20

  I did not see anything that resolved the bug.  Maybe you could quote =
the
  part of your message that resolves the bug?

   /m

  On Wed, 5 Oct 2005 21:04:25 -0700, "Rich"  wrote:

  >   Still demonstrating that you would rather complain then read and =
learn how you are wrong.
  >
  >Rich
  >
  >  "Mike '/m'"  wrote in message =
news:5oi8k15acbme7bhvo1vnnsh7iehooc94fg{at}4ax.com...
  >
  >  Another interesting aspect of this bug is that the From: fields and =
the
  >  Reply To: fields allow the dotted quad email address.  Only the To:
  >  field has the bug that does not allow a valid dotted quad email =
address
  >  to be entered.
  >
  >  If a valid email address is accepted in the From: and Reply To: =
fields,
  >  why isn't it accepted in the To: field?
  >
  >  Sounds like someone has a UI consistency bug to fix, at the very =
least.
  >
  >   /m
  >
  >
  >
  >  On Thu, 29 Sep 2005 19:13:54 -0700, "Rich"  wrote:
  >
  >  >   Or you could have just read my email before you replied to it =
with more complaints and more evidence that you care more about =
complaining than the topics about which you complain.
  >  >
  >  >Rich
  >  >
  >  >  "Mike '/m'"  wrote in message =
news:8rmoj111q3g7s3sbuarrdenedijcsrvvuc{at}4ax.com...
  >  >
  >  >  I played with this a bit more today.
  >  >
  >  >  I changed the address that Outlook puts in the From: field for =
outgoing
  >  >  emails to email{at}[123.123.123.123] (I'll call this a "dotted =
quad"
  >  >  address for this message), then saved that new config.  I sent =
myself an
  >  >  email.  When the email arrived in my inbox, the From: address =
was the
  >  >  dotted quad.  I OMB clicked on the dotted quad address, and =
selected the
  >  >  add it to my address book option.
  >  >
  >  >  Then I changed the From: address back to what it should be.
  >  >
  >  >  Now I can send an email to that dotted quad address, Outlook =
accepts it
  >  >  as input.
  >  >
  >  >  The reason I did this is that previously when I wanted to send =
an email
  >  >  to a dotted quad address, I could enter it into the To: field, =
but
  >  >  Outlook would not allow me to send it.  Outlook would push me =
over to
  >  >  enter the address into Outlook's address book.  =20
  >  >
  >  >  I guess that Outlook doesn't allow me to send an email to =
someone who is
  >  >  not in my address book?  I'm not sure why it would do this, I =
know that
  >  >  Outlook 97 didn't have this behavior.  Maybe that's why Outlook =
'97
  >  >  worked and Outlook 2003 doesn't.
  >  >
  >  >  In any case, it looks like it may be the input routines for =
entering an
  >  >  email address into Outlook's address book that has the problem =
with the
  >  >  RFC-compliant dotted quad address.  Once a dotted quad address =
is in the
  >  >  address book, I can send email to it.
  >  >
  >  >  Weird.
  >  >
  >  >   /m
  >  >
  >  >
  >  >
  >  >  On Mon, 26 Sep 2005 21:50:32 -0400, "Geo"
 =
wrote:
  >  >
  >  >  >"Mike '/m'"  wrote in message
  >  >  >news:25ugj1psik6mb69ifo2vfg6u7fg5uapm43{at}4ax.com...
  >  >  >
  >  >  >> I have not been able to get Outlook to send an email to
  >  >  >>
  >  >  >>    email{at}[123.123.123.123]
  >  >  >>
  >  >  >> where 123.123.123.123 is the IP address of a email server, =
and 'email'
  >  >  >> is a valid email account on that server.  I believe this is =
an RFC
  >  >  >> requirement, just like proper SMTP handling.
  >  >  >
  >  >  >Perhaps you have an email admin like me who blocks email to an =
{at}ipaddress
  >  >  >address? Some things need to change because of spam and many of =
the rfc's
  >  >  >are sort of unchanging if you know what I mean.
  >  >  >
  >  >  >Oh, I also block remote bounce notifications because they cause =
more
  >  >  >problems than they solve. If you accept the email then deliver =
it, don't be
  >  >  >returning it as undeliverable after you accept delivery is how =
it works in
  >  >  >todays spam and virus filled world.
  >  >  >
  >  >  >> Also, I keep nicknames for my friends.  For example, I use =
bob-w for Bob
  >  >  >> at work, Bob-h for Bob at home.  Well, Bob changed
jobs, so I =
changed
  >  >  >> the email address for Bob-w in the address book to his new =
email
  >  >  >> address.  Unfortunately, Outlook also stores the email =
address somewhere
  >  >  >> else, and insists on sending Bob-w emails to his old email =
address. I've
  >  >  >> not found the other location in the address book or =
configuration
  >  >  >> options yet.  I now have a NewBob-w entry in the
address book =
to work
  >  >  >> around this feature.
  >  >  >
  >  >  >Yeah, Microsoft probably let the guy who did IE's braindead =
autocomplete
  >  >  >write that stupid routine. He need to be 2x4'd.
  >  >  >
  >  >  >> Don't get me started on Outlook and IMAP....
  >  >  >
  >  >  >I don't believe in IMAP in the ISP world, it's a po box not a =
damn garage.
  >  >  >
  >  >  >Geo.
  >  >  >
------=_NextPart_000_02EC_01C5CA9E.0E186350
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   It's not a work =
around.  That is=20
how you specify an email address with special characters.  As you
= have made=20
clear you prefer to whine and complain and will repeatedly do =
so.
 
Rich
 

  "Mike '/m'" <mike{at}barkto.com>=20">mailto:mike{at}barkto.com">mike{at}barkto.com>=20
  wrote in message news:vj4bk1p6lbo=
9umbic44q9kph80vbvqdb28{at}4ax.com...I=20
  read and saw a kludgy workaround. I did not see anything that =
resolved=20
  the bug.  Maybe you could quote thepart of your message that =
resolves=20
  the bug? /mOn Wed, 5 Oct
2005 21:04:25 -0700, =
"Rich"=20
  <{at}> wrote:>  
Still demonstrating that you =
would=20
  rather complain then read and learn how you are=20
 
wrong.>>Rich>> 
"Mike '/m'" <mike{at}barkto.com>">mailto:mike{at}barkto.com">mike{at}barkto.com>
wrote in =
message news:5oi8k15acbm=
e7bhvo1vnnsh7iehooc94fg{at}4ax.com...>> =20
  Another interesting aspect of this bug is that the From: fields and=20
  the>  Reply To: fields allow the dotted quad email =
address. =20
  Only the To:>  field has the bug that does not allow a =
valid=20
  dotted quad email address>  to be =
entered.>> =20
  If a valid email address is accepted in the From: and Reply To:=20
  fields,>  why isn't it accepted in the To:=20
  field?>>  Sounds like someone
has a UI consistency =
bug to=20
  fix, at the very least.>>  =20
 
/m>>>> 
On Thu, 29 Sep 2005 19:13:54 =
-0700,=20
  "Rich" <{at}>
wrote:>> 
>   Or you =
could=20
  have just read my email before you replied to it with more complaints =
and more=20
  evidence that you care more about complaining than the topics about =
which you=20
  complain.> 
>> 
>Rich> =20
  >>  >  "Mike
'/m'" <mike{at}barkto.com>">mailto:mike{at}barkto.com">mike{at}barkto.com>
wrote in =
message news:8rmoj111q3g=
7s3sbuarrdenedijcsrvvuc{at}4ax.com...> =20
  >>  >  I played with
this a bit more=20
  today.>  >> 
>  I changed the =
address that=20
  Outlook puts in the From: field for outgoing> 
>  =
emails=20
  to email{at}[123.123.123.123]">mailto:email{at}[123.123.123.123">email{at}[123.123.123.123]
(I'll =

  call this a "dotted quad"> 
>  address for this =
message),=20
  then saved that new config.  I sent myself
an>  =
> =20
  email.  When the email arrived in my inbox, the From: address was =

  the>  >  dotted quad. 
I OMB clicked on the =
dotted=20
  quad address, and selected the> 
>  add it to my =
address=20
  book option.> 
>>  >  Then I =
changed the=20
  From: address back to what it should be.>  =
>> =20
  >  Now I can send an email to that dotted quad address, =
Outlook=20
  accepts it>  >  as
input.>  =
>> =20
  >  The reason I did this is that previously when I wanted to =
send an=20
  email>  >  to a dotted quad
address, I could enter =
it into=20
  the To: field, but>  >  Outlook
would not allow me =
to send=20
  it.  Outlook would push me over to> 
>  enter =
the=20
  address into Outlook's address book.  
> =20
  >>  >  I guess that
Outlook doesn't allow me to =
send an=20
  email to someone who is>  > 
not in my address =
book? =20
  I'm not sure why it would do this, I know that>  =
> =20
  Outlook 97 didn't have this behavior.  Maybe that's why Outlook=20
  '97>  >  worked and Outlook 2003 =
doesn't.> =20
  >>  >  In any case, it
looks like it may be the =
input=20
  routines for entering an>  > 
email address into =
Outlook's=20
  address book that has the problem with the> 
> =20
  RFC-compliant dotted quad address.  Once a dotted quad address is =
in=20
  the>  >  address book, I can
send email to=20
  it.>  >> 
>  Weird.> =20
  >>  >  
/m>  =
>> =20
  >>  >> 
>  On Mon, 26 Sep 2005 =
21:50:32=20
  -0400, "Geo" <georger{at}nls.net>=20">mailto:georger{at}nls.net">georger{at}nls.net>=20
  wrote:>  >> 
>  >"Mike '/m'" =
<mike{at}barkto.com>">mailto:mike{at}barkto.com">mike{at}barkto.com>
wrote in=20
  message>  > =20
 
>news:25ugj1psik6mb69ifo2vfg6u7fg5uapm43{at}4ax.com...> =20
  >  >> 
>  >> I have not been able =
to get=20
  Outlook to send an email to>  >  =
>>> =20
  >  >>    email{at}[123.123.123.123]>=">mailto:email{at}[123.123.123.123">email{at}[123.123.123.123]>=
; =20
  >  >>> 
>  >> where =
123.123.123.123 is=20
  the IP address of a email server, and 'email'> 
>  =

  >> is a valid email account on that server.  I
believe this =
is an=20
  RFC>  >  >>
requirement, just like proper =
SMTP=20
  handling.>  > 
>>  >  =
>Perhaps=20
  you have an email admin like me who blocks email to an=20
  {at}ipaddress>  > 
>address? Some things need to =
change=20
  because of spam and many of the rfc's> 
>  >are =
sort of=20
  unchanging if you know what I mean.> 
> =20
  >>  >  >Oh, I
also block remote bounce =
notifications=20
  because they cause more>  > 
>problems than =
they solve.=20
  If you accept the email then deliver it, don't be>  =
> =20
  >returning it as undeliverable after you accept delivery is how it =
works=20
  in>  >  >todays spam and
virus filled=20
  world.>  > 
>>  >  >> =
Also, I=20
  keep nicknames for my friends.  For example, I use bob-w for=20
  Bob>  >  >> at
work, Bob-h for Bob at =
home. =20
  Well, Bob changed jobs, so I changed> 
>  >> =
the=20
  email address for Bob-w in the address book to his new =
email> =20
  >  >> address.  Unfortunately,
Outlook also stores =
the=20
  email address somewhere>  > 
>> else, and =
insists on=20
  sending Bob-w emails to his old email address. I've>  =
> =20
  >> not found the other location in the address book or=20
  configuration>  > 
>> options yet.  I =
now have=20
  a NewBob-w entry in the address book to work> 
>  =
>>=20
  around this feature.>  > 
>>  =
> =20
  >Yeah, Microsoft probably let the guy who did IE's braindead=20
  autocomplete>  >  >write
that stupid routine. =
He need=20
  to be 2x4'd.>  > 
>>  >  =
>>=20
  Don't get me started on Outlook and IMAP....> 
> =20
  >>  >  >I don't
believe in IMAP in the ISP =
world,=20
  it's a po box not a damn garage.>  >  =
>> =20
  >  >Geo.>  >  =
>

------=_NextPart_000_02EC_01C5CA9E.0E186350--

--- BBBS/NT v4.01 Flag-5