Madhur K Tanwani writes:
> Hi,=20
> I'm using maildrop 1.6.3 on Linux (kernel 2.6.11-1.1369_FC4).=20
> Recently I switched to using a script for delivery of my messages.The=20
> filter rules file is attached with this mail. However, I've been gettin=
g=20
> the following log file trace since then.=C2=A0 The values of the variab=
les and=20
> fields printed in the log message are all correct.The log message is=20
> something like :
>=20
>=20
> Starting Maildrop Delivery
> LFROM =3D <sone from addr>
> mail sent to =3D <sone to addr>
> LOGNAME =3D<sone non-root username>
> recipient =3D
> hostname =3D <some hostname>
> Starting delivery_script
> Date: Thu Feb 16 15:59:07 2006
> From: <some from address>
> Subj: This Week at HSN
> !Err: | /var/qmail/delivery_scripts/delivery_script.sh=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=20
> (66613)
> =20
> I've double-checked the script and nothingseems to be wrong there. I ev=
en=20
> replaced the script's content with a simple "echo" and then "exit" with=20
> proper codes but the log message is the same.
That's because your script did not read the entire message from=20
standard input before terminating.
If maildrop detects that the external delivery program terminated before =
it=20
read the entire message, it interprets it as a crash, and a temporary=20
delivery failure.
|