[fetchmail]Re: socket error

[Rob MacGregor]

On 10/07/05, mbox mbarsalou <barjunk@attglobal.net> wrote:
>=20
> Rob, I'm going to take you up on your offer. Spamstop is there just to
> report the error that might be returned from sendmail. It appears that
> sendmail is not returning any error during the process.  Interestingly,
> it takes exactly two minutes for the socket error to occur after it
> starts retrieving the offending message.  If that helps any.
>=20
> I appreciate the time you are spending on this...this problem has been
> bothering me for some time.
>=20
> Although the probability that it is actually a fetchmail issue is very
> low, I'm having a heck of a time getting to the real problem.

I'd put money on it being an issue with your script.  I'd have to ask
why you're using it - what are you expecting it to give you that the
SMTP error codes wouldn't?
=20
> Thanks.
>=20
> Here is the relevent fetchmailrc from fetchmail 6.2.5:
>=20
> set logfile fetchmail.log
> set no spambounce
> server pop4.attglobal.net:
>         proto pop3;
>         user barjunk there password "*****" is barsalou here;
> antispam 451 flush
> mda "~/spamstop  -i -f %F %T"

Looks reasonable.

> Spamstop looks like this:
> #!/bin/sh
> /usr/sbin/sendmail $@
> a=3D$?
> echo "spamstop: Error returned - $a"
> if [ $a =3D 65 ] ; then
>   exit 0
> fi
> if [ $a =3D 64 ] ; then
>   exit 0
> fi
> if [ $a =3D 451 ] ; then
>   exit 0
> fi
>=20
> exit $a

At a rough guess, fetchmail is passing the mail to stdin, but your
script isn't using that.  You may need to prefix the line calling
sendmail with "cat |".

--=20
                 Please keep list traffic on the list.
Rob MacGregor
      Whoever fights monsters should see to it that in the process he=20
        doesn't become a monster.                  Friedrich Nietzsche