Geesh! I was surprised to discover that sending email to EdsaMail addresses resulted to failure on my mail servers. I don’t think the problem is from my end since all emails sent through my mail server are sent successfully and my DNS servers are functioning pretty well since it’s directly connected to ROOT servers and doesn’t just forward queries to my ISP’s DNS servers.
Here’s the log I see in my personal mail server using QMail-LDAP (replaced real edsamail username to XXX):
@40000000429282bf21ca9ca4 starting delivery 3287: msg 331217 to remote XXX@edsamail.com.ph
@40000000429282bf21cac3b4 status: local 0/10 remote 1/20
@40000000429282d32241d42c delivery 3287: deferral: Sorry,_I_couldn't_find_any_host_by_that_name._(#4.1.2)/
@40000000429282d32241ff24 status: local 0/10 remote 0/20
Thinking that EdsaMail is a mail service provider, I don’t think this kind of error should ever occur. It’s ok if it’s just a personal mail server of some wannabe geeks, but for a company hosting email solutions, this is quite unacceptable. This is not the first time that this occurred for I’ve seen this error before in some mail servers I host. In fairness to EdsaMail, this is an intermittent problem meaning that sometimes it works, and sometimes it doesn’t.
I think the problem might also be in their DNS servers, namely ns1.edsamail.com.ph and ns2.edsamail.com.ph for when I try to query MX and NS entries on the said servers for their domain, I get a timeout. This means their DNS servers doesn’t reply for domain queries on edsamail.com.ph. I’m not sure if their DNS servers are down or if they are blocking DNS queries for their own domain which shouldn’t be the case. This are the results of the dig command to query their domain info:
# dig @ns1.edsamail.com.ph edsamail.com.ph ANY
; < <>> DiG 9.2.3 < <>> @ns1.edsamail.com.ph edsamail.com.ph ANY
;; global options: printcmd
;; connection timed out; no servers could be reached
# dig @ns2.edsamail.com.ph edsamail.com.ph ANY
; < <>> DiG 9.2.3 < <>> @ns2.edsamail.com.ph edsamail.com.ph ANY
;; global options: printcmd
;; Got answer:
;; ->>HEADER< <- opcode: QUERY, status: SERVFAIL, id: 20041
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;edsamail.com.ph. IN ANY
;; Query time: 134 msec
;; SERVER: 203.177.1.18#53(ns2.edsamail.com.ph)
;; WHEN: Tue May 24 10:42:52 2005
;; MSG SIZE rcvd: 33
# dig edsamail.com.ph ANY
; <<>> DiG 9.2.3 < <>> edsamail.com.ph ANY
;; global options: printcmd
;; Got answer:
;; ->>HEADER< <- opcode: QUERY, status: NOERROR, id: 54398
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;edsamail.com.ph. IN ANY
;; ANSWER SECTION:
edsamail.com.ph. 80192 IN NS ns1.edsamail.com.ph.
edsamail.com.ph. 80192 IN NS ns2.edsamail.com.ph.
;; Query time: 36 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue May 24 10:43:00 2005
;; MSG SIZE rcvd: 69
# dig edsamail.com.ph MX
; <<>> DiG 9.2.3 < <>> edsamail.com.ph MX
;; global options: printcmd
;; connection timed out; no servers could be reached
The way their DNS servers reply to queries is kinda weird, and worst of all, they don’t provide MX records for their domain. I’m not sure if I’m doing something wrong, but definitely this kind of domain query replies cause mail servers not being able to send email messages to EdsaMail users. 
Oh well, I just hope they do something about this since this is not a good business case for such company.