Mule
  1. Mule
  2. MULE-5699

In the bookstore example, the expected recipient doesn't receive email; the sender receives the email instead

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.2.x
    • Fix Version/s: 3.2.0
    • Component/s: Examples / Tutorials
    • Labels:
      None
    • User impact:
      High
    • Similar Issues:
      MULE-5073bookstore example email not working
      MULE-2266Remove ENDPOINT_TYPE_SENDER_AND_RECEIVER endpoint type.
      MULE-855Improve testing of email sending/receiving
      MULE-5426Mule example launcher: bookstore example missing instructions on how to set up email
      MULE-2755EMails received by POP3 connector that don't pass a subsequent filter, cause incorrect exception
      MULE-6177Bookstore example should run deployed in an app server with MMC
      MULE-546Receive/send SMTP flows from/to an MTA
      MULE-4184Bookstore admin example Get Stats return data as text/plain instead of text/html
      MULE-1782Dynamic creation of message receiver endpoints doesn't work
      MULE-5014bookstore example fails on 3.0-RC1

      Description

      Expected recipient doesn't receive the email. However, the sender receives a copy of the email sent. It appears that the "TO_ADDRESSES_PROPERTY" property used in the example doesn't work.

        Activity

        Hide
        Claude Mamo added a comment -

        One small note, the recipient does receive the email if I use the "to" attribute in the "smtp:outbound-endpoint" element

        Show
        Claude Mamo added a comment - One small note, the recipient does receive the email if I use the "to" attribute in the "smtp:outbound-endpoint" element
        Hide
        Dirk Olmes added a comment -

        We always advise against the use of RequestContext yet the OrderToEmailTransformer uses that hack to send the recipient of the email

        I assume that some message rewriting goes on and the message that gets the recipient set is not the message that finally arrives in the SmtpMessageDispatcher - at least I don't see a "to" Message property there.

        Show
        Dirk Olmes added a comment - We always advise against the use of RequestContext yet the OrderToEmailTransformer uses that hack to send the recipient of the email I assume that some message rewriting goes on and the message that gets the recipient set is not the message that finally arrives in the SmtpMessageDispatcher - at least I don't see a "to" Message property there.
        Show
        Dirk Olmes added a comment - http://fisheye.codehaus.org/changelog/mule/?cs=22714

          People

          • Assignee:
            Dirk Olmes
            Reporter:
            Claude Mamo
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development