From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sending mail; setting smtp server
Date: Sat, 06 Oct 2007 08:51:49 -0700 [thread overview]
Message-ID: <1191685867-sup-9423@south> (raw)
In-Reply-To: <20071006021120.GI422@chrislee.dhs.org>
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 <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-10-06 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 4:06 Edward Ocampo-Gooding
2007-10-03 5:17 ` Ian Taylor
2007-10-03 17:51 ` [sup-talk] Knowledge Store? vasudeva
2007-10-03 21:13 ` William Morgan
2007-10-03 21:44 ` [sup-talk] sending mail; setting smtp server William Morgan
2007-10-03 21:52 ` William Morgan
2007-10-05 21:34 ` William Morgan
[not found] ` <20071006021120.GI422@chrislee.dhs.org>
2007-10-06 15:51 ` William Morgan [this message]
2007-10-07 9:37 ` Claes Nästén
2007-10-07 20:06 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1191685867-sup-9423@south \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox