On Thu, Jun 23, 2011 at 2:49 PM, Matthew Fluet <span dir="ltr"><<a href="mailto:matthew.fluet@gmail.com">matthew.fluet@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">I believe that Wesley is referring to some of the e-mail delivery</div>
options available via Google Apps:<br></blockquote><div></div></div><br><div>I was imagining an even lower tech solution. Setup <a href="http://mlton.org">mlton.org</a> on google apps to handle mail. Create a 'mlton' and 'mlton-devel' user. In the user's gmail settings add a forwarding address to '<a href="mailto:mlton@lists.sf.net">mlton@lists.sf.net</a>'.</div>
<div><br></div><div>This forwarding isn't like the 'forward' button in an email client. The mail is left unchanged but delivered to a new address. (I assume people are aware that the 'To/CC/etc' fields of an email are just for informational use and don't actually control the destination of an email)</div>
<div><br></div><div>That said, 'split delivery might work', but I suspect it will leave the recipient address unmodified. Thus, <a href="http://sf.net">sf.net</a> will drop the mail as it doesn't know the address '<a href="mailto:mlton@mlton.org">mlton@mlton.org</a>'. My low tech proposal would have changed the delivery address to '<a href="mailto:mlton@lists.sf.net">mlton@lists.sf.net</a>' whilst leaving the 'To/etc' fields showing <a href="mailto:mlton@mlton.org">mlton@mlton.org</a>.</div>
<div><br></div>