Re: More problems w/ EXIM upgrade

1999-06-30 Thread Didi Damian
I had that problem also and I entered this in my .muttrc in the sendmail section: ### sendmail ### Type: string ### Default: /usr/lib/sendmail -oi -oem ### Specifies the program and arguments used to deliver mail sent by Mutt. ### Mutt expects that the specified program will read the message head

Re: More problems w/ EXIM upgrade

1999-06-30 Thread Lex Chive
On Wed, Jun 30, 1999 at 08:02:57AM -0500, [EMAIL PROTECTED] wrote: > But now I have a problem with mutt. When ever I try to send a message from > within mutt, I get: > > 'Error sending message, child exited 127 ().' > > And the message is not sent. > > So I went and looked in /etc/Muttrc and f

Re: More problems w/ EXIM upgrade

1999-06-30 Thread Dan Everton
On Wed, Jun 30, 1999 at 08:02:57AM -0500, [EMAIL PROTECTED] wrote: >[snip exim config changes that I know nothing about] > But now I have a problem with mutt. When ever I try to send a message from > within mutt, I get: > > 'Error sending message, child exited 127 ().' > > And the message is n

More problems w/ EXIM upgrade

1999-06-30 Thread vandeveb
I upgraded to the new exim 3.02 and got bitten with the IPV6 problem. So I think I fixed that part. Next I had a config file problem. Whenever I did this: exim -bm -t < message I got this: 1999-06-30 07:53:53 10zJs9-0005ZU-00 Expansion of "Received: ${if def:sender_rcvhost {from ${sender_rcv