1 |
Starting on July 26, my email client started displaying a number |
2 |
of messages lacking subject lines. The messages were all cronjob |
3 |
outputs. |
4 |
|
5 |
Here's a sample: |
6 |
|
7 |
From relson@×××××××××××××××××××.com Mon Jul 27 00:15:02 2009 |
8 |
Return-Path: <relson@×××××××××××××××××××.com> |
9 |
X-Original-To: root@×××××××××××××.com |
10 |
Delivered-To: root@×××××××××××××.com |
11 |
Received: from osage (osage.osagesoftware.com [192.168.1.10]) |
12 |
by mail.osagesoftware.com (Postfix) with SMTP id AC1C27BC85 |
13 |
for <root@×××××××××××××.com>; Mon, 27 Jul 2009 00:15:01 |
14 |
-0400 (EDT) Received: by osage (sSMTP sendmail emulation); Mon, 27 |
15 |
Jul 2009 00:13:02 -0400 From: is an optional port number that |
16 |
defaults to 25. Message-Id: |
17 |
<20090727041501.AC1C27BC85@××××××××××××××××××.com> Date: Mon, 27 |
18 |
Jul 2009 00:15:01 -0400 (EDT) To: undisclosed-recipients:; |
19 |
|
20 |
Date: Mon, 27 Jul 2009 00:13:02 -0400 |
21 |
To: root@×××××××××××××.com |
22 |
Subject: Cron <relson@osage> /home/relson/bogofilter/mail/n2o |
23 |
X-Cron-Env: <SHELL=/bin/bash> |
24 |
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin> |
25 |
X-Cron-Env: <MAILTO=root@×××××××××××××.com> |
26 |
X-Cron-Env: <HOME=/> |
27 |
X-Cron-Env: <LOGNAME=relson> |
28 |
X-Cron-Env: <USER=relson> |
29 |
|
30 |
...[snip]... |
31 |
|
32 |
The peculiar bits of this message are the lines |
33 |
|
34 |
From: is an optional port number that defaults to 25. |
35 |
|
36 |
and |
37 |
|
38 |
To: undisclosed-recipients:; |
39 |
|
40 |
What the heck is the "optional port number message" and why is there a |
41 |
second "To:" line (with the first one being bogus). |
42 |
|
43 |
The blank line after the "To: undisclosed-recipients:;" line is also |
44 |
strange, as a blank line is the separator between the message header |
45 |
and the message body. This presence of this blank line causes a mail |
46 |
client to ignore the "To: root..." and "Subject: " header lines. |
47 |
|
48 |
Checking /var/log/portage, I noticed that mail-mta:ssmtp-2.62-r4 was |
49 |
upgraded to 2.62-r6 shortly before the messages started. After |
50 |
downgrading back to r4, the problem went away. |
51 |
|
52 |
Anybody familiar with this problem and know the cause and what to do |
53 |
about it? |