Re: Inbound email problem
- From: KC <kcalfee@xxxxxxxxx>
- Date: Thu, 17 Jan 2008 09:18:42 -0800 (PST)
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@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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.
.
- Follow-Ups:
- Re: Inbound email problem
- From: Steve
- Re: Inbound email problem
- References:
- Inbound email problem
- From: KC
- Re: Inbound email problem
- From: Buddy
- Re: Inbound email problem
- From: KC
- Re: Inbound email problem
- From: Buddy
- Re: Inbound email problem
- From: KC
- Re: Inbound email problem
- From: Steve
- Inbound email problem
- Prev by Date: Re: SBS 2003 needs SP1 installed
- Next by Date: Re: One user having messages stuck in Local Delivery
- Previous by thread: Re: Inbound email problem
- Next by thread: Re: Inbound email problem
- Index(es):
Relevant Pages
|
Loading