Re: Inbound email problem

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

See a bit earlier in the thread, Steve. I'm with you in that I can't
understand what is going on with Qwest.

They have an mx record with a priority of 10 that points to
mail.stpaulsumctucson.net KC says that the IP address associated with that
pointer is the static IP of the DSL modem. I can verify that this is
correct by going to his RWW login page.

The problem is that I cannot telnet into the exchange server on port 25.
When I try, it acts strange. There may be something wrong with the port
forwarding, or maybe there are more than one smtp server running on the sbs
that is causing a conflict.

I would think the qwest mail server is either POP or IMAP which would need
to be setup inside Outlook on the workstations, not the SBS. Still, it will
cause problems later on with outbound mail.

KC, if you want to accept mail directly into your SBS using addresses such
as user_name@xxxxxxxxxxxxxxxxxxxx, then you should probably drop the Qwest
email service. As it is, you won't be able to have a properly configured
reverse DNS when you have mail.stpaulsumctucson.net pointing to one IP
address and stpaulsumctucson.net pointing to another.

The problem, however, is that the outside world cannot connect to your
exchange server.

Can you telnet to the server from within your LAN? How about from the "DMZ"
network between the modem and your external NIC?

If so, then you need to re-configure the modem for port forwarding. If not,
then you need to make sure you have only one smtp server running on the sbs
(Exchange) and that it is listening on port 25. Did qwest have you install
any software on the SBS?

Buddy G ~

"Steve" <newsgroup@xxxxxxxxxx> wrote in message
news:%23M6fP8SWIHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
Sorry I still don't see what the Qwestoffice email and server have to do
with incoming SMTP traffic for your registered company domain. Perhaps we
need to know what that company domain name is as well as the A and MX
records you have setup.

"KC" <kcalfee@xxxxxxxxx> wrote in message
news:7540680d-c38d-4d19-b87d-6dfe6f58f951@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jan 16, 9:52 pm, "Steve" <newsgr...@xxxxxxxxxx> wrote:
What do you mean by "Qwest moved our email to their new servers
(Qwestoffice)" as that should have nothing to do with your incoming SMTP
mail?

"KC" <kcal...@xxxxxxxxx> wrote in message

news:36d7def0-4ab6-48eb-a902-ec01a35217d4@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jan 16, 4:55 pm, "Buddy" <bu...@xxxxxxxxxxxxxxxxx> wrote:





DNS checks out OK.

Could it be that Qwest is blocking port 25 traffic? Probably not if
outbound mail works.

As a test, change the port that Exchange smtp listens on (and make sure
you
port forward the new setting to your sbs external nic)

look at:http://support.microsoft.com/kb/274842

When is the last time you ran the CEICW? Maybe you should try that
first.

Thanks,
Buddy G ~

"KC" <kcal...@xxxxxxxxx> wrote in message

news:c0ff7746-03d1-4921-bdf8-e314e87ed5ff@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jan 16, 1:49 pm, "Buddy" <bu...@xxxxxxxxxxxxxxxxx> wrote:

What is the name of your company domain and what is the public ip
address?
It sounds like they are not matching in DNS.
Can you telnet into your exchange server?
Do you have exchange server antispam or connection filtering enabled?

Buddy G ~

"KC" <kcal...@xxxxxxxxx> wrote in message

news:353019c8-68d4-4b57-9a04-5d3fb7a2672b@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I am running SBS 2003 Standard on a Dell PowerEdge 1800 with 2 NICs.
External NIC is connected to Qwest provided Actiontec GT701WG
modem/
router. I can RWW, I can send email, I can receive pop mail for our
qwestoffice email addresses. I cannot receive inbound email if it
is
sent to our company domain name address. I have a public static IP
with MX and A records setup. When I used dnsstuff to obtain a dns
report, the report indicated fail at connect to mail servers
(Error: I
could not complete a connection to any of your mailservers) When I
did an email test I received the error "The mailserver terminated
the
connection before the transaction was complete (state1). This is
not
RFC compliant, and therefore either due to an error, or it may be
the
result of a non-RFC-compliant mailserver or non-RFC-complaint anti-
spam program.

Any insight on what is creating my problem would be greatly
appreciated.- Hide quoted text -

- Show quoted text -

company domain: stpaulsumctucson.net
public IP: 65.101.185.33
no connection filtering enabled
Intelligent message filtering gateway blocking - block messages with
SCL rating greater than or equal to 8
Recipient filtering - filter recipients not in the directory
Telnet fails - error - Could not complete connection to host. on port
25: connect failed- Hide quoted text -

- Show quoted text -

Qwest checked it out and verified that Port 25 had no filtering
assigned. I ran the CEICW yesterday after forwarding ports on the
Actiontec. I might tell you I started having these problems after
Qwest moved our email to their new servers (Qwestoffice) and told me I
needed to change my DNS server at my registrar. The funny thing is,
if I don't use the old primary DSN IP as one of the entries in CEICW
(using it as the alternate) I can't access a lot of internet sites.
Internet access is still at Qwest.net. Don't know if this is any help
or just muddies the water. I'll rerun CEICW tomorrow when I get to
work. In the mean time, I'll read the KB you sent the link for.- Hide
quoted text -

- Show quoted text -

In Sep 2007 I received an email from qwest.net saying they were
upgrading our qwest.net email service and as a result our email
address ending in qwest.net would end in qwestoffice.net. Our email
accounts were qwest.net accounts with email aliases. Additionally
Qwest indicated I needed to change the DNS servers to the Qwestoffice
servers at my registrar. After I made the change at the registrar I
ran the CEICW and entered the new DNS IP addresses at the appropriate
point in the wizard and my problems began and I havent't been able to
find a solution. Actually all of this didn't happen until the end of
November.



.

Relevant Pages

  • Re: Inbound email problem
    ... Could it be that Qwest is blocking port 25 traffic? ... Can you telnet into your exchange server? ... Do you have exchange server antispam or connection filtering enabled? ...
    (microsoft.public.windows.server.sbs)
  • Re: Inbound email problem
    ... totally sure that port 25 is forwarded to the SBS external nic? ... Can you telnet into your exchange server? ... Do you have exchange server antispam or connection filtering enabled? ...
    (microsoft.public.windows.server.sbs)
  • Re: IP filtering
    ... IP filtering won't prevent the server from listening. ... Having said all that, closing a port is not just about filtering, it's also ...
    (microsoft.public.win2000.security)
  • Re: Online Arrmor
    ... the proper way to do that is a port scan. ... As you know, most filtering implementations are dynamic, i.e. ... you're scanning not your box but some NAT box outside ... or even some proxy server from the outside. ...
    (comp.security.firewalls)
  • RE: Win2K TCP/IP filtering and security
    ... Win2K TCP/IP filtering and security ... for each port inbound to the server and your ... NetBIOS port 137. ...
    (Focus-Microsoft)