bgo@PacBell.COM (Bud Odekirk) (02/21/90)
I would like to send mail to a friend that works for AT&T in Denver, Colorado.
The only information I have is his userid (rbs). Any AT&T users from Denver
out there ????
Appreciate any help.
*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\
Bud Odekirk
2600 Camino Ramon, Room 3W600E
San Ramon, Ca. 94583
415 823-1379
{att,bellcore,sun,ames,pyramid}!pacbell!pbhya!bgo
/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\*/\seeba@amelia.nas.nasa.gov (Thomas D. Seeba) (02/23/90)
In article <33476@pbhya.PacBell.COM> bgo@PacBell.COM (Bud Odekirk) writes: >I would like to send mail to a friend that works for AT&T in Denver, Colorado. >The only information I have is his userid (rbs). Any AT&T users from Denver >out there ???? I have been attempting to e-mail an AT&T employee also, and had every attempt rebuffed until recently. After perusing the uucp maps, I found that the following seems to work: <firstname>.<mi>.<lastname>@att.com Evidently, the att.com node is able to decode employee names when they are given in the format of firstname, middle initial, last name separated by '.'s. I know the user I was trying to reach has an AT&TMAIL mail account identified by his last name only; mail addressed this way was refused by the postmaster at att.com. The above assumes, of course, that you are originating the mail from the Internet, and that the recipient is known by the att.com node. I believe that most, but not all, AT&T employees are so known. I would be interested in hearing from any others who have knowledgeable tidbits to add, since the above is mainly the result of conclusions gained from hacking around. .o0o. Tom Seeba seeba@prandtl.nas.nasa.gov