summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-September/008342.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-September/008342.html')
-rw-r--r--zarb-ml/mageia-dev/2011-September/008342.html185
1 files changed, 185 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-September/008342.html b/zarb-ml/mageia-dev/2011-September/008342.html
new file mode 100644
index 000000000..e75689ee6
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-September/008342.html
@@ -0,0 +1,185 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA?
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20msec%20%28nail%29%20can%27t%20send%20reports%20to%0A%20local%09users%20accounts%20-%20require%20an%20MTA%3F&In-Reply-To=%3C4E7C8A63.7080503%40roadrunner.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="008341.html">
+ <LINK REL="Next" HREF="008346.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA?</H1>
+ <B>Frank Griffin</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20msec%20%28nail%29%20can%27t%20send%20reports%20to%0A%20local%09users%20accounts%20-%20require%20an%20MTA%3F&In-Reply-To=%3C4E7C8A63.7080503%40roadrunner.com%3E"
+ TITLE="[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA?">ftg at roadrunner.com
+ </A><BR>
+ <I>Fri Sep 23 15:32:19 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="008341.html">[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA?
+</A></li>
+ <LI>Next message: <A HREF="008346.html">[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#8342">[ date ]</a>
+ <a href="thread.html#8342">[ thread ]</a>
+ <a href="subject.html#8342">[ subject ]</a>
+ <a href="author.html#8342">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On 09/23/2011 06:49 AM, andre999 wrote:
+&gt;<i>
+</I>&gt;<i> Currently, entering a userid alone does not work. It has to be an
+</I>&gt;<i> email address.
+</I>&gt;<i> Note however that <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">userid at localhost</A> _is_ an email address.
+</I>&gt;<i> We could change it to accept only a valid format email address or a
+</I>&gt;<i> valid userid, in the latter case msec adding the @localhost part.
+</I>&gt;<i> IIRC, @localhost must be in a certain config file, which is the case
+</I>&gt;<i> by default.
+</I>
+If you're referring to the Security panel in Summary, you certainly
+*can* enter a userid. I regularly enter &quot;root&quot;, and then give &quot;root&quot; a
+.forward file to redirect from there.
+
+There seems to be some confusion between the functioning of an MUA and
+MTA. They function identically, except that the MUA uses SMTP on behalf
+of a single user and the MTA uses it on behalf of many users. Also, an
+MUA receives mail for its single user by polling an MTA, while an MTA
+typically listens for incoming connections from MUAs or other MTAs and
+receives unsolicited mail for its many users.
+
+Both of them use exactly the same SMTP exchange to hand mail off to an
+intermediate or final-destination MTA, and both of them need to be
+configured with the information necessary to open a socket connection to
+that receiving MTA.
+
+You only need an MTA on the sending system if the recipient is a user
+who uses the sending system as its MTA. Unfortunately, that includes
+the case of the user-to-user mail on the same system.
+
+So, regardless of what the RPMs require, msec really only needs an MUA
+that is properly configured to hand mail off to the desired MTA, which
+can be on another system entirely. The requirement for a local MTA only
+arises if you want users on your system to be able to receive mail,
+whether it's sent by msec or anything else.
+
+But in either case, you can't get around having to configure the MUA.
+If you don't, the default config is usually to target an MTA on
+localhost. And the default config for most MTAs when presented with a
+userid as an address is to rewrite the address to <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">user at localhost</A> and
+deliver it locally. So yes, if you don't configure the MUA to use an
+off-host MTA, you will need an on-host (localhost) MTA. If you don't
+have one, the MUA's response is unpredictable; it may throw an error, or
+it may (if it has root access) put the mail in /dead.letter.
+
+
+&gt;<i>
+</I>&gt;<i> The best solution is to ensure that an MTA is always installed.
+</I>&gt;<i>
+</I>
+I'd vote for that for simplicity, provided the default configuration
+made it usable only for local delivery to minimize security implications.
+
+However, I think there is a better solution. MTAs all simulate the
+sendmail API, and since sendmail is usable as an MUA as well, so are the
+various MTAs. Real MUAs aren't that uniform. Virtually all mail reader
+apps use their own internal MUAs to send mail, and have their own
+specific configuration mechanisms, e.g. thunderbird, seamonkey-mail,
+evolution.
+
+In fact:
+[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> ftg]# rpm -q --whatrequires mail
+no package requires mail
+[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> ftg]# rpm -q --whatrequires mailx
+msec-0.80.10-2.mga1
+[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> ftg]# rpm -q --whatrequires nail
+lsb-core-noarch-4.1-9.mga2
+[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> ftg]# rpm -q --whatrequires sendmail-command
+lsb-core-noarch-4.1-9.mga2
+[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> ftg]# rpm -q --whatrequires mail-server
+no package requires mail-server
+
+So, it might be a lot cleaner if we just changed msec to do its own
+crippled send-only MUA activities, This is really a trivial programming
+exercise, as indicated by this comment block from a C program I wrote to
+do exactly this:
+
+************************************************************
+ The mail file contains SMTP commands with interspersed message
+ data, as follows:
+ HELO ...
+ MAIL FROM:...
+ RCPT TO:...
+ (repeats for each recipient)
+ DATA
+ (mail headers and body)
+ .
+ QUIT
+
+ We open a session to the remote host's port 25, and ship each
+ of the SMTP commands, waiting for an acceptable response. The
+ &quot;acceptable response&quot; to each SMTP command begins with three
+ digits and ends with a CRLF. We examine only the three digits,
+ although we record the rest of the text. The acceptable
+ response for most commands is a &quot;250&quot;; for DATA, it is a &quot;354&quot;,
+ and for QUIT it is a 221. We do not actually verify the
+ responses, since mailservers may vary, but simply forge on
+ unless we get an I/O error from the socket. The user should
+ be able to diagnose any errors from the transcript.
+***********************************************************
+
+That's if you do it from scratch; I have to think that perl already has
+library support for sending mail. Of course, you'd probably not want to
+hardcode port 25, and msec would need configuration which could be
+handled by having a disabled entry field for host/port that gets enabled
+if you fill in a mail recipient.
+
+If the host is missing, localhost, or the known host name of the local
+machine, you'd want additional checks that something providing
+mail-server is installed, and prompts to choose one if none is installed.
+
+Same support in msecgui, of course.
+
+
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="008341.html">[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA?
+</A></li>
+ <LI>Next message: <A HREF="008346.html">[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#8342">[ date ]</a>
+ <a href="thread.html#8342">[ thread ]</a>
+ <a href="subject.html#8342">[ subject ]</a>
+ <a href="author.html#8342">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>