Re: Exchange 2007 Users cant send mail to 2003

Well ... from MS themselves ... If there is a message in the poison message
queue, we recommend that you contact Microsoft Product Support to report the
potentially harmful message that Exchange detected. For more information
about how to contact support, visit the Microsoft Help and Support Web site.


Good luck.




"Michael Jones" <MichaelJones@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4400604E-8580-4630-BCAB-4BAEC2D739F7@xxxxxxxxxxxxxxxx
I tried to send mail via telnet from 2007 to 2003, but I get the same
problem
with it in the Poison Message Queue. Exchange 2007 doesn't sseem to be
responding to the same telnet mail commands I am used to, so I can't send
that way via telnet due to ignorance i think.

"WorkingHard" wrote:

by the way can you send mail fron e2k7 to e2k3 using telnet?

"Michael Jones" <MichaelJones@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F99E3311-EAC8-43B9-8EEF-085C088DFBF3@xxxxxxxxxxxxxxxx
Strange. Ran the mail flow troubleshooter and it sas it cannot open
port
25
or 389 on E2K7 server, but I can telnet to and from both just file.

EHLO output is as follows

Exchange 2003 server----

220 EXCHANGE2007.towill.com Microsoft ESMTP MAIL Service ready at Fri,
14
Dec 20
07 16:32:22 -0800
EHLO
250-EXCHANGE2007.towill.com Hello [192.168.115.9]
250-SIZE
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-X-ANONYMOUSTLS
250-AUTH NTLM
250-X-EXPS GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250-XEXCH50
250 XRDST

Exchange 2007 server----

220 exchange2003.towill.com Microsoft ESMTP MAIL Service, Version:
6.0.3790.3959
ready at Fri, 14 Dec 2007 16:33:34 -0800
EHLO
250-exchange2003.towill.com Hello [192.168.115.7]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-X-EXPS GSSAPI NTLM LOGIN
250-X-EXPS=LOGIN
250-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-X-LINK2STATE
250-XEXCH50
250 OK

Not sure what you mean by 7/8 bit. Everything is fairly vanilla. Not
a
complex setup.

Thanks sooooo much for taking the time on this. I cannot tell you how
much
I appreciate it. I searched all over the web and found many
complaining
of a
similar issue but now posts of anyone solving the problem.

Your work here is greatly appreciated

"WorkingHard" wrote:

poisend message normally indicates server failure with corrupt mails
that
are considered harmfull.. otherwise they normally get stuck in another
queue.

hmmm

7/8 bit enabled on both exchange servers? . .. do a telnet and excute
ehlo
to both servers. see if they are similar. post the results if you
want.
just
trying to get a grip on the situation here.

"Michael Jones" <MichaelJones@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:B41A2A88-EB2D-456B-B777-63971958CF85@xxxxxxxxxxxxxxxx
I haven't even gotten to installing anti-virus yet. Machine is
pretty
valilla except that it is a domain member. I didn't wan't to get
fancy
until
I knew things were working.

As far as resubmitting them, I've tried resending, having someone
from
that
server send me a message and then replying, just about everything I
can
think
of.

The message tracking center is no help. Doesn't even look like the
message
is even attempted to be sent to the exchange 2003 server.

"WorkingHard" wrote:

can you resubmit them? any server failures transport agents issues?
for
some
reason they must end up there ... any anti virus running?




"Michael Jones" <MichaelJones@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:DA8B7080-3F4D-44B6-BFC1-F1446B32B8A2@xxxxxxxxxxxxxxxx
I checked the Authentication settings on the 2007 receive
connectors.
All
look good to me.

The messages all wind up in the Poison Message Queue. I can see
them
with
the Queue viewing tool in E2K7. There is no error code next to
"Last
Error:"when each messages info is reviewed. The user gets no
indication
the
delivery failed in
outlook or OWA.

"WorkingHard" wrote:

did you check the authentication settings? can you see the mail
from
e2k7
to
2k3 stuk in the queue and if so what if any is the error
message?


"Michael Jones" <MichaelJones@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message
news:CB7692C2-B9A5-4152-B5EA-F4FF009DB584@xxxxxxxxxxxxxxxx
All this appears to be configured correctly. ip ranges are
always
0.0.0.0 -
255.255.255.255 and the ports are 25 on both. All connectors
exist
on
both
servers but as far as working I am unsure. I only know the
following

I can send mail to the internet from the 2003 & 2007 users
I can send mail to the 2007 users from 2003 users
I can't send mail to 2003 users from 2007 users

Thanks for the ideas. Any others?

"WorkingHard" wrote:

check the security settings, ports and ip ranges of teh
receive
connector
on
e2k7 and also make sure the routing group connectors between
e2k3
and
e2k7
exist and are functioning.

"Michael Jones" <MichaelJones@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote
in
message
news:0647BED6-A919-419D-A061-CA6040E4665A@xxxxxxxxxxxxxxxx
I have just recently setup a brand new server on Windows
2003
Server
R2
as
a
member server in an existing domain with Exchange 2003 SP2
installed
and
running. I Installed Exchange 2007, and started to perform
a
migration.
both servers see each other and appear to be configured
properly
yet
users
with accounts moved from the Exchange 2003 server to the
Exchange
2007
Server
can receive mail, send mail to the internet, but not send
mail
to
any
users
on the Exchange 2003 server.

Please Help! Thanks in advance.

Michael Jones

















.

Relevant Pages

  • Re: No inbound emails from outside domain
    ... The SMTP Virtual Server is still not available. ... So are all the Exchange services still running now? ... The MAD Monitoring thread was unable to read the queue information, ...
    (microsoft.public.windows.server.sbs)
  • RE: Exchange Bandwidth
    ... queue on your exchange server. ... what kind of emails in your queue? ... Open Exchange System Manager and SMTP Queues to open the Properties of the ...
    (microsoft.public.windows.server.sbs)
  • Re: No inbound emails from outside domain
    ... Output Queue Length = 0 ... I don't think reinstalling Exchange will help. ... Maybe I need to run out to work and sit down at the server. ... On TELNET - it responded with code 220. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2007 Users cant send mail to 2003
    ... what worries me is the possoin message queue ... ... or 389 on E2K7 server, but I can telnet to and from both just file. ... "WorkingHard" wrote: ... is even attempted to be sent to the exchange 2003 server. ...
    (microsoft.public.exchange.setup)
  • Re: unexpected outbound e-mail messages appear in the SMTP queue
    ... Please check the following Exchange setting. ... You can find the sender of the e-mails in the Queue. ... Overview of Exchange Server 2003 and Antivirus Software ... Open the properties page of the Default SMTP Virtual Server in Exchange ...
    (microsoft.public.exchange.admin)