[ 
http://issues.apache.org/jira/browse/JAMES-424?page=comments#action_12434868 ] 
            
Noel J. Bergman commented on JAMES-424:
---------------------------------------

> as you keep saying this is a problem in Javamail (and I could agree)

Keep it in context.  It is a problem with JavaMail because the content is 
invalid, and JavaMail requires valid content, sometimes resulting in "even 
more" invalid content.  Without JavaMail having problems, we could still 
transport such messages.

>  I would like to know where you would add the Received: header in the 
> following message:

--------------------------------
This is a test
Received: <a received header>
--------------------------------

I tested ecelerity, and received:

  550 5.6.0 Required headers not found (see RFC2822 section 3.6)

qmail, however, accepted it, and I received (so delivered by qmail and added to 
by JAMES):

---------------------------------------------
Return-Path: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-MessageIsInfected: false
Received: from minotaur.apache.org ([209.237.227.194])
          by mail.devtech.com (JAMES SMTP Server 2.3.0rc3) with SMTP ID 986
          for <[EMAIL PROTECTED]>;
          Thu, 14 Sep 2006 16:38:25 -0400 (EDT)
Date: Thu, 14 Sep 2006 16:38:25 -0400 (EDT)
From: [EMAIL PROTECTED]
Received: (qmail 95997 invoked by uid 1589); 14 Sep 2006 20:11:44 -0000
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 95992 invoked from network); 14 Sep 2006 20:11:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 14 Sep 2006 20:11:44 -0000
Received: (qmail 1843 invoked by uid 500); 14 Sep 2006 20:11:44 -0000
Delivered-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 1840 invoked by uid 99); 14 Sep 2006 20:11:44 -0000
X-ASF-Spam-Status: No, hits=9.2 required=10.0
        
tests=MISSING_FROM,MISSING_HB_SEP,MISSING_HEADERS,MISSING_SUBJECT,TO_CC_NONE
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from [66.112.202.2] (HELO devtech.com) (66.112.202.2)
    by apache.org (qpsmtpd/0.29) with SMTP; Thu, 14 Sep 2006 13:11:44 -0700
X-Virus-Checked: Checked by ClamAV on apache.org
this is a test
Received: a test header
---------------------------------------------

So qmail prepended headers to the message, but did not take the existing 
content and try to make a body out of it.

> Invalid DATA for Message shows up in Headers in mailstore
> ---------------------------------------------------------
>
>                 Key: JAMES-424
>                 URL: http://issues.apache.org/jira/browse/JAMES-424
>             Project: James
>          Issue Type: Bug
>          Components: MailStore & MailRepository, SMTPServer
>    Affects Versions: 2.2.0
>         Environment: WinXP
>            Reporter: Scott Carr
>
> If you open a connection to the server, and send in the following in the DATA 
> for the message:
> This is a test
> .
> Then the data shows up in the headers instead of after the headers like it 
> should.  Here is what I recieved in the message:
> Return-Path: <[EMAIL PROTECTED]>
> Received: from localhost ([127.0.0.1])
>           by QRGMAIN (JAMES SMTP Server 2.2.0) with SMTP ID 792
>           for <[EMAIL PROTECTED]>;
>           Thu, 6 Oct 2005 21:40:21 -0500 (CDT)
> this is a test
> Date: Thu, 6 Oct 2005 21:40:21 -0500 (CDT)
> From: [EMAIL PROTECTED]
> Delivered-To: [EMAIL PROTECTED]
> Content-Transfer-Encoding: 7bit
> Content-Type: text/plain; charset=us-ascii
> Mime-Version: 1.0
> Message-ID: <[EMAIL PROTECTED]>
> Notice where 'this is a test' appears in the message.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to