Quoting Tim Pierce ([EMAIL PROTECTED]) from Thu, Oct 07, 1999 at 02:31:39AM -0400:
> On Wed, Oct 06, 1999 at 11:51:55PM -0500, Jeremy Blosser wrote:
> > Raju K V [[EMAIL PROTECTED]] wrote:
> > > Suppose my machine does not have smtp capabilities? ie it does not have
> > > sendmail or any other MTA, can I use another machine as smtp host? I am
> > > looking for something equivalent to pine's smtp-server option.
> >
> > When you have pine doing this, your machine /does/ have SMTP capabilities
> > and an MTA installed - Pine. Pine speaks SMTP to the remote host you
> > specify to get the message there.
> >
> > Mutt doesn't believe in wasting developers' time and bloating the code base
> > this way. There are plenty of real MTAs out there, get one of them.
>
> It doesn't seem to me that a simple SMTP delivery-only client should
> have to involve a great deal of code, and it could certainly be made a
> compile-time option.
Seems silly considering all of the other alternatives. Like this:
#!/usr/bin/perl -wT
# little smtp smarthost-relay to quiet mutt-users
# 1999/10/07 Rich Lafferty <[EMAIL PROTECTED]>
# Use this under the same terms as Perl itself. No warranty.
use strict;
use Net::SMTP;
use Net::Domain;
# Change this line!
my $smarthost = "clyde.concordia.ca";
my $smtp = Net::SMTP->new($smarthost, Debug => 1);
my $me = $ENV{USER} . '@' . Net::Domain::hostfqdn();
$smtp->mail($me) or die "Invalid sender\n";
foreach my $recipient (@ARGV) {
if ($recipient ne "--") {
$recipient .= "." . Net::Domain::hostdomain()
unless $recipient =~ /\./;
$smtp->to($recipient) || warn "Invalid recipient\n";
}
}
$smtp->data() or die "Can't make a message\n";
while (<STDIN>) { $smtp->datasend($_) or die Can't make a message (c)\n"; }
$smtp->dataend() or die "Message delivery refused\n";
$smtp->quit or warn "SMTP session terminated abnormally\n";
__END__
> I see at least two significant advantages to having SMTP delivery
> support built directly into the client:
>
> * Many ISPs, as a spam prevention measure, require all mail delivery
> to go through their smarthost. Configuring an MTA to use a
> smarthost is not always trivial.
>
> * More generally, configuring an MTA when you are not thoroughly
> familiar with it can introduce security risks.
This is not true. A daemon, perhaps, but if you install ssmtp in ~/bin and
make it only executable by you, the security risks are less than those of,
say, rm.
>I don't think it's
> a feature if Mutt's design promotes more machines being set up as,
> say, open relays, even indirectly.
Mutt *does not send over port 25*. There's no way that you could use
an ssmtp-configured machine as a relay because *it doesn't accept mail*.
It just sends it on its way. Whether or not a machine receives mail over
smtp is completely orthogonal to mutt.
If we decide to include SMTP, I'm going to rally for UUCP and
PMDF-over-DECnet support. :-)
> and Chief Hacking Officer
Puh-lease.
-r.
--
------------------------------ Rich Lafferty ---------------------------
Sysadmin/Programmer, Information and Instructional Technology Services
Concordia University, Montreal, QC (514) 848-7625
------------------------- [EMAIL PROTECTED] ----------------------
PGP signature
