Considering sendmail already knows about the other aliases file, and
already trusts majordomo, and `wrapper config-test` reports no problems,
and your list.config file is generated automatic by majordomo (if you
let it), and there is no real "port" between OSes for a perl script, I
have to guess that your problem is in the content of the aliases file
or the content of the majordomo.cf file. Majordomo.cf probably lives
in (or should live in) /etc.
Look for missing pipe symbols, missing quote marks, missing colons, or
too many of any of the above in any one line of your majordomo.aliases
file. Especially, dig through some of the majordomo-users archives for
emails/responses from me with test-approval: in the body of the message.
These messages will contain full examples of what your aliases for your
lists should look like.
If you are using a version of sendmail that makes use of smrsh, you will
also need to be sure you have a symbolic link created in the proper
location to your /path-to-majordomo/wrapper program.
Dan Liston
Grant Stockly wrote:
>
> Do you have any idea why sendmail would exit with a unexpected error 1?
>
> Could you show me a list config chunk from your machine that works? Maybe
> someone messed up in the BSD port patches...
>
> Grant
>
> >I would say so far, your problem is either in your
> >aliases file, the majordomo.cf file, or possibly
> >the ownerships/permissions on your majordomo
> >directory tree.
> >
> >Does sendmail know about majordomo yet? Does it
> >trust majordomo?
> >
> >Dan Liston
> >--
References:
|
|
