| Author |
Message |
Jeff Foster
Guest
|
 Posted:
Fri Dec 09, 2005 5:58 pm Post subject:
Test Exchange before changing MX records |
|
|
I am in the process of setting up an Exchange server for my network. It's
part of SBS but since this question is related solely to Exchange, I figured
I would do better to ask it here.
Our email is currently hosted by our ISP. The clients currently use Outlook
to download their POP3 mail directly from the ISP's servers. I have
Exchange set up and running and all appears fine, but before I change our
DNS MX records to point to our IP address and move everyone to Exchange, I
would like to test the Exchange setup by sending it an email to see if it
receives it without any problem.
How can I send it a test email when there is no current MX record pointing a
domain name to our IP address?
I tried creating an account in outlook and using our IP address as the SMTP
server in the account details and then sending an email, but Outlook said it
couldn't find the outgoing server. I guess that's a good thing so that
people can't just point their email apps to our server to send mail from,
but it didn't help me out.
I have port 25 open on our firewall and routed to the Exchange server (using
port forwarding since we only have one static IP).
Do I need to set up a test email server offsite with DNS on it and set up a
DNS entry on that test server to point our domain to our IP, and then send
an email using that box as the sending email accounts MTA server? This
seems like a long way around what should be a simple problem.
Any suggestions?
Thanks,
Jeff
|
|
| Back to top |
|
 |
Bharat Suneja
Guest
|
| Posted:
Fri Dec 09, 2005 5:58 pm Post subject:
Re: Test Exchange before changing MX records |
|
|
- Send email from a telnet session (from outside your firewall)
http://www.suneja.com/blog/2005/10/sending-mail-from-telnet-session.html
- Make sure Recipient Policy has generated email addresses with your
public/registered domain as default
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------
"Jeff Foster" <noone@nowhere.com> wrote in message
news:%23BMPUuM$FHA.2264@tk2msftngp13.phx.gbl...
| Quote: | I am in the process of setting up an Exchange server for my network. It's
part of SBS but since this question is related solely to Exchange, I
figured I would do better to ask it here.
Our email is currently hosted by our ISP. The clients currently use
Outlook to download their POP3 mail directly from the ISP's servers. I
have Exchange set up and running and all appears fine, but before I change
our DNS MX records to point to our IP address and move everyone to
Exchange, I would like to test the Exchange setup by sending it an email
to see if it receives it without any problem.
How can I send it a test email when there is no current MX record pointing
a domain name to our IP address?
I tried creating an account in outlook and using our IP address as the
SMTP server in the account details and then sending an email, but Outlook
said it couldn't find the outgoing server. I guess that's a good thing so
that people can't just point their email apps to our server to send mail
from, but it didn't help me out.
I have port 25 open on our firewall and routed to the Exchange server
(using port forwarding since we only have one static IP).
Do I need to set up a test email server offsite with DNS on it and set up
a DNS entry on that test server to point our domain to our IP, and then
send an email using that box as the sending email accounts MTA server?
This seems like a long way around what should be a simple problem.
Any suggestions?
Thanks,
Jeff
|
|
|
| Back to top |
|
|
Jeff Foster
Guest
|
| Posted:
Fri Dec 09, 2005 5:58 pm Post subject:
Re: Test Exchange before changing MX records |
|
|
Thank you very much. That looks like exactly what I need. I'll try that
out as soon as I get a chance.
Jeff
"Bharat Suneja" <bharat@nospam.org> wrote in message
news:%23H53OAN$FHA.3568@TK2MSFTNGP09.phx.gbl...
| Quote: | - Send email from a telnet session (from outside your firewall)
http://www.suneja.com/blog/2005/10/sending-mail-from-telnet-session.html
- Make sure Recipient Policy has generated email addresses with your
public/registered domain as default
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------
"Jeff Foster" <noone@nowhere.com> wrote in message
news:%23BMPUuM$FHA.2264@tk2msftngp13.phx.gbl...
I am in the process of setting up an Exchange server for my network. It's
part of SBS but since this question is related solely to Exchange, I
figured I would do better to ask it here.
Our email is currently hosted by our ISP. The clients currently use
Outlook to download their POP3 mail directly from the ISP's servers. I
have Exchange set up and running and all appears fine, but before I
change our DNS MX records to point to our IP address and move everyone to
Exchange, I would like to test the Exchange setup by sending it an email
to see if it receives it without any problem.
How can I send it a test email when there is no current MX record
pointing a domain name to our IP address?
I tried creating an account in outlook and using our IP address as the
SMTP server in the account details and then sending an email, but Outlook
said it couldn't find the outgoing server. I guess that's a good thing
so that people can't just point their email apps to our server to send
mail from, but it didn't help me out.
I have port 25 open on our firewall and routed to the Exchange server
(using port forwarding since we only have one static IP).
Do I need to set up a test email server offsite with DNS on it and set up
a DNS entry on that test server to point our domain to our IP, and then
send an email using that box as the sending email accounts MTA server?
This seems like a long way around what should be a simple problem.
Any suggestions?
Thanks,
Jeff
|
|
|
| Back to top |
|
|
Jeff Foster
Guest
|
| Posted:
Sat Dec 10, 2005 1:38 am Post subject:
Re: Test Exchange before changing MX records |
|
|
Alright...I tried that and have two questions relating to those
instructions.
1. I did step one from inside the firewall and I got a response from
Exchange. However that was it. I didn't get another prompt to type in any
of the remaining commands. Do I need to start a new telnet session for step
two or am I missing something necessary for this telnet email session to
work?
2. I tried step one from outside the firewall and received no response. The
telnet session would not connect. I verified that the firewall was set to
allow TCP packets destined for port 25 through and I verified that the port
forwarding was set to send them to the Exchange server's private IP address.
is there a second port hat needs to be opened and forwarded to the Exchange
server to complete the telnet connection?
I have not yet verified with my personal ISP that they are not blocking port
25 traffic on their network (although I doubt they are since my personal
email has to connect to their email server using port 25). I will be
researching that right away but I wanted to post this first.
Thanks,
Jeff
"Bharat Suneja" <bharat@nospam.org> wrote in message
news:%23H53OAN$FHA.3568@TK2MSFTNGP09.phx.gbl...
| Quote: | - Send email from a telnet session (from outside your firewall)
http://www.suneja.com/blog/2005/10/sending-mail-from-telnet-session.html
- Make sure Recipient Policy has generated email addresses with your
public/registered domain as default
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------
"Jeff Foster" <noone@nowhere.com> wrote in message
news:%23BMPUuM$FHA.2264@tk2msftngp13.phx.gbl...
I am in the process of setting up an Exchange server for my network. It's
part of SBS but since this question is related solely to Exchange, I
figured I would do better to ask it here.
Our email is currently hosted by our ISP. The clients currently use
Outlook to download their POP3 mail directly from the ISP's servers. I
have Exchange set up and running and all appears fine, but before I
change our DNS MX records to point to our IP address and move everyone to
Exchange, I would like to test the Exchange setup by sending it an email
to see if it receives it without any problem.
How can I send it a test email when there is no current MX record
pointing a domain name to our IP address?
I tried creating an account in outlook and using our IP address as the
SMTP server in the account details and then sending an email, but Outlook
said it couldn't find the outgoing server. I guess that's a good thing
so that people can't just point their email apps to our server to send
mail from, but it didn't help me out.
I have port 25 open on our firewall and routed to the Exchange server
(using port forwarding since we only have one static IP).
Do I need to set up a test email server offsite with DNS on it and set up
a DNS entry on that test server to point our domain to our IP, and then
send an email using that box as the sending email accounts MTA server?
This seems like a long way around what should be a simple problem.
Any suggestions?
Thanks,
Jeff
|
|
|
| Back to top |
|
|
Bharat Suneja
Guest
|
| Posted:
Sat Dec 10, 2005 1:58 am Post subject:
Re: Test Exchange before changing MX records |
|
|
If you follow the instructions - the server doesn't prompt you to
type/complete remaining commands - simply responds back with a 220 banner
and 250s after each command completed.
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------------
"Jeff Foster" <noone@nowhere.com> wrote in message
news:%23kE8fgP$FHA.1256@TK2MSFTNGP15.phx.gbl...
| Quote: | Alright...I tried that and have two questions relating to those
instructions.
1. I did step one from inside the firewall and I got a response from
Exchange. However that was it. I didn't get another prompt to type in
any of the remaining commands. Do I need to start a new telnet session
for step two or am I missing something necessary for this telnet email
session to work?
2. I tried step one from outside the firewall and received no response.
The telnet session would not connect. I verified that the firewall was
set to allow TCP packets destined for port 25 through and I verified that
the port forwarding was set to send them to the Exchange server's private
IP address. is there a second port hat needs to be opened and forwarded to
the Exchange server to complete the telnet connection?
I have not yet verified with my personal ISP that they are not blocking
port 25 traffic on their network (although I doubt they are since my
personal email has to connect to their email server using port 25). I
will be researching that right away but I wanted to post this first.
Thanks,
Jeff
"Bharat Suneja" <bharat@nospam.org> wrote in message
news:%23H53OAN$FHA.3568@TK2MSFTNGP09.phx.gbl...
- Send email from a telnet session (from outside your firewall)
http://www.suneja.com/blog/2005/10/sending-mail-from-telnet-session.html
- Make sure Recipient Policy has generated email addresses with your
public/registered domain as default
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------
"Jeff Foster" <noone@nowhere.com> wrote in message
news:%23BMPUuM$FHA.2264@tk2msftngp13.phx.gbl...
I am in the process of setting up an Exchange server for my network.
It's part of SBS but since this question is related solely to Exchange, I
figured I would do better to ask it here.
Our email is currently hosted by our ISP. The clients currently use
Outlook to download their POP3 mail directly from the ISP's servers. I
have Exchange set up and running and all appears fine, but before I
change our DNS MX records to point to our IP address and move everyone
to Exchange, I would like to test the Exchange setup by sending it an
email to see if it receives it without any problem.
How can I send it a test email when there is no current MX record
pointing a domain name to our IP address?
I tried creating an account in outlook and using our IP address as the
SMTP server in the account details and then sending an email, but
Outlook said it couldn't find the outgoing server. I guess that's a
good thing so that people can't just point their email apps to our
server to send mail from, but it didn't help me out.
I have port 25 open on our firewall and routed to the Exchange server
(using port forwarding since we only have one static IP).
Do I need to set up a test email server offsite with DNS on it and set
up a DNS entry on that test server to point our domain to our IP, and
then send an email using that box as the sending email accounts MTA
server? This seems like a long way around what should be a simple
problem.
Any suggestions?
Thanks,
Jeff
|
|
|
| Back to top |
|
|
Leif Pedersen [MVP]
Guest
|
| Posted:
Sat Dec 10, 2005 1:58 am Post subject:
Re: Test Exchange before changing MX records |
|
|
Hi,
Telnet to a SMTP server doesn't give you a prompt. You should get a 250
(which means OK) after each successfull command.
Leif
"Jeff Foster" <noone@nowhere.com> wrote in message
news:%23kE8fgP$FHA.1256@TK2MSFTNGP15.phx.gbl...
| Quote: | Alright...I tried that and have two questions relating to those
instructions.
1. I did step one from inside the firewall and I got a response from
Exchange. However that was it. I didn't get another prompt to type in
any of the remaining commands. Do I need to start a new telnet session
for step two or am I missing something necessary for this telnet email
session to work?
2. I tried step one from outside the firewall and received no response.
The telnet session would not connect. I verified that the firewall was
set to allow TCP packets destined for port 25 through and I verified that
the port forwarding was set to send them to the Exchange server's private
IP address. is there a second port hat needs to be opened and forwarded to
the Exchange server to complete the telnet connection?
I have not yet verified with my personal ISP that they are not blocking
port 25 traffic on their network (although I doubt they are since my
personal email has to connect to their email server using port 25). I
will be researching that right away but I wanted to post this first.
Thanks,
Jeff
"Bharat Suneja" <bharat@nospam.org> wrote in message
news:%23H53OAN$FHA.3568@TK2MSFTNGP09.phx.gbl...
- Send email from a telnet session (from outside your firewall)
http://www.suneja.com/blog/2005/10/sending-mail-from-telnet-session.html
- Make sure Recipient Policy has generated email addresses with your
public/registered domain as default
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------
"Jeff Foster" <noone@nowhere.com> wrote in message
news:%23BMPUuM$FHA.2264@tk2msftngp13.phx.gbl...
I am in the process of setting up an Exchange server for my network.
It's part of SBS but since this question is related solely to Exchange, I
figured I would do better to ask it here.
Our email is currently hosted by our ISP. The clients currently use
Outlook to download their POP3 mail directly from the ISP's servers. I
have Exchange set up and running and all appears fine, but before I
change our DNS MX records to point to our IP address and move everyone
to Exchange, I would like to test the Exchange setup by sending it an
email to see if it receives it without any problem.
How can I send it a test email when there is no current MX record
pointing a domain name to our IP address?
I tried creating an account in outlook and using our IP address as the
SMTP server in the account details and then sending an email, but
Outlook said it couldn't find the outgoing server. I guess that's a
good thing so that people can't just point their email apps to our
server to send mail from, but it didn't help me out.
I have port 25 open on our firewall and routed to the Exchange server
(using port forwarding since we only have one static IP).
Do I need to set up a test email server offsite with DNS on it and set
up a DNS entry on that test server to point our domain to our IP, and
then send an email using that box as the sending email accounts MTA
server? This seems like a long way around what should be a simple
problem.
Any suggestions?
Thanks,
Jeff
|
|
|
| Back to top |
|
|
Jeff Foster
Guest
|
| Posted:
Sat Dec 10, 2005 1:58 am Post subject:
Re: Test Exchange before changing MX records |
|
|
Regarding number two below...I contacted my ISP and they were blocking port
25. I have requested that they remove that filter.
My confusion still stands regarding number one below.
Jeff
"Jeff Foster" <noone@nowhere.com> wrote in message
news:%23kE8fgP$FHA.1256@TK2MSFTNGP15.phx.gbl...
| Quote: | Alright...I tried that and have two questions relating to those
instructions.
1. I did step one from inside the firewall and I got a response from
Exchange. However that was it. I didn't get another prompt to type in
any of the remaining commands. Do I need to start a new telnet session
for step two or am I missing something necessary for this telnet email
session to work?
2. I tried step one from outside the firewall and received no response.
The telnet session would not connect. I verified that the firewall was
set to allow TCP packets destined for port 25 through and I verified that
the port forwarding was set to send them to the Exchange server's private
IP address. is there a second port hat needs to be opened and forwarded to
the Exchange server to complete the telnet connection?
I have not yet verified with my personal ISP that they are not blocking
port 25 traffic on their network (although I doubt they are since my
personal email has to connect to their email server using port 25). I
will be researching that right away but I wanted to post this first.
Thanks,
Jeff
"Bharat Suneja" <bharat@nospam.org> wrote in message
news:%23H53OAN$FHA.3568@TK2MSFTNGP09.phx.gbl...
- Send email from a telnet session (from outside your firewall)
http://www.suneja.com/blog/2005/10/sending-mail-from-telnet-session.html
- Make sure Recipient Policy has generated email addresses with your
public/registered domain as default
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------
"Jeff Foster" <noone@nowhere.com> wrote in message
news:%23BMPUuM$FHA.2264@tk2msftngp13.phx.gbl...
I am in the process of setting up an Exchange server for my network.
It's part of SBS but since this question is related solely to Exchange, I
figured I would do better to ask it here.
Our email is currently hosted by our ISP. The clients currently use
Outlook to download their POP3 mail directly from the ISP's servers. I
have Exchange set up and running and all appears fine, but before I
change our DNS MX records to point to our IP address and move everyone
to Exchange, I would like to test the Exchange setup by sending it an
email to see if it receives it without any problem.
How can I send it a test email when there is no current MX record
pointing a domain name to our IP address?
I tried creating an account in outlook and using our IP address as the
SMTP server in the account details and then sending an email, but
Outlook said it couldn't find the outgoing server. I guess that's a
good thing so that people can't just point their email apps to our
server to send mail from, but it didn't help me out.
I have port 25 open on our firewall and routed to the Exchange server
(using port forwarding since we only have one static IP).
Do I need to set up a test email server offsite with DNS on it and set
up a DNS entry on that test server to point our domain to our IP, and
then send an email using that box as the sending email accounts MTA
server? This seems like a long way around what should be a simple
problem.
Any suggestions?
Thanks,
Jeff
|
|
|
| Back to top |
|
|
Jeff Foster
Guest
|
| Posted:
Mon Dec 12, 2005 5:58 pm Post subject:
Re: Test Exchange before changing MX records |
|
|
Thank you for your help. I fugured out what the issue was. My ISP did have
a port 25 block which I had them lift. Once lifted, I still couldn't
connect so I checked my firewall settings again and found that the port 25
filter on my firewall was not set up correctly. I changed it and was then
able to connect without any trouble. The telnet session worked fine.
Thanks again.
Jeff
"Bharat Suneja" <bharatsuneja@no.spam.org> wrote in message
news:ePcCF1Q$FHA.292@TK2MSFTNGP14.phx.gbl...
| Quote: | If you follow the instructions - the server doesn't prompt you to
type/complete remaining commands - simply responds back with a 220 banner
and 250s after each command completed.
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------------
"Jeff Foster" <noone@nowhere.com> wrote in message
news:%23kE8fgP$FHA.1256@TK2MSFTNGP15.phx.gbl...
Alright...I tried that and have two questions relating to those
instructions.
1. I did step one from inside the firewall and I got a response from
Exchange. However that was it. I didn't get another prompt to type in
any of the remaining commands. Do I need to start a new telnet session
for step two or am I missing something necessary for this telnet email
session to work?
2. I tried step one from outside the firewall and received no response.
The telnet session would not connect. I verified that the firewall was
set to allow TCP packets destined for port 25 through and I verified that
the port forwarding was set to send them to the Exchange server's private
IP address. is there a second port hat needs to be opened and forwarded
to the Exchange server to complete the telnet connection?
I have not yet verified with my personal ISP that they are not blocking
port 25 traffic on their network (although I doubt they are since my
personal email has to connect to their email server using port 25). I
will be researching that right away but I wanted to post this first.
Thanks,
Jeff
"Bharat Suneja" <bharat@nospam.org> wrote in message
news:%23H53OAN$FHA.3568@TK2MSFTNGP09.phx.gbl...
- Send email from a telnet session (from outside your firewall)
http://www.suneja.com/blog/2005/10/sending-mail-from-telnet-session.html
- Make sure Recipient Policy has generated email addresses with your
public/registered domain as default
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------
"Jeff Foster" <noone@nowhere.com> wrote in message
news:%23BMPUuM$FHA.2264@tk2msftngp13.phx.gbl...
I am in the process of setting up an Exchange server for my network.
It's part of SBS but since this question is related solely to Exchange,
I figured I would do better to ask it here.
Our email is currently hosted by our ISP. The clients currently use
Outlook to download their POP3 mail directly from the ISP's servers. I
have Exchange set up and running and all appears fine, but before I
change our DNS MX records to point to our IP address and move everyone
to Exchange, I would like to test the Exchange setup by sending it an
email to see if it receives it without any problem.
How can I send it a test email when there is no current MX record
pointing a domain name to our IP address?
I tried creating an account in outlook and using our IP address as the
SMTP server in the account details and then sending an email, but
Outlook said it couldn't find the outgoing server. I guess that's a
good thing so that people can't just point their email apps to our
server to send mail from, but it didn't help me out.
I have port 25 open on our firewall and routed to the Exchange server
(using port forwarding since we only have one static IP).
Do I need to set up a test email server offsite with DNS on it and set
up a DNS entry on that test server to point our domain to our IP, and
then send an email using that box as the sending email accounts MTA
server? This seems like a long way around what should be a simple
problem.
Any suggestions?
Thanks,
Jeff
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in