How to disable x400 and send using smtp

[CindyLu]

Hi -
I'm trying to get (what I thought was) as very simple new Exchange
installation going. I'm testing using OWA, but whenever I attempt to send a
message, an Event ID 290 is thrown, which indicates that it is trying to use
x400 to send the message. This is quite strange to me, since in the Active
Directory definition of the sending user, there is only an smtp email address
(it did originally contain an x400 address, but I've since removed it). The
smtp service is running on the exchange server.

Can some wise, kind soul instruct me how to get Exchange to send using
smtp instead of attempting to use x400?

Many thanks!

 

[neo [mvp outlook]]

Add the x400 back as it is required for Exchange/Outlook.

 

[Diane Poremsky [MVP]]

why did you remove it? it's required for exchange to work.

 

[CindyLu]

OK, I'll put it back, but that doesn't solve the original issue at all -
anytime I try to send an EvenID 290 is thrown. That's the root cause - ideas?

 

[CindyLu]

OK, I'll put it back, but that doesn't solve the original issue at all -
anytime I try to send an EvenID 290 is thrown. That's the root cause - ideas?

 

[CindyLu]

I removed the x400 *AFTER* I saw the entry in the event log (290) stating
that there was an x400 error. I did put the x400 entry back since you wrote
that its required, but I'm still baffled as to why the 290 error is being
generated and the mail is not being sent, even though the connector in the
routing group points to the default smtp server and the Address Space is SMTP
with "*" for address. Does there need to be an x400 in the address space? I
tried that too, using the same properties for Organization and Domain Name
that I saw in the 290 message, but that didn't help. I don't pretend at all
to be an Exchange expert - just the schmuck who has to have this thing
working by Tuesday. Any ideas???

 

[Milly Staples [MVP - Outlook]]

YOu are best off posting this in an Exchange news group as it has little if anything to do with Outlook. microsoft.public.exchange.clients would be a good place to start.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, CindyLu asked:

| I removed the x400 *AFTER* I saw the entry in the event log (290)
| stating that there was an x400 error. I did put the x400 entry back
| since you wrote that its required, but I'm still baffled as to why
| the 290 error is being generated and the mail is not being sent, even
| though the connector in the routing group points to the default smtp
| server and the Address Space is SMTP with "*" for address. Does
| there need to be an x400 in the address space? I tried that too,
| using the same properties for Organization and Domain Name that I saw
| in the 290 message, but that didn't help. I don't pretend at all to
| be an Exchange expert - just the schmuck who has to have this thing
| working by Tuesday. Any ideas???

 

[CindyLu]

Oh, of course you're right - please excuse my bleary-eye-edness.

 

[Diane Poremsky [MVP]]

Are you still using Ex5.5 in the organization or upgraded from it?

http://support.microsoft.com/kb/836563
http://support.microsoft.com/kb/841834

 

[neo [mvp outlook]]

I read the other posts, if you happen to go the route of posting in one of
the m.p.exchange.* groups, make sure you post the complete text of the x400
error in the event logs. W/out it, they are just going to say there isn't
enough info.

 

[CindyLu]

See, that's what's weird - all the posts I see pertaining to a 290 in the
Event Log have to do with an upgrade from 5.5. But we've NEVER used 5.5 -
this is a totally clean 2003 install. I'm so confused!

 

[Diane Poremsky [MVP]]

Did you ever use 5.5 on the network? I think if you do any type of
migration, short of a totally new network/AD, it knows 5.5 used to exist
there.

Otherwise, check with the exchange newsgroups - the regulars there are more
familiar with the nuts and bolts on the backend.