hi ya bob...
try.... looking closely at the messages...
mail -v -s Testing Majordomo@your_server.com < /dev/null
and repeat for the other majordomo related aliases
c ya
alvin
> Todd Lyons wrote:
>
> Bob wrote:
>
> > Coupla days ago, MJ stopped working and we cannot firure out why. We have tried
> > seting debugs, trusses, etc. but no clues. I would greatly appreciate any
> > debugging help/suggestions you might be able to provide.
>
> Gonna need just a tad bit more information than that. How about posting (to
> the list):
> 1) aliases file(s). I figure this hasn't changed, but you might notice
> something while you're posting it.
> 2) If there are multiple aliases files, make sure that in sendmail.cf that
> all are defined. For example, when you do a 'newaliases', does it see all
> alias files that it should be seeing? By any chance, did you just upgrade a
> newer sendmail? That points to this one.
> 3) Is mj set to queue mail? If so, is your sendmail set to run the queue
> (defaults to 1 hour, I believe, so it seems it should be). Also, if
> sendmail is set to HoldExpensive, then it will queue majordomo mail until
> the queue is next run (piping to a program is considered "expensive").
> 4) Snippets from your mail logs where it receives mail and says what it
> does with it.
> 5) Is it messages to majordomo that are the problem, or is it messages to
> the list, or both?
> 6) If it's a problem with the list only, post your list.config file (minus
> passwords of course).
>
> Anything further will only be guesses. I'm sure Dan will be able to figure
> it out in short order for you :)
>
> Blue skies... Todd
> --
> Most traditional Pee-Cee user groups, I've noticed, function mainly as
> commiseration societies for people who've bought lousy hardware, are
> struggling and wasting time trying to deal with it, and want to exchange
> coping-strategy tips with others in the same boat. -- Rick Moen
>
References:
|
|
