Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: Exchange 2k7 SMTP problem

6 views
Skip to first unread message

Gregorio P.

unread,
Apr 3, 2009, 12:29:18 PM4/3/09
to
Maybe, this behavior is because the another server only supports RFC 821...
I'll check my docs, so it will take a couple hours to get a complete answer
related to this point :)

-GP

"Thomas" <Tho...@discussions.microsoft.com> wrote in message
news:43F93A92-F13F-4D46...@microsoft.com...
> Hello guys,
>
> I have a problem with a smtp connection from exchange 2k7 sp1 + ur 7 to a
> thrid party smtp server. Sometimes Exchange sends messages to that smtp
> server an the other server rejects this message with 503 Sender already
> specified.
>
> In the exchange smtp send logs i see that Exchange does the following:
> 220 <othersmtpserver> SMTP
> EHLO <myserversfqdn>
> 500 Command unrecognized
> HELO <myserversfqdn>
> 250 <otherserversname> Hello <myserversfqdn>, pleased to meet you
> MAIL FROM: <myuser@mydomain>
> 250 Sender <myuser@mydomain> OK
> RCPT TO: <recipient@otherdomain>
> 250 Recipient <recipient@otherdomain> OK
> DATA
> 354 Enter mail, end with "." on a line by itself
> 250 Message accepted for delivery
>
> MAIL FROM: <thesame_myuser@mydomain>
> 503 Sender already specified
> QUIT
> 221 <otherserversname> closind connection
>
> The problem is, that the Exchange server tries to send two messages in one
> connection. But why?
> By the way, we use a .net Application that generates the email messages,
> puts them into the outbox of <myuser>'s Outlook 2003 and then the mails
> are
> send to the Exchange 2007 server with HT,MB,CAS,UM roles installed.
>
> I've no idea what the problem is. The problem occurs when many messages
> are
> send through the seperate SMTP connector to the other smtp server.
>
> Pleas help!!!
>
> Thanks!

Gregorio P.

unread,
Apr 3, 2009, 1:02:37 PM4/3/09
to
hi
this is a problem from other server,
check this link pls [ http://support.microsoft.com/kb/202765 ]

for Exchange 2007, maybe one workaround is create a smtp domain name scoped
send connector (sorry about my English) and set this send connector to use
helo instead ehlo... [you could use set-sendconnector ]

I will continue checking, but maybe it takes a couple days, because I don't
have a destination server to test this behavior...


OT: I get this funny but aybe useful thread...
http://lists.exim.org/lurker/message/19990301.103915.0eb43454.en.html

good luck!!

-GP

"Gregorio P." <gregor...@NOSPAMmsn.com> wrote in message
news:7301A693-F4D7-4993...@microsoft.com...

Thomas

unread,
Apr 5, 2009, 8:11:01 AM4/5/09
to
Thanks for the very helpful solution. So the other server is not RFC 821
compliant because as in 4.1.1 they say "There may be zero or more
transactions in a session." which the other server does not support, right?

I'll test this scenario and will tell you what helped me.

btw. the hotline of the other application says that exchange 2007 will not
work correctly because it sends more than one message in a connection (which
is false)!

0 new messages