Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 13933 invoked from network); 20 Jan 2006 17:56:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Jan 2006 17:56:25 -0000 Received: (qmail 3162 invoked by uid 500); 20 Jan 2006 17:56:23 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 2936 invoked by uid 500); 20 Jan 2006 17:56:22 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 2925 invoked by uid 99); 20 Jan 2006 17:56:22 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2006 09:56:22 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [195.41.45.119] (HELO mail.eos.dk) (195.41.45.119) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 20 Jan 2006 09:56:21 -0800 Received: (qmail 18487 invoked by uid 510); 20 Jan 2006 17:55:58 -0000 Received: from jrf@trifork.com by mail.eos.dk by uid 508 with qmail-scanner-1.20st (clamuko: 0.66. spamassassin: 3.0.4. Clear:RC:0(85.81.68.95):. Processed in 0.071259 secs); 20 Jan 2006 17:55:58 -0000 Received: from 0x5551445f.adsl.cybercity.dk (HELO ?10.0.0.5?) (jrf@trifork.com@85.81.68.95) by mail.eos.dk with SMTP; 20 Jan 2006 17:55:58 -0000 Message-ID: <43D12421.5090107@trifork.com> Date: Fri, 20 Jan 2006 18:55:45 +0100 From: =?ISO-8859-1?Q?=22Jakob_F=E6rch_=28Trifork=29=22?= User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: user@geronimo.apache.org Subject: Re: javamail References: <43CD2359.90701@dekasoft.com.ua> <43CD3002.6000706@dekasoft.com.ua> <43CDF96B.3070502@dekasoft.com.ua> <43CE676F.5040106@dekasoft.com.ua> <43D0B4A2.3040504@trifork.com> <43D0C08A.50209@dekasoft.com.ua> <43D0C414.1030401@trifork.com> <43D0C85D.5010007@dekasoft.com.ua> <43D0CA67.1020701@dekasoft.com.ua> In-Reply-To: <43D0CA67.1020701@dekasoft.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Alex Andrushchak wrote: > Ok, i've moved from dead point :-) > Wonderful! > Now i have another problem: > Cannot send the message with MailerBean:java.lang.Exception: The message > can not be send : Unable to locate provider for protocol: smtp The transport for smtp is located in the file geronimo-1.0\repository\geronimo\jars\geronimo-javamail-transport-1.0.jar. By some odd mistake, it is not included in the tomcat distribution. If you are using a jetty distribution, the jar file should be there all right in GERONIMO_INSTALL_DIR/repository/geronimo/jars. If you are on a tomcat distribution, I _guess_ you would be fine downloading the jetty distribution and manually copying the jar file from the above directory in the jetty distribution to the same directory in the tomcat distribution - anyone: feel free to correct me on this! In order to make the smtp transport available to your application, you need to add the following dependency to the application's plan: geronimo geronimo-javamail-transport 1.0 > My application configuration is: > class="org.apache.geronimo.mail.SMTPTransportGBean"> > 192.168.1.2 > 25 > name="from">queryphone-geronimo@dekasoft.com.ua > > class="org.apache.geronimo.mail.MailGBean"> > smtp > true > mail.debug=true > > protocol.smtp > > It's not (yet) entirely well documented how to set up the necessary GBeans - to say the least. It seems in the AdventureBuilder (which is able to send mail using the smtp transport and javamail), the following GBean is sufficient: ${smtpHost} mail.from=${smtpFrom} mail.smtp.port=${smtpPort} Note that compared to you configuration, the smtp host and port is on the MailGBean, not the SMTPTransportGBean. I guess things will work with the SMTPTransportGBean configured alongside the MailGBean, but my experience was that the SMTPTransportGBean was not necessary - anyone: correct me on this! Alex, I hope this helps you; please keep the list updated on your progress. Jakob