On Tue, 22 Sep 1998, Chris Wedgwood wrote:
On Tue, Sep 22, 1998 at 02:26:58PM +1200, Simon Blake wrote:
Upon further reflection, in occured to me that an even better technique for avoiding traffic bills would be to MX city.wellington.net.nz to 127.0.0.1, which I did, and all my spam problems have gone away :-). My question - is this a dodgy thing to do, have I missed some critical reason why I shouldn't do this?
If no MX records exist, delivery via the A record will be attempted.
Which was what was happening, and crashing the mail server every 20 minutes under extreme syslog load.
If you don't need the A records, loose it and the MX records, that way, mail won't even attempt to be delivered.
Mmm, have to have the A records, they're used for other services.
Having MX records, IMO implies the domains is `mail-connected' and therefore postmaster(a)city.wellington.net.nz should be a valid reachable email address (RFC requirement):
Agreed, it's just a pity that there is no way to flag the reverse case, when a host *does not* wish to receive mail under any circunstances, but still wants IP connectivity. In the circumstances, I think I'll just put up with breaking the RFC's for a while, at least until I get some SMTP filtering going to reject mail for city.wellington.net.nz as it arrives.
Using 127.0.0.1 might cause mailer loops and other evils at remote sites (depending on their setup and other stuff). At the very least, it will generate for some sites postmaster double-bounces...
That's kinda the idea :-). Cheers Si --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog