At 11:03 AM 11/29/02 -0500, Haines Brown wrote:
Is this perhaps the source of the troublesome bogus linux-newbie address that almost always shows up in your messages to the list? If it is, PLEASE change this practice ... you are being very inconsiderate, inconveniencing the very people you want to get help from.I use an e-mail alias list: ~/.aliases/NARL.aliases. My individual aliases work OK (I'm using it for this message),
This is a security-related message; your MTA (sendmail?) will not use aliases from a world-writable directory because if it did, it could be tricked into using incorrect ones (incorrect from the account owner's perspective, forged by another user on the system).but I'm having trouble using an alias list, or at least this NARL.aliases list.I now get the error message: ----- The following addresses had permanent fatal errors ----- :include:/home/brownh/aliases/NARL.aliases (expanded from: NARL) ----- Transcript of session follows ----- 550 5.2.4 :include:/home/brownh/aliases/NARL.aliases... Cannot open /home/brownh/aliases/NARL.aliases: World writable directory I believe I know the source of the problem, but would appreciate an explanation and a possible work-around.
Check the status of the directory with "ls -l /home/brown/aliases" and (probably) chmod it from mode 777 (this is just a guess) to mode 755 (this will work, assuming brownh owns the directory). That should deal with your problem here (or you may also have to chmod the actual NARL.aliases file as well ... oh, and I am assuming that NARL.aliases is a file, not a directory ... if that's wrong, adapt this guidence to fit your circumstances).
All the stuff you discuss below probably has nothing to do with your problem.
User "brownh" uses rmail under emacs. However, for an OT reason, user brownh can't log in to his own account, but must access to it via an xterm in another account, in which is run the command su - brownh, and then emacs. Is this complicated procedure preventing the NARL.aliases file from being read? I've played with permissions for it and its directory, including any write permission at all from both directory and file, but to no avail. I have not yet tried running emacs with # emacs -u brownh, however.
-- -------------------------------------------"Never tell me the odds!"-------- Ray Olszewski -- Han Solo Palo Alto, California, USA [EMAIL PROTECTED] ------------------------------------------------------------------------------- - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
