I think what's happening is that RemoteDelivery is requeueing the messages
into it's own outgoing folder and then you have a 50/50 chance as to which
instance's delivery threads will pick it up.

Try configuring each mailet with a different outgoing folder, e.g.


  <mailet match="RemoteAddrInNetwork=172.21.1.34" class="RemoteDelivery">
    <delayTime>21600000</delayTime> 
    <maxRetries>5</maxRetries> 
    <gateway>gw1</gateway> 
    <outgoing>file://var/mail/outgoing1</outgoing>
  </mailet>

and

  <mailet match="RemoteAddrInNetwork=172.21.1.34" class="RemoteDelivery">
    <delayTime>21600000</delayTime> 
    <maxRetries>5</maxRetries> 
    <gateway>gw1</gateway> 
    <outgoing>file://var/mail/outgoing2</outgoing>
  </mailet>

Cheers
Steve

-----Original Message-----
From: Laurent Licour [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 26, 2002 7:29 AM
To: '[EMAIL PROTECTED]'
Subject: James 2.0a2 RemoteDelivery Bug 


I try to use a configuration to processing inbound and outbound messages
For each, i use a gateway mail server

Here is a part of the config file

<!-- Outbound messages -->
</mailet>
  <mailet match="RemoteAddrInNetwork=172.21.1.34" class="RemoteDelivery">
  <delayTime>21600000</delayTime> 
  <maxRetries>5</maxRetries> 
  <gateway>gw1</gateway> 
</mailet>

<!-- Default : inbound messages -->
<mailet match="All" class="RemoteDelivery">
  <delayTime>21600000</delayTime> 
  <maxRetries>6</maxRetries> 
  <gateway>gw2</gateway> 
</mailet>

It's seems that james confuse between the twice RemoteDelivery mailets. For
example, if i send a mail from 172.21.1.34, 
the first mailet will process mail, but sometimes (~50%) with the memory
context of the second mailet (in others words
to gateway gw2)
I try to debugging but not find the bug
I also try to create a copy of the mailet : SecureRemoteDelivery for the
outbound trafic
After recompile, the problem still exist !!!

Fri Apr 26 14:10:03 GMT-01:00 2002 [INFO   ] (James.Mailet): ToProcessor:
Sending mail org.apache.james.core.MailImpl@1671b2 to transport
Fri Apr 26 14:10:03 GMT-01:00 2002 [INFO   ] (James.Mailet): RemoteDelivery:
Remotely delivering mail Mail1019833803074-5-!1301900932
Fri Apr 26 14:10:03 GMT-01:00 2002 [INFO   ] (James.Mailet): RemoteDelivery:
sending mail to [[EMAIL PROTECTED]] on althes.fr
Fri Apr 26 14:10:03 GMT-01:00 2002 [INFO   ] (James.Mailet):
SecureRemoteDelivery: Secure Remote delivery thread (0) will process mail
Mail1019833803074-5-!1301900932-to-althes.fr
Fri Apr 26 14:10:03 GMT-01:00 2002 [INFO   ] (James.Mailet):
SecureRemoteDelivery: attempting to deliver
Mail1019833803074-5-!1301900932-to-althes.fr
Fri Apr 26 14:10:03 GMT-01:00 2002 [INFO   ] (James.Mailet):
SecureRemoteDelivery: ### echo maxRetries = 5
Fri Apr 26 14:10:03 GMT-01:00 2002 [INFO   ] (James.Mailet):
SecureRemoteDelivery: ### echo gateway : gw1

I really don't understand what's append : the good mailet start
(RemoteDelivery  with gw1) (method service() i think) and then a part of the
second mailet is executed

PS : the bug also exist if you use one mailet with DNS resolution insteed of
gateway. Il you only use DNS, the problem exist but there is no side effect

Please help...

Laurent Licour



*---------------------------------------------------------------*
* Cet e-mail et toutes les pi�ces jointes sont destin�s aux     *
* seules personnes auxquelles ils sont sp�cifiquement adress�s  *
* et n'engagent que le signataire de ces documents et non la    *
* structure dont il d�pend.                                     *
* Leur existence et leur contenu ont un caract�re confidentiel. *
* Toute utilisation ou diffusion non autoris�e est interdite.   *
* Si vous avez re�u cet  e-mail ou si vous d�tenez sans en �tre *
* le destinataire, nous vous demandons de bien vouloir nous en  *
* informer imm�diatement.                                       *
* Cette note assure que ce message a �t� contr�l� et ne         *
* comprenait aucun virus connu � ce jour, n�anmoins tout        *
* message �lectronique est susceptible d'alt�ration.            *
* Nous d�clinons toute responsabilit� au titre de ce message    *
* s'il a �t� alt�r�, d�form� ou falsifi�.                        *
*---------------------------------------------------------------*
 


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to