Outlook adds =SMTP: to e-mail address?

[Eugene Nine]

I have one user who is getting NDR messages because +SMTP: gets added to the
front of the e-mail address. He is working remote using a roadrunner Cable
modem connection through a vpn to connect to the exhange server. The
problem seems intermittent as I can look back through his sent items and the
same address has been sent to before without the =smtp in the front. He
receives this message from the mail server:

The original message was received at Tue, 15 Jul 2003 09:24:26 -0400 (EDT)
from [xxx.xxx.xxx.xxx]

----- The following addresses had permanent fatal errors -----
<=SMTP:[email protected]>
(reason: 550 5.1.1 unknown or illegal alias: =SMTP:[email protected])

^^^Note the =SMTP: in front of the address
----- Transcript of session follows -----
.... while talking to ms-mta-02-fn.columbus.rr.com.:<<< 550 5.1.1 unknown or illegal alias: =SMTP:[email protected]
550 5.1.1 <=SMTP:[email protected]>... User unknown
<<< 554 5.5.0 No recipients have been specified.

I have searched his contacts for anything with the text =SMTP but the
problem is not limited to one contact and so far any address that has
generated the error has not done it more than once. Other people in the
copany have the same setup Office 2000, windows 2000, etc and no one else
has had the problem.

 

[Lanwench [MVP - Exchange]]

I can't see how Outlook itself could possibly be doing it. Perhaps there's
an add-in? I've never seen this before <scratches head>

I have one user who is getting NDR messages because +SMTP: gets added
to the front of the e-mail address. He is working remote using a
roadrunner Cable modem connection through a vpn to connect to the
exhange server. The problem seems intermittent as I can look back
through his sent items and the same address has been sent to before
without the =smtp in the front. He receives this message from the
mail server:

The original message was received at Tue, 15 Jul 2003 09:24:26 -0400
(EDT) from [xxx.xxx.xxx.xxx]

----- The following addresses had permanent fatal errors -----
<=SMTP:[email protected]>
(reason: 550 5.1.1 unknown or illegal alias:
=SMTP:[email protected])

^^^Note the =SMTP: in front of the address
----- Transcript of session follows -----
... while talking to ms-mta-02-fn.columbus.rr.com.:<<< 550 5.1.1 unknown or illegal alias: =SMTP:[email protected]
550 5.1.1 <=SMTP:[email protected]>... User unknown
<<< 554 5.5.0 No recipients have been specified.

I have searched his contacts for anything with the text =SMTP but the
problem is not limited to one contact and so far any address that has
generated the error has not done it more than once. Other people in
the copany have the same setup Office 2000, windows 2000, etc and no
one else has had the problem.

 

[Eugene Nine]

Through an exchange server. He is typing the name or replying to an
previous message. Seems to only happen to address not on the exchange
server, the receipents I checked were not in either the GAL or his contacts.

What sort of account is the user using to send the message - Exchange or
POP/IMAP? Are the problem recipients internal or external addresses? How
is the user entering the recipients - selecting them from the address book,
or typing them in?

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


"Lanwench [MVP - Exchange]"

I can't see how Outlook itself could possibly be doing it. Perhaps there's
an add-in? I've never seen this before <scratches head>

I have one user who is getting NDR messages because +SMTP: gets added
to the front of the e-mail address. He is working remote using a
roadrunner Cable modem connection through a vpn to connect to the
exhange server. The problem seems intermittent as I can look back
through his sent items and the same address has been sent to before
without the =smtp in the front. He receives this message from the
mail server:

The original message was received at Tue, 15 Jul 2003 09:24:26 -0400
(EDT) from [xxx.xxx.xxx.xxx]

----- The following addresses had permanent fatal errors -----
<=SMTP:[email protected]>
(reason: 550 5.1.1 unknown or illegal alias:
=SMTP:[email protected])

^^^Note the =SMTP: in front of the address
----- Transcript of session follows -----
... while talking to ms-mta-02-fn.columbus.rr.com.:
DATA
<<< 550 5.1.1 unknown or illegal alias: =SMTP:[email protected]
550 5.1.1 <=SMTP:[email protected]>... User unknown
<<< 554 5.5.0 No recipients have been specified.

I have searched his contacts for anything with the text =SMTP but the
problem is not limited to one contact and so far any address that has
generated the error has not done it more than once. Other people in
the copany have the same setup Office 2000, windows 2000, etc and no
one else has had the problem.

 

[Eugene Nine]

Only thing I can think of would be ACT2000 but the one contact I was
checking with was not in ACT. he's just typeing the name in the address bar
or replying to message he was sent.
"Lanwench [MVP - Exchange]"

I can't see how Outlook itself could possibly be doing it. Perhaps there's
an add-in? I've never seen this before <scratches head>

I have one user who is getting NDR messages because +SMTP: gets added
to the front of the e-mail address. He is working remote using a
roadrunner Cable modem connection through a vpn to connect to the
exhange server. The problem seems intermittent as I can look back
through his sent items and the same address has been sent to before
without the =smtp in the front. He receives this message from the
mail server:

The original message was received at Tue, 15 Jul 2003 09:24:26 -0400
(EDT) from [xxx.xxx.xxx.xxx]

----- The following addresses had permanent fatal errors -----
<=SMTP:[email protected]>
(reason: 550 5.1.1 unknown or illegal alias:
=SMTP:[email protected])

^^^Note the =SMTP: in front of the address
----- Transcript of session follows -----
... while talking to ms-mta-02-fn.columbus.rr.com.:

DATA

<<< 550 5.1.1 unknown or illegal alias: =SMTP:[email protected]
550 5.1.1 <=SMTP:[email protected]>... User unknown
<<< 554 5.5.0 No recipients have been specified.

I have searched his contacts for anything with the text =SMTP but the
problem is not limited to one contact and so far any address that has
generated the error has not done it more than once. Other people in
the copany have the same setup Office 2000, windows 2000, etc and no
one else has had the problem.

 

[Jeff Stephenson [MSFT]]

I don't know anything about ACT - is it possible to disable it temporarily?
If so, try doing that and seeing if the problem continues.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights

Only thing I can think of would be ACT2000 but the one contact I was
checking with was not in ACT. he's just typeing the name in the address bar
or replying to message he was sent.
"Lanwench [MVP - Exchange]"

I can't see how Outlook itself could possibly be doing it. Perhaps there's
an add-in? I've never seen this before <scratches head>

I have one user who is getting NDR messages because +SMTP: gets added
to the front of the e-mail address. He is working remote using a
roadrunner Cable modem connection through a vpn to connect to the
exhange server. The problem seems intermittent as I can look back
through his sent items and the same address has been sent to before
without the =smtp in the front. He receives this message from the
mail server:

The original message was received at Tue, 15 Jul 2003 09:24:26 -0400
(EDT) from [xxx.xxx.xxx.xxx]

----- The following addresses had permanent fatal errors -----
<=SMTP:[email protected]>
(reason: 550 5.1.1 unknown or illegal alias:
=SMTP:[email protected])

^^^Note the =SMTP: in front of the address
----- Transcript of session follows -----
... while talking to ms-mta-02-fn.columbus.rr.com.:
DATA
<<< 550 5.1.1 unknown or illegal alias: =SMTP:[email protected]
550 5.1.1 <=SMTP:[email protected]>... User unknown
<<< 554 5.5.0 No recipients have been specified.

I have searched his contacts for anything with the text =SMTP but the
problem is not limited to one contact and so far any address that has
generated the error has not done it more than once. Other people in
the copany have the same setup Office 2000, windows 2000, etc and no
one else has had the problem.