diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2011-September/008390.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2011-September/008390.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-September/008390.html | 199 |
1 files changed, 199 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-September/008390.html b/zarb-ml/mageia-dev/2011-September/008390.html new file mode 100644 index 000000000..544b61681 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/008390.html @@ -0,0 +1,199 @@ +<!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=%3C4E7F82A7.6070802%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="008348.html"> + <LINK REL="Next" HREF="008396.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA?</H1> + <B>andre999</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=%3C4E7F82A7.6070802%40laposte.net%3E" + TITLE="[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA?">andre999mga at laposte.net + </A><BR> + <I>Sun Sep 25 21:36:07 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="008348.html">[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA? +</A></li> + <LI>Next message: <A HREF="008396.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#8390">[ date ]</a> + <a href="thread.html#8390">[ thread ]</a> + <a href="subject.html#8390">[ subject ]</a> + <a href="author.html#8390">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Frank Griffin a écrit : +><i> On 09/23/2011 06:49 AM, andre999 wrote: +</I>>><i> +</I>>><i> Currently, entering a userid alone does not work. It has to be an +</I>>><i> email address. +</I>>><i> Note however that <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">userid at localhost</A> _is_ an email address. +</I>>><i> We could change it to accept only a valid format email address or a +</I>>><i> valid userid, in the latter case msec adding the @localhost part. +</I>>><i> IIRC, @localhost must be in a certain config file, which is the case +</I>>><i> by default. +</I>><i> +</I>><i> If you're referring to the Security panel in Summary, you certainly +</I>><i> *can* enter a userid. I regularly enter "root", and then give "root" +</I>><i> a .forward file to redirect from there. +</I> +You're right. I just tested it and it works now. +When I first installed postfix (on mdv2010.0 or earlier), it didn't work +until I added @localhost to my userid. It was probably a config +problem, which was solved with subsequent updates. + +><i> There seems to be some confusion between the functioning of an MUA and +</I>><i> MTA. They function identically, except that the MUA uses SMTP on +</I>><i> behalf of a single user and the MTA uses it on behalf of many users. +</I>><i> Also, an MUA receives mail for its single user by polling an MTA, +</I>><i> while an MTA typically listens for incoming connections from MUAs or +</I>><i> other MTAs and receives unsolicited mail for its many users. +</I>><i> +</I>><i> Both of them use exactly the same SMTP exchange to hand mail off to an +</I>><i> intermediate or final-destination MTA, and both of them need to be +</I>><i> configured with the information necessary to open a socket connection +</I>><i> to that receiving MTA. +</I>><i> +</I>><i> You only need an MTA on the sending system if the recipient is a user +</I>><i> who uses the sending system as its MTA. Unfortunately, that includes +</I>><i> the case of the user-to-user mail on the same system. +</I>><i> +</I>><i> So, regardless of what the RPMs require, msec really only needs an MUA +</I>><i> that is properly configured to hand mail off to the desired MTA, which +</I>><i> can be on another system entirely. The requirement for a local MTA +</I>><i> only arises if you want users on your system to be able to receive +</I>><i> mail, whether it's sent by msec or anything else. +</I>><i> +</I>><i> But in either case, you can't get around having to configure the MUA. +</I>><i> If you don't, the default config is usually to target an MTA on +</I>><i> localhost. And the default config for most MTAs when presented with a +</I>><i> 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 +</I>><i> deliver it locally. So yes, if you don't configure the MUA to use an +</I>><i> off-host MTA, you will need an on-host (localhost) MTA. If you don't +</I>><i> have one, the MUA's response is unpredictable; it may throw an error, +</I>><i> or it may (if it has root access) put the mail in /dead.letter. +</I> +So in sum, you seem to be saying that an MUA needs an MTA, which may be +on a remote machine. Except if it is to be delivered locally without +accessing a remote machine, the MTA (of course) has to be on the local +machine. + +>><i> The best solution is to ensure that an MTA is always installed. +</I>><i> +</I>><i> I'd vote for that for simplicity, provided the default configuration +</I>><i> made it usable only for local delivery to minimize security implications. +</I> +That makes sense. + +><i> However, I think there is a better solution. MTAs all simulate the +</I>><i> sendmail API, and since sendmail is usable as an MUA as well, so are +</I>><i> the various MTAs. Real MUAs aren't that uniform. Virtually all mail +</I>><i> reader apps use their own internal MUAs to send mail, and have their +</I>><i> own specific configuration mechanisms, e.g. thunderbird, +</I>><i> seamonkey-mail, evolution. +</I>><i> +</I>><i> In fact: +</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> ftg]# rpm -q --whatrequires mail +</I>><i> no package requires mail +</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> ftg]# rpm -q --whatrequires mailx +</I>><i> msec-0.80.10-2.mga1 +</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> ftg]# rpm -q --whatrequires nail +</I>><i> lsb-core-noarch-4.1-9.mga2 +</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> ftg]# rpm -q --whatrequires sendmail-command +</I>><i> lsb-core-noarch-4.1-9.mga2 +</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at ftgme2</A> ftg]# rpm -q --whatrequires mail-server +</I>><i> no package requires mail-server +</I>><i> +</I>><i> So, it might be a lot cleaner if we just changed msec to do its own +</I>><i> crippled send-only MUA activities, This is really a trivial +</I>><i> programming exercise, as indicated by this comment block from a C +</I>><i> program I wrote to do exactly this: +</I>><i> +</I>><i> ************************************************************ +</I>><i> The mail file contains SMTP commands with interspersed message +</I>><i> data, as follows: +</I>><i> HELO ... +</I>><i> MAIL FROM:... +</I>><i> RCPT TO:... +</I>><i> (repeats for each recipient) +</I>><i> DATA +</I>><i> (mail headers and body) +</I>><i> . +</I>><i> QUIT +</I>><i> +</I>><i> We open a session to the remote host's port 25, and ship each +</I>><i> of the SMTP commands, waiting for an acceptable response. The +</I>><i> "acceptable response" to each SMTP command begins with three +</I>><i> digits and ends with a CRLF. We examine only the three digits, +</I>><i> although we record the rest of the text. The acceptable +</I>><i> response for most commands is a "250"; for DATA, it is a "354", +</I>><i> and for QUIT it is a 221. We do not actually verify the +</I>><i> responses, since mailservers may vary, but simply forge on +</I>><i> unless we get an I/O error from the socket. The user should +</I>><i> be able to diagnose any errors from the transcript. +</I>><i> *********************************************************** +</I>><i> +</I>><i> That's if you do it from scratch; I have to think that perl already +</I>><i> has library support for sending mail. Of course, you'd probably not +</I>><i> want to hardcode port 25, and msec would need configuration which +</I>><i> could be handled by having a disabled entry field for host/port that +</I>><i> gets enabled if you fill in a mail recipient. +</I>><i> +</I>><i> If the host is missing, localhost, or the known host name of the local +</I>><i> machine, you'd want additional checks that something providing +</I>><i> mail-server is installed, and prompts to choose one if none is installed. +</I>><i> +</I>><i> Same support in msecgui, of course. +</I> +I like that approach. +There are a lot of mail-related perl packages. Hopefully one is +appropriate (or readily modified to be so). + +We should also have code that gracefully deals with cases where it is +requested to send security messages to a remote host. (For example, if +a remote-capable MTA is not installed or accessible.) + +-- +André + +</PRE> + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="008348.html">[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA? +</A></li> + <LI>Next message: <A HREF="008396.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#8390">[ date ]</a> + <a href="thread.html#8390">[ thread ]</a> + <a href="subject.html#8390">[ subject ]</a> + <a href="author.html#8390">[ 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> |