Shal Jain wrote:
No I haven't
The following
<outgoing> db://maildb/spool/outgoing </outgoing>
is the same in both cases. I didn't think that would make a difference
I'd appreciate an explanation
Here is how a RemoteDelivery works:
When James start RemoteDelivery create a number of delivery threads.
The threads simply wait for new messages appearing in its outgoing spool
and send them. The delivery threads are specific to the RemoteDelivery
that create them.
When the spoolmanager got a new message for the remote delivery it call
the service() method of the RemoteDelivery.
RemoteDelivery will eventually split the mail in multiple parts (if no
gateway is specified and the message recipients are from different
domains) and store each copy in the outgoing spool.
So you understand that the bridge between a RemoteDelivery mailet and
its delivery threads IS the *outgoing spool*. If you share the outgoing
then you don't know what delivery thread will send what mail.
So add an
<outgoing> db://maildb/spool/outgoing2 </outgoing>
To one of the remote delivery mailets.
Stefano
PS: we should add a comment in the default configuration to remember
this to new users.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
