synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SYNAPSE-446) Multipart/mixed mail message not forwarded to proxy
Date Mon, 15 Sep 2008 17:43:44 GMT

    [ https://issues.apache.org/jira/browse/SYNAPSE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631080#action_12631080
] 

Andreas Veithen commented on SYNAPSE-446:
-----------------------------------------

I think the problem is totally unrelated to the content type of the message. The real explanation
can be seen from the following lines in the logs:

MailTransportSender Setting From header to credoc.out@posthouse.com from OutTransportInfo
MailTransportSender Setting To header to credoc.in@posthouse.com from transport headers
MailTransportSender Setting Subject header to 'WSO2ESB - The subject of the mail - without
an attachment !' from transport headers

To determine the recipient of the message, MailTransportSender gives precedence to the transport
headers and only if there are no transport headers it will check the OutTransportInfo (which
contains the address you specify as target of the proxy service). Why does the message context
contain transport headers? Because the message initially came in as a mail (BTW, that's why
you see a difference between mail and HTTP). Instead of sending the message to bank.in@posthouse.com,
the transport sends the message to the original recipient, i.e. credoc.in@posthouse.com.

Why does the sender give precedence to the transport headers to determine the recipient? I
don't know. Note that for the From and CC addresses, it's the other way round: the sender
firsts looks at OutTransportInfo. Maybe somebody else knows why this was implemented in this
way?

As a workaround you can try to clear the transport headers before sending the message out.

> Multipart/mixed mail message not forwarded to proxy
> ---------------------------------------------------
>
>                 Key: SYNAPSE-446
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-446
>             Project: Synapse
>          Issue Type: Bug
>            Reporter: Stefan Lecho
>         Attachments: log.txt
>
>
> https://wso2.org/jira/browse/ESBJAVA-566

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message