putbody: write error: Broken pipe

[Butch Kemper]

I need some help to determine what is causing this error:

Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: SYSERR(root):
putbody: write error: Broken pipe
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: 0: fl=0x0, mode=
20666: CHR: dev=3/1, ino=60251, nlink=1, u/gid=0/0, size=0
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: 1: fl=0x1, mode=
20666: CHR: dev=3/1, ino=60251, nlink=1, u/gid=0/0, size=0
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: 2: fl=0x1, mode=
20666: CHR: dev=3/1, ino=60251, nlink=1, u/gid=0/0, size=0
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: 3: fl=0x2, mode=
140777: SOCK localhost->[[UNIX: /dev/log]]
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: 5: fl=0x0, mode=
100600: dev=3/6, ino=356945, nlink=1, u/gid=0/105, size=1724
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: 6: fl=0x8000, mode=
100644: dev=3/5, ino=94092, nlink=1, u/gid=1980/50, size=45056
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: 7: fl=0x8000, mode=
100640: dev=3/1, ino=24483, nlink=1, u/gid=0/105, size=12288
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: 8: fl=0x1, mode=
100600: dev=3/6, ino=2310157, nlink=1, u/gid=0/105, size=1178
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: 9: fl=0x1, mode=
10600: FIFO: dev=0/7, ino=230778035, nlink=1, u/gid=0/105, size=0
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: 10: fl=0x0, mode=
10600: FIFO: dev=0/7, ino=230778036, nlink=1, u/gid=0/105, size=0
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: MCI@0x0: NULL
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: MCI@0x0: NULL
Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: to="| cat /dev/null",
ctladdr=<tra...@tbcprint.com> (1/0), delay=00:00:05, xdelay=00:00:00,
mailer=prog, pri=32585, dsn=2.0.0, stat=Sent

Thanks.

Butch

[Hugo Villeneuve]

Butch Kemper <kem...@tstar.net> wrote:

> I need some help to determine what is causing this error:
>
> Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: SYSERR(root):

...

> Feb 13 20:02:03 mail sm-mta[16758]: m1E21s3g016577: to="| cat /dev/null",
> ctladdr=<tra...@tbcprint.com> (1/0), delay=00:00:05, xdelay=00:00:00,
> mailer=prog, pri=32585, dsn=2.0.0, stat=Sent
>

to="| cat /dev/null"

this seems very wrong. "cat /dev/null" ends immediatly and sendmail ends
up trying to write to a already ended program (and a closed pipe).

I don't know what you want to acheive (maybe ">" was ignored), but
usually you can write directly "/dev/null" as an alias destination in
/etc/mail/aliases.

I'm not sure about a .forward though.

> Thanks.
>
> Butch

[Butch Kemper]

hu...@EINTR.net (Hugo Villeneuve) wrote in
news:1ica36q.14fuyto1uit1e4N%hu...@EINTR.net:

Thank you for spotting the error.

The alias destination was missing a ">". The correct alias destination
is "| cat > /dev/null". Making that change eliminated the errors.

Butch

[Kari Hurtta]

Butch Kemper <kem...@tstar.net> writes in comp.mail.sendmail:

> > to="| cat /dev/null"
> >
> > this seems very wrong. "cat /dev/null" ends immediatly and sendmail
> > ends up trying to write to a already ended program (and a closed
> > pipe).
> >
> > I don't know what you want to acheive (maybe ">" was ignored), but
> > usually you can write directly "/dev/null" as an alias destination in
> > /etc/mail/aliases.
> >
> > I'm not sure about a .forward though.
>
> Thank you for spotting the error.
>
> The alias destination was missing a ">". The correct alias destination
> is "| cat > /dev/null". Making that change eliminated the errors.
>
> Butch

I think that you can point alias to /dev/null without pipe and cat
also.

( And I think that sendmail actually even does not write to /dev/null
--- this is lot cheaper ... )

/ Kari Hurtta

deliver.c:

/*
** Special case /dev/null. This allows us to restrict file
** delivery to regular files only.
*/

if (sm_path_isdevnull(filename))
return EX_OK;