We have a spam forwarding problem. Specifically, we forward spam,although not through choice; it's a political mandate not to imposefiltering on people, and some of the people who don't filterforward their email elsewhere, and predictable things ensue .

We're dealing with this in three ways:

• we use a different source IP address when forwarding spam-tagged email , splitting good emailtraffic away from the spam so we avoid contaminating the formerwith the latter.

  This is especially important for places where

We got contacted by a user reporting that he couldn't get mail withan address in kuet.ac.bd; our inbound mail gateway was consistentlyrejecting the address as temporarily unresolvable. When I startedlooking into the DNS situation, all sorts of peculiar things startedcrawling out of the woodwork.

• in the root zone, the bd country domain has two servers, dns.bdand slave.bttb.net.
• if you query either of them you get a third server as well,dns.bttb.net