Jamees,
As Shaun pointed out, the issues are not just internal to Imail but also in
DNS.
For every possible recipient host or domain after the @, you need to have
an MX for reliable delivery, and you can't actually have "too many", so
here one of yr pb's:
# dig netmajik.com mx
; <<>> DiG 8.2 <<>> netmajik.com mx
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUERY SECTION:
;; netmajik.com, type = MX, class = IN
;; AUTHORITY SECTION:
netmajik.com. 1H IN SOA ns1.netmajik.com.
administrator.netmajik.com. (
14 ; serial
1H ; refresh
10M ; retry
1D ; expiry
1H ) ; minimum
which is an error good, just fix the above like this one:
# dig ns1.netmajik.com mx
; <<>> DiG 8.2 <<>> ns1.netmajik.com mx
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; QUERY SECTION:
;; ns1.netmajik.com, type = MX, class = IN
;; ANSWER SECTION:
ns1.netmajik.com. 1H IN MX 10 ns1.netmajik.com.
;; ADDITIONAL SECTION:
ns1.netmajik.com. 1H IN A 64.50.158.132
The above error also listed DNS Expert report, sent privately.
Len
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
