Forum

Bir domainden Mail ...
 
Bildirimler
Hepsini Temizle

Bir domainden Mail alım sorunu

Deniz ASLAN
(@DenizASLAN)
Üye

Merhabalar;


Arkadaşlar 3 gündür bir firmadan mail almaya çalışıyoruz fakat bir türlü sonuca ulaşamadık. Benim firmamın mailleri TRNET tarafından host ediliyor ve SBS 2003 server üzerinde pop3 ile mailleri çekiyorum. Ben den mail gidiyor. fakat karşı sunucudan bana mail gelmiyor. KArşı tarafa ulaşan bir hata iletiside olmuyor mail gitmiş gibi gözüküyor. Hem kendimizi hemde diğer firmayı spam listelerinde göremiyorum.


Gönderici domain : @demiralnakliyat.com.tr


Alıcı domain  : @evrimsigorta.com.tr


Sebepleri neler olabilir yardımcı olabilir misiniz ?

Alıntı
Topic starter Gönderildi : 01/03/2010 14:36
Murat AYDIN
(@murataydin)
Üye

Merhaba;

İlk Aklıma gelen @demiralnakliyat.com.tr domainin kullandığı RBL ve Spam listlere sizin domaininiz düşmüş olabilir.

 

CevapAlıntı
Gönderildi : 01/03/2010 14:42
Deniz ASLAN
(@DenizASLAN)
Üye

Karşı sunucuya  Dönen hata şağıdaki gibi  


MailEnable: Message could not be delivered to some recipients.
 The following recipient(s) could not be reached [SMTP:[email protected]] Reason: General Failure Message contents follow: Received: from ugur ([78.186.134.37]) by host210.websahibi.com with MailEnable ESMTP; Mon, 1 Mar 2010 0924 +0200 From: "ugur" To: '=?iso-8859-9?Q?Evrim_Sigortac=FDl=FDk_Hizmetleri_=28BILGIISLEM_Merkezi=29?='


CevapAlıntı
Topic starter Gönderildi : 01/03/2010 14:56
Deniz ASLAN
(@DenizASLAN)
Üye

PTR ve SPF kayıtlarımız tabiki mevcut. Mailler kendi üzerimizde değil TRNET üzerinde duruyor ve spam listelerinde bulunmuyoruz.


 


 

CevapAlıntı
Topic starter Gönderildi : 01/03/2010 17:42
Murat AYDIN
(@murataydin)
Üye

İlgili Kayıtlar olmazsa zaten hiçbir yere mail gönderimi alımı olamazdı.

TRNET ile irtibata gecip sorunu bildirdiniz mi ? Birde Karşı domainin adminiyle görüşürseniz eğer oda gerekli kontrolleri yapabilir.

Bana Black Liste girmiş gibi geldi.

CevapAlıntı
Gönderildi : 01/03/2010 18:24
Deniz ASLAN
(@DenizASLAN)
Üye

Murat hocam, bizim hosting firmamız ile sürekli görüşüyorum fakat mailin hiç bu tarafa ulaşmadığı iletiliyor. Bizim sunuculara mail gelmiyorki diyorlar birşey yapamayız.


- Blacklist sorunu yok keza karşı firmanın.


-Acaba 587 port ayarı mı yapılması gerekiyor diye aklıma geliyor. Karşı tarafın firma admini testler yapıyor ve bizde sorun yok herkesle mailleşiyoruz diyor, keza onlarda hosting işini websahibi.com pop3 ile çekiyorlar. Websahibi 'nden bir sorumlu ile görüşme fırsatı bulamadım. sürekli arıyorum fakat meşguller.


 

CevapAlıntı
Topic starter Gönderildi : 01/03/2010 18:28
Murat AYDIN
(@murataydin)
Üye

587 nolu portla ilgili sıkıntı olsa mailler outlooktan bile cıkmaz giden kutusunda kalır.

http://www.mxtoolbox.com/blacklists.aspx   kontrol eder misiniz?

CevapAlıntı
Gönderildi : 01/03/2010 18:39
Mesut SARIYAR
(@mesutsariyar)
Kıdemli Üye Forum Yöneticisi

Umarım yardımcı olur,


DNSreport for demiralnakliyat.com.tr






























Category Status Test Name Information
Parent PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:


ns2.websahibi.com. [91.151.92.92 (NO GLUE)] [TR]
ns1.websahibi.com. [91.151.91.91 (NO GLUE)] [TR]
[These were obtained from ns3.nic.tr]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.
WARN Glue at parent nameservers WARNING. The parent servers (I checked with ns3.nic.tr.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.
PASS DNS servers have A records OK. All your DNS servers either have A records at the zone parent servers, or do not need them (if the DNS servers are on other TLDs). A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers. Note that there will be problems if your DNS servers do not have these same A records.











































































NS INFO NS records at your nameservers Your NS records at your nameservers are:


server-6e290821.
ns.demiralnakliyat.com.tr. [213.142.141.127] [TTL=3600]
PASS Open DNS servers OK. Your DNS servers do not announce that they are open DNS servers. Although there is a slight chance that they really are open DNS servers, this is very unlikely. Open DNS servers increase the chances that of cache poisoning, can degrade performance of your DNS, and can cause your DNS servers to be used in an attack (so it is good that your DNS servers do not appear to be open DNS servers).
PASS Mismatched glue OK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.
PASS No NS A records at nameservers OK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.
WARN All nameservers report identical NS records WARNING: Your nameservers report somewhat different answers for your NS records (varying TTL, for example).
PASS All nameservers respond OK. All of your nameservers listed at the parent nameservers responded.
FAIL Nameserver name validity ERROR: One or more of the NS records that your nameservers report are invalid:
server-6e290821. is not a valid host name
PASS Number of nameservers OK. You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
PASS Lame nameservers OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
FAIL Missing (stealth) nameservers FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNSreport will not query these servers, so you need to be very careful that they are working properly.


server-6e290821.
ns.demiralnakliyat.com.tr.
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).
FAIL Missing nameservers 2 ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns2.websahibi.com.
ns1.websahibi.com.
PASS No CNAMEs for domain OK. There are no CNAMEs for demiralnakliyat.com.tr. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
PASS No NSs with CNAMEs OK. There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
WARN Nameservers on separate class C's WARNING: We cannot test to see if your nameservers are all on the same Class C (technically, /24) range, because the root servers are not sending glue. We plan to add such a test later, but today you will have to manually check to make sure that they are on separate Class C ranges. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.
PASS All NS IPs public OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
PASS TCP Allowed OK. All your DNS servers allow TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems.
INFO Nameservers versions Your nameservers have the following versions:

91.151.92.92: "Microsoft DNS 6.0.6002 (17724655)"
91.151.91.91: No version info available (CHAOS not implemented).
PASS Stealth NS record leakage Your DNS servers do not leak any stealth NS records (if any) in non-NS requests.







































SOA INFO SOA record Your SOA record [TTL=3600] is:


Primary nameserver: ns2win2008x64.
Hostmaster E-mail address: hostmaster.
Serial #: 13
Refresh: 900
Retry: 600
Expire: 86400
Default TTL: 3600
PASS NS agreement on SOA Serial # OK. All your nameservers agree that your SOA serial number is 13. That means that all your nameservers are using the same data (unless you have different sets of data with the same serial number, which would be very bad)! Note that the DNSreport only checks the NS records listed at the parent servers (not any stealth servers).
FAIL SOA MNAME Check ERROR: Your SOA (Start of Authority) record states that your master (primary) name server is: ns2win2008x64.. However, that is not a valid domain name!

 

FAIL SOA RNAME Check ERROR: Your SOA (Start of Authority) record states that your DNS contact E-mail address in hostname format is: hostmaster.. However, that is NOT valid (it must have at least 2 '.''s in it and no '@')!
WARN SOA Serial Number WARNING: Your SOA serial number is: 13. That is OK, but the recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision. For example, if you are making the 3rd change on 02 May 2006, you would use 2006050203. This number must be incremented every time you make a DNS change.
WARN SOA REFRESH value WARNING: Your SOA REFRESH interval is : 900 seconds. This seems low. You should consider increasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours). A value that is too low will unncessarily increase Internet traffic.
PASS SOA RETRY value OK. Your SOA RETRY interval is : 600 seconds. This seems normal (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
WARN SOA EXPIRE value WARNING: Your SOA EXPIRE time is : 86400 seconds. This seems a bit low. You should consider increasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
PASS SOA MINIMUM TTL value OK. Your SOA MINIMUM TTL is: 3600 seconds. This seems normal (about 3,600 to 86400 seconds or 1-24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.















































MX INFO MX Record Your 1 MX record is:


10 mail.demiralnakliyat.com.tr. [TTL=3600] IP=213.142.141.127 [TTL=3600] [TR]
PASS Low port test OK. Our local DNS server that uses a low port number can get your MX record. Some DNS servers are behind firewalls that block low port numbers. This does not guarantee that your DNS server does not block low ports (this specific lookup must be cached), but is a good indication that it does not.
PASS Invalid characters OK. All of your MX records appear to use valid hostnames, without any invalid characters.
PASS All MX IPs public OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.
PASS MX records are not CNAMEs OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.
PASS MX A lookups have no CNAMEs OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3).
PASS MX is host name, not IP OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).
INFO Multiple MX records NOTE: You only have 1 MX record. If your primary mail server is down or unreachable, there is a chance that mail may have troubles reaching you. In the past, mailservers would usually re-try E-mail for up to 48 hours. But many now only re-try for a couple of hours. If your primary mailserver is very reliable (or can be fixed quickly if it goes down), having just one mailserver may be acceptable.
PASS Differing MX-A records OK. I did not detect differing IPs for your MX records (this would happen if your DNS servers return different IPs than the DNS servers that are authoritative for the hostname in your MX records).
PASS Duplicate MX records OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.
PASS Reverse DNS entries for MX records OK. The IPs of all of your mail server(s) have reverse DNS (PTR) entries. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. Note that this information is cached, so if you changed it recently, it will not be reflected here (see the 'Reverse DNS Tool' for the current data). The reverse DNS entries are:


127.141.142.213.in-addr.arpa net213-142-141-ip127.adeox.com. [TTL=1866]



































Mail PASS Connect to mail servers OK: I was able to connect to all of your mailservers.
WARN Mail server host name in greeting WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.


mail.demiralnakliyat.com.tr claims to be host host210.websahibi.com [but that host is at 213.142.141.210 (may be cached), not 213.142.141.127]. <br />
PASS Acceptance of NULL <> sender OK: All of your mailservers accept mail from "<>". You are required (RFC1123 5.2.9) to receive this type of mail (which includes reject/bounce messages and return receipts).
FAIL Acceptance of postmaster address ERROR: One or more of your mailservers does not accept mail to [email protected] Mailservers are required (RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1) to accept mail to postmaster.


mail.demiralnakliyat.com.tr's postmaster response:<br /> >>> RCPT TO:<[email protected]><br /> <<< 550 Requested action not taken: mailbox unavailable or not local <br />
WARN Acceptance of abuse address WARNING: One or more of your mailservers does not accept mail to [email protected] Mailservers are expected by RFC2142 to accept mail to abuse.


mail.demiralnakliyat.com.tr's abuse response:<br /> >>> RCPT TO:<[email protected]><br /> <<< 550 Requested action not taken: mailbox unavailable or not local <br />
INFO Acceptance of domain literals WARNING: One or more of your mailservers does not accept mail in the domain literal format ([email protected][0.0.0.0]). Mailservers are technically required RFC1123 5.2.17 to accept mail to domain literals for any of its IP addresses. Not accepting domain literals can make it more difficult to test your mailserver, and can prevent you from receiving E-mail from people reporting problems with your mailserver. However, it is unlikely that any problems will occur if the domain literals are not accepted (mailservers at many common large domains have this problem).


mail.demiralnakliyat.com.tr's [email protected][213.142.141.127] response:<br /> >>> RCPT TO:<[email protected][213.142.141.127]><br /> <<< 550 Requested action not taken: mailbox unavailable or not local <br />
PASS Open relay test OK: All of your mailservers appear to be closed to relaying. This is not a thorough check, you can get a thorough one here.


mail.demiralnakliyat.com.tr OK: 503 This mail server requires authentication when attempting to send to a non-local e-mail address. Please check your mail client settings or contact your administrator to verify that the domain or address is defined for this server. <br />
WARN SPF record Your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004 was the target date for domains to have SPF records in place (Hotmail, for example, started checking SPF records on 01 Oct 2004).



















WWW
INFO WWW Record Your www.demiralnakliyat.com.tr A record is:


www.demiralnakliyat.com.tr. CNAME demiralnakliyat.com.tr. [TTL=3600]
demiralnakliyat.com.tr. A 213.142.141.127 [TTL=3600] [TR]
PASS All WWW IPs public OK. All of your WWW IPs appear to be public IPs. If there were any private IPs, they would not be reachable, causing problems reaching your web site.
PASS CNAME Lookup OK. You do have a CNAME record for www.demiralnakliyat.com.tr, which can cause some confusion. However, this is legal. Your CNAME entry also returns the A record for the CNAME entry, which is good -- otherwise, it would require an extra DNS lookup, which slightly delays the initial access to the website and use extra bandwidth. Note that if the CNAME points to another CNAME, it will likely cause problems.
INFO Domain A Lookup Your demiralnakliyat.com.tr A record is:


demiralnakliyat.com.tr. A 213.142.141.127 [TTL=3600]


 


DNSreport for evrimsigorta.com.tr






























Category Status Test Name Information
Parent PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:


ns1.tr.net.tr. [195.155.1.3 (NO GLUE)] [TR]
ns2.tr.net.tr. [195.155.11.4 (NO GLUE)] [TR]
[These were obtained from ns2.nic.tr]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.
WARN Glue at parent nameservers WARNING. The parent servers (I checked with ns2.nic.tr.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.
PASS DNS servers have A records OK. All your DNS servers either have A records at the zone parent servers, or do not need them (if the DNS servers are on other TLDs). A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers. Note that there will be problems if your DNS servers do not have these same A records.











































































NS INFO NS records at your nameservers Your NS records at your nameservers are:


ns1.tr.net.tr. [195.155.1.3] [TTL=86400]
ns2.tr.net.tr. [195.155.11.4] [TTL=86400]
PASS Open DNS servers OK. Your DNS servers do not announce that they are open DNS servers. Although there is a slight chance that they really are open DNS servers, this is very unlikely. Open DNS servers increase the chances that of cache poisoning, can degrade performance of your DNS, and can cause your DNS servers to be used in an attack (so it is good that your DNS servers do not appear to be open DNS servers).
PASS Mismatched glue OK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.
PASS No NS A records at nameservers OK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.
PASS All nameservers report identical NS records OK. The NS records at all your nameservers are identical.
FAIL All nameservers respond ERROR: Some of your nameservers listed at the parent nameservers did not respond. The ones that did not respond are:

195.155.11.4


Note: If you are running a Watchguard Firebox with DNS Proxy enabled, there may be a bug causing port numbers get mixed up -- if this is the case, you can contact Watchguard to see if they have a fix.
PASS Nameserver name validity OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
PASS Number of nameservers OK. You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
PASS Lame nameservers OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
PASS Missing (stealth) nameservers OK. All 2 of your nameservers (as reported by your nameservers) are also listed at the parent servers.
PASS Missing nameservers 2 OK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers.
PASS No CNAMEs for domain OK. There are no CNAMEs for evrimsigorta.com.tr. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
PASS No NSs with CNAMEs OK. There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
WARN Nameservers on separate class C's WARNING: We cannot test to see if your nameservers are all on the same Class C (technically, /24) range, because the root servers are not sending glue. We plan to add such a test later, but today you will have to manually check to make sure that they are on separate Class C ranges. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.
PASS All NS IPs public OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
WARN TCP Allowed WARNING: One or more of your DNS servers does not accept TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems. This message could also appear if your DNS servers are using anycast. The problem servers are:


195.155.11.4: Error [No response to TCP packets].
INFO Nameservers versions Your nameservers have the following versions:

195.155.1.3: "9.2.3"
195.155.11.4: No version info available (timeout on lookup). Could be tinydns 1.00 through 1.04.
PASS Stealth NS record leakage Your DNS servers do not leak any stealth NS records (if any) in non-NS requests.







































SOA INFO SOA record Your SOA record [TTL=86400] is:


Primary nameserver: ns1.tr.net.tr.
Hostmaster E-mail address: admin.tr.net.
Serial #: 2010021604
Refresh: 10800
Retry: 3600
Expire: 3600000
Default TTL: 86400
WARNING: The following nameservers did not respond:
195.155.11.4
PASS NS agreement on SOA Serial # OK. All your nameservers agree that your SOA serial number is 2010021604. That means that all your nameservers are using the same data (unless you have different sets of data with the same serial number, which would be very bad)! Note that the DNSreport only checks the NS records listed at the parent servers (not any stealth servers).
PASS SOA MNAME Check OK. Your SOA (Start of Authority) record states that your master (primary) name server is: ns1.tr.net.tr.. That server is listed at the parent servers, which is correct.

 

PASS SOA RNAME Check OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: [email protected] (techie note: we have changed the initial '.' to an '@' for display purposes).
PASS SOA Serial Number OK. Your SOA serial number is: 2010021604. This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. So this indicates that your DNS was last updated on 16 Feb 2010 (and was revision #4). This number must be incremented every time you make a DNS change.
PASS SOA REFRESH value OK. Your SOA REFRESH interval is : 10800 seconds. This seems normal (about 3600-7200 seconds is good if not using DNS NOTIFY; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours)). This value determines how often secondary/slave nameservers check with the master for updates.
PASS SOA RETRY value OK. Your SOA RETRY interval is : 3600 seconds. This seems normal (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
WARN SOA EXPIRE value WARNING: Your SOA EXPIRE time is : 3600000 seconds. This seems a bit high. You should consider decreasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
PASS SOA MINIMUM TTL value OK. Your SOA MINIMUM TTL is: 86400 seconds. This seems normal (about 3,600 to 86400 seconds or 1-24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.















































MX INFO MX Record Your 1 MX record is:


10 fmx.tr.net.tr. [TTL=86400] IP=195.155.1.26 [TTL=3600] [TR]
IP=195.155.1.27 [TTL=3600] [TR]
PASS Low port test OK. Our local DNS server that uses a low port number can get your MX record. Some DNS servers are behind firewalls that block low port numbers. This does not guarantee that your DNS server does not block low ports (this specific lookup must be cached), but is a good indication that it does not.
PASS Invalid characters OK. All of your MX records appear to use valid hostnames, without any invalid characters.
PASS All MX IPs public OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.
PASS MX records are not CNAMEs OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.
PASS MX A lookups have no CNAMEs OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3).
PASS MX is host name, not IP OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).
INFO Multiple MX records NOTE: You only have 1 MX record. If your primary mail server is down or unreachable, there is a chance that mail may have troubles reaching you. In the past, mailservers would usually re-try E-mail for up to 48 hours. But many now only re-try for a couple of hours. If your primary mailserver is very reliable (or can be fixed quickly if it goes down), having just one mailserver may be acceptable.
PASS Differing MX-A records OK. I did not detect differing IPs for your MX records (this would happen if your DNS servers return different IPs than the DNS servers that are authoritative for the hostname in your MX records).
PASS Duplicate MX records OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.
PASS Reverse DNS entries for MX records OK. The IPs of all of your mail server(s) have reverse DNS (PTR) entries. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. Note that this information is cached, so if you changed it recently, it will not be reflected here (see the 'Reverse DNS Tool' for the current data). The reverse DNS entries are:


27.1.155.195.in-addr.arpa mailfilterenda.tr.net.tr. [TTL=86399]



































Mail PASS Connect to mail servers OK: I was able to connect to all of your mailservers.
PASS Mail server host name in greeting OK: All of your mailservers have their host name in the greeting:


fmx.tr.net.tr:<br />    220 fmx.tr.net.tr SMTP <br />
PASS Acceptance of NULL <> sender OK: All of your mailservers accept mail from "<>". You are required (RFC1123 5.2.9) to receive this type of mail (which includes reject/bounce messages and return receipts).
PASS Acceptance of postmaster address OK: All of your mailservers accept mail to [email protected] (as required by RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1).
PASS Acceptance of abuse address OK: All of your mailservers accept mail to [email protected]
PASS Acceptance of domain literals OK: All of your mailservers accept mail in the domain literal format ([email protected][195.155.1.27]).
PASS Open relay test OK: All of your mailservers appear to be closed to relaying. This is not a thorough check, you can get a thorough one here.


fmx.tr.net.tr OK: 554 5.7.1 <[email protected]com>: Relay access denied <br />
PASS SPF record You have an SPF record. This is very good, as it will help prevent spammers from abusing your domain. Your SPF record (I don't check to see if it is well designed!) is:

"v=spf1 ip4:195.155.1.0/24 a mx include:tr.net ~all" [TTL=86400]



















WWW
INFO WWW Record Your www.evrimsigorta.com.tr A record is:


www.evrimsigorta.com.tr. CNAME evrimsigorta.com.tr. [TTL=86400]
evrimsigorta.com.tr. A 195.142.105.19 [TTL=86400] [TR]
PASS All WWW IPs public OK. All of your WWW IPs appear to be public IPs. If there were any private IPs, they would not be reachable, causing problems reaching your web site.
PASS CNAME Lookup OK. You do have a CNAME record for www.evrimsigorta.com.tr, which can cause some confusion. However, this is legal. Your CNAME entry also returns the A record for the CNAME entry, which is good -- otherwise, it would require an extra DNS lookup, which slightly delays the initial access to the website and use extra bandwidth. Note that if the CNAME points to another CNAME, it will likely cause problems.
INFO Domain A Lookup Your evrimsigorta.com.tr A record is:


evrimsigorta.com.tr. A 195.142.105.19 [TTL=86400]


 


Spam Database Lookup










 





  Run Test  
Reverse lookup: mailfilterenda.tr.net.tr


Summary
















Lists checked 51  
Timed out 0  
Listed on 1 BACKSCATTERER


Details

























Name Result Code Result Text Removal URL
AHBL http://www.ahbl.org/gettingout.php
ASPEWS Not Available
BACKSCATTERER 127.0.0.2 "Sorry 195.155.1.27 is blacklisted at http://www.backscatterer.org/?ip=195.155.1.2 7" http://www.backscatterer.org

CevapAlıntı
Gönderildi : 01/03/2010 19:27
Murat AYDIN
(@murataydin)
Üye

Teşekkür ederim Hocam,

Özellikle Fail'leri dikkate almanız gerekmektedir.

CevapAlıntı
Gönderildi : 01/03/2010 19:36
Deniz ASLAN
(@DenizASLAN)
Üye

Teşekkürler Hocam


Hangi siteden sorguladınız rica etsem siteadını alabilir miyim?

CevapAlıntı
Topic starter Gönderildi : 01/03/2010 19:57
Mesut SARIYAR
(@mesutsariyar)
Kıdemli Üye Forum Yöneticisi

Merhaba,


http://www.dnsstuff.com/


Kolay gelsin.

CevapAlıntı
Gönderildi : 01/03/2010 22:59
Deniz ASLAN
(@DenizASLAN)
Üye

Teşekkür ederim Mesut hocam bilgilendirme için.

CevapAlıntı
Topic starter Gönderildi : 02/03/2010 11:58
Paylaş: