Re: mail not sent outside



Hi Wolter,

Don't assume Exchange is wrong. I would contact planet for this. They are
known for having problems with their mailservers often. One of the reasons I
hate clients who have planet as their ISP.

--
Regards,

Marina Roos
Microsoft SBS-MVP
One of the Magical M&M's
www.smallbizserver.net
Take part in SBS forum:
http://www.smallbizserver.net/Default.aspx?tabid=53

"Wolter Kaper" <WolterKaper@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:561DC798-B22E-41BB-95F7-BCDAE2A55F85@xxxxxxxxxxxxxxxx
Yes, my idea is to keep on using the smart host of the ISP for SMTP-out.
They do the POP3-collection (+spam filtering) quite well.

There's no reason for direct sending and indeed, in our current setup it
won't work.

So I return to my original question:
How is it possible that I can't reach the smart host anymore if I type the
FQDN into the "smart host" box, while it still worksd if I type the
IP-address of the smart host?
I verified using nslookup that the FQDN and the IP of the smart host still
belong together and my DNS setup is good to recognise this.
So, what's wrong with Exchange??
It used to work!

Any advice appreciated.
Wolter

"Jim Behning SBS MVP" wrote:

Many email servers will not accept email if the MX record and the
sending email server do not match. And then they may do reverse dns. I
am sure that something in my statement is incorrect but the short
story is if you collect all your company email with a pop collector,
sending email with dns will probably fail often. Maybe all this starts
with having a static real world ip. If you have that you can get the
reverse dns issue resolved, You can get the A record resolved to the
name of the sending server. By then you are almost to the point of
accepting email directly. On the other hand some isps do a pretty good
job of washing spam which can be a benefit of doing pop collection.

On Sun, 19 Aug 2007 17:47:31 +0800, "ThatsIT.net.au" <me@thatsit>
wrote:

why not use dns to send all mail?

is it a problem at the ISP end?

"Wolter Kaper" <WolterKaper@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9054DCD0-7AA3-48EB-9DB2-58FD662B80FC@xxxxxxxxxxxxxxxx
Hi,

We have SBS2003 configured using the Internet Connection Wizard.
We receive email using the POP3 connector from our ISP.
We send mail NOT using DNS but to a smart host,
"mailrelay.planet.nl",
given
to us by our ISP. This setup worked fine for over a year.

A week ago, some days after installing SP2, mail stopped going out
and
senders immediately received this message:
"A configuration error in the e-mail system caused the message to
bounce
between two servers or between two recipients. Contact you
administrator"
<ourdomain.nl #5.3.5>
The same message (error 5.3.5) was also found in the logs under
"MSExchangeTransport".

I found these knowledge base articles: KB326304, KB555418, KB316617

Following KB326304, I checked the "SMTP-Connector for SmallBusiness"
that
was found in "First Organisation (Exchange)". I checked that the
right
smart
host was mentioned there, by FQDN, and that the Exchange server was
not
referring to itself.

Following KB555418, I checked the address space tab of this same
"SMTP
connector for Smallbusiness". The address space should be "*", as
indeed
it
was.
Next I checked the "Default SMTP virtual server", Advanced delivery
tab:
Configure button. No internal or external DNS servers should be
configured
there. Indeed, the list of DNS-servers was empty.

I tried various changes, after each change, restarting the server.
Also, noting all changes and finally carefully restoring the original
state.

Finally, the following change succeeded in solving the problem. BUT
it is
an
ugly solution:
On the "SMTP connector for SmallBusiness Server" I changed the smart
host
FQDN ("mailrelay.planet.nl") into the corresponding ip-address, as
reported
by ping and by nslookup.
This solved it.
However, our ISP frequently changes the active machine, so the
ip-address
is
ever changing. So this is not a good solution.

Why is Exchange suddenly unable to lookup "mailrelay.planet.nl" in
DNS?
When I type: nslookup mailrelay.planet.nl
then the DNS-service on the SBS server replies correctly and mentions
the
ip-address that currently works.
(Our DNS has been setup automatically by the SBS2003 installer, I
didn't
make changes to it).

Anybody had any problem like this?
Any suggestions or explanations appreciated!

With best regards,
Wolter Kaper



.


Loading