Anyone else having bouncing e-mail problems with MTN?

[Terencek]

Along with several colleagues also using the MTN outgoing mail server, I've been having several days of difficulty with bouncing mails. MWeb, my ISP, acknowledges there is 'a possible issue on one of the mail servers on the
MTN mail platform'. Getting really irritating now, not being able to rely on mail getting through. Anyone have any information on this?

 

[orange]

Along with several colleagues also using the MTN outgoing mail server, I've been having several days of difficulty with bouncing mails. MWeb, my ISP, acknowledges there is 'a possible issue on one of the mail servers on the
MTN mail platform'. Getting really irritating now, not being able to rely on mail getting through. Anyone have any information on this?

MTN's entire network is always going to be iffy - because of their DNS:

They use:
ns1.mtnns.net. 209.212.96.6
ns2.mtnns.net. 209.212.97.6

they both sit on the same ASN in the same (apparantly) rack. One small break between their servers and the rest of the world and bang! mail bouncing...

What I'm really interested in is how their poor (and thats the most complimentary word i can summon) DNS affects their GSM network. My guess is the answers are scary.

 

[YelloFever]

Your comments are incorrect. Our DNS servers are dns1.mtnns.net and dns2.mtnns.net and they are not in the same location or same rack. DNS1 is located at our Randburg Datacentre and DNS2 is located at New Doornfontein switching center. NS1 and NS2 are the zone carriers and not caching DNS servers.

 

[Terencek]

All well and good but that doesn't address the original question: why MWeb, responding to mail-bouncing complaints from its MTN Broadband customers, states that there is 'a possible issue on one of the mail servers on the
MTN mail platform'.

?????????

 

[Tinuva]

Actually there are other problems I have seen with clients sending mail directly from mtnns's network.

X-Spam-Report:
* 1.6 RCVD_IN_SORBS_WEB RBL: SORBS: sender is a abuseable web server * [41.208.50.176 listed in dnsbl.sorbs.net]
* 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net * [Blocked - see <http://www.spamcop.net/bl.shtml?41.208.50.176>]
* 1.0 RCVD_IN_PSBL RBL: Received via a relay in PSBL (Passive Spam Block * List) * [41.208.50.176 listed in psbl.surriel.com]
* 1.0 RCVD_IN_BRBL_RELAY RBL: received via a relay rated as poor by * Barracuda * [41.208.50.176 listed in b.barracudacentral.org] * 0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60% * [score: 0.5000]

dig -x 41.208.50.176

; <<>> DiG 9.5.0-P2 <<>> -x 41.208.50.176
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63884
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;176.50.208.41.in-addr.arpa. IN PTR

;; ANSWER SECTION:
176.50.208.41.in-addr.arpa. 78723 IN PTR gprs02.rb.mtnns.net.

Unfortunately that will always be a problem if not using their smtp server for sending mail, which I do not know what it is.