Re: More questions about trying to use mutt with ssmtp
On Mon, Feb 02, 2004 at 03:30:48PM +0000, Stewart V. Wright wrote:
> G'day Chris,
>
> * Chris Green <chris@xxxxxxxxxxx> [040202 15:23]:
> > OK, I've resolved the initial question of why mutt wasn't telling me
> > that I'd given it a non-existent program in 'set sendmail=xxxxx'.
> >
> > However having now fixed 'set sendmail=' so it's correct I'm still
> > getting "Error sending message, child exited 127 (Exec error.).".
> >
> > Now I guess this is because ssmtp is failing for some reason, I can
> > call it from the command line though and it does do vaguely sensible
> > things when I do that. How can I get more feedback from mutt/ssmtp to
> > try and see what's wrong?
>
> I know this isn't answering your question, but don't set your sendmail
> variable, then in mutt type:
> set ?sendmail
> to find out what flags are being passed to sendmail by default. Use
> these for ssmtp.
>
> For example I use
> set sendmail="${HOME}/bin/linux/ssmtp -oem -oi"
>
> Yeah, I know it ain't science, and it sure as hell doesn't teach you
> what's going on, but for me life is too short. :)
>
I finally read this properly and realised what you meant. Yes, my mutt
has the same defaults for sendmail. However the -oem and -oi options
are explicitly listed in the ssmtp man page as doing nothing or being
the default so adding them is going to make no difference.
Anyway, as I said, nbsmtp seems to be working for me and if some
further checking confirms this I'm sorted at last.
--
Chris Green (chris@xxxxxxxxxxx)