Re: Please help I cannot send messages from exchange 2003 account



Hello,

At the moment we are using FT Gates sowtware to send and recieve email for
our domain, and it is configured to send and recieve email throught our ISP
servers, but know I've setup exchange server mercury.mydomain.com. I know
that I will not be able to recieve email untill I will get MX records sorted
out for our new server, but I do not understad why all the messages I sent
going into spam folder into yahoo or hotmail accounts.If I sent email from
using FT gates account test@xxxxxxxxxxxx it goes OK, but if I send email
test@mydomain .com from the exchange server account it goes to spam folder.

Thanks

"Donatas Grasys" <don@xxxxxxxxx> wrote in message
news:fgac6i$676$1$8300dec7@xxxxxxxxxxxxxxxxxxx
Hello

I have just installed exchange 2003 server and I am trying to send message
from exchange account but they never reach the external recipient.
Everything is OK with internal mail.

I have run smtpdiag.exe and I have got the log. Could you possibly point
me to the right direction because I am new with exchange. I think it could
be something wrong with DNS settings. We have Windows 2003 DC and Exchange
2003 on Windows 2003 member server.

Thanks in advance.

C:\>smtpdiag.exe user@xxxxxxxxxxxx donatux25@xxxxxxxxx /v

Searching for Exchange external DNS settings.
Computer name is MERCURY.
VSI 1 has the following external DNS servers:
There are no external DNS servers configured.

Checking SOA for yahoo.com.
Checking external DNS servers.
Checking internal DNS servers.

Checking TCP/UDP SOA serial number using DNS server [192.1.1.176].
TCP test succeeded.
UDP test succeeded.
Serial number: 2007103104
SOA serial number match: Passed.

Checking local domain records.
Starting TCP and UDP DNS queries for the local domain. This test will try
to
validate that DNS is set up correctly for inbound mail. This test can fail
for
3 reasons.
1) Local domain is not set up in DNS. Inbound mail cannot be routed to
local mailboxes.
2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound
mail,
but will affect outbound mail.
3) Internal DNS is unaware of external DNS settings. This is a valid
configuration for certain topologies.
Checking MX records using TCP:mydomain .com.
A: mydomain.com [192.1.1.156]
A: mydomain.com [192.1.1.176]
A: mydomain.com [192.1.1.173]
Checking MX records using UDP: mydomain.com.
A: mydomain .com [192.1.1.156]
A: mydomain.com [192.1.1.173]
A: mydomain.com [192.1.1.176]
Both TCP and UDP queries succeeded. Local DNS test passed.

Checking remote domain records.
Starting TCP and UDP DNS queries for the remote domain. This test will try
to
validate that DNS is set up correctly for outbound mail. This test can
fail for
3 reasons.
1) Firewall blocks TCP/UDP queries which will block outbound mail.
Windows
2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP
queries first, then fall back to TCP queries.
2) Internal DNS does not know how to query external domains. You must
either use an external DNS server or configure DNS server to query
external
domains.
3) Remote domain does not exist. Failure is expected.
Checking MX records using TCP: yahoo.com.
MX: g.mx.mail.yahoo.com (1)
MX: a.mx.mail.yahoo.com (1)
MX: b.mx.mail.yahoo.com (1)
MX: c.mx.mail.yahoo.com (1)
MX: d.mx.mail.yahoo.com (1)
MX: e.mx.mail.yahoo.com (1)
MX: f.mx.mail.yahoo.com (1)
A: g.mx.mail.yahoo.com [209.191.88.239]
A: g.mx.mail.yahoo.com [206.190.53.191]
A: a.mx.mail.yahoo.com [209.191.118.103]
A: b.mx.mail.yahoo.com [66.196.97.250]
A: c.mx.mail.yahoo.com [216.39.53.3]
A: c.mx.mail.yahoo.com [68.142.237.182]
A: d.mx.mail.yahoo.com [216.39.53.2]
A: e.mx.mail.yahoo.com [216.39.53.1]
A: f.mx.mail.yahoo.com [209.191.88.247]
A: f.mx.mail.yahoo.com [68.142.202.247]
Checking MX records using UDP: yahoo.com.
MX: a.mx.mail.yahoo.com (1)
MX: b.mx.mail.yahoo.com (1)
MX: c.mx.mail.yahoo.com (1)
MX: d.mx.mail.yahoo.com (1)
MX: e.mx.mail.yahoo.com (1)
MX: f.mx.mail.yahoo.com (1)
MX: g.mx.mail.yahoo.com (1)
Both TCP and UDP queries succeeded. Remote DNS test passed.

Checking MX servers listed for donatux25@xxxxxxxxxx
Connecting to f.mx.mail.yahoo.com [68.142.202.247] on port 25.
Received:
421 Message from (62.49.25.145) temporarily deferred - 4.16.50. Please
refer to http://help.yahoo.com/help/us/mail/defer/defer-06.html


Error: Expected "220". Server is not accepting connections.
Failed to submit mail to f.mx.mail.yahoo.com.
Connecting to c.mx.mail.yahoo.com [68.142.237.182] on port 25.









.



Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)

Loading