Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-98

Mailet NotifySender has several problems with the headers it generates

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Resolution: Fixed
    • 2.1
    • None
    • None
    • Operating System: Solaris
      Platform: Sun
    • 18307

    Description

      I'm using James 2.1.2, Solaris 9 and it's all working well, but I have a few
      grumbles about the header
      of a messages produced by NotifySender:

      Date: Mon, 24 Mar 2003 17:15:43 +0000 (GMT)
      From: postmaster@amserve.com
      To: postmaster@amserve.com
      Subject: Re:SMTP Monitor Test Message
      In-Reply-To: null
      Mime-Version: 1.0
      Content-Type: multipart/mixed;
      boundary="----=_Part_2_9800697.1048526143712"

      There are some problems with this header:

      1) The address in the To: line is the postmaster's address, not the
      recipient's address. However, the notify message is correctly
      delivered to the recipient.

      2) Arguably this isn't a reply, but a notification, so "Re:" should
      not have been added to the subject. But even if "Re:" were to
      be added it should have a space after the colon "Re: ".

      3) The In-Reply-To: line is syntactically invalid according to
      RFC2822 - "null" isn't a message-id. (Even if it were valid
      it's certainly not what was intended).

      4) Finally a wish: please can we have RFC1894 format notification
      messages?

      Here is the relevant part of my config.xml

      <mailet match="All" class="NotifySender">
      <notice>
      We were unable to deliver the attached message
      </notice>

      <passThrough>false</passThrough>
      </mailet>

      Attachments

        Activity

          People

            Unassigned Unassigned
            paulo@turnpike.com Paul Overell
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: