In the message dated: Mon, 06 Feb 2012 18:59:17 EST, The pithy ruminations from Ken Hornstein on <[Nmh-workers] masquerade settings & spost> were: => Greetings all, => => I've been (slowly) working on sorting out the whole From: mess that => was discussed earlier, and of course like many things in nmh there are => a ton of assumptions that makes this a lot harder than it needs to be. => But I digress ...
Many thanks for all your work! => => I came across the code in post that handles the masquerade settings and I've => realized that a) it makes post more complex, and b) I don't think we need => it, especially since we're switching to configuring our userid in .mh_profile. => => To remind everyone, there are currently three settings in mts.conf for => masquerade: => => draft_from - if you don't have this then post will use what it thinks is => your "real" from as the Sender: header (and the envelope from => address as well). I guess this was done to prevent undergrads => from easily forging email; I would submit that the days when => you had to know the details of SMTP to forge email are long => over since nearly every email client out allows you to change => the from: header (although I fondly remember that as a rite => of passage in college ... ah, good times). I think that => we should simply remove the flag and always use the From: => header in the draft as the envelope from. I disagree. I was under the impression that the "From" field in .mh_profile would be a default, particularly if nothing else was set or could be determined as the 'right' address. Like most of us, I've got multiple mail address personality disorder. I set the body From: to several different addresses daily. I really don't want the envelope and body From addresses to differ. Certainly, if nothing is set, then the value in .mh_profile should be used for both...but if the user does set the body From to something else, I'd like to see that masqueraded in the envelope too. => => mmailid - Allows you to format your GECOS field so the envelope from => will be taken from the GECOS field. I can see getting rid of this. => => username_extension - Adds $USERNAME_EXTENSION to the your userid. And this too... => => Like I said, I don't believe draft_from is relevant in the modern email => world, and if we're going to configuring your userid in .mh_profile I think => that's a better way of accomplishing the last two. I propose to junk it => all. Thanks, Mark => => And while we're talking about post .... I always forget about it, but there's => also spost. It opens a pipe to sendmail -t and uses that to submit email. => It's not documented and there's a lot of duplicated code there. I propose => to just get rid of it (because, frankly, I don't want to have to hack on that => code twice). Objections? => => --Ken => => _______________________________________________ => Nmh-workers mailing list => [email protected] => https://lists.nongnu.org/mailman/listinfo/nmh-workers => _______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
