From mboxrd@z Thu Jan 1 00:00:00 1970 From: wmorgan-sup@masanjin.net (William Morgan) Date: Sat, 06 Oct 2007 08:51:49 -0700 Subject: [sup-talk] sending mail; setting smtp server In-Reply-To: <20071006021120.GI422@chrislee.dhs.org> References: <47031532.800@edwardog.net> <1191447868-sup-1612@south> <1191619979-sup-726@south> <20071006021120.GI422@chrislee.dhs.org> Message-ID: <1191685867-sup-9423@south> Excerpts from CHRIS LEE's message of Fri Oct 05 19:11:20 -0700 2007: > As a *nix junkie, the automatic answer is: let each tool do it's job > and not include your own SMTP client. However, most gui-based MUAs for > Windows include an SMTP client. That's been my philosophy with Sup so far. And if the question really is better Windows support, that's not compelling enough of an argument for me (at least right now!). Sup makes a lot of Unix-specific assumptions and fixing those is pretty low on the priority queue. > So how about this for a compromise: Write a stand-alone tool, > supmailer, that sup can use in place of sendmail, but uses the sup > configuration files? There actually is good SMTP support right in the Ruby standard library, so I don't think I'd have to be that dramatic. The question is, is there a significant fraction of users trying to run Sup on systems that don't have a working sendmail setup? I'm guessing the answer is no. (Sorry Edward!) Opinions to the contrary (and patches) accepted. -- William