Steve wrote:
bgahl(_at_)thesphere(_dot_)com wrote:
> On a whim, I tried an experiment. I set up an alias with a .forward
> (actually to my pager) and this does not work!
>
> I bet the patches broke the sendmail .forward functionality some how!
> Which, in turn, breaks my procmail!
>
> I will be testing further and let y'all know.
>
> First off, check /var/log/syslog to see if there are permission problems.
> Sendmail, in it's current implementation, is pretty anal about permissions.
Make
> sure that (a) your home directory is not group writeable (i.e., chmod 755
> ~scarter) and (b) your .forward file is only writeable by you (i.e. chmod
644
> .forward). Any permission problems "should be" logged in /var/log/syslog,
and
> that sounds like what this is now.
>
> It does sound like sendmail got upgraded by the patch. If you had procmail
as an
> MTA in your sendmail.cf, I'll bet that is gone, too.
I checked /var/log/syslog and found:
Jul 2 12:50:28 magi.primenet.com sendmail[257]: MAA00255: forward
/usr/users/sc/.forward: Group writable directory
I assure you, neither my home dir or my .forward file were group/world
writable. This being a workstation, I added some 'DontBlameSendmail' options
to turn off the checking feature.
Everything seems to work now. The anal-retentive in me doesn't like this
hack, but at least my procmail is now working. :)
Well, sendmail checks from the root all the way down. If ANY directory is group
writable along the path to your directory, you'll need to "remove" the group
write permissions, or as you have surmised, tell sendmail to quit worrying about
it :(
Bob "who knows more about sendmail now than he ever thought he would or wanted
to"