Perfect thx for the feedback. Bye Norman
2010/5/28, Eric Charles <[email protected]>: > Just for info, everything works now. > Tks, > Eric > > On 05/27/2010 09:21 PM, Eric Charles wrote: >> Now working with 2 RemoteDelivery processors and MX changed for users >> migration. >> Hopefully will confirm tomorrow that everything is running as expected. >> >> Tks, >> >> Eric >> >> >> On 05/27/2010 08:56 PM, Norman Maurer wrote: >>> Hopefully fixed. There were a problem with multiple instances of the >>> mailet. Bye, >>> Norman >>> >>> 2010/5/27 Eric Charles<[email protected]>: >>>> I need to define different processors, each having >>>> <mailet match="All" class="ActiveMQRemoteDelivery"> with >>>> different<gateway> >>>> values. >>>> >>>> Whatever the values I define for<outgoingQueue> >>>> and<outgoingRetryQueue>, >>>> I've got: >>>> Caused by: org.apache.camel.FailedToStartRouteException: Failed to >>>> start >>>> route route5 because of Multiple consumers for the same endpoint is not >>>> allowed: Endpoint[direct://outgoingQueueInjectorEndpoint] >>>> >>>> Seems AbstractRemoteDelivery doesn't take into account >>>> the<outgoingQueue> >>>> and<outgoingRetryQueue> values and uses a fixed >>>> outgoingQueueInjectorEndpoint String. >>>> >>>> Finally, I will eat my piece of cake a bit later. >>>> >>>> Tks in advance, >>>> >>>> Eric >>>> >>>> >>>> On 05/27/2010 07:30 PM, Eric Charles wrote: >>>>> Hi Norman, >>>>> Just tested: works fine. Tks a lot for your patches. >>>>> I will now configure the servers-per-domains with the RegExp >>>>> matcher and >>>>> RemoteDelivery processor. >>>>> Should be piece-of-cake. >>>>> >>>>> Tks again, >>>>> >>>>> Eric >>>>> >>>>> >>>>> On 05/27/2010 08:19 AM, Norman Maurer wrote: >>>>>> Hi Eric, >>>>>> >>>>>> I just fixed this. Sorry for the trouble. >>>>>> >>>>>> Bye, >>>>>> Norman >>>>>> >>>>>> >>>>>> 2010/5/26 Eric Charles<[email protected]>: >>>>>>> Hi, >>>>>>> >>>>>>> I just updated to revision 948330 with the AbstractRemoteDelivery >>>>>>> patch. >>>>>>> Mails are now forwarded, but without title, body nor header (see >>>>>>> hereafter >>>>>>> 1.Direct and 2.ViaJames from wireshark). >>>>>>> Maybe the camel configuration needs some modifications. >>>>>>> >>>>>>> Tks, >>>>>>> >>>>>>> Eric >>>>>>> >>>>>>> 1. DIRECT TO RELAY >>>>>>> 220 relay.skynet.be ESMTP >>>>>>> EHLO [192.168.1.11] >>>>>>> 250-relay.skynet.be >>>>>>> 250-8BITMIME >>>>>>> 250 SIZE 16777216 >>>>>>> MAIL FROM:<[email protected]> SIZEA1 >>>>>>> 250 sender<[email protected]> ok >>>>>>> RCPT TO:<[email protected]> >>>>>>> 250 >>>>>>> recipient<eric.charlesReturn-Path:<server-user-return-18554-eric.charles=u-mangate....@james.apache.org> >>>>>>> >>>>>>> >>> Message-ID:<1888223278.594.1274986641107.javamail.r...@srv001> >>> MIME-Version: 1.0 >>> Received: from hermes.apache.org ([140.211.11.3]) >>> by 172.16.1.131 (JAMES SMTP Server ) with SMTP ID 572 >>> for<[email protected]>; >>> Thu, 27 May 2010 20:57:19 +0200 (CEST) >>> Received: (qmail 42168 invoked by uid 500); 27 May 2010 18:57:18 -0000 >>> Mailing-List: contact [email protected]; run by ezmlm >>> Precedence: bulk >>> List-Unsubscribe:<mailto:[email protected]> >>> List-Help:<mailto:[email protected]> >>> List-Post:<mailto:[email protected]> >>> List-Id: "James Users List"<server-user.james.apache.org> >>> Reply-To: "James Users List"<[email protected]> >>> Delivered-To: mailing list [email protected] >>> Received: (qmail 42160 invoked by uid 99); 27 May 2010 18:57:18 -0000 >>> Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) >>> by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 May 2010 >>> 18:57:18 +0000 >>> X-ASF-Spam-Status: No, hits=0.0 required=10.0 >>> tests=FREEMAIL_FROM,SPF_PASS >>> X-Spam-Check-By: apache.org >>> Received-SPF: pass (nike.apache.org: domain of >>> [email protected] designates 74.125.82.49 as permitted >>> sender) >>> Received: from [74.125.82.49] (HELO mail-ww0-f49.google.com) >>> (74.125.82.49) >>> by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 May 2010 >>> 18:57:12 +0000 >>> Received: by wwc33 with SMTP id 33so240701wwc.22 >>> for<[email protected]>; Thu, 27 May 2010 11:56:52 >>> -0700 (PDT) >>> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; >>> d=googlemail.com; s=gamma; >>> h=domainkey-signature:mime-version:received:sender:received >>> >>> :in-reply-to:references:date:x-google-sender-auth:message-id:subject >>> :from:to:content-type:content-transfer-encoding; >>> bh=MGU3qYyzBgYxO/ajYutqNp5e6p0bM+hMlUyPEXTUAp0=; >>> >>> b=AwiDxDNSvqWiva5i5nuq/vSoAKZ+PBmnSrsMao3E2Tpag//yUBL8YIWIBSb4vxIN2h >>> >>> OUChE75AzCZf9fMqb+/1Ehagf7pvrhXUkHn2Io6oYOULkgeJXDkE+kxbh/y6XzHUyv8x >>> e4XF5RRb7E+8rHzg7b+6uG4QIbrOKHcxguiLk= >>> DomainKey-Signature: a=rsa-sha1; c=nofws; >>> d=googlemail.com; s=gamma; >>> h=mime-version:sender:in-reply-to:references:date >>> :x-google-sender-auth:message-id:subject:from:to:content-type >>> :content-transfer-encoding; >>> >>> b=q8ODFsqMYDDU7Xvfz8GvRtUfgtenewwSHBGQ43NU5g9RKFSjvinFT/akV/CTF15A18 >>> >>> yIOcd1HNIUuDTRKkVlZV+tBlWxRVvR12iO9EAolL/mSThVJ8L+Lurfawc5u9ztY4F/Bt >>> kpdQE4IEZgeh9Qg5q1+EepsA1vWJbP/91phyc= >>> Received: by 10.216.91.81 with SMTP id >>> g59mr932267wef.83.1274986612368; Thu, >>> 27 May 2010 11:56:52 -0700 (PDT) >>> Sender: [email protected] >>> Received: by 10.216.2.79 with HTTP; Thu, 27 May 2010 11:56:52 -0700 >>> (PDT) >>> In-Reply-To:<[email protected]> >>> References:<[email protected]> >>> <1356642928.20259.1274374117178.javamail.r...@srv001> >>> <1910152324.41.1274699708952.javamail.r...@srv001> >>> <2133247665.127.1274700617642.javamail.r...@srv001> >>> <[email protected]> >>> <889802249.25495.1274941179334.javamail.r...@srv001> >>> <534159043.33021.1274981453842.javamail.r...@srv001> >>> <[email protected]> >>> Date: Thu, 27 May 2010 20:56:52 +0200 >>> X-Google-Sender-Auth: Hj39HITUnV9MXyplKSU_pH0EkfI >>> Subject: Re: Server Mail Forward/RestrictedRelay >>> From: Norman Maurer<[email protected]> >>> To: James Users List<[email protected]> >>> Content-Type: text/plain; charset=ISO-8859-1 >>> Content-Transfer-Encoding: quoted-printable >>> X-Virus-Checked: Checked by ClamAV on apache.org >>> >>> Hopefully fixed. There were a problem with multiple instances of the >>> mailet. >>> >>> Bye, >>> Norman >>> >>> 2010/5/27 Eric Charles<[email protected]>: >>>> I need to define different processors, each having >>>> <mailet match="All" class="ActiveMQRemoteDelivery"> with >>>> different<gateway> >>>> values. >>>> >>>> Whatever the values I define for<outgoingQueue> >>>> and<outgoingRetryQueue>, >>>> I've got: >>>> Caused by: org.apache.camel.FailedToStartRouteException: Failed to >>>> start >>>> route route5 because of Multiple consumers for the same endpoint is not >>>> allowed: Endpoint[direct://outgoingQueueInjectorEndpoint] >>>> >>>> Seems AbstractRemoteDelivery doesn't take into account >>>> the<outgoingQueue> >>>> and<outgoingRetryQueue> values and uses a fixed >>>> outgoingQueueInjectorEndpoint String. >>>> >>>> Finally, I will eat my piece of cake a bit later. >>>> >>>> Tks in advance, >>>> >>>> Eric >>>> >>>> >>>> On 05/27/2010 07:30 PM, Eric Charles wrote: >>>>> Hi Norman, >>>>> Just tested: works fine. Tks a lot for your patches. >>>>> I will now configure the servers-per-domains with the RegExp >>>>> matcher and >>>>> RemoteDelivery processor. >>>>> Should be piece-of-cake. >>>>> >>>>> Tks again, >>>>> >>>>> Eric >>>>> >>>>> >>>>> On 05/27/2010 08:19 AM, Norman Maurer wrote: >>>>>> Hi Eric, >>>>>> >>>>>> I just fixed this. Sorry for the trouble. >>>>>> >>>>>> Bye, >>>>>> Norman >>>>>> >>>>>> >>>>>> 2010/5/26 Eric Charles<[email protected]>: >>>>>>> Hi, >>>>>>> >>>>>>> I just updated to revision 948330 with the AbstractRemoteDelivery >>>>>>> patch. >>>>>>> Mails are now forwarded, but without title, body nor header (see >>>>>>> hereafter >>>>>>> 1.Direct and 2.ViaJames from wireshark). >>>>>>> Maybe the camel configuration needs some modifications. >>>>>>> >>>>>>> Tks, >>>>>>> >>>>>>> Eric >>>>>>> >>>>>>> 1. DIRECT TO RELAY >>>>>>> 220 relay.skynet.be ESMTP >>>>>>> EHLO [192.168.1.11] >>>>>>> 250-relay.skynet.be >>>>>>> 250-8BITMIME >>>>>>> 250 SIZE 16777216 >>>>>>> MAIL FROM:<[email protected]> SIZEA1 >>>>>>> 250 sender<[email protected]> ok >>>>>>> RCPT TO:<[email protected]> >>>>>>> 250 recipient<[email protected]> ok >>>>>>> DATA >>>>>>> 354 go ahead >>>>>>> Message-ID:<[email protected]> >>>>>>> Date: Wed, 26 May 2010 17:57:10 +0200 >>>>>>> From: Eric Charles<[email protected]> >>>>>>> User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) >>>>>>> Gecko/20100322 Thunderbird/3.0.3 >>>>>>> MIME-Version: 1.0 >>>>>>> To: [email protected] >>>>>>> Subject: mail_title >>>>>>> Content-Type: text/plain; charset=O-8859-1; format=flowed >>>>>>> Content-Transfer-Encoding: 7bit >>>>>>> >>>>>>> mail_body >>>>>>> . >>>>>>> 250 ok: Message 681392225 accepted >>>>>>> QUIT >>>>>>> 221 relay.skynet.be >>>>>>> >>>>>>> >>>>>>> 2. TO RELAY VIA JAMES >>>>>>> 220 relay.skynet.be ESMTP >>>>>>> EHLO 127.0.1.1 >>>>>>> 250-relay.skynet.be >>>>>>> 250-8BITMIME >>>>>>> 250 SIZE 16777216 >>>>>>> MAIL FROM:<[email protected]> >>>>>>> 250 sender<[email protected]> ok >>>>>>> RCPT TO:<[email protected]> >>>>>>> 250 recipient<[email protected]> ok >>>>>>> DATA >>>>>>> 354 go ahead >>>>>>> >>>>>>> . >>>>>>> 250 ok: Message 390806655 accepted >>>>>>> QUIT >>>>>>> 221 relay.skynet.be >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 05/24/2010 01:30 PM, Eric Charles wrote: >>>>>>>> Took from a fresh james setup and simply enabled the<gateway> >>>>>>>> tag with >>>>>>>> a >>>>>>>> valid smtp relay and got same exception when attempting to deliver >>>>>>>> mails via >>>>>>>> gateway: >>>>>>>> INFO 13:26:30,682 | james.mailetcontext | Exception delivering >>>>>>>> message >>>>>>>> (Mail1274700389857-3) - SMTP can only send RFC822 messages >>>>>>>> >>>>>>>> For 2.3, I simply enabled the<gateway> tag (with eventual >>>>>>>> username/pwd), >>>>>>>> and it was OK. >>>>>>>> >>>>>>>> Something else to configure in current trunk? >>>>>>>> >>>>>>>> Tks, >>>>>>>> >>>>>>>> Eric >>>>>>>> >>>>>>>> >>>>>>>> On 05/24/2010 01:15 PM, Eric Charles wrote: >>>>>>>>> Hi Norman, >>>>>>>>> >>>>>>>>> I tried this config : >>>>>>>>> >>>>>>>>> <mailet [email protected]" class="ToProcessor"> >>>>>>>>> <processor>domainprocessor</processor> >>>>>>>>> </mailet> >>>>>>>>> <processor name=omainprocessor"> >>>>>>>>> >>>>>>>>> <mailet match=ll" class="ActiveMQRemoteDelivery"> >>>>>>>>> <outgoingQueue> outgoing2</outgoingQueue> >>>>>>>>> <outgoingRetryQueue> outgoing2.retry</outgoingRetryQueue> >>>>>>>>> <delayTime> 5 minutes</delayTime> >>>>>>>>> <delayTime> 10 minutes</delayTime> >>>>>>>>> <delayTime> 45 minutes</delayTime> >>>>>>>>> <delayTime> 2 hours</delayTime> >>>>>>>>> <delayTime> 3 hours</delayTime> >>>>>>>>> <delayTime> 6 hours</delayTime> >>>>>>>>> <maxRetries> 25</maxRetries> >>>>>>>>> >>>>>>>>> <maxDnsProblemRetries> 0</maxDnsProblemRetries> >>>>>>>>> <deliveryThreads> 1</deliveryThreads> >>>>>>>>> <sendpartial>true</sendpartial> >>>>>>>>> <bounceProcessor>bounces</bounceProcessor> >>>>>>>>> <gateway>172.16.1.206</gateway> >>>>>>>>> <gatewayPort>25</gatewayPort> >>>>>>>>> <gatewayUsername>xxx</gatewayUsername> >>>>>>>>> <gatewayPassword>yyy</gatewayPassword> >>>>>>>>> >>>>>>>>> </mailet> >>>>>>>>> >>>>>>>>> </processor> >>>>>>>>> >>>>>>>>> >>>>>>>>> and got in James1 log: >>>>>>>>> INFO 12:52:47,502 | james.mailetcontext | Exception delivering >>>>>>>>> message >>>>>>>>> (Mail1274698287300-18) - SMTP can only send RFC822 message >>>>>>>>> >>>>>>>>> James replies with >>>>>>>>> >>>>>>>>> Hi. This is the James mail server at srv001. >>>>>>>>> I'm afraid I wasn't able to deliver your message to the following >>>>>>>>> addresses. >>>>>>>>> This is a permanent error; I've given up. Sorry it didn't work >>>>>>>>> out. >>>>>>>>> Below >>>>>>>>> I include the list of recipients and the reason why I was >>>>>>>>> unable to >>>>>>>>> deliver >>>>>>>>> your message. >>>>>>>>> >>>>>>>>> >>>>>>>>> I also tried the initial config I proposed (which was more >>>>>>>>> applicable >>>>>>>>> for >>>>>>>>> a servers configured in series, yours being more suited for >>>>>>>>> tree-like >>>>>>>>> servers), and got the same error in James1 log. >>>>>>>>> >>>>>>>>> James2 can handle mails (tested via telnet). >>>>>>>>> When I send via James1, nothing is written in the log (so I >>>>>>>>> assume the >>>>>>>>> mail does not even leave James1). >>>>>>>>> >>>>>>>>> Finally I am wondering if the "SMTP can only send RFC822 message" >>>>>>>>> comes >>>>>>>>> from my config, or from the handling of mails via gateway in >>>>>>>>> current >>>>>>>>> trunk. >>>>>>>>> I have difficulties to test "gateways" config from my environment >>>>>>>>> (firewalls,...). >>>>>>>>> Any idea if it comes from my configs or from issues with james >>>>>>>>> handling >>>>>>>>> "gateways"? >>>>>>>>> >>>>>>>>> Many Tks, >>>>>>>>> >>>>>>>>> Eric >>>>>>>>> >>>>>>>>> >>>>>>>>> On 05/20/2010 06:48 PM, Norman Maurer wrote: >>>>>>>>>> Hi Eric, >>>>>>>>>> >>>>>>>>>> sorry for the delay.... >>>>>>>>>> >>>>>>>>>> Just add the domains to domain configuration on both servers >>>>>>>>>> and use >>>>>>>>>> a >>>>>>>>>> matcher to "forward" the mails to the other server. >>>>>>>>>> >>>>>>>>>> Bye, >>>>>>>>>> Norman >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2010/5/17 Eric Charles<[email protected]>: >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> As far as I understand, james current trunk considers that smtp >>>>>>>>>>> authentication is needed for mails not being in its domains >>>>>>>>>>> list (I >>>>>>>>>>> use >>>>>>>>>>> JDBCDomainList, so domains not being in database). >>>>>>>>>>> >>>>>>>>>>> This avoids to expose james as openrelay by default even if >>>>>>>>>>> <authRequired>true</authRequired> remains commented in >>>>>>>>>>> smptserver.xml. >>>>>>>>>>> >>>>>>>>>>> Now I need to split domain management in 2 separate servers >>>>>>>>>>> (different >>>>>>>>>>> SLA), >>>>>>>>>>> let's say James1 and James2. >>>>>>>>>>> >>>>>>>>>>> I would define in James1 all James1+James2 domains. >>>>>>>>>>> >>>>>>>>>>> In James1 spoolmanager.xml, I would comment the >>>>>>>>>>> <mailet match=ostIsLocal" class="ToProcessor"> >>>>>>>>>>> <processor> local-address-error</processor> >>>>>>>>>>> <notice>550 - Requested action not taken: no such user >>>>>>>>>>> here</notice> >>>>>>>>>>> </mailet> >>>>>>>>>>> >>>>>>>>>>> and would define >>>>>>>>>>> <mail.smtp.localhost>James2<mail.smtp.localhost> >>>>>>>>>>> >>>>>>>>>>> to forward all permitted mails not handled by James1 to James2. >>>>>>>>>>> >>>>>>>>>>> Do this make sense? >>>>>>>>>>> >>>>>>>>>>> Tks, >>>>>>>>>>> >>>>>>>>>>> Eric >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>>>>> For additional commands, e-mail: >>>>>>>>>> [email protected] >>>>>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> >>>>>>> >>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>> For additional commands, e-mail: [email protected] >>>>>>> >>>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
