Hi all: I need help to configure a exchange smtp 2003 connector. I already had create a connector to send the emails to a windows 2003 smtp server with but it seems to be override by another exchange configuration. The mails keep going to the threadwall. Any Help would be appreciate. My configuration is as Follow: Exchange 2003 Server Threadwall Windows 2003 server with smtp services Best Regards, Hildemar Antoyma

On Tue, 15 Feb 2011 20:44:08 +0000, Hildemar Antoyma wrote: >I need help to configure a exchange smtp 2003 connector. I already had create a connector to send the emails to a windows 2003 smtp server with but it seems to be override by another exchange configuration. The mails keep going to the threadwall. Any Help would be appreciate. What are the address space values assigned to each SMTP Connector? >My configuration is as Follow: > >Exchange 2003 Server > >Threadwall > >Windows 2003 server with smtp services --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

The adress space in the smtp connector is mossha.something.net, and the scope is entire organization, the option "Allow messages to be relayed to these domains" is check. Thanks

On Wed, 16 Feb 2011 13:21:27 +0000, Hildemar Antoyma wrote: >The adress space in the smtp connector is mossha.something.net, and the scope is entire organization, the option "Allow messages to be relayed to these domains" is check. If you have the samme address space in both SMTP Connectors you'll have problems like what you're seeing. If you want all mail addressed to that domain to go to the smart host then only the one SMTP Connector should have that domai in its address apce. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich, i don't think that's the problem, I have 4 smtp connectors and everyone has a distinct address space, but the smtp connector with mossha.something.net keep routing the mails to the Threadwall Best Regards, Hildemar Antoyma On Wed, 16 Feb 2011 13:21:27 +0000, Hildemar Antoyma wrote: >The adress space in the smtp connector is mossha.something.net, and the scope is entire organization, the option "Allow messages to be relayed to these domains" is check. If you have the samme address space in both SMTP Connectors you'll have problems like what you're seeing. If you want all mail addressed to that domain to go to the smart host then only the one SMTP Connector should have that domai in its address apce. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP Hildemar Antoyma Web Developer

On Thu, 17 Feb 2011 13:15:02 +0000, Hildemar Antoyma wrote: >Hi Rich, i don't think that's the problem, I have 4 smtp connectors and everyone has a distinct address space, Well, when I asked what address spaces were assigned to the SMTP connectors you only supplied one domain name. :-) >but the smtp connector with mossha.something.net keep routing the mails to the Threadwall So, looking at just this one SMTP Connector, is it using DNS to find the target server, or is it forwarding mail to a smart host? I'm not sure what a "threadwall" is. Do you mean "firewall"? Are the messages that are addressed to the domain mossha.something.net being sent by Outlook clients using RPC connections, or are they being sent by SMTP clients to your server for delivery to somewhere else? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich, On Thu, 17 Feb 2011 13:15:02 +0000, Hildemar Antoyma wrote: >Well, when I asked what address spaces were assigned to the SMTP connectors you only supplied one domain name. :-) Jajajaja... sorry about that ;-) >So, looking at just this one SMTP Connector, is it using DNS to find the target server, or is it forwarding mail to a smart host? The SMTP connector is using DNS, >I'm not sure what a "threadwall" is. Do you mean "firewall"? Yes, the ""threadwall" means firewall >Are the messages that are addressed to the domain mossha.something.net being sent by Outlook clients using RPC connections, or are they being sent by SMTP clients to your server for delivery to somewhere else? The messages are being sent using outlook clients i don't know is this is relevant, but the domain mossha.something.net referes to a windows 2003 server with smpt. Thanks for your help Hildemar Antoyma Web Developer

On Thu, 17 Feb 2011 22:42:47 +0000, Hildemar Antoyma wrote: >>So, looking at just this one SMTP Connector, is it using DNS to find the target server, or is it forwarding mail to a smart host? >The SMTP connector is using DNS, [ snip ] >>Are the messages that are addressed to the domain mossha.something.net being sent by Outlook clients using RPC connections, or are they being sent by SMTP clients to your server for delivery to somewhere else? >The messages are being sent using outlook clients >i don't know is this is relevant, but the domain mossha.something.net referes to a windows 2003 server with smpt. What O/S it runs, or even which MTA, isn't relevant to your problem. Is that Windows 2003 server on your internal LAN? If you use 'nslookup', is there a MX record for the domain 'mossha.something.net'? To what server (and IP address) does that MX direct the e-mail? If there's no MX rcord, is there an "A" record for 'mossha.something.net'? When your Exchange server sends the e-mail to 'mossha.something.net', to what IP address is it sending the message? Also, if you're using DNS to discover the target server, why are you using another SMTP Connector? Wouldn't the default SMTP connector (the one with the address space of "*") work just as well? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Please answer Rich's question to clarify this symptom. One more question, what does “The mails keep going to the threadwall” mean? Can the message flow successfully if you turn off the firewall? Please also run Telnet to check whether the mail can be flowed normally via the MX record. Thanks. Novak Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Rich >Is that Windows 2003 server on your internal LAN? Yes >If you use 'nslookup', is there a MX record for the domain 'mossha.something.net'? To what server (and IP address) does that MX direct the e-mail? The mx record for the domain 'mossha.something.net' exist, it is sending the mail to the server mossha.something.net, i not sure how to check to what ip adress is sending the mail >When your Exchange server sends the e-mail to 'mossha.something.net', to what IP address is it sending the message? I don't know how to check this Also, if you're using DNS to discover the target server, why are you using another SMTP Connector? Wouldn't the default SMTP connector (the one with the address space of "*") work just as well? I need this configuration because i want all email with domain mossha.something.net to be redirected a windows 2003 smtp server, i think that the problem has something to do with my firewall because everything is somehow being redirected to it. Is there a way to tell exchange to override this configuration? Thanks for your help Hildemar Antoyma Web Developer

On Mon, 21 Feb 2011 13:46:19 +0000, Hildemar Antoyma wrote: >Hi Rich >>Is that Windows 2003 server on your internal LAN? >Yes >>If you use 'nslookup', is there a MX record for the domain 'mossha.something.net'? To what server (and IP address) does that MX direct the e-mail? >The mx record for the domain 'mossha.something.net' exist, it is sending the mail to the server mossha.something.net, i not sure how to check to what ip adress is sending the mail The nslookup should show you the IP A records and IP addresses used by the MX record: > yahoo.com. Server: srvr005.XXXXX.com Address: 192.168.1.25 Non-authoritative answer: yahoo.com MX preference = 1, mail exchanger = i.mx.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = j.mx.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = k.mx.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = l.mx.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = m.mx.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = a.mx.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = b.mx.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = c.mx.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = d.mx.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = e.mx.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = f.mx.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = g.mx.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = h.mx.mail.yahoo.com i.mx.mail.yahoo.com internet address = 74.6.140.64 j.mx.mail.yahoo.com internet address = 66.94.237.64 k.mx.mail.yahoo.com internet address = 98.139.54.60 l.mx.mail.yahoo.com internet address = 74.6.136.244 m.mx.mail.yahoo.com internet address = 66.94.238.147 a.mx.mail.yahoo.com internet address = 67.195.168.31 b.mx.mail.yahoo.com internet address = 74.6.136.65 c.mx.mail.yahoo.com internet address = 206.190.54.127 d.mx.mail.yahoo.com internet address = 209.191.88.254 e.mx.mail.yahoo.com internet address = 67.195.168.230 f.mx.mail.yahoo.com internet address = 98.137.54.237 g.mx.mail.yahoo.com internet address = 98.137.54.238 h.mx.mail.yahoo.com internet address = 66.94.236.34 >>When your Exchange server sends the e-mail to 'mossha.something.net', to what IP address is it sending the message? >I don't know how to check this The SMTP send protocol log has that information. You have the logging set to "Verbose" on your send and receive connectors, don't you? You should. >>Also, if you're using DNS to discover the target server, why are you using another SMTP Connector? Wouldn't the default SMTP connector (the one with the address space of "*") work just as well? >I need this configuration because i want all email with domain mossha.something.net to be redirected a windows 2003 smtp server, Then the MX record for the domain should use an "A" record for that server. Which is why I asked why you were using a different send connector since the other send connector you have is already using DNS to find the MX and A records to do this. If you want to avoid DNS (which it sounds like you do) then change the send connector to use a smart host and put the IP address of the SMTP server for the domain 'mossha.something.net' into the smart host edit box. >i think that the problem has something to do with my firewall because everything is somehow being redirected to it. Is there a way to tell exchange to override this configuration? Thanks for your help My guess is that the MX is sending your mail to an IP address in your DMZ and not to the SMTP server that's on your LAN. To fix that, use a smart host, not DNS, to deliver the mail. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich: Sorry for not writing to you in some time, but i was making some tests in my company infrastructure and i found some insteresting facts about the exchange configuration: 1) I have to mention that i need this exchange configuration because i'm implementing incoming email for sharepoint 2007. 2) Mi exchange server is configured to send all emails to the firewall. 3) In the firewall, i only can configure one domain (something.com) and when it receives a element with another domain name (mossha.something.net), the firewall doesn't know what to do with it. That's why i can't get this configuration working. 4) The Question is ¿is there a way in exchange 2003 to create a local virtual domain? if this is possible, i can create a connector to this domain and then route the mail to my smtp sever (mossha.something.net). Thanks for all your help in this matter Hildemar Antoyma Web Developer

On Wed, 2 Mar 2011 23:12:42 +0000, Hildemar Antoyma wrote: >Sorry for not writing to you in some time, but i was making some tests in my company infrastructure and i found some insteresting facts about the exchange configuration: > >1) I have to mention that i need this exchange configuration because i'm implementing incoming email for sharepoint 2007. But incoming mail doesn't use a send connector! >2) Mi exchange server is configured to send all emails to the firewall. So you have a send connector that's configured to use a smart host, and you've used the IP address of the firewall as the smart host??? Usually, it;s the job of the network to deal with IP routing. Why not let it do it's job and let Exchange handle the e-mail stuff? Why use a smart host at all? >3) In the firewall, i only can configure one domain (something.com) and when it receives a element with another domain name (mossha.something.net), the firewall doesn't know what to do with it. That's why i can't get this configuration working. But if DNS resolves mossha.something.net to an IP address on your LAN it shouldn't go anywhere near your perimeter firewall -- if you don't use the firewall as the smart host. >4) The Question is is there a way in exchange 2003 to create a local virtual domain? if this is possible, i can create a connector to this domain and then route the mail to my smtp sever (mossha.something.net). If I were you I'd rethink the design of your e-mail delivery. It sounds like you're trying to force Exchange into acting as a sort of network router. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP