>Number:         3304
>Category:       other
>Synopsis:       bugdb is producing emails with mal-formed headers
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Oct 28 05:30:00 PST 1998
>Last-Modified:
>Originator:     [EMAIL PROTECTED]
>Organization:
apache
>Release:        
>Environment:
any
>Description:

I'm reading some apache mailing lists from a read-only mail-to-news
gateway, and it is showing up a persistent problem with qmail in the
bugdb list. The mail-to-news software tries to post a message with
headers like this:

Subject: blah blah blah
Sender: [EMAIL PROTECTED]
X-Send-Pr-Version: 3.2
To: [EMAIL PROTECTED]
From: someone
X-Original-Date: 28 Oct 1998 08:41:28 -0000
X-Original-Message-Id: <[EMAIL PROTECTED]>
Return-path: <[EMAIL PROTECTED]>
X-Received: from taz.hyperreal.org (hyperreal.org) [209.133.83.16]
        by chiark.greenend.org.uk with smtp (Exim 2.02 #1)
        id 0zYRIy-0007fG-00 (Debian); Wed, 28 Oct 1998 08:50:12 +0000
X-Received: (qmail 5328 invoked by uid 6000); 28 Oct 1998 08:50:11 -0000
X-Received: (qmail 5098 invoked by uid 2001); 28 Oct 1998 08:50:00 -0000
X-Received:(qmail 2757 invoked by uid 2012); 28 Oct 1998 08:41:28 -0000
Reply-To: someone
Newsgroups: chiark.mail.apache.bugdb
Path: mail-to-news!not-for-mail
Date: Wed, 28 Oct 1998 09:32:01 GMT
Precedence: bulk
Message-ID: <[EMAIL PROTECTED]>

and the news server complains about the last X-Received: line not
having a space after the colon. 
>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]



Reply via email to