🚀 go-pugleaf

when i explode a message to a large mailing list and half the recipients
are all going to people inside the same remote organization but with addresses
in different subdomains such that i'm going to use the same MX for all of
them, i end up sending N copies of the mail since M...F=m only works if
all the S0 $@'s have the same string in them.

i'm about to hack on King James Sendmail to deal with this problem, but it's
going to be a pretty significant change since i'll have to search for all the
MX's fairly early and save the results so that they can be part of the sort/
merge operation.  does anyone have any special requests as to other things i
should do while i'm in there, or does anyone have a suggestion as to how i
ought (not) to implement this?

i'm going to add the ability to keep an external host status database at the
same time.  i run a lot of parallel sendmail daemons here and they currently
do not benefit from eachother's experiences as to unreachable hosts et al.
(they may also be keeping their database in terms of $@ names instead of
actual hostnames a la MX, which is what makes me think of this just now).

cheers,
--
Paul Vixie
DEC Western Research Lab	<vixie@pa.dec.com>	<paul@vixie.sf.ca.us>
Palo Alto, California, USA	...!decwrl!vixie	...!vixie!paul