On Sun, Oct 19, 2003 at 09:07:22PM -0500, Butch Evans wrote:
> I wanted to see exactly what was being piped to sendmail to see what
> was causing it to fail.  Nothing ends up in the logfile that I can
> see.  I added an entry to the log file in the above program at the
> beginning and end to see if it was really being called executed, and
> still nothing.  I set the trapmail.pl to "chmod 777 trapmail.pl"
> once just to see if it was permissions.  The /var/log/trapmail.log
> is set with world read/write permissions.
> 
> >So: are you using a homebuild dbmail ? If you're using the debian
> >version dbmail-smtp is running suid dbmail. Is your trapmail script
> >accessible for that user ? And the logfile ?
> 
> dbmail (v1.2 now) was compiled with build.sh.  I am running FreeBSD
> 4.5-STABLE.  Everything else seems to run fine.  I am just not sure
> where to start.  The documentation seems pretty much non-existant,
> or I am looking in the wrong places.
> 
> >If you're using debian it may be that dbmail-smtp is having trouble
> >accessing /usr/sbin/sendmail since it's running suid dbmail.
> 
> I thought of that.  That is why I set my "test" trapmail.pl to world
> read/write/execute just to test it.  Perhaps I am missing something
> else.  Is there more information I can provide that would be
> helpful?

Try applying this patch, and then check the error log to see if you can
glean anymore information as to why sendmail is failing.

xn
Index: pipe.c
===================================================================
RCS file: /cvsroot-dbmail/dbmail/pipe.c,v
retrieving revision 1.95
diff -u -w -r1.95 pipe.c
--- pipe.c      2003/03/17 16:04:08     1.95
+++ pipe.c      2003/10/20 02:41:17
@@ -675,7 +675,7 @@
   result = pclose(mailpipe);
   trace(TRACE_DEBUG, "send_reply(): pipe closed");
   if (result != 0)
-    trace(TRACE_ERROR,"send_reply(): reply could not be sent: sendmail error");
+    trace(TRACE_ERROR,"send_reply(): reply could not be sent: error executing 
%s [%s]", sendmail, strerror(errno));
 
   return 0;
 }

Reply via email to