Do yourself a favor and create a link to your majordomo.aliases file
in the same directory as your regular aliases file.
`ln -s /usr/local/majordomo-1.94.5/majordomo.aliases /etc`
Now in your sendmail.cf file, set
O AliasFile=/etc/aliases,/etc/majordomo.aliases
Restart sendmail, and rebuild your aliases database. Everything
should now work without complaints.
Dan Liston
PS. I should explain that the most likely reason newaliases works
as the majordomo user, but not root is the ownership of the
majordomo.aliases file. 10-1 says it is owned by majordomo when
it should be owned by root. The same would be true even if the
file was in the etc directory. Aliases should be owned by root.
HAx0r wrote:
>
> Gooday!
>
> I was just wondering when, the 'newaliases' (sendmail -bi) command is run,
> does the following errors presented below cause problems in the actually
> delivery/workings of majordomo. I tried getting it to work with normal
> user and root, but the same error always appears......
>
> /etc/aliases: 7 aliases, longest 48 bytes, 218 bytes total
> hash map "Alias1": unsafe map file
> /usr/local/majordomo-1.94.5/majordomo.aliases.db: Permission denied
> WARNING: cannot open alias database
> /usr/local/majordomo-1.94.5/majordomo.aliases
> Cannot create database for alias file
> /usr/local/majordomo-1.94.5/majordomo.aliases
>
> However when I run it as the majordom (majordomo) user itself, I get a
> clean completion.
>
> /etc/aliases: 7 aliases, longest 48 bytes, 218 bytes total
> /usr/local/majordomo-1.94.5/majordomo.aliases: 10 aliases, longest 128
> bytes, 497 bytes total
>
> So basically, does this pose a problem to majordomo's functionality or
> does Majordom account only need this to work?????
>
> Kindly
> Dane
References:
|
|
