Why would messages be returned?

[Michael Hartmann]

Why do some mail messages arrive at our server and not others?
They're addressed identically. Is there something I can do to Exchange
Server 5.5 to fix this?

[Kirill S. Palagin]

You would better to give us more details.

Michael Hartmann wrote:

--
Intel is trying to spoil AMD by pressuring motherboard makers.
Say YES to AMD at
http://www.petitionpetition.com/cgi-bin/cgi12.cgi?petition_id=34
Demand investigation from FTC
http://www.usdoj.gov/atr/contact/newcase.htm
If you have any information on this send it here
newca...@usdoj.gov
Thanks.

Kirill S. Palagin

[Michael Hartmann]

We have Exchange Server configured as our primary mail domain and our
ISP's mail spooler as secondary. If the Exchange Server is running
24x7, why would anything ever get to the mail spooler? There seem to
be more than a dozen messages a day that do. Sometimes I see a
particular sender is sending to the same user more than once in a day,
and most of the messages correctly go into Exchange Server, but others
have to be picked up by dialing into the spooler.

[Chris Scharff]

mich...@ibo.nyc.ny.us (Michael Hartmann) is rumored to have said:

>We have Exchange Server configured as our primary mail domain and our
>ISP's mail spooler as secondary. If the Exchange Server is running
>24x7, why would anything ever get to the mail spooler? There seem to
>be more than a dozen messages a day that do. Sometimes I see a
>particular sender is sending to the same user more than once in a day,
>and most of the messages correctly go into Exchange Server, but others
>have to be picked up by dialing into the spooler.

If the other server is unable to contact yours it will try the next
highest Mx record. That could happen for a variety of reasons.. DNS
problems on their server, transient network problems, slow response
from your server, etc.

--
Chris Scharff
Exchange Administrator
BV Solutions Group

Be sure to read the Exchange FAQ:
http://www.swinc.com/resource/exch_faq.htm

[Rich Matheisen [MVP]]

cscharff@*NOSPAM*bigsecret.com (Chris Scharff) wrote:

>mich...@ibo.nyc.ny.us (Michael Hartmann) is rumored to have said:
>
>>We have Exchange Server configured as our primary mail domain and our
>>ISP's mail spooler as secondary. If the Exchange Server is running
>>24x7, why would anything ever get to the mail spooler? There seem to
>>be more than a dozen messages a day that do. Sometimes I see a
>>particular sender is sending to the same user more than once in a day,
>>and most of the messages correctly go into Exchange Server, but others
>>have to be picked up by dialing into the spooler.
>
>If the other server is unable to contact yours it will try the next
>highest Mx record. That could happen for a variety of reasons.. DNS
>problems on their server, transient network problems, slow response
>from your server, etc.

Or your IMS is unable to handle more than "X" number of incoming
connections. That limit can be raised on the "Connections" tab's
"Advanced..." button.

But that defaults to 30, and if your server is incapable of managing
that many inbound connections then you may need another IMS.

But that also raises the questions of why you need your ISP acting as
a secondary MX. If the transmitting server can't contact your server
it'll just retry the message later. There's no need to have a
secondary MX unless you're using an intermittant connection.

------------------
Rich Matheisen
MCSE, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm