Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm having an issue that I need to try and have fixed. Fetchmail on my machine is complaining that it can't read my .procmailrc file in my home directory that is used for mail filtering.
What I am getting in my fetchmail log is:
procmail: Suspicious rcfile "/home/lmcilwain/.procmailrc"
procmail: Couldn't read "/home/lmcilwain/.procmailrc"
Nothing has changed with this file in months and all of a sudden it just stopped working.
Here are the permissions on my .procmailrc file:
Suspicious rcfile "x" The owner of the rcfile was not the recipient or root, the file was
world writable, or the directory that contained it was world
writable, or this was the default rcfile ($HOME/.procmailrc) and ei-
ther it was group writable or the directory that contained it was
group writable (the rcfile was not used).
Alternatively, you have lmcilwain as the home directory name but you have lmcilwai as the user:group - is there a typo?
Because the directory is group/world-writable, it will not use the .procmailrc file for fear that someone else could have placed a malicious .procmailrc file there to obtain copies of your email. Try removing group and world write permissions.
Edit: Hopefully Matir's suggestions fixes the problem before you get to trying this...
On my system, I can create a user:group of lmcilwain:lmcilwain and the ownership displays correctly (doesn't truncate the last 'n'). Are the other files in that directory owned the same way? If so, does running the following as root work?
Code:
chown -Rc lmcilwain:lmcilwain /home/lmcilwain
If not, you should be able to type the following to get the uid:gid for the lmcilwain user:
On my system, I can create a user:group of lmcilwain:lmcilwain and the ownership displays correctly (doesn't truncate the last 'n'). Are the other files in that directory owned the same way? If so, does running the following as root work?
Code:
chown -Rc lmcilwain:lmcilwain /home/lmcilwain
If not, you should be able to type the following to get the uid:gid for the lmcilwain user:
Many setups truncate usernames to 8 characters (the original UNIX max username length). Others replace usernames > 8 chars with the numeric UID. I doubt it's mis-owned.
Well it seems that the issue was that my user directory was set to world writeable. I didn't put two and two together...
I was working on trying to share a folder via smb on my system and I must have done something screwy. I went back to what I was doing and noticed that mistake (wierd). So I sent the permission as close to what I remember as possible and then checked my fetchmail and procmail logs and low and behold it is filtering again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.