Given that sendmail, these days, comes configured by default to already 
use procmail as the local delivery agent, try removing your .forward 
files, and see if it works.

On Fri, 11 Oct 2002, Tomki wrote:

> I have had a very similar problem, Odhiambo.
>    I've reported it here twice already, but nobody has been able to help me 
> find the problem.
> I encountered the same issue on my mailserver this morning, and incurred a 
> mail loop that sent about 3000 messages to postmaster@ my domain.
> The symptom that makes me think we're having the same problem: the exit 
> code '70'.
> Here is an excerpt from one of the double-bounce messages:
> 
> ------------------------message excerpt begin -----------------------
>     ----- The following addresses had permanent fatal errors -----
> "|IFS=' ' && exec /bin/procmail -f- || exit 75 #user"
>      (reason: Internal error)
>      (expanded from: <[EMAIL PROTECTED]>)
> "|IFS=' ' && exec /bin/procmail -f- || exit 75 #user"
>      (reason: Internal error)
>      (expanded from: <[EMAIL PROTECTED]>)
> 
>     ----- Transcript of session follows -----
> 554 5.3.0 Internal error
> procmail: Program failure (70) of "/usr/bin/spamc"
> procmail: Rescue of unfiltered data succeeded
> 554 5.3.0 Internal error
> Reporting-MTA: dns; lonestar.alink.net
> Received-From-MTA: DNS; spoon.sv-server1.alink.net
> Arrival-Date: Fri, 11 Oct 2002 07:30:11 -0700 (PDT)
> ---------------------------------message excerpt 
> end----------------------------
> 
> and here is the point that the failure occurred, as logged:
> Oct 11 07:30:14 lonestar sm-mta[37118]: g9BEUBUR037080: to="|IFS=' ' && 
> exec /bin/procmail -f- || exit 75 #user", ctladdr=<[EMAIL PROTECTED]> 
> (1024/1024), delay=00:00:03, xdelay=00:00:01, mailer=prog, pri=151360, 
> dsn=2.0.0, stat=Sent
> Oct 11 07:30:14 lonestar sm-mta[37123]: g9BEUBUR037081: to="|IFS=' ' && 
> exec /bin/procmail -f- || exit 75 #user", ctladdr=<[EMAIL PROTECTED]> 
> (1007/1007), delay=00:00:03, xdelay=00:00:02, mailer=prog, pri=121128, 
> dsn=2.0.0, stat=Sent
> Oct 11 07:30:14 lonestar spamc[37154]: connect() to spamd at 127.0.0.1 
> failed, retrying (1/3): Connection refused
> Oct 11 07:30:14 lonestar spamc[37157]: connect() to spamd at 127.0.0.1 
> failed, retrying (1/3): Connection refused
> 
> It appears that this failure sends an email to 
> [EMAIL PROTECTED]  which is actually an alias to 3 separate system 
> admins here, whose ending account targets are on the afflicted 
> server.  :-p  So the cycle continues, because each of THOSE emails ALSO 
> generate failure messages to postmaster..  so the cycle continues.
> "We don't die, we MULTIPLY!!"..  so I can fix that looping bit by taking 
> [EMAIL PROTECTED] into its own mailbox, but it still doesn't 
> tell me what the root problem is: spamd dies occassionally.  :-p
> 
> Does anyone have any ideas about this yet?
> I'm currently running SA 2.42 release, Sendmail 8.12.5.  Procmail 3.22
> 
> Thanks
> 
> --Tomki
> 
> 
> At 09:45 10/11/2002 +0300, Odhiambo Washington wrote:
> 
> 
> >I am trying to upgrade to 2.42, not for any any good reason than putting
> >a smile on the face of my Japanese/Korean clients since 2.31 really hates
> >their encoding.
> >
> >PROBLEM 1:
> >
> >When I install 2.31, I have these files in /usr/bin
> >
> >-r-xr-xr-x  1 root  wheel  18751 Oct  8 17:30 /usr/bin/spamassassin
> >-r-xr-xr-x  1 root  wheel  13372 Oct  8 17:30 /usr/bin/spamc
> >-r-xr-xr-x  1 root  wheel  27290 Oct  8 17:30 /usr/bin/spamd
> >-r-xr-xr-x  1 root  wheel  14723 Oct  8 17:30 /usr/bin/spamproxyd
> >
> >When I install 2.42 (by whichever means) I do not see spamproxyd in
> >the bin directory. Is there a good explanation for this? I believe
> >it was removed from the distro, yes? Do I still need it for smooth
> >operation?
> >
> >
> >
> >PROBLEM 2:
> >
> >Once I install 2.42 and start spamd, mail delivery failures begin.
> >A sample error I get is this:
> >
> >2002-10-11 09:29:55 17ztJ1-0000UO-00 ** [EMAIL PROTECTED] 
> ><[EMAIL PROTECTED]> R=procmail T=procmail_pipe: Child process
> >of procmail_pipe transport returned 70 (could mean internal software 
> >error) from command: /usr/local/bin/procmail
> >2002-10-11 09:29:56 7 args: /usr/local/sbin/exim -t -oem -oi -f <> 
> >-E17ztJ1-0000UO-00
> >2002-10-11 09:29:56 17ztIz-0000Rk-00 ** [EMAIL PROTECTED] 
> ><[EMAIL PROTECTED]> R=procmail
> >T=procmail_pipe: Child process of procmail_pipe transport returned 70 
> >(could mean internal software error) from command: /usr/local/bin/procmail
> >
> >
> >This does not happen with 2.31. Any pointers??
> >
> >
> >
> >
> >
> >-Wash
> >
> >--
> >Odhiambo Washington   <[EMAIL PROTECTED]>  "The box said 'Requires
> >Wananchi Online Ltd.  www.wananchi.com      Windows 95, NT, or better,'
> >Tel: +254 2 313985-9  +254 2 313922         so I installed FreeBSD."
> >GSM: +254 72 743223   +254 733 744121       This sig is McQ!  :-)
> >
> >
> >If you only have a hammer, you tend to see every problem as a nail.
> >                 -- Maslow
> >
> >
> >-------------------------------------------------------
> >This sf.net email is sponsored by:ThinkGeek
> >Welcome to geek heaven.
> >http://thinkgeek.com/sf
> >_______________________________________________
> >Spamassassin-talk mailing list
> >[EMAIL PROTECTED]
> >https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Spamassassin-talk mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
> 

-- 
Mike Burger
http://www.bubbanfriends.org

Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to