--
>>>> > is the new sendmail (8.6.9) objecting to the double-quotes? the documentatio
**** Command '>' not recognized.
>>>>
>>>> No, it doesn't object to double quotes.
**** Command 'no,' not recognized.
>>>>
>>>> Try (this takes sendmail out of the equation):
**** Command 'try' not recognized.
>>>>
>>>> cat sample_mesg | /bin/sh -c "applic/ath/majordomo/wrapper resend -l psi -h callisto.pas.rochester.edu psi-outgoing" ; echo $?
**** Command 'cat' not recognized.
>>>>
>>>> where sample_mesg is something resend would want to see.
**** Command 'where' not recognized.
>>>>
>>>> You would seem to be getting "1" from this command (that's what unknown
**** Command 'you' not recognized.
>>>> mailer error 1 means - in it's entirety).
**** Command 'mailer' not recognized.
>>>> You want to be getting 0. If you get a 0 sendmail shouldn't complain.
**** Command 'you' not recognized.
>>>>
>>>> > John P Rouillard writes:
**** Command '>' not recognized.
>>>> > > Error code 1 is generated when wrapper is called by itself with no
**** Command '>' not recognized.
>>>> > > arguments. This can happen in alias files if there aren't quotes in
**** Command '>' not recognized.
>>>> > > the propper place, or \ doesn't continue a line etc. The exact format
**** Command '>' not recognized.
>>>> > > for long command lines seems to change from sendmail to sendmail. Your
**** Command '>' not recognized.
>>>> > > milage may vary.
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> > i've added the list.config file and chopped out the old options to
**** Command '>' not recognized.
>>>> > resend, and i still have unknown mailer error 1. mail -v doesn't give
**** Command '>' not recognized.
>>>> > me any information that the bounce message didn't.
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> > the list entry is
**** Command '>' not recognized.
>>>> > psi: "|/applic/ath/majordomo/wrapper resend -l psi -h callisto.pas.rochester.
**** Command '>' not recognized.
>>>> edu psi-outgoing"
**** Command 'edu' not recognized.
>>>> > [all one line],
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> > the bounce in its entirety is:
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> > > The original message was received at Fri, 3 Jun 1994 01:47:23 -0400
**** Command '>' not recognized.
>>>> > > from colin@localhost
**** Command '>' not recognized.
>>>> > >
**** Command '>' not recognized.
>>>> > > ----- The following addresses had delivery problems -----
**** Command '>' not recognized.
>>>> > > "|/applic/ath/majordomo/wrapper resend -l psi -h callisto.pas.rochester.edu
**** Command '>' not recognized.
>>>> ps
**** Command 'ps' not recognized.
>>>> > > i-outgoing" (unrecoverable error)
**** Command '>' not recognized.
>>>> > > (expanded from: psi)
**** Command '>' not recognized.
>>>> > >
**** Command '>' not recognized.
>>>> > > ----- Transcript of session follows -----
**** Command '>' not recognized.
>>>> > > Message delivered to mailing list psi
**** Command '>' not recognized.
>>>> > > 554 "|/applic/ath/majordomo/wrapper resend -l psi -h callisto.pas.rochester
**** Command '>' not recognized.
>>>> .ed
**** Command '.ed' not recognized.
>>>> > > u psi-outgoing"... unknown mailer error 1
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> > i get the same error even if i remove the -h flag as you suggested.
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> > the list files are:
**** Command '>' not recognized.
>>>> > -rw-rw-r-- 1 daemon majordom 900 May 30 21:52 psi
**** Command '>' not recognized.
>>>> > -rw-rw-r-- 1 daemon majordom 146 Jun 3 01:24 psi.config
**** Command '>' not recognized.
>>>> > -rw-rw-r-- 1 daemon majordom 6 Jun 3 00:50 psi.passwd
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> > is the new sendmail (8.6.9) objecting to the double-quotes? the documentatio
**** Command '>' not recognized.
>>>> n
**** Command 'n' not recognized.
>>>> > is so byzantine i have no idea where to look for that kind of detail.
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> > if not that, what else could it possibly be? i've sunk a ridiculous amount
**** Command '>' not recognized.
>>>> > of time in to trying to make this work :-{
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> > --
**** Command '>' not recognized.
>>>> > colin | the avalanche has already started. it is too late for the pebbles
**** Command '>' not recognized.
>>>> > roald | to vote. (kosh naranek, _babylon 5_)
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>>
**** No valid commands found.
**** Commands must be in message BODY, not in HEADER.
**** Help for Majordomo@foo.GreatCircle.COM:
This is Brent Chapman's "Majordomo" mailing list manager, version 1.90.
In the description below items contained in []'s are optional. When
providing the item, do not include the []'s around it.
It understands the following commands:
subscribe <list> [<address>]
Subscribe yourself (or <address> if specified) to the named <list>.
unsubscribe <list> [<address>]
Unsubscribe yourself (or <address> if specified) from the named <list>.
get <list> <filename>
Get a file related to <list>.
index <list>
Return an index of files you can "get" for <list>.
which [<address>]
Find out which lists you (or <address> if specified) are on.
who <list>
Find out who is on the named <list>.
info <list>
Retrieve the general introductory information for the named <list>.
lists
Show the lists served by this Majordomo server.
help
Retrieve this message.
end
Stop processing commands (useful if your mailer adds a signature).
Commands should be sent in the body of an email message to
"Majordomo@foo.GreatCircle.COM".
Commands in the "Subject:" line NOT processed.
If you have any questions or problems, please contact
"Majordomo-Owner@foo.GreatCircle.COM".
|
|
