Starting on July 26, my email client started displaying a number
of messages lacking subject lines.  The messages were all cronjob
outputs.

Here's a sample:

    From rel...@osage.osagesoftware.com  Mon Jul 27 00:15:02 2009
    Return-Path: <rel...@osage.osagesoftware.com>
    X-Original-To: r...@osagesoftware.com
    Delivered-To: r...@osagesoftware.com
    Received: from osage (osage.osagesoftware.com [192.168.1.10])
            by mail.osagesoftware.com (Postfix) with SMTP id AC1C27BC85
            for <r...@osagesoftware.com>; Mon, 27 Jul 2009 00:15:01
    -0400 (EDT) Received: by osage (sSMTP sendmail emulation); Mon, 27
    Jul 2009 00:13:02 -0400 From: is an optional port number that
    defaults to 25. Message-Id:
    <20090727041501.ac1c27b...@mail.osagesoftware.com> Date: Mon, 27
    Jul 2009 00:15:01 -0400 (EDT) To: undisclosed-recipients:;

    Date: Mon, 27 Jul 2009 00:13:02 -0400
    To: r...@osagesoftware.com
    Subject: Cron <rel...@osage> /home/relson/bogofilter/mail/n2o
    X-Cron-Env: <SHELL=/bin/bash>
    X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
    X-Cron-Env: <mailto=r...@osagesoftware.com>
    X-Cron-Env: <HOME=/>
    X-Cron-Env: <LOGNAME=relson>
    X-Cron-Env: <USER=relson>

    ...[snip]...

The peculiar bits of this message are the lines

    From: is an optional port number that defaults to 25.

and

    To: undisclosed-recipients:;

What the heck is the "optional port number message" and why is there a
second "To:" line (with the first one being bogus).

The blank line after the "To: undisclosed-recipients:;" line is also
strange, as a blank line is the separator between the message header
and the message body. This presence of this blank line causes a mail
client to ignore the "To: root..." and "Subject: " header lines.

Checking /var/log/portage, I noticed that mail-mta:ssmtp-2.62-r4 was
upgraded to 2.62-r6 shortly before the messages started.  After
downgrading back to r4, the problem went away.

Anybody familiar with this problem and know the cause and what to do
about it?

Reply via email to