- Date: Fri, 12 Mar 1999 11:48:24 +0000
On Fri, Mar 12, 1999 at 10:42:01AM +0000, Paul Mansfield wrote:
> Sort of related topic...
> When we find a customer with an open mail relay, and they're running some
> antique creaky old MTA which they can't upgrade and can't be fixed, there's
> usually only one solution.
> We check they have working backup MX records, and then they filter the SMTP
> port at their router. Noone except us (our backup MXers) can "see" their mail
> machines, and their mail is forced to come via us.
While a five minute delay on a single mail is usually acceptable, several
five minute delays on every post to a mailing list really starts to hurt
those list managers that work their way through a list sequentially (and
I can only speculate what it does to those that insist on simultaneously
forking a process for every recipient).
It's a good solution, but this LISTSERV maintainer for one would be a lot
happier if the reachable MTA were the primary MX host, and the MTA was either
configured to forward to the customer, or run off a different zone file.