> Bryant,
> I recently did this exact same thing while testing a new exchange
> server, and finally figured out that I was not able to receive incoming
> mail to Exchange until I opened up each user in the Exchange system
> course, when the system goes live). I think this is only necessary if
> you have the SMTP virtual server configured to not relay mail, which you
> should.
> In any case, if you cannot telnet to port 25 from outside the lan, you
> will never get any mail, period. If it works from the local subnet and
> you are sure you have really taken the firewall down, then you probably
> have a restriction in the SMTP virtual server to only allow SMTP from
> your local subnet (just a guess).
> Also, did you set up more than one preference value for the
> "testmail.domain.com" mx record (if you had an ISP make the DNS change,
> then they almost certainly did)? If so, then the mail may be piling up
> at the backup mail server, where it usually will not bounce or expire
> for 72 hours. I found it useful to make sure there was no backup for
> the "testmail.domain.com" mx record (only while testing of course!),
> such that any delivery problems will result in an immediate bounce.
> For example, your isp might have set up an mx record for
> testmail.domain.com with a prefernce value of 10 that resolves to
> exchange.domain.com (A record for your server IP address), and then a
> second mx record with a preference value higher than 10 (usually 20),
> which resolves to backupmailserver.isp-domainname.com (your isp's backup
> mail server). Have them remove the 20 value record, and you should get
> bounces right away.
> Hope that helps!
> > We have just set up an Exchange 2000 server and want to have it
> > completely tested and verified before making an MX record change. We
> > have completed the telnet to port 110 from both inside the LAN and
> > outside. The telnet test to port 25 works from inside the lan, but
> > not from outside. After completely opening my firewall to allow
> > everything through I still could not get a response. I had figured
> > this was ok, because the telent to 25 is an SMTP test and only my
> > domain users will be using this server as an SMTP Server. Please tell
> > me if a am wrong about that.
> > The following was suggested by an ISP to test mail without disrupting
> > current settings:
> > Add an MX record for testmail.<domain-name>.com
> > did that and it is pingable
> > changed all of the smtp address porperties for my users to reflect the
> > testmail.<domain-name>.com
> > into the great internet abyss. no returned mail, no errors, no
> > received mail
> > Does anyone know if the "not able to telnet to 25 from outside"
> > problem is keeping mail out.
> > Note: All outbound mail works properly.
> > Any help greatly appreciated.
First of all thanks to all who have posted. I am further along now,
though not out of the woods. I can telnet from outside and the telnet
Yes there is an MX record setup. I have not yet contacted the ISP
asking them to remove the backup mail server record for
testmail.domain.com. This is what is happening now...mail sent to
So, mail is getting to the machine. The queues get clogged with mail
that is not able to be forced out and badmail gets the messages that
are not deliverable. I think I am close and have to mess with
connectors now to get it right. Such will be my Sunday. Thanks for
the posts and any further input.
Bryant
by