Stefan
Can you attach the full log file to see the stack trace..
asankha
stlecho wrote:
Asankha,
I've configured a Proxy and when I set an email to the configured email
address, I'm receving an error: "BaseUtils Charset encoding of transport
differs from that of the payload". When the message arrives at ESB, I've
noticed that charset="us-ascii" is used. How can this be changed to use the
same charset as defined in the XML request ?
C: RETR 1
S: +OK message follows
Delivered-To: [EMAIL PROTECTED]
Received: by 10.187.191.9 with SMTP id t9cs51430fap;
Wed, 27 Aug 2008 06:47:00 -0700 (PDT)
Received: by 10.103.16.14 with SMTP id t14mr4660708mui.130.1219844819921;
Wed, 27 Aug 2008 06:46:59 -0700 (PDT)
Return-Path: <[EMAIL PROTECTED]>
Received: from relay.belnot.home (178.31-246-81.adsl-static.isp.belgacom.be
[81.246.31.178])
by mx.google.com with ESMTP id
j2si40689442mue.4.2008.08.27.06.46.59;
Wed, 27 Aug 2008 06:46:59 -0700 (PDT)
Received-SPF: neutral (google.com: 81.246.31.178 is neither permitted nor
denied by best guess record for domain of [EMAIL PROTECTED])
client-ip=81.246.31.178;
Authentication-Results: mx.google.com; spf=neutral (google.com:
81.246.31.178 is neither permitted nor denied by best guess record for
domain of [EMAIL PROTECTED]) [EMAIL PROTECTED]
Received: from sanmail.fednot.be (unknown [192.168.17.7])
by relay.belnot.home (Postfix) with ESMTP id 53A611D42B41
for <[EMAIL PROTECTED]>; Wed, 27 Aug 2008 15:46:59 +0200 (CEST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: FW: Test
Date: Wed, 27 Aug 2008 15:46:58 +0200
Message-ID: <[EMAIL PROTECTED]>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Test
Thread-Index: AckISCDl5JGuwbSxTneBtjK8wewNswAAzMeg
From: "Stefan Lecho" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
<?xml version=3D'1.0' encoding=3D'utf-8'?>
<soapenv:Envelope
xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/";>
<soapenv:Body>
<findPerson xmlns=3D"urn://fsb.belgium.be/fphp/v3_0">
<query
xmlns=3D"urn://fsb.belgium.be/fphp/v3_0/query" version=3D"1.0">
<context version=3D"1.0">
<client
xmlns=3D"urn://fsb.belgium.be/fphp/v3_0/context">
=09
<nationalNumber>63080214114</nationalNumber>
=09
<enterpriseNumber>0477430931</enterpriseNumber>
<eid />
=09
<callerId>211011</callerId>
<language>fr</language>
</client>
<message
xmlns=3D"urn://fsb.belgium.be/fphp/v3_0/context">
=09
<messageId>FPHP-C5A86B63-C34A-428A-A425-8DE5AD791134</messageId>
=09
<correlationId>FPHP-C5A86B63-C34A-428A-A425-8DE5AD791134</correlationId>
</message>
<application
xmlns=3D"urn://fsb.belgium.be/fphp/v3_0/context">
=09
<application>enot-fphp</application>
</application>
</context>
<criteria version=3D"1.0">
<registers
xmlns=3D"urn://fsb.belgium.be/fphp/v3_0/searchcriteria">
<register>RN</register>
<register>RR</register>
</registers>
<searchByNumber
xmlns=3D"urn://fsb.belgium.be/fphp/v3_0/searchcriteria" version=3D"1.0">
=09
<number>60210401511</number>
</searchByNumber>
</criteria>
<filter version=3D"1.0">
<summary
xmlns=3D"urn://fsb.belgium.be/fphp/v3_0/searchfilter">true</summary>
<details
xmlns=3D"urn://fsb.belgium.be/fphp/v3_0/searchfilter">ALL</details>
<filterName
xmlns=3D"urn://fsb.belgium.be/fphp/v3_0/searchfilter">all</filterName>
</filter>
</query>
</findPerson>
</soapenv:Body>
</soapenv:Envelope>
.
2008-08-27 15:47:05,962 [-] [mailto-Worker-5] DEBUG MailTransportListener
Processing message as Content-Type : text/plain;
charset="us-ascii"
2008-08-27 15:47:06,071 [-] [mailto-Worker-5] ERROR BaseUtils Charset
encoding of transport differs from that of the payload
Regards, Stefan Lecho.
asankha wrote:
Stefan
Thanks for the supplied information. Would it be possible to provide some
example code/configuration ?
http://wso2.org/project/esb/java/1.7.1/docs/ESB_Samples.html#Sample256
Also see
http://wso2.org/project/esb/java/1.7.1/docs/ESB_Samples_Setup.html#mailsender
for some more information
asankha
Paul Fremantle-2 wrote:
Stefan
We do support incoming email via POP3. The system polls at set intervals
and formats the incoming email message as a standard Synapse
MessageContext. From there you could either write a Mediator to handle
the message (and call your Spring bean) or you could forward it via SOAP
to a system running WSF/Spring and access the Spring system that way.
For onbound email its easy, simply target the email at a smtp based URL
and it will be emailed on - provided you have set up the email transport
correctly with your SMTP server.
Paul
stlecho wrote:
Hi,
The earlier reported requirements are key points of a POC I'm currently
building. Could someone provide me with an answer, please ?
Regards, Stefan.
stlecho wrote:
Hi,
I have the following requirements to implement and I was wondering if
they
are supported by WSO2ESB.
-Poll a mailserver for incoming - i.e. newly received - messages on a
pre-defined interval and forward the messages to a Spring-based bean
that
can handle the documents attached to the mail.
-On an incoming request - mail, http, ... - create a mail message and
send
it to a specified email address.
Regards, Stefan Lecho.
_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
