From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0037_01C5C47A.576F3FD0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

  Don't you even read messages before you jump to complain more and make =
yourself look like an idiot?

Rich

  "Mike '/m'"  wrote in message =
news:dv6mj1peabfgr52ikd77dugsu7l2c9oeun{at}4ax.com...
  email{at}[123.123.123.123]  is a valid email address everywhere I've =
tried
  except MS Outlook.  There are no special characters in it.  Nice try,
  though.

  from RFC 2821, section 4.1.3

     4.1.3 Address Literals

     Sometimes a host is not known to the domain name system and
     communication (and, in particular, communication to report and =
repair
     the error) is blocked.  To bypass this barrier a special literal =
form
     of the address is allowed as an alternative to a domain name.  For
     IPv4 addresses, this form uses four small decimal integers =
separated
     by dots and enclosed by brackets such as [123.255.37.2], which
     indicates an (IPv4) Internet Address in sequence-of-octets form.  =
For
     IPv6 and other forms of addressing that might eventually be
     standardized, the form consists of a standardized "tag" that
     identifies the address syntax, a colon, and the address itself, in =
a
     format specified as part of the IPv6 standards [17].



  When I deleted it as you mention, it goes away only temporarily.  In =
any
  case, why should I, as a user, have to manually delete an item in
  Outlook's name cache?  MS Outlook's name caching "service" should =
handle
  that by itself, without me asking.  Besides, Microsoft wants $35 a pop
  for me to ask why the program doesn't clear its name cache when it
  should.  I'll give you another nice try for that, though.  Plus a =
bonus
  point for trying to increase MS revenue.



    /m



  On Mon, 26 Sep 2005 18:07:33 -0700, "Rich"  wrote:

  >   An email address with a domain literal like your example =
(email{at}[123.123.123.123]) still gets delivered to your SMTP server.  It =
is your overloaded email server's responsiblity to route this.  Or maybe =
you simply don't know how to enter an address containing special =
characters.  In this case it would be [smtp:email{at}\[123.123.123.123\]].
  >
  >   In regard to deleting your now out of date favorite, did you try =
pressing the delete key when the name appears as you type?  It appears = not.
  >
  >   You sure do like to complain alot.  If you don't know how to do =
something you might consider an alternative.  It's a pretty popular one. =
 Ask.
  >
  >Rich
  >
  >
  >  "Mike '/m'"  wrote in message =
news:25ugj1psik6mb69ifo2vfg6u7fg5uapm43{at}4ax.com...
  >
  >
  >  I have not been able to get Outlook to send an email to=20
  >
  >     email{at}[123.123.123.123]=20
  >
  >  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.
  >
  >  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.
  >
  >
  >   /m
------=_NextPart_000_0037_01C5C47A.576F3FD0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








  Don't you
even read =
messages before you=20
jump to complain more and make yourself look like an idiot?
 
Rich
 

  "Mike '/m'" <mike{at}barkto.com>=20">mailto:mike{at}barkto.com">mike{at}barkto.com>=20
  wrote in message news:dv6mj1peabf=
gr52ikd77dugsu7l2c9oeun{at}4ax.com...email{at}[123.123.123.123]">mailto:email{at}[123.123.123.123">email{at}[123.123.123.123] 
= is a=20
  valid email address everywhere I've triedexcept MS Outlook.  =
There=20
  are no special characters in it.  Nice =
try,though.from RFC=20
  2821, section 4.1.3   4.1.3 Address=20
  Literals   Sometimes a host is not
known to the =
domain name=20
  system and   communication (and, in particular, =
communication to=20
  report and repair   the error) is
blocked.  To =
bypass this=20
  barrier a special literal form   of the address is =
allowed as an=20
  alternative to a domain name.  For   IPv4 =
addresses, this=20
  form uses four small decimal integers separated   by =
dots and=20
  enclosed by brackets such as [123.255.37.2], which   =
indicates=20
  an (IPv4) Internet Address in sequence-of-octets form. =20
  For   IPv6 and other forms of addressing that might =
eventually=20
  be   standardized, the form consists of a
standardized =
"tag"=20
  that   identifies the address syntax, a
colon, and the =
address=20
  itself, in a   format specified as part of the IPv6 =
standards=20
  [17].When I deleted it as you
mention, it goes away =
only=20
  temporarily.  In anycase, why should I, as a user, have to =
manually=20
  delete an item inOutlook's name cache?  MS Outlook's name =
caching=20
  "service" should handlethat by itself, without me
asking.  =
Besides,=20
  Microsoft wants $35 a popfor me to ask why the program doesn't =
clear its=20
  name cache when itshould.  I'll give you another nice try for =
that,=20
  though.  Plus a bonuspoint for trying to increase MS=20
  revenue. 
/mOn Mon, 26 Sep 2005 =
18:07:33=20
  -0700, "Rich" <{at}>
wrote:>   An email =
address with a=20
  domain literal like your example (email{at}[123.123.123.123])">mailto:email{at}[123.123.123.123">email{at}[123.123.123.123])
=
still gets=20
  delivered to your SMTP server.  It is your overloaded email =
server's=20
  responsiblity to route this.  Or maybe you simply don't know how =
to enter=20
  an address containing special characters.  In this case it would =
be=20
 
[smtp:email{at}\[123.123.123.123\]].>>  
In =
regard to=20
  deleting your now out of date favorite, did you try pressing the =
delete key=20
  when the name appears as you type?  It appears=20
  not.>>   You sure do
like to complain =
alot.  If=20
  you don't know how to do something you might consider an =
alternative. =20
  It's a pretty popular one. =20
 
Ask.>>Rich>>> 
"Mike '/m'" =
<mike{at}barkto.com>">mailto:mike{at}barkto.com">mike{at}barkto.com>
wrote in =
message news:25ugj1psik6=
mb69ifo2vfg6u7fg5uapm43{at}4ax.com...>>> =20
  I have not been able to get Outlook to send an email to=20
 
>>    
email{at}[123.123.123.123]=20">mailto:email{at}[123.123.123.123">email{at}[123.123.123.123]=20
  >>  where 123.123.123.123 is
the IP address of a =
email=20
  server, and 'email'>  is a valid email account on that=20
  server.  I believe this is an RFC> 
requirement, just =
like=20
  proper SMTP handling.>>  Also,
I keep nicknames for =
my=20
  friends.  For example, I use bob-w for
Bob>  at work, =
Bob-h=20
  for Bob at home.  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 email address=20
  somewhere>  else, and insists on sending Bob-w
emails to =
his old=20
  email address. I've>  not found the other
location in the =
address=20
  book or configuration>  options yet. 
I now have a =
NewBob-w=20
  entry in the address book to work>  around this=20
 
feature.>>>  
=
/m

------=_NextPart_000_0037_01C5C47A.576F3FD0--

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